
Most sellers lose their first sale before they have a customer. The page is done, the ad is ready, and then someone asks where the money goes. There is no answer. The seller has a login on someone else’s platform, and the money, the customer list and the right to be there all belong to that platform.
Sold starts the other way round. Before Company, before Hook, before any selling, you make a key. It is yours. It makes your wallets, your identity and your private messages. Then you set up how you get paid, and you make one payment link your agent can send. This is Stage 0, ahead of Foundation.
The objective of this step: to leave with a private key made on your own device, wallets that can take payment, a way to take cards, and one payment link your agent can send, so that nothing later in the course waits on money.
Who sits beside you here. Anyone reading gets the free Sold tutor in the chat. An enrolled learner gets onboarder instead, the agent that walks a stranger to a first key and a first link (stageAgentFor).
What is true today
Read this table first. The chapter teaches the whole path, and marks every part that does not work yet with “Not yet”.
| Part | State today |
|---|---|
| The key: 24 words, made on your device | Built. The /get-key page, or npx oneie key new in a terminal |
| Identity and messaging keys from the same words | Built. Sealed notes and sign-in work from the key |
| Wallets: Sui, Ethereum, Base, Solana, Bitcoin, ASI | Built. The key makes five addresses; the Ethereum address serves Base too |
| Cards through Stripe | Built, in Stripe’s practice mode on a seller’s own shop. Not yet: real cards on your shop, until ONE switches Stripe to live there. ONE’s cut of a card sale is 0 by default |
| Crypto on the real networks | Not yet. ONE runs on a practice network (Sui testnet) until ONE switches to mainnet |
| ONE pays the gas on USDC sends | Not yet. ONE counts each wallet’s first 1,000 sends as eligible, but no relayer pays the fee. A wallet with no SUI cannot send USDC today |
| A crypto payment link to a shared address | Not yet. That rail is closed, so the Pay link button is hidden. A storefront link takes a card, or crypto to an address made for each buyer |
| A real paid link sent by an agent | Not yet proven. No seller has taken one |
1. Your key is 24 words on paper
Your key starts as 24 words. They are not a password. They are the key written in a form you can put on paper. From the words ONE derives one private key, and from that key everything else.
Three facts decide whether you can trust it.
- It is made on your device. The words never leave it.
- It is shared with nobody. Not ONE, and not your employer. ONE keeps only a locked copy it cannot open.
- ONE cannot recover it. If you lose the paper and the device, the key is gone.
What you do. Open /get-key and press the button. Your device makes the key, and the words never leave it. On the next screen, keep it: write the 24 words on paper, or save a key file, or seal it to Touch ID. Paper is the one that survives a lost device. Keep the paper where you keep a passport.
In a terminal instead? npx oneie wallet new --dir ~/.one/me --keychain makes a vault sealed to Touch ID, and prints only your addresses. npx oneie wallet paper --dir ~/.one/me shows the 24 words once. To open the same key in a browser, npx oneie wallet file writes a copy sealed with a passphrase you type. Drop it on /w/restore → Key file, sign in, and take the Touch ID offer.
What you hold at the end. 24 words on paper, and one private key on your device. /keys shows where the key is kept and what is still missing.
Your agent’s key is its own. You own the agent through the sweep. Think of a shop till that empties into your safe at closing. Your agent keeps a little to work with; the rest comes home to you.
Four steps. Give the agent a vault of its own (npx oneie wallet new --dir ~/.one/agents/<name> --keychain). Bring it into your workspace (npx oneie staff add-agent <name>). Register its addresses (wallet register --kind agent). Then set the rule with your key: npx oneie key sweep-rule --agent <id> --workspace <you> --chain sui --threshold 1000000000 --float 100000000 --dir ~/.one/me.
Above 1 SUI, its money moves to your proven address; it keeps 0.1 to work with. You never hold its key. It never names another destination. /treasury in Claude Code, or /wallets, shows every agent, its limit and its sweep on one board.
What your agent does beside you. It never sees your words. The command refuses to print them to a shell that looks like an agent, and under --json the words never reach the output at all. Your agent runs one key public to read the public side, your lock and your addresses, and one key verify to check that this device and the server agree. It can also make its own key, a separate one, with npx oneie.
A key made today follows the standard derivation paths, so its 24 words open the same wallets in any standard wallet app. A key made before that change restores on ONE only. Do not promise the first to someone holding the second.
Worksheet. Write one line: my words are kept ___. If the blank is “in a file on this laptop”, it is not kept. Paper is kept.
2. One key, four jobs
You made one key. It now does four jobs.
| Job | What it does |
|---|---|
| Identity | proves you are you, to people and to agents |
| Sign in | signs you in with no password |
| Lock | a public lock. Anyone can seal a note to it. Only your key opens it |
| Wallets | signs and moves your money |
The lock is the part a seller uses first. Give it out and a buyer can send you a sealed note that nobody between you can read. The format is standard (age), so any age tool opens it.
What you do. On /keys, find your lock. Press See them work. It seals a note to your lock and opens it again, on your device.
What you hold at the end. A public lock you can share, and an opener you never share. The public half names you. It opens nothing.
What your agent does beside you. It seals notes to other people’s locks and reads the notes sealed to its own. It asks you before it signs anything in your name. Privacy here covers keys and messages. A payment on a public chain can still be seen on that chain.
Worksheet. Write the lock of one person you will sell to. If you do not have one, write who you will ask.
3. One key, six blockchains
Your key makes your wallets. You name six: Sui, Ethereum, Base, Solana, Bitcoin and ASI. The key makes five addresses, because one Ethereum address serves both Ethereum and Base.
Receiving works on all six. A ONE checkout settles on Ethereum, Base, Solana and Sui (pay-settling.ts). Bitcoin and ASI can receive into your wallet, and have no checkout rail yet.
What you do. Open /wallets. Signed out, it sends you to the wallet page for strangers, where you make a key first. Signed in, it shows your balances. Copy the Sui address. It is the one the course uses most.
What you hold at the end. Six chains’ worth of receiving addresses, from one key. Your agent gets its own wallet, with a spending limit that only you can raise.
What your agent does beside you. It reads balances and receives payment. Spending is another matter. A wallet with a limit of zero spends nothing, and an agent can ask for more but cannot grant itself more.
The sovereign line is short. Nobody can move money from your wallet or your agent’s unless you or your agent allow it.
On the gas. Sending USDC on Sui costs a small fee in SUI. We mean ONE to pay it, on the first 1,000 sends from each wallet your key makes. Not yet: ONE counts those sends today and pays nothing. Until a relayer does, a wallet with no SUI in it cannot send USDC.
Worksheet. Write which of the six chains your first buyer will pay on, and why. If you do not know, write Sui and say what you will check.
4. Cards land in Stripe, crypto lands in your wallet
A buyer pays one of two ways, and they land in different places.
- Cards. Stripe takes them, plus Apple Pay and Google Pay where your Stripe account switches them on. The money goes into your own Stripe account, never into a wallet. ONE never holds it.
- Crypto. The buyer pays through a checkout that settles to the wallet your key made.
Neither is free in every sense, and we will not tell you it is. ONE takes nothing from a card sale by default. Stripe and the card network take their own fee, and a blockchain payment carries its own network fee. So never write a “no fees” line on your page.
What you do. Open /cards and connect your Stripe account. It walks you through. Stripe is in practice mode on your shop until ONE switches it to live, so nothing real moves yet. For crypto you do nothing. Your wallets already exist.
What you hold at the end. A card account connected, and wallets that receive. Both run on practice money until ONE switches to live. Not yet: a real sale on your own shop.
What your agent does beside you. It explains each fee to a buyer who asks, using the numbers on this page. It does not promise a payout time.
Worksheet. Write your price, then subtract the card network’s fee from Stripe’s pricing page. That is what you keep on a card sale. If the number surprises you, change the price now, not after the first sale.
5. The link is what a buyer clicks
You have a key, wallets and a way to be paid. Now make the thing a buyer clicks.
Our own first link is the worked example. Sold is one product: $100 for a human, one time. A buyer pays, and the payment enrols them in the course.
What you do. Open /products. Add a product with a name and a price. Then press Storefront link and copy it. That link takes a card, or crypto to an address made for each buyer. Signed out, the same page offers a practice sale on ONE’s practice network, so you can buy the product from yourself and watch it arrive. Not yet: the Pay link button, a crypto link to one shared address. That rail is closed, so the button is hidden.
What you hold at the end. One product and one storefront link you can send. Open it yourself and check the page and the price.
What your agent does beside you. It sends the link. In a chat, in an email or in a message to another agent, it puts the link next to a sentence about the result, and it reads the receipt when a payment lands. Sending the link is what an agent is good at. Choosing the price is yours.
We do not yet have a real paid link sent by an agent to prove all this end to end. Until we do, treat the first link as practice and say so to the buyer.
Worksheet. Fill the blanks, then send the link to yourself.
- My product, in six words: ___.
- My price: ___.
- The sentence my agent puts beside the link: ___.
- Who gets the first link: ___.
Accelerating with AI
Hand your agent the worksheet, not your words. It drafts the product line and the sentence beside the link in a minute. Check every claim in it. A model will happily write “no fees” or “pay on any blockchain” if you let it. Neither is true here.
Never paste your 24 words, your key in hex, or your opener into any chat, ours included. If you do, treat that key as exposed: make a new one and move what is in it.
What good looks like
You leave with:
- 24 words on paper and a key on your device
- a lock you can give to a buyer
- wallets that receive on six chains
- a card account connected, in practice mode
- one product and one storefront link, checked by opening it yourself
No benchmark exists for this step, because the payoff is that nothing later waits on money. The check is a short one: can you make a key, set up payment and send a link, from nothing, in one sitting, with no help? If yes, go on to Company.
Make it yours
Capture it in the Setup Worksheet:
- Where my 24 words are kept.
- The lock I will give to buyers.
- The chain my first buyer pays on.
- My price and what I keep after fees.
- The product, the link and the sentence beside it.
- What is not live yet, in my own words, for the buyer who asks.