Developers

About Developers

What this workspace reads, from which source, under which contract — and exactly what the kit refuses to do. The SDK and MCP tool layer is registered as RYN-SOL-A6; publishing it to a public repository is a founder decision, not a build step.

Workspace

Registry entry

Shipped

Why an adapter registers

Agent Control artifacts name their adapter and action by versioned, hash-pinned reference, so a verifier that has never heard of Solana still reads that the action commits value. The adapter entered the shipped registry through a neutral manifest — the central sources never name a provider, and a test fails if one appears.

Adapteradapter:solana-token-2022@1

Actionaction:solana-token-2022/spl-transfer@1

Canonical classVALUE_TRANSFER — readable without knowing the chain

AmountsRaw base-unit strings end to end; a float cannot exist as a concept.

Published contracts

In the source tree

Where these live

Four JSON Schemas generated from the zod sources into docs/solana/schemas/, with a parity test that regenerates and compares — drift fails the suite. They ship to the public repository with the RYN-SOL-A6 kit, behind its founder gate.

solana-asset-passportsolana-asset-passport.schema.json

spl-transfer-preflightspl-transfer-preflight.schema.json

solana-owner-policysolana-owner-policy.schema.json

solana-policy-verdictsolana-policy-verdict.schema.json

RPC sources

Config fact

How an endpoint is chosen

An explicit endpoint wins over the environment; the environment wins over the public default. Every read carries a timeout and one bounded retry — retries are for the transport, never for the answer, because “not found” is a fact and re-asking does not change facts.

Mainnethttps://solana-rpc.publicnode.com

Devnethttps://api.devnet.solana.com

Environment overridesRYNTRA_SOLANA_RPC_MAINNET · RYNTRA_SOLANA_RPC_DEVNET

Venue quoteshttps://lite-api.jup.ag/swap/v1/quote — lite tier, read-only; a key enters only through RYNTRA_JUPITER_API_KEY

What this kit refuses

By construction

Why refusals are listed

A boundary that is not written down gets renegotiated by accident. These are structural: there is no code path that signs, holds a key, or submits a transaction from this workspace.

Keys and signingNever. No key reaches Ryntra; nothing here can sign or execute.

GuessingAn account that is not a mint is refused by name; an extension without written semantics is reported, not interpreted.

Unknown referencesThe registry resolves fail-closed: an unknown adapter, version or kind is a refusal, not a fallback.

Verdict vocabularyThe policy ladder bottoms out at NO_KNOWN_BLOCKER — the word “safe” is not in it, and a test holds that.