Treasury surveillance for community coins
Multisight reads Squads v4 multisig accounts byte by byte from Solana mainnet. It shows who can move the money, how many of them must agree, and what has left the vault lately. No sign-up. No keys. Nothing custodied.
Live Each monitor is a real Squads v4 multisig seen on mainnet today, decoded from its account bytes. The ring shows its members; the amber arc is how many must sign. Select a monitor to inspect it. Channel 08 lists the newest Squads v4 transactions on mainnet as they land. These wallets are unnamed public accounts; Multisight does not know or claim who runs them.
CH 02
Paste a multisig, its vault, or one of its members. Multisight fetches the account with getAccountInfo, checks the 8-byte Anchor discriminator, decodes every field, and derives the vault addresses itself.
| Member | Rights | SOL | Last seen |
|---|---|---|---|
CH 03
Every Squads transaction has a proposal account at an address derived from the multisig and its index. Multisight derives the last twelve, reads them in two batched calls and decodes who approved, who rejected and what is still waiting.
Inspect a multisig to load its queue.
CH 04
The vault's last 25 transactions, read from mainnet and reduced to what moved in and out of it. Anything over your alert line is flagged. Switch on watch mode and the log checks for new signatures every 30 seconds.
No log yet.
CH 05
This is the raw data of the multisig you inspected, exactly as getAccountInfo returned it. Hover or tap a field to see how Multisight reads it. Spare bytes at the end are space Squads reserves so members can be added without a resize.
CH 06
Using the multisig on the inspector.
CH 07
A threshold trades theft against lock-out. Set how likely any one key is to be stolen or lost in a year, and the model shows both risks for every threshold. It is a model: it treats keys as independent, which real teams rarely are.
CH 08
A Squads vault has no private key. Its address is a SHA-256 hash of seeds that must land off the Ed25519 curve. Run the derivation here: your browser hashes each bump from 255 down and tests every result against the curve.
CH 09
Connect a wallet, or paste any address, and Multisight reads its recent transactions for Squads multisigs it has touched. It decodes each one, confirms the seat, and lists proposals still waiting on that key.
CH 10
Pin the treasuries you care about. Your wall is kept in this browser only, refreshes every 30 seconds, and flashes a monitor when its vault balance changes.
CH 11
getAccountInfo returns the multisig's bytes in base64. Multisight never asks for a list of all multisigs, which public RPC does not allow.
The first 8 bytes must equal sha256("account:Multisig"). Anything else is refused, so a token account can't pose as a treasury.
Two keys, the threshold, the time lock, both transaction indexes, the rent collector, the bump and the member list with permission masks.
Seeds multisig · address · vault · index are hashed in your browser and tested off-curve. The derived multisig address is checked against its create key.
SOL and both token programs are read through /api/rpc, then priced with Jupiter's public price feed. Unpriced tokens show a dash, never a guess.
Vault transactions are fetched four at a time and reduced to balance changes. A transfer out over your line becomes an alert.
CH 12
Squads Protocol v4, the program at SQDS4ep6…52pCf. Older Squads v3 accounts are recognised and named, but not decoded. Other multisig programs are not supported yet.
No. The wall shows public Squads multisigs Multisight found in recent mainnet activity. They are unnamed. Multisight does not know who runs them and makes no claims about them.
It shares your public key only. Multisight uses it to find multisigs your key belongs to and the proposals waiting for your vote. It never asks you to sign anything and never moves funds.
Some members are hardware or cold keys that rarely sign. If the RPC returns no recent signatures for a key, Multisight shows a dash rather than inventing a date.
They use Jupiter's live price for each mint, and the current price for past transfers in the alert log. Tokens Jupiter can't price are listed with no USD value and left out of totals.
The threshold chart is a model. It assumes every key fails independently with the chance you set. Real keys share devices, people and habits, so treat it as a way to think, not a forecast.
Public RPC rate-limits transaction reads. Multisight reads at most 25 per lookup, four at a time, so it stays polite and fast.