Who can spend from a token account and how much. Try a live revoke on the demo's test validator.
Reading the chain…
Permission infrastructure for Solana
Know what can act on your wallet.
Understand native permissions. Try a token delegate revoke with proof on a test validator.
Velon, working
Permissions, backed by evidence.
A real permission from the chain, in the same words Velon uses for every protocol.
Try it in the console
Who can act
How much, and what is left
The state it was read from
How a revoke is proven.
-
One finalized read of the token account, its owner, its delegate, the clock and the token program. The program bytes must match a verified build.
-
The revoke is simulated in the same finalized bank. The result must equal the expected account change exactly, or nothing is offered for signing.
-
Your wallet signs the reviewed bytes only. The message and signature are checked again before anything is sent.
-
The finalized transaction is fetched, the account is observed again, and the permission must be absent before the page says revoked.
Authority, not balances.
Token delegates and subscriptions are read by separate adapters and compiled into one record: who, capability, resource, limit, remaining, lifecycle. The console renders that record, not a screen per protocol.
A subscription's on-chain delegate is a program address. Velon derives the merchant and pullers who can move funds through it and keeps the program address as lineage.
When several keys draw on the same allowance, Velon reports one permission with all of them as principals, so the limit is never doubled.
Each record names the finalized slot, the account bytes it came from, the program build hash and the adapter version. Open any permission in the console to see them.
An unverified program version or a missing account yields unsupported or incomplete, and no permission is shown. An empty result never claims a wallet is clean.
After signing, Velon waits for finality, reads the account again and only then reports success. The receipt replays later without contacting the chain.
What it reads today.
Fixed and recurring delegations, plans, merchant and puller authority, cancellation and expiry. Read from recorded native executions.
Token spending limits on controlled multisigs, proven against the deployed mainnet program. Not yet wired into the runtime or this console.