> For the complete documentation index, see [llms.txt](https://basket-fund.gitbook.io/basket.fund-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://basket-fund.gitbook.io/basket.fund-docs/how-cross-chain-exposure-works.md).

# How cross-chain exposure works

When a basket contains both Solana and Base assets, basket.fun handles the required execution behind the scenes.

Solana assets are bought and sold on Solana. Base assets are bought and sold on Base. USDC moves between Solana and Base through Circle CCTP.

A user does not need to bridge manually to follow a basket with Base exposure. The system routes the USDC, executes the swaps, and tracks the final settled position.

For buys, Solana to Base bridging is part of the execution process when needed.

For exits, Base USDC may need to come back to Solana before the user receives their payout. Standard bridge mode is cheaper but can take longer. Fast mode can be offered when speed matters more than cost.

The app should make this visible when it affects the user experience. Cross-chain execution should feel simple, but it should not pretend that bridges are instant when they are not.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://basket-fund.gitbook.io/basket.fund-docs/how-cross-chain-exposure-works.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.