Skip to main content
Solana Solana is where most ramp partners hold USDC liquidity. Corridor keeps two vaults there: egress (funds partner payouts) and ingress (receives collections). Every transfer carries the Corridor Reference.

​
The transaction

One @solana/kit transaction does three things atomically:
1

Create the recipient's USDC account if missing

Idempotent associated-token-account creation, so a first-time partner deposit address works.
2

TransferChecked

USDC from the vault to the partner’s one-off funding address, amount and decimals checked by the token program.
3

SPL Memo

corridor:<hex>: the 32-byte reference as hex, logged by the Memo program.

​
Reading it back

RPC signature lists expose each transaction’s memo as [N] corridor:<hex>. extractReference pulls the reference out, so the observer can join Solana movements to ledger entries without decoding instructions. SolanaWatcher reads amounts from each transaction’s pre- and post-token balances, so it sees the real amount and asset of any stablecoin movement, whichever program made it. It needs only an address, which is what a read-only pilot runs on.

​
Stablecoins

Transfers create the recipient’s token account and move funds with the mint’s own token program, so Token-2022 stablecoins work the same way as SPL ones. The vault signs through any @solana/kit transaction signer, including solanaSigner(...) from Keys and signers.

​
Environments

​
Evidence

Partner funding for a EUR → NGN payout on devnet, with the reference in the Memo program logs: nDGHfRgM…. When the devnet vault holds USDC, the runtime funds the mock partner with a real transfer; otherwise it records a clearly marked simulated funding reference, so a demo never pretends a transfer happened.