From your phone to Stellar

Your device generates a STARK proof. A smart contract on Stellar testnet checks it with nothing but hashes. No wallet, no sign-up.

Research prototype, not audited.

The secret in this proof is a test value, the same for everyone, and whether the proof hides it has not been reviewed. This measures cost; it is not a private app.

What is this?

Your device runs S-two, StarkWare's STARK prover, compiled to WebAssembly: about a second of arithmetic over a table of 512 rows and 301 columns, in one thread, with about 200 MB of memory. Nothing is installed. The only thing that leaves this page is the finished proof, sent to Stellar's public testnet server.

Stellar runs the S-two verifier inside a Soroban smart contract. It needs no elliptic curves and no trusted setup: only hash functions.

The proof says: “I know a secret whose commitment is one of the 1,048,576 leaves of this Merkle tree, and this is its nullifier.” A nullifier is a one-time tag: with it, an application can refuse a second use without learning which leaf was used. It is the check at the centre of a privacy pool or an anonymous vote.

What it is not. Not private yet and not audited: the secret is a fixed test value, and no cryptographer has reviewed whether the proof hides it. The contract only verifies; there is no application around it. The call is a simulation on testnet: the network's server runs the deployed contract and reports what a transaction would cost, and nothing is written to the ledger.