Skip to workspace
Mainnet reads · Devnet actions
Mainnet dataDevnet actions

Devnet lifecycle

About Devnet lifecycle

One transfer, built from the chain's own facts, judged by policy before a signature exists, signed in your wallet, submitted through a boundary that only accepts cleared bytes, then read back independently and reconciled into a receipt anyone can verify without trusting this site.

Devnet · user-signed

Sign one devnet transfer

What happens, in order

Read — the mint is read from devnet this visit: decimals, authorities, every extension, and nothing assumed from a previous read. Preview — the exact transfer is computed from that read, including the cluster’s own simulation of the built bytes. Judge — thirteen rules run against a declared policy before a signature exists, so a refusal costs nothing.

Sign — your wallet, your key. Ryntra holds none, and asks for a signature rather than a send, so there is a moment afterwards in which the returned bytes are compared to the ones that were built. Submit — only cleared bytes go out. Observe — the chain is read back independently and compared to what was expected; a deviation is recorded as a deviation, because an outcome that mostly matched is not a match. Receipt — an Ed25519-signed record anyone can verify without trusting this site.

No key, seed phrase or secret passes through Ryntra at any point. Set the wallet to devnet before connecting — Phantom labels every non-mainnet cluster “Testnet”.

Wallet

Everything here runs on a signature only you can give. Connect a wallet and it reads what that account holds; nothing is built, signed or sent until you say so.

No wallet is registered in this browser. Phantom, Solflare and Backpack all implement the Wallet Standard — install one, set it to devnet, and this page will find it.

Transfer
Review and sign
Outcome