strk20.run

Quickstart

From opening the page to holding shielded value — what happens at each step and what it costs you.

There is no install step and no signup. What follows is what actually happens.

Open the app

The browser derives an account key on first load and stores it in localStorage. That is your account. Nothing was sent anywhere to create it, and no server knows it exists yet.

The key is in localStorage in plaintext. Anything that can run JavaScript on that origin can read it, and so can anyone with the unlocked device. The app's "lock" is a screen lock, not encryption. This is an accepted trade — it is what removes the wallet, the extension and the seed phrase — and it is argued in the code rather than hidden.

Deploy the account, then register

An account contract has to exist on-chain before it can sign anything, so the app deploys it. Then it registers with the pool.

Registration is the step to read twice. It publishes an encrypted copy of your viewing private key on-chain, readable by anyone, decryptable by the auditor. It cannot be rotated and cannot be opted out of. The auditor explains exactly what that means.

The first registration is sponsored — our relayer pays for it, so you need no funds to start. There is a real one on mainnet you can go and look at.

Deposit

You send tokens into the pool from a public address. This step is public: an observer sees your address and the amount. That is not a limitation of strk20.run, it is what a deposit is.

Deposits are also screened by a third-party provider the pool operator chose. A refusal is silent — if a deposit does not arrive, it will look like our bug.

Hold, send, swap, bridge, bet, launch

Inside the pool your value is a set of shielded notes. From here the surfaces do what they say: sends are private to everyone except your recipient, and swaps and bridges use the invoke sandwich so value never lands on a public address of yours in between.

Amounts on any leg that touches an open note remain public. What is hidden is who.

Running it yourself

See build and verify.

On this page