> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usespoke.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Aurora wallet funding

> Understand the separate mainnet funding integration, its activation status, and its network boundaries.

<Note>
  **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.
</Note>

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

```mermaid theme={null}
sequenceDiagram
  actor User
  participant App as Spoke funding screen
  participant API as Spoke API
  participant Aurora as Aurora Intents
  participant Monad as Monad Mainnet
  User->>App: Select supported source asset and amount
  App->>API: Request preview
  API->>Aurora: Get quote and deposit instructions
  Aurora-->>App: Route, fees, expiry, and deposit destination
  User->>Aurora: Authorize and send source funds with wallet
  Aurora->>Monad: Deliver canonical USDC
  API->>Monad: Verify recipient, token, amount, and confirmation depth
  API-->>App: Confirm wallet funding after verification
```

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](https://api.usespoke.xyz/v1/funding/aurora). The API also defines authenticated preview, create-deposit, and own-deposit-status routes. See [API reference](/developers/api).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.