Paste a Solana transaction and ReadFirst tells you, in plain English, what it will do. Token approvals, authority changes and account ownership changes get flagged. The reader runs entirely in your browser and nothing is uploaded. Simulate and the delegation check contact the RPC you choose, and only when you click them.
Paste the transaction a site asks you to sign (base64, base58 or hex).
Samples are synthetic transactions built in your browser with random addresses. They are not real transactions. Never paste a seed phrase or private key anywhere, including here.
Simulate sends this transaction to the Solana RPC you choose (the Custom RPC field under Check wallet delegations, or the public default) and shows what would change. It does not sign or send anything, and that RPC provider can see the transaction.
Check wallet delegations
Paste a Solana wallet address to see every token account where a delegate is set, so you know who can still move your tokens. Read only. No wallet connect.
Saved in this browser only. The public RPC can rate limit or block requests. Your address is sent only to the RPC you use, and that RPC provider can see it.
Results may be incomplete. This is a reading aid, not a guarantee.
How to remove a delegation: open your wallet, find the token, and revoke or remove the delegate. Wallets differ. ReadFirst cannot remove anything for you.
How it works: ReadFirst asks the RPC for your SPL Token and Token-2022 accounts, then lists only the ones that have a delegate set.
Drainer patterns
Six shapes that show up again and again in wallet drains. Each card explains one in plain words and can load a matching example into the reader above. The examples are synthetic and use random addresses.
Unlimited token approval
A token approval lets another address spend from one of your token accounts. An unlimited one sets the allowance to the largest possible number, so that address can move the whole balance until the approval is removed.
What you see before signing
An Approve instruction with a huge amount and a spender address you do not recognize.
What to do
Approve only what an app you chose needs, and look for old approvals with the delegations check above.
Account owner change
Every token account has an owner that decides where its tokens can go. A Set authority instruction can hand that role to another address, and from then on the new owner can move everything in that account.
What you see before signing
A Set authority line of type AccountOwner that names an address that is not yours.
What to do
Reject it unless you are deliberately moving control to an address you own.
Close account, paid to someone else
Closing a token account pays its rent deposit, usually around 0.002 SOL, to whichever address the transaction names. It only works on an empty account, so by itself it moves that deposit and not your tokens.
What you see before signing
A Close account line whose destination is not your own address.
What to do
Check the destination, and reject it if it is not a wallet you control.
Large SOL transfer
A plain SOL transfer can send most of your balance to another address. It uses the same instruction as an everyday payment, so its shape alone gives no hint that anything is off.
What you see before signing
A Transfer SOL line with a large amount and a destination you did not choose.
What to do
Read the amount and the destination before signing, and reject it if either one surprises you.
The reader treats this as a routine transfer and shows no warning. The amount and the destination are what you check.
Claim button with many instructions
A page that offers a free claim can put many instructions behind one signature request. Some wallet pop-ups show only a short summary, so approvals or ownership changes can sit in the middle of a long list.
What you see before signing
Far more instructions than a simple claim needs, often several Approve lines for different token accounts.
What to do
Read every line in the full list, and reject the transaction if you cannot explain each one.
Delayed signing with a durable nonce
A normal transaction expires after about a minute, but one that starts with an Advance nonce instruction stays valid until that nonce is used, so it can be signed now and sent much later. Some services do this on purpose, but it means a signature can be used at a time you no longer expect.
What you see before signing
An Advance nonce line as the very first instruction.
What to do
Unless you chose a service that uses durable nonces, stop and ask why it is needed.
ReadFirst only recognizes the patterns it has rules for, and a clean reading is not a guarantee. A reading cannot tell you whether the receiving address can be trusted.
What it checks today
A fixed, readable rule set for well known programs. No AI guessing, no hidden backend.
Token approvals
SPL Token and Token-2022 Approve / ApproveChecked. Flags the delegate and whether the amount is effectively unlimited.
Authority changes
SetAuthority, especially account owner changes, which is the classic way a token account gets taken over.
Account ownership
System Program Assign and AssignWithSeed, which hand an account to another program.
Durable nonces
Advance nonce instructions create a transaction that does not expire, so it can be submitted much later.
Closes and burns
CloseAccount, Burn and nonce withdrawals are shown with where funds or rent go.
Unknown programs
Anything outside the known list is labeled "cannot explain" instead of being guessed at.
What it cannot do
Read this part. A green result is not a promise.
The reading does not run the transaction. It reads instructions as written. The optional Simulate button asks an RPC to run it against current chain state, and the result can differ from what happens when it is really sent.
The wallet delegation check reads token accounts from an RPC. It can miss accounts and does not cover other kinds of permissions.
It only understands a short list of programs. Everything else is marked as unrecognized.
Transactions using address lookup tables hide some accounts. ReadFirst tells you which ones it could not resolve.
It cannot tell whether a recipient address is a scammer. There is no address reputation list yet.
A "no known risky patterns" result means exactly that. ReadFirst reads instructions as written, and the reading itself does not simulate them.
This is Day 1 software and may have bugs. If you find one, open an issue on GitHub.
Roadmap
Only the lines marked LIVE are live. Everything else is planned and may change or never ship.
LIVEOffline transaction reader for known programs (this page)
LIVEWallet delegation check: paste an address, list token accounts with an active delegate (read only, needs an RPC)
LIVESimulate before signing: balance changes from an RPC simulation (read only, needs an RPC)
PLANNEDCommunity sourced known-bad address list, each entry with a public source
PLANNEDOne click revoke helper for stale token approvals
PLANNEDWatchlist alerts for approvals on addresses you choose (X or Telegram)
PLANNEDBrowser extension that shows the reading at the moment a site requests a signature
PLANNEDEVM support: permit, Permit2 and setApprovalForAll
PLANNEDIndependent review of the rule set, published openly
Token
The reader is free and stays free. The token is for the planned extras only.
Planned utility (not live)
Holding a minimum amount of the token would unlock watchlist alerts once they exist (roadmap item 6).
No utility is gated today. Nothing on this page requires the token.
The token does not pay for, fund or secure the reader. It does not pay yield or a revenue share.
Token details
Name, ticker and contract address only. Values are taken from the mint on Solana.