Made on this device · held by nobody else
The gift is the payment that lands in your wallet and the credits it buys — answers, agents, promises staked on your story. The key is how that happens with nobody but you holding anything: touch the sensor and thirty-two bytes come into existence in this browser, and they become four addresses — Sui, Ethereum, Solana and Bitcoin — that take money from the first second. The secret behind them never leaves the machine you are reading this on, so ONE cannot hand it over, lose it or freeze it. Nor can ONE get it back for you. That trade is the whole of it.
One key · 4 chain keys · 6 wallets · 24 words
Four keys, six wallets: ONE is a coin at your Sui address and FET an ERC-20 at your Ethereum one, so neither needs a key of its own.
The offer
It was built as one gift for one person. It costs nothing to give it to everybody, so that is what happens to it. What follows is what the gift is, and what it is not.
Tap once and a real address exists — not a demo, not a placeholder. It can take a payment the second it appears, and that is exactly why the next thing you do is write the key down. An address is worth nothing without the key that opens it.
No fee to keep a key, no fee to restore one, and neither sits behind an account. That is the only sense in which any of this is free — moving money still costs gas, and the sponsored path takes 1% on top of it.
The secret is made in your browser and never leaves it. ONE cannot pass it to anyone, cannot freeze it, and cannot restore it for you. Those are not three promises; they are one fact read from three sides.
One secret answers both: the address that takes money, and the identity that proves you are the same person tomorrow. Today sign-in still signs with the funded address — the separate sign-in key exists in the code and nothing calls it yet.
A gift that only opens at one.ie still has our name on it. So the derivation moves to the standard paths, and the offline recovery tool — words in; addresses and a signer out; any machine, no server — has to exist before that claim is true. It does not yet.
Two roots, and paper is one of them. There is no support queue that can restore you and none that can lock you out either. The same property, both directions.
Authority
ONE answers every question about authority with one rule: walk UP the tree and take the first answer. A parent decides for its children; siblings cannot reach each other. The key makes that rule physical, and Sui is where it stops needing a server to be true.
Two ledgers, and nothing yet checks they agree. The walk lives in ONE and the ceiling lives on chain. The read that must answer “may this agent spend this?” by consulting BOTH — and refusing when they disagree — is designed and not built. Until it is, the mirror is a schema and an intention, and this page will not call it a guarantee.
The lifecycle
One secret at the top. Everything after it is something that secret derives.
Thirty-two random bytes come into existence in this browser, from this device's own generator or from a passkey only this device can evaluate. No server is asked for anything. This is the only step that is ever about a secret; every step after it is about what the secret derives.
The same bytes give you a public identity and four chain keys: Sui, Ethereum, Solana, Bitcoin. The root is a mould rather than a key — it cuts keys and signs nothing itself. One child signs you in, another spends, so a signature you are tricked into giving at the front door opens the front door and nothing more. That separation is built on the server and no screen uses it yet: today sign-in still signs with the address that holds the money.
Three places count, and you pick at the moment the key is made: an encrypted file in a folder, the twenty-four words on paper, or sealed behind the fingerprint on this device. Any one of them is enough, and writing the file takes milliseconds. A browser tab is none of them — a key that lives only in a tab dies with it, and the address it made keeps showing a balance nobody can reach. So the rule is narrow: the key is written to a vault file, paper or your fingerprint before the address appears. This page obeys it — mint, keep, then addresses — and it is not in production yet.
Your addresses are registered so money sent to you is recognised as yours. The receiver that records them takes addresses and structurally cannot take a phrase. The same key names three things at once: who you are, whether you are a person or an agent, and which person an agent belongs to.
wallet:create and the wallet doorsThis is the part that is the gift. The address takes a real payment the moment it appears — no ceremony first, and one warning beside it that is simply true: save this key, it is a real key and it can accept payments instantly. Balances are read from the chain, never from us, because a reply from us proves nothing about money.
identity:addressMoney in the wallet buys credits, and credits buy work: replies, tool and skill calls, agent runs, storage. They are prepaid service units, not a balance you withdraw. Then you promise something, stake on it with a signature your own key makes on your own device, and agents go and make it true. That loop — a payment landing, and thinking bought with it — is what the key was for.
credits, billing:topup and tasks:stakeThe architecture
Not because of a promise about how carefully we behave. Because of where the secret is and what each piece is allowed to do.
A break-in at ONE reaches no key, because no key was ever sent. Seal one behind your fingerprint later and what we hold is ciphertext whose only opener is the biometric on your device. A dumped database is public addresses and locked boxes.
It derives. Sign-in, spending and every agent get a child key of their own, so one borrowed signature costs one door instead of everything. It is the rule the rest of the design hangs from, and sign-in is where the code has not caught up: today it still signs with the address that holds the money.
Proving something about yourself — a passkey, a domain, a checked document — writes a small claim bound to your address that cannot be sold or moved: the method, the level, who issued it, and a scrambled fingerprint of the detail. Never the detail itself. This part is specified and not built yet.
Agents that work for you
A helper is a child of your key with a ceiling you own. It signs for itself; it spends only what you allow.
An agent that works for you is a child of your key. It signs its own work with its own key, and it never holds yours. Because yours can derive its, you can always sweep its money home without asking it.
What it may spend is a separate object on chain that you own and it does not. You set the number, including zero, and you start it low. Proven on testnet today, where the contract itself refuses a caller who is not the owner.
Nobody can claw back a key on a blockchain, so nothing here pretends to. Revoking sets the ceiling to zero on an object you own. The agent keeps its key, keeps signing, and cannot spend.
A ceiling bounds what an agent may spend, not what it may hold, so a busy agent on a rented server becomes a target worth taking. Earnings are to settle back to your address on a threshold, leaving a working float — which is all a wiped server would then cost you. That sweep is designed and is not built yet.
The price, said plainly
Free attaches to the key and the wallets. It does not attach to a transaction, and it does not attach to credits.
Free under the ONE License — unlimited use, modification and resale, irrevocable — with exactly one obligation in return: keep the ONE mark and the link to one.ie in whatever you deploy. That obligation is the whole price, and it is how a key somebody recovers can still find the door it opens.
Moving money on the crypto rail costs gas plus one percent, deducted on the rail itself. Nothing on this page claims otherwise, because something is deducted and a sentence that says "free" about a transaction would be false.
Keys and wallets are free and sovereign; credits are a product you buy, prepaid, with no overdraft behind them. Money in the wallet becomes credits, credits buy the thinking. That boundary is the one place the word free stops.
The threat model, as a table
Every line on the left is paid for by the line on its right. Nothing here is free.
Defends A break-in on our servers
Accepts Lose the paper and every device and the money is gone. No reset, no support line, no escape hatch
Defends A phished password — there is no password to give away
Accepts Whoever holds your twenty-four words holds everything. Paper is a copy of the key, not a hint at it
Defends An agent that misbehaves — its ceiling is the most it can cost
Accepts Sealing a key behind a fingerprint ties it to a platform account. That is why the paper exists
Defends A lost phone — the paper brings the same addresses back
Accepts Typing the words into other wallet software today derives a different, empty address without saying so
Your side of it
One tap. The secret is made in this tab, and the four addresses appear with it.
Write the twenty-four words by hand, or download the encrypted file, or seal it behind your fingerprint. One of the three, before the address is worth anything to you — that is the whole of your side of this.
Give out the address that matches the chain your payer is using. The balance you then see is read from that chain, not from us.
Buy credits with what arrives, then spend them on replies, skills, agent runs and storage at one.ie/keys. Keys and wallets are free; credits are the part you pay for.
Start the ceiling low. Raise it once the agent has earned it, drop it to zero the moment it has not.
Recovery
One you carry without knowing it. One you can hold in your hand. Either brings the same four addresses back.
Root one
The passkey is one of the three places the key can rest. The key itself is random and made once; your fingerprint opens a sealed copy of it on this device, and the seal is useless without the finger. Lose the device and that copy is gone — which is why there is a second place.
Root two
The same thirty-two bytes, written as twenty-four words you can copy onto paper. They are not a backup of the key — they are the key. Type them at one.ie/w/restore and the same four addresses come back. Paper survives a dead laptop.
They are BIP-39 words, and they are not a seed phrase another wallet can open. A standard wallet takes the phrase through PBKDF2 and BIP-32; ONE takes the entropy those words encode straight into HKDF. Same words, different key. Typed into other software they will produce an address that looks perfectly valid and is not yours. Restore them at one.ie.
That is decided, not built: new keys will derive by the standard paths, and keys already made keep every address they have. Until that ships, the words restore your key here, and a different wallet fed the same words lands on an address that is empty and says nothing about it. This page will say otherwise on the day it is true, and not before.
The boundary
The key is never written to this browser's storage and there is no row for it in any database. What this page does is ask you to keep it before it shows you an address: an encrypted file you save to your own disk, the twenty-four words on paper, or a seal behind your fingerprint. The only thing it records afterwards is a note to itself that a durable copy exists — never the key, never anywhere but this browser.
Deriving a key makes no request of its own. The secret is computed in this tab by your browser's own crypto, and no code on this page sends it anywhere. The page loads the way any page does — scripts, styles, one analytics beacon — and none of that carries the key.
This page makes a key, takes your keep, and then shows the addresses. It moves no funds and signs no transaction — there is nothing here that can spend. To seal a key under your fingerprint, prove the words on paper, and see where you stand in the six steps above, the manager at one.ie/keys is where that happens.