App
X
GitHub
  • use
    • Wallet
    • Faucet
    • Issue a token
  • read
    • Explorer
    • Side by side
    • Network
  • check
    • Check it yourself
    • What everyone sees
    • Prove a balance
  • token
    • Token
    • Burns
  • papers
    • Docs
    • Whitepaper

Docs

The chain's asset moves with encrypted amounts and encrypted balances by default. Anyone can verify every transfer is valid; only the holder can read his balance.

Reading the chain

Contents

  1. How a sealed transfer works
  2. Keys and recovery
  3. Faucet
  4. Public RPC
  5. What our index and gateway keep
  6. Known limits

The full public list: what everyone sees.

1

How a sealed transfer works

  1. Create a wallet. Your browser makes a keypair. The keys that seal and open your balance are derived from it the same way the official spl-token CLI derives them.
  2. Seal your account. You create your TEST account, configure it for sealed transfers and turn off public credits. From then on a public transfer to it is refused.
  3. Receive. The faucet sends test gas (GAS, public) for fees, then a sealed transfer of TEST. Incoming amounts land in your pending balance. The wallet applies pending to available.
  4. Send. Your browser builds three zero-knowledge proofs: equality, ciphertext validity and range. They go to the chain with the transfer. This takes a few transactions; the wallet shows step n of m, with the count from the transfer as it runs.
  5. The chain checks the proofs. It learns that the amount is valid and that you had enough. It does not learn the amount.
  6. Open your own. Only you decrypt your available balance and pending amounts, in your browser. Nobody else can.

What stays public along the way: what everyone sees.

2

Keys and recovery

  • Your key is kept in this browser only. It is never sent to our servers.
  • When you create a wallet you get a recovery phrase, shown once, and a key file to download.
  • Either one restores the wallet in another browser.
  • The same key file opens the same balance in the official spl-token CLI.
  • Lose both and the balance cannot be opened. We cannot recover it.

With the key file from the wallet, the official CLI applies your pending balance:

spl-token --url $RPC apply-pending-balance --owner key.json $MINT
3

Faucet

basic grant
test gas and test coin
how often
once per address every 24 hours
100,000 $OMERTA
2x the basic grant
1,000,000 $OMERTA
5x the basic grant
5,000,000 $OMERTA
10x the basic grant
  • The grant size is fixed, so a fresh account's first balance can be guessed.
  • Holders of $OMERTA on Solana get more. Linking a Solana wallet is a signed message, not a transaction. It links that wallet to your OMERTA address in the faucet's records. Holder grants leave from the same faucet account as basic grants.

Go to the faucet

4

Public RPC

Reading the network settings.

requests
50 a second per client
WebSocket
20 connections per client
refused
admin methods and node-address methods
history
Nodes keep under an hour of history. Older transactions cannot be read from the node.

Each client has a rate limit. A refused request says so. Test gas for fees comes straight from the CLI:

solana --url $RPC slot
solana --url $RPC airdrop 1 <address>

TEST and larger grants of GAS come from the faucet. Check it yourself with the official tools.

5

What our index and gateway keep

index
counters; single transfers for a rolling a short window; no history per address
gateway
nothing per request; per-client counters in memory only
your key
nothing; it stays in your browser

The full list, with the faucet's records, is on what everyone sees.

6

Known limits

  • Who sent to whom is public.
  • Minting is public, so total supply and moves between public and sealed balance are public.
  • Wallets that do not know the confidential-transfer extension show 0 and cannot send.
  • The chain has 4 validators, all operated by the OMERTA project.
  • Not Solana mainnet. A fork we run.
  • The chain runs on test coins. Neither TEST nor GAS is $OMERTA.

OMERTA (omerta.computer). Not Solana mainnet. A fork we run.

The gate on Solana

The program through which $OMERTA is burned on Solana and issued on OMERTA. It opens with the switch.

program
omerta_gate
program address
6ZHKdzBWh7Sw4EKgReCovuQtFMgrzijwr5WziGfRhjyoSolscan
state
Closed