Documentation
Rosh
A mobile-first chain for private payments. This is how to hold R, send it, and build against the network.
Start
The coin is R. Amounts are whole coins. A payment is signed with ML-DSA-65, and that signature is the only thing that can move the coins. A certified block stays.
The wallet creates the key on your device and signs there. The network checks the signature. It does not receive the key.
Liquid R is what you can send. Locked R is the weight behind certification. You choose when coins move from one to the other.
Wallet
Open the wallet. Create a wallet, or import a key you already exported. The key is stored in this browser. Closing the page does not remove it. Replacing the key does.
The balance at the top is liquid R. Under it is the amount you have locked. The address is the short form of your account. Receive shows the full address, which is 64 hex characters.
The header reads Live while the network answers, and Offline when it does not. A payment you have signed shows in the list once it is in a block.
Send and receive
To receive, open Receive and copy the address. Give that address to the sender. Do not send them the spending key.
To send, open Send and enter their address and a whole number of R. The wallet signs the payment and submits it. The balance updates when the block is certified. You can only send liquid R.
Each payment uses the next nonce for your account. The wallet reads that for you. A second attempt with the same nonce is refused, so a payment cannot be applied twice.
Stake
Stake locks liquid R, or unlocks it back to liquid. Locked R is what certifies blocks. Weight follows the coins you lock, not the number of machines you run. Liquid coins do not certify.
Unlock returns coins to the balance you can send. A certified block is not replaced by a later private history.
Build
A program that can make an HTTP request and an ML-DSA-65 signature can submit a payment. Reads are JSON.
GET /statusreturns the chain name, the height, and the tip.GET /block/<height>returns that block.GET /account/<address>returnsbalance,locked, andnext_nonce. Sign withnext_nonce.GET /activity/<address>returns payments that touch the address, newest first.POST /txsubmits one signed transaction. The account must already be able to cover it.
kind is transfer, lock, or unlock. For lock and unlock, to is 32 zero bytes, written as 64 hex zeros.
{
"kind": "transfer",
"nonce": 0,
"to": "<64 hex characters>",
"amount": 10,
"public_key": "<hex>",
"signature": "<hex>"
}
The network checks the signature, the nonce, and the balance before the transaction enters a block. A transaction that fails the check is not included.
Transaction bytes
Sign these bytes, in order:
- The ASCII bytes
ROSH-TX-V1 - The ASCII bytes
rosh-1 - One byte:
1transfer,2lock,3unlock - The nonce as a little-endian u64
- The 32-byte destination
- The amount as a little-endian u64
- The ML-DSA-65 public key
The signature context is the ASCII bytes rosh-tx. The address is the first 32 bytes of SHAKE256 over ROSH-ADDR-V1 followed by the public key. The sender is that address. The public key on the transaction has to be the key for that account.
Keys
Spend keys are ML-DSA-65. There is no second signature scheme on an account. A classical signature cannot move the same coins.
Export asks before it copies the spending key. Anyone who reads that copy can spend the coins. Keep it with you. The network cannot restore a key you lose, and replacing the key in the browser does not move the coins.
Import accepts a key you exported from this wallet. Check the address after import. It should be the account you expect before you sign anything.