Three steps, and what each one actually does.
A wallet that asks you to verify nothing is only worth anything if you can check the mechanism. So this page describes what you do, what gets written down, and what this system is not able to do for you.
Open an account
The form asks for a name, a phone number, an email address, a username and a passphrase. None of it is verified: no document is uploaded, no code is sent, no reviewer decides whether you are allowed in. The account works from the moment the form is submitted.
- You do
- Fill in five fields and choose a passphrase. That is the entire sign-up.
- We create
- One Bitcoin address and one balance record, opening at zero. The address is yours for the life of the account.
- We store
- The name, phone, email and username exactly as typed, plus a bcrypt hash of the passphrase at cost 10, the address, and the moment the account was created.
- We never ask for
- An ID document, a selfie, proof of address, a source-of-funds answer or an occupation. There is no approval queue behind the form.
- You get
- A signed session cookie the page's own scripts cannot read, valid for 7 days. Signing out ends it immediately.
Receive to your address
Give your address to whoever is paying you. It does not expire, it does not have to be requested in advance, and reusing it is fine. When a payment is credited it appears in your ledger as a movement in, with the time and the counterparty attached.
- You do
- Copy the address out of the wallet and hand it to the payer. It is the only thing they need.
- You see
- A row in your ledger with the amount, the direction and the timestamp. Your own receive address is the one value in the interface shown in full rather than covered.
- We store
- The amount to 8 decimal places, the address at the other end and the time. The row is attached to an account, not to anything about you we checked.
- We cannot do
- Recover an amount sent to the wrong string. Read the address before you hand it out, and read it again before anyone pays it.
Send from your balance
A send moves value between two accounts on this system. Your balance falls, the recipient's rises, and both sides get a row written to their own ledger with the fee breakdown attached. This is a custodial wallet: the movement is a change to records we keep, not a transaction broadcast to the Bitcoin network on your behalf.
- You do
- Paste a destination address, enter an amount in BTC, and read the review screen before you confirm.
- You are charged
- The amount, plus a flat network fee of 0.0001 BTC, plus a platform fee of 1% of the amount. All three are shown together before you confirm.
- It is refused when
- The destination is not an address on this system, the destination is your own address, or the balance does not cover the amount and both fees. Nothing moves in any of those cases.
- We store
- The destination, the amount, both fees and the time — one row on your ledger, one on theirs, and nothing beside it.
One send, written twiceillustrative — sending 0.01 BTCYour ledgerSent−0.01020000BTCamount + both fees- Destination
- bc1q7yd…r9lfc
- Network fee
- 0.00010000
- Platform fee (1%)
- 0.00010000
Their ledgerReceived+0.01000000BTCthe amount you typed, in full- Sender
- bc1qm3f…zl5pt
- Network fee
- —
- Platform fee (1%)
- —
Both rows are written in the same movement, so the arithmetic on either side can be checked against the other. Fees are charged on top of the amount, which is why the recipient sees the figure you typed.
Two things worth knowing first.
Nothing is verified, but plenty is collected
Your name, phone and email sit in the account record because the form asks for them. What never happens is a check against them — no document, no code, no queue. Treat them as labels you chose, not as proof of anything.
A lost passphrase cannot be reset for you
The passphrase exists only as a hash, so nobody here can read it back, and an unverified email is not proof that an account is yours. Keep it somewhere you will still have in a year.