Network Configuration
How Cookie and Solana appear together in Morsel, how to configure RPC endpoints, and how to use devnet.
Morsel shows Cookie and Solana at the same time — there is no network selector to switch between them. Both chains appear in the same home screen, the same token list, and the same activity feed. Your Cookie balances and your Solana balances are always visible together.
How Networks Appear
- The home screen groups your assets by chain — Cookie tokens and Solana tokens each have their own section
- When you tap Send or Swap, you pick a token — the chain follows automatically from whichever token you choose
- Activity shows transactions from both chains in a unified feed, with a chain label on each entry
- NFTs from both chains appear in the same gallery
Configuring a Custom RPC Endpoint
For lower latency or private RPC access, you can replace the default endpoint for either chain:
- Go to Settings → Networks
- Tap Cookie or Solana
- Tap Custom RPC
- Paste your endpoint URL and tap Save
bash
# Cookie public endpoints
https://rpc.dumpsack.xyz # Primary
https://rpc.cookiescan.io # Fallback
# Solana public endpoints
https://api.mainnet-beta.solana.comOnly use RPC endpoints you trust. A malicious RPC cannot steal your funds but could return incorrect balance or transaction data.
Devnet
Developer mode unlocks devnet endpoints for both chains. Enable it in Settings → Developer Mode. Devnet balances are separate from mainnet — tokens there have no real value.
Cookie vs Solana — Key Differences
| Feature | Cookie | Solana |
|---|---|---|
| Native token | COOK | SOL |
| Avg confirmation | < 1 second | < 1 second |
| Avg fee | < $0.001 | $0.001–$0.01 |
| Explorer | Cookiescan (cookiescan.io) | Solscan (solscan.io) |
| Address format | Base58 (same as Solana) | Base58 |
Cookie and Solana use the same address format. When sending, always confirm the token — it determines which chain the transaction goes out on.