Developer preview · Solana devnet
Build on the duel protocol.
Discover eligible packs, match wallets, prepare transactions, follow finality, and publish verifiable duel results without ever handling a player’s private key.
Choose your entry point
Move from pack discovery to a shareable duel receipt using the hosted devnet API.
ContractInteractive API referenceInspect every preview endpoint, schema, request, and response in the canonical OpenAPI contract.
TransactionsWallet-signed Solana flowUnderstand prepared transactions, submission binding, finality, recovery, and escrow checks.
VerificationValuation and result proofReproduce the winner calculation from the committed policy, outcomes, and public receipt.
Hosted surfaces
Player-facing game rules
The product app is the canonical source for current readiness and player-language boundaries. These Devnet surfaces separate committed state, card ownership, and settlement finality before any wallet action:
The v1 API is a preview contract. Devnet responses, mock provider outcomes, and prepared transactions do not imply production custody or mainnet readiness.
Security model
- Wallets inspect and sign Solana transactions locally.
- The API and MCP server never accept a seed phrase or private key.
- Mutating API requests require authentication and an idempotency key.
- A duel is final only after the required on-chain confirmation and asset-state checks.
- Winner calculation uses the immutable valuation policy committed before funding.
The public Solana program lives in the escrow repository . Agent integrations can also use the hosted MCP server or the public skills repository .