Shunt

Docs

What Shunt does, how it does it, and what can go wrong. No marketing in this page — if something is not built yet, it says so.

What it is

Sending crypto to someone who has never held crypto fails at the same three points every time. They do not have a wallet. You need their address. And once they have it, they need gas before they can move anything.

Shunt deletes all three from the receiving side. You make a drop, you get a link, you send the link. They open it, pick where it goes, and it lands. They never install anything first and they never pay a fee.

What is actually built

This is the honest list. It matches the status panel on the front page.

Send and claim on Solana devnetWorking
PIN-locked linksWorking
Vault — track and reclaim your dropsWorking
QR codes for hand-offWorking
MainnetNot open
Sending SPL tokens, not just SOLNot built
$SHUNT token3 Sep · 5 PM UTC
Third-party auditNot started

Devnet coins are worth nothing. They exist so people can test without risk. Nobody should be moving real money through Shunt yet. If an account tells you otherwise, it is not us.

How a drop works

  1. Load. A brand new Solana keypair is generated in your browser. Your SOL goes into it, plus a small extra amount for the claim fee.
  2. Link. That wallet's private key is encoded and placed in the link after the #.
  3. Claim. Whoever opens the link gets the key back, picks a destination, and the drop wallet signs a transfer of its entire balance.
  4. Close. The wallet ends at zero and Solana closes the account by itself.

There is no smart contract in this. No program to audit, no admin key to steal, no upgrade authority. A drop is a plain wallet holding plain SOL.

The link is the key

Everything after the # in a URL is called the fragment. Browsers never send the fragment to a server — not to ours, not to anyone's. That is a rule of how the web works, not a promise we are asking you to believe.

So the key travels inside the link and nowhere else. Which cuts both ways:

Send the link the way you would send a password. Anything that shows link previews to other people — a public channel, a shared inbox, a group chat — is a bad place for it.

Reclaiming

A drop nobody claimed is not stuck. Open your own link and send it to your own address. It is the exact same claim flow — the link does not care who is holding it.

PIN locking

A plain link is bearer money: whoever sees it can take it. That is the honest weakness of this whole design. PIN locking is the answer to it.

Tick a PIN when you make a drop and the wallet key is encrypted before it ever goes into the link. What travels is scrambled data. Your browser derives the encryption key from your PIN with PBKDF2 — 310,000 rounds of SHA-256 — and encrypts with AES-GCM. All of it runs in the browser, using the crypto built into the browser itself. No library, no server, nothing sent anywhere.

The wallet address travels in the clear alongside it, on purpose: the person receiving the link can see the amount is real before typing anything. What they cannot do without the PIN is move it.

Where PIN locking stops helping

310,000 rounds slows an attacker down. It does not stop one. A 4-digit PIN is 10,000 possibilities — someone holding your link can grind through that offline, at their own pace, with no server of ours to rate-limit them. There is no lockout, because there is nothing to lock out.

Use a phrase, not four digits. And send the PIN through a different channel than the link — a PIN pasted under the link in the same chat protects nobody.

There is no recovery. Forget the PIN and that drop is gone for everyone, including us. That is not a policy we could change; we never had the key.

Your vault

Glinty-style drops have a second quiet failure: lose the link and the money is stranded with nobody able to reach it. The vault fixes that.

Every drop you make is recorded in your browser's own storage. The vault reads each of those wallets straight off Solana and tells you which were claimed and which are still sitting there — then lets you sweep the unclaimed ones back to any address, in one go.

What we can see

Shunt is a set of static files. There is no account system, no database, and no server that processes drops. Your browser talks to Solana directly.

Your private keysNever. They stay in the fragment.
Who you sent a link toNever. We never see the link.
Drop wallets and amountsPublic — like every Solana transaction.
Which pages get visitedWhatever the web host logs. Standard traffic logs.
Your vault listNever. It is in your browser's storage, not ours.
Your PINNever. It is never transmitted and never stored anywhere.

Fees

On devnet there is no Shunt fee at all — you pay only Solana's own network cost, which is a fraction of a cent, and the drop wallet covers the claim side out of its balance.

There is no announced mainnet fee, because there is no mainnet. If you read a specific percentage somewhere, it did not come from this page.

Risks — read this part

FAQ

Does the person receiving it need a wallet?

To hold the money afterwards, yes — it has to land at a Solana address. But they need nothing to claim it, and they never need SOL for gas.

Can I send meme coins instead of SOL?

Not yet. Today a drop carries SOL only. SPL token support is on the list above, unbuilt.

What if two people open the same link?

First one to press Claim gets it. The second sees an empty drop wallet.

Why is there no smart contract?

Because it does not need one. A contract would be more code to audit and one more thing that can be exploited or rugged. A plain wallet with the key in the link does the same job with less that can go wrong.

Can I change or remove a PIN after making the drop?

No. The PIN is baked into the link at the moment the drop is created. To change it, reclaim the drop from your vault and make a new one.

What if I clear my browser data?

Your vault list goes with it. The drops themselves are untouched on Solana — but without the links you have no way to reach them. Download a backup before you clear anything.

Is there a token?

Not yet. $SHUNT launches 3 Sep, 5 PM UTC. The contract address will appear in the header of the front page the moment it exists — until then that slot reads TBA, and any address you see elsewhere is somebody else's.