Multichain Architecture
MAGMA uses a hub-and-spoke multichain model. All oracle resolution, conviction scoring, Forge distributions, and Echo Pool mechanics happen on Solana — the canonical settlement hub. Users on other chains commit capital through spoke contracts that communicate with the Solana hub via bridge protocols.
This design means:
- Oracle resolution is always on Solana, using the same M-of-N consensus regardless of which chain the backer is on.
- Conviction Score and Eruption Streak accumulate on Solana regardless of where capital came from.
- The Forge, Seam, Core, and Echo pools all live on Solana.
- EVM and TRON backers receive settlements routed back to their chain after Solana resolution.
Chain groups
Group A — Solana and SVM chains
SVM-compatible chains use the same Anchor programs, the same IDL, and the same wallet adapter as Solana. No new wallet integration is needed — existing Phantom / Solflare / Backpack connections work for all of them. The only change is the RPC endpoint.
| Chain | Status | Gas token | Notes |
|---|---|---|---|
| Solana mainnet | Live (devnet) | SOL | Canonical hub |
| Eclipse | V2 | ETH (bridged) | SVM chain |
| SOON | V2 | ETH (bridged) | SVM chain |
| Sonic | V2 | SOL | SVM chain |
Deploying to an SVM chain requires only: deploy the existing Anchor programs to that chain's RPC, register the new program IDs, and update the backend's RPC routing — roughly 2–3 days of effort per chain once Solana mainnet is stable.
Group B — EVM chains via Chainlink CCIP
EVM chains use LockVault.sol contracts. When a user backs a narrative from Base or Arbitrum,
their capital enters the LockVault on that chain. When oracle resolution completes on Solana, a
Chainlink CCIP settlement message is sent to the LockVault, which distributes funds accordingly.
| Chain | Status | Yield protocol | CCIP status |
|---|---|---|---|
| Base | V2 (Base Sepolia testnet ready) | Morpho Blue | Live |
| Arbitrum | V2 | Morpho Blue | Live |
| OP Mainnet | V2 | Morpho Blue | Live |
| BNB Chain | V2 | Morpho Blue | Live |
| HyperEVM | V2 | Felix (Liquity V2 fork) | Verify at docs.chain.link |
| Monad | V3 | TBD | Verify at docs.chain.link |
| Berachain | V3 | TBD | Verify at docs.chain.link |
| MegaETH | V4 | TBD | V4 only |
Following the April 2026 KelpDAO exploit ($292M lost via compromised single-verifier LayerZero infrastructure), MAGMA permanently switched to CCIP. CCIP runs two completely separate verification networks (a Committing DON and an Executing DON) plus an independent Risk Management Network, making the single-point-of-failure attack architecturally impossible. See the CCIP decision article for the full rationale.
Group C — TRON via Wormhole
TRON uses Wormhole for bridge messaging, not CCIP — CCIP does not support TRON. TRON backing is USDT-TRC20 only: no ETH, no TRX, no USDC.
| Chain | Status | Backing token | Bridge | Yield |
|---|---|---|---|---|
| TRON mainnet | V3 | USDT-TRC20 | Wormhole | JustLend (50% cap) |
V3 activates only after EVM mainnet has been live and stable for 3+ months and has passed a
separate TronLockVault.sol audit.
The LockVault architecture (EVM)
Each EVM chain has one LockVault.sol contract that:
- Accepts user deposits (ETH or USDC, depending on chain).
- Routes capital to Morpho Blue yield vaults immediately on deposit.
- Records the backing via backend confirmation.
- Receives settlement messages from Solana via CCIP after oracle resolution.
- Distributes funds to backers after a 48-hour timelock following settlement-message receipt.
The 48-hour EVM timelock mirrors the Solana challenge window, so users can dispute an incorrect resolution during the same period.
Supported EVM chains at mainnet
CCIP chain selectors for the V2 set (verify others at docs.chain.link):
| Chain | Version | CCIP chain selector |
|---|---|---|
| Base | V2 | 15971525489660198786 |
| Arbitrum | V2 | 4949039107694359620 |
| OP Mainnet | V2 | 3734403246176062136 |
| BNB Chain | V2 | 11344663589394136015 |
| HyperEVM | V2 | Verify at docs.chain.link |
| Monad | V3 | Verify at docs.chain.link |
| Berachain | V3 | Verify at docs.chain.link |
| MegaETH | V4 | Verify at docs.chain.link |
Base Sepolia testnet addresses
| Contract | Address |
|---|---|
| LockVault | 0x5501A1bcCfF02825138EbFA379C39A8db2343f71 |
| ForgePool | 0xe85314D7bF6D70b43788BC46E771F5c95B0e9108 |
| SeamPool | 0x18246618911550b813b3A9733dd1ac7Ab476fCf1 |
| CorePool | 0x7c8Cc90B7620C43dbb3B8F1c220e6bf4F02572Db |
Wallet requirements per chain type
| Chain group | Wallet |
|---|---|
| Solana + SVM (Eclipse, SOON, Sonic) | Phantom, Solflare, Backpack — existing connection works |
| EVM chains | MetaMask, Coinbase Wallet, Rainbow — via Privy (WalletConnect v2) |
| TRON | TronLink — separate integration, V3 only |
Echo Pool cross-chain
The Echo Pool lives on Solana. For EVM and TRON backers to earn Echo tickets, they must have a linked Solana wallet — the backend maps EVM/TRON backing to a Solana wallet for ticket issuance. This wallet linking is enforced during onboarding for EVM-chain users.
RPC endpoints
RPC endpoint addresses are available in the MAGMA app settings and via the SDK configuration. Public chain RPC endpoints are documented at each chain's official developer portal:
- Solana: https://solana.com/docs/references/clusters
- EVM chains: refer to each chain's official documentation.
- SVM chains (Eclipse, SOON, Sonic): refer to each chain's official developer documentation.
At beta, Solana is the only functional chain. EVM deposit/withdraw flows activate when LockVault contracts are deployed to mainnet; the web app already exposes chain switching across the full target set. See Security for the current beta scope.