Base: an inflow source
Base is not part of the payout path. Anchors settle on Stellar, so a payout never passes through an EVM chain. Base appears for one reason: a customer may already hold USDC there.
Inflows
Section titled “Inflows”USDC on Base reaches the hub over CCTP, which burns on Base and mints canonical USDC on Stellar, so no wrapped asset is ever credited:
cctp.transfer (Base → Stellar) → ledger.creditThe edge is in the route graph and the planner produces it; the cctp.transfer leg is not built. See CCTP.
Read-only
Section titled “Read-only”Erc20Watcher reads USDC and EURC Transfer logs in and out of any address and emits the same Observation shape as every other observer. It needs only an address, so a read-only pilot can include a company’s Base wallets alongside its Stellar accounts.
Base has no memo field, so Base movements in read-only mode match by amount and counterparty rather than by reference. That gap is visible in the pilot’s own output, and it is one of the arguments for settling where a reference can travel.
Signing
Section titled “Signing”The EVM side signs with secp256k1 rather than Ed25519, through the same signer interface: awsKmsSigner for AWS KMS, turnkeySecp256k1Signer for Turnkey, localSecp256k1Signer for development. See Keys and signers.
Precision
Section titled “Precision”USDC is 6 decimal places on Base and 7 on Stellar. rescale converts, and refuses any conversion that would drop value (ADR 0012).
Environments
Section titled “Environments”| Network | Chain id | USDC |
|---|---|---|
| Base | 8453 | 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 |
| Base Sepolia | 84532 | 0x036CbD53842c5426634e7929541eC2318f3dCF7e |