Argon
[Client]
Argon Payments
[Year]
2024
[Project Focus]
- Settle payments across AirDAO, Solana, BSC, and TON from one backend.
- Verify on-chain transfers without exposing that complexity to the product.
Scroll to explore
[Overview]
Argon exists so products can accept and settle payments across chains without maintaining four separate backends.
[What I did]
- Architected backend services for reliable multi-chain payment execution
- Integrated blockchain SDKs for wallet operations, transfers, and verification
- Implemented scalable data models for transaction history and balance tracking
[The role]
Blockchain and Backend Engineer
Njay
Project Info
Argon is a payment gateway for products that need to accept and settle value across more than one chain. AirDAO, Solana, BSC, and TON do not share wallets, confirmation rules, or failure modes. A separate backend for each network would have been impractical to operate.
I architected the Node.js and GraphQL services that sit in the middle: wallet operations, transfer execution, on-chain verification, and a history model that can explain a payment after it leaves the interface. The product requests a settlement; it does not implement chain-specific logic.
Overview
2024
Argon is a payment gateway for products that need to accept and settle value across more than one chain. AirDAO, Solana, BSC, and TON do not share wallets, confirmation rules, or failure modes. A separate backend for each network would have been impractical to operate.
I architected the Node.js and GraphQL services that sit in the middle: wallet operations, transfer execution, on-chain verification, and a history model that can explain a payment after it leaves the interface. The product requests a settlement; it does not implement chain-specific logic.
The Process
The first design problem was the contract, not the SDK. I defined a shared orchestration layer for create, send, confirm, and record — then implemented each chain behind that contract. Confirmation depth, retry windows, and wallet formats remain inside the adapter so the GraphQL surface stays stable.
Wallet operations and transfer verification were integrated through each network’s SDK, with balances and transaction history written to MongoDB so the product can present state without scanning a chain on every view.
Failure was treated as a first-class path. A transfer can stall, confirm late, or rest on an incorrect assumption about finality. The backend records enough information to reconcile those cases without requiring the user to understand four networks.
The Outcome
Argon settles and verifies payments across AirDAO, Solana, BSC, and TON from one backend. Products integrate a single payment flow rather than four chain implementations.
Transaction history and balances are queryable through a single API. The complexity of heterogeneous networks remains inside the gateway.