Receiving
Derive, publish, find.
The recipient's three stations, on one page. Station 01 runs in your browser and nothing leaves the tab. Station 02 writes to the canonical registry, from your wallet or from any wallet by hand. Station 04 reads the canonical announcer and checks every announcement against your viewing key, here. The payer's station is on its own page.
Nothing here is stored
The keys exist only in memory and are gone when you close the tab. There is no key store yet. If you publish, keep the private keys the page offers you first, because a meta-address whose keys are lost receives payments nobody can ever spend.
01 Derive Live
A spending key and a viewing key. The viewing key can be handed to a scanner so it can find incoming payments without ever being able to move them.
02 Publish Live
The meta-address goes to the canonical ERC-6538 registry under the account that sends it. The registry was deployed by other people at a canonical address; this page only produces the calldata and, if you choose, hands it to your wallet.
Derive a key pair first. The calldata is built from it.
04 Find Live, bounded
Every announcement on the canonical announcer is a candidate. The viewing key rejects almost all of them on the view tag, one byte, before doing any curve work, and recognises its own. The scan reads the blocks the public endpoint will answer for, about twenty minutes of chain, and reports exactly which. Older payments wait on the indexer.
Derive a key pair first. The scan needs the viewing key.