Private by default.
Every amount and balance of its main asset is ciphertext. Anyone verifies a transfer; only the holder reads it.
- –
- slot
- –
- sealed transfers
- –
- sealed-transfer amounts an outsider can read
TokenWhitepaperNot Solana mainnet. A fork we run.
The same transfer, twice
On Solana a transfer carries its amount and both balances in the open. Here the same transfer shows who, to whom, when and the fee, and the amount stays sealed.
- Solana, amount
- –
- Solana, sender after
- –
- OMERTA, amount
- sealed
Ciphertext, where the amount would be
The amount is encrypted in the sender’s browser and stays encrypted on chain. Zero-knowledge proofs travel with it, so every validator checks the transfer without reading it.
Bring the light as close as you like.
Open your own
The holder’s key stays in the holder’s browser. It opens that holder’s balance and incoming amounts there, and nowhere else.
- the project’s own specimen
- sealed
Check it yourself
The official solana and spl-token tools read this chain as it stands. A sealed account shows a public balance of 0 and ciphertext. A public transfer into it is refused.
$ spl-token --url https://rpc.omerta.computer display <token-account>
$ spl-token --url https://rpc.omerta.computer transfer <mint> 1 <recipient>
custom program error: 0x31Every command and its output$OMERTA
$OMERTA is the gas and stake of the OMERTA chain. It enters one way: burned on Solana, issued on OMERTA. Until the switch, the chain runs on test coins.
Today, holding $OMERTA raises your faucet allowance on the OMERTA chain. It is not the chain's gas yet.
- holding 100,000
- 2x allowance
- holding 1,000,000
- 5x allowance
- holding 5,000,000
- 10x allowance
Send one sealed transfer.
A wallet in this browser, a grant from the faucet, one sealed transfer. About a minute.
Make a wallet