Glinty documentation

Glinty sends onchain assets through a private link. The recipient taps once, picks a wallet, and the tokens land — no account, no setup, no gas.

01Introduction

Sending tokens to someone who is new to crypto usually fails at the same three points: they need a wallet, they need its address, and they need gas to do anything with what they receive. Glinty removes all three from the recipient's side.

Instead of sending to an address, you create a drop. The tokens go into escrow, and you get a link. Whoever opens the link picks a wallet and claims. The claim itself costs them nothing.

02How Glinty works

1. You create a drop Choose any token with liquidity and an amount. You pay in SOL; the swap happens in the same step.
2. The tokens enter escrow A brand new Solana keypair is generated in your browser and funded. That keypair is the escrow — there is no contract behind it.
3. You get a claim link The link carries the key that unlocks that one escrow — and nothing else. Share it with the person you meant to pay.
4. They open it and pick a wallet If they don't have a wallet yet, this is the moment they make one. Nothing needs to exist beforehand.
5. They claim The page signs a transfer with the key from the link. The escrow pays its own fee, empties itself, and closes.

03Claim links

A claim link is the key to one drop. It looks like this, and the important part is everything after the #:

https://glinty.example/claim#<claim-key>

Anything after # is a URL fragment. Browsers do not send fragments to the server — so the key stays on the two devices that have the link, and never touches Glinty's infrastructure. That is what makes claiming possible without an account or a login.

04Escrow & refunds

Every drop gets its own escrow. It holds the tokens until one of exactly two things happens:

• The recipient claims — tokens move to their wallet, escrow closes.
• You refund it — available once the claim window has passed.

There is no waiting period, because there is no contract enforcing one. Whoever holds the link holds the key — including you. If a drop goes unclaimed, open your own link and claim it back to your own wallet. That is the refund.

05Gasless claiming

The recipient never pays a network fee. This is not done with a relayer or a server — it is simpler than that.

When a drop is created, the escrow wallet is funded with the amount plus a few thousand lamports. At claim time the escrow itself is the fee payer: it signs the transfer and pays the fee out of its own balance, then closes.

What that costs the sender

06Security & privacy

Non-custodial

Glinty never holds your tokens, and cannot. The escrow key exists only in your browser and in the link. We have no server, no database, and no copy of it — which also means we can never freeze, seize, or recover a drop.

Keys stay off our servers

The claim key lives in the URL fragment. It is not logged, not stored, and not recoverable by us — which also means we cannot restore a lost link.

What we can see

Ordinary web analytics: that a drop was created, that a claim page was opened. The on-chain side is public by nature — anyone can see that an escrow was funded and later emptied. Glinty does not make transfers private.

07Supported assets

Glinty is built for Solana. Any SPL token with routable liquidity can be dropped — you pay in SOL and the swap happens on the way into escrow.

Thin-liquidity tokens are the exception worth naming: a swap into a shallow pool can lose a meaningful share of the value to slippage before it ever reaches escrow. The app shows the expected amount before you confirm — check it.

08Fees & limits

09FAQ