Deploy a token
Horai can prepare a token launch on Robinhood Chain. It cannot perform one. The transaction is signed by your wallet, from your wallet, and the token is created by you.
Non-custodial, and what that means here
The agent has no key and no path to one. What it produces is an unsigned transaction; the only way that transaction ever reaches the chain is you approving it in your own wallet.
The consequences are worth stating rather than implying:
- The on-chain creator is your address, not Horai's.
- Creator fees accrue to you.
- The launch fee and gas are paid in ETH from your own wallet, not from your Horai balance. A free start covers the thinking, never the on-chain cost.
- Horai cannot undo, recall, edit or claw back a launched token, and neither can you. It is irreversible.
The confirmation preview
Nothing goes on-chain without an explicit action from you. When the agent is ready, a confirmation panel shows the real terms it is about to ask you to sign:
| Row | What it is |
|---|---|
chain |
Robinhood Chain |
supply |
total token supply |
graduates at |
the ETH threshold at which the token graduates |
launch fee |
the fee, in ETH |
initial buy |
ETH spent buying your own token — none unless you asked for it |
est. gas |
estimated gas, in ETH |
you pay |
fee plus gas — what leaves your wallet |
logo url |
the full URL that will be written on-chain |
creator fees |
who receives them |
your wallet |
the address that will be the creator |
initial buy is shown even when it is none, because a launch can buy your own token with any ETH sent above the fee. Seeing none is the assurance that the value being sent is exactly the fee.
Read it and either approve or cancel. Cancelling costs nothing and sends nothing.
The prompts you will see
Approving raises two prompts in your wallet, and only the second one is a signature:
- Switch network. Robinhood Chain has to be the active network. If your wallet does not know the chain yet, this prompt adds it (RPC
https://rpc.mainnet.chain.robinhood.com, explorerhttps://robinhoodchain.blockscout.com) and then switches. Approving this signs nothing. - Sign and send the transaction. This is the launch. Your wallet signs it and broadcasts it, and the token exists from that moment.
The launch must be signed by the same wallet it was prepared for — the one you signed in with. If your wallet is on a different account, you get told which account to switch to before anything is sent, and the server checks the same thing independently.
The fee is re-read before you sign
The fee you previewed could be stale by the time you approve, because it can change upstream. So it is re-read immediately before signing.
If it has moved, nothing is signed. The change is shown as two explicit numbers — what you previewed, and what it is now — and you re-confirm at the current fee or cancel. A launch fee is never adjusted silently.
After it is broadcast
The moment the wallet returns a transaction hash, the launch has happened. From that point the Sign button is permanently retired for that job: signing again would create a second token and pay a second fee, with no way back. Everything that follows — recording it, verifying it, waiting for the receipt — can fail without un-launching anything, and none of those failures re-enable the button.
The transaction hash is shown, and it is the authority on what happened. The job's receipt keeps the deploy lines.
Where the logo is hosted
A logo is stored by Horai and served from the app domain, addressed by the hash of its own bytes:
https://apps.horai.sh/logos/<sha256>.<ext>
Content-addressed, so the URL cannot come to mean a different picture later. This URL is written on-chain and can never be edited — which is why the preview shows the whole URL as a link rather than just a thumbnail. A rendering thumbnail proves the bytes exist; only the URL tells you where they will be read from for as long as the token does. Open it and check it before signing.
Next
FAQ answers the questions people ask first.