Docs / Networks

Solana

Solana is a planned binding. This page records the design so that the protocol’s universality is concrete: which carriers Solana supplies for the same offer, receipt, predicates and claim semantics. No program is deployed, no test vectors are published, and the API serves no Solana network.

Planned binding Design, not a deployment

The design at a glance

Aspect	Solana binding (design)
Programs	Anchor (Rust): a bond registry program, a claims program and one validator program per predicate, with the same states, checks, outcomes, error names and events
Signatures	Ed25519 by a dedicated service signing key registered in the service account
Hashing	SHA-256 over Borsh-serialised bodies, domain-separated with the same type tags, a network identifier (the genesis hash) and the registry program address
Stake token	USDC SPL token, 6 decimals; the 100 USDC floor is `100_000_000` units
P6 oracle	A Pyth price update verified in-program; the cited price update plays the role of Stellar’s oracle timestamp and Chainlink’s round id
x402 scheme	`exact` on `solana:<genesis>` with an SPL transfer; `payment_reference` is the settlement transaction signature, `buyer` the payer
Wire form	Borsh encoding of `SignedOffer` and `SignedReceipt` inside `extensions.lopw`

Networks

Network	Name	CAIP-2	Status
Solana devnet	`solana-devnet`	`solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1`	Planned; nothing deployed
Solana mainnet	`solana`	`solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp`	Planned; nothing deployed

What stays identical

Offer, receipt and terms fields and their meaning; request_hash and response_hash as SHA-256.
Predicates P1 to P6 and their proven / not proven / not verifiable rules, including the exact integer deviation test.
The seven claim checks, the paid record per (service_id, payment_reference), the error names and the events.
Service states, floors, launch limits, fees, the slash rate limit and time-locked admin changes.
The ChainBinding interface: offerHash, receiptHash, termsHash, sign and verify, getService, getTerms, getKey, oraclePrice, submitClaim, registerService, deposit, and the encode / decode pair for the wire form.

For agents

Item	Value
Network name in API paths	`solana-devnet`, `solana`; not served (no deployment)
CAIP-2 id	`solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1`, `solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp`
Wire encoding of `extensions.lopw`	Borsh bytes of `SignedOffer` / `SignedReceipt` in the design; no schema or test vectors are published for this binding
Status	Design only. Treat any `solana` offer as unsupported until a deployment and test vectors are published

All networksStellar as the reference binding and the EVM networks with their chain ids, addresses and deployment status.Chain bindings (reference)The contract every binding, including this one, must satisfy.