Skip to main content
Implemented, currently disabled. The deployed application contains Aurora funding screens and API routes, but the integration reports configured: false until its provider configuration is completed. No end-to-end mainnet transfer is claimed as verified.
The intended flow lets a user move a supported source-chain asset into canonical USDC on Monad Mainnet, delivered to the authenticated external wallet. Aurora Intents provides routing and deposit instructions.

​
How the flow is designed

Spoke’s API does not sign or broadcast the source transfer. The user executes it with their wallet. A provider status alone is insufficient for final confirmation: the destination receipt must match the expected token, recipient, amount, and required confirmation depth.

​
Keep mainnet and testnet separate

  • Destination network: Monad Mainnet, chain 143.
  • Settlement application today: Monad Testnet, chain 10143.
  • Mainnet USDC does not become SDUSD.
  • Funding does not credit a campaign budget, buyer checkout, earnings balance, or reward vault.
  • You still need mainnet MON to pay gas for later mainnet wallet transactions.

​
Activation checklist

Before calling this flow live, complete the provider configuration, confirm supported routes and canonical token settings, and record a user-executed transfer from source deposit through verified destination receipt. Test expiry, underpayment, delayed delivery, refund, and retry behavior as supported by the provider. The current public configuration is available at GET /funding/aurora. The API also defines authenticated preview, create-deposit, and own-deposit-status routes. See API reference.