Understand
the boundary.
An independent Solana workspace with a local wallet and confidential test-token operations on devnet. Start with the working flow and understand what remains public.
A clear first step.
This release includes the website, a signing web wallet, documentation, a devnet transaction service and a browser companion. Confidential amounts use the official Solana Token-2022 and ZK ElGamal Proof programs.
An interface you can explore
Inspect public wallet data and RPC connectivity. The browser companion saves a public address and reads its actual SOL balance and recent signatures after your consent. These checks require no wallet signature.
Confidential test-token amounts
Generate proofs in your browser, approve local signatures, and submit sponsored transactions. Deposits, confidential transfers, pending-balance application and withdrawals use the configured OMIT CT test mint.
Privacy has a boundary.
Confidential transfers encrypt token amounts and balances. Sender and recipient accounts, test mint, timing, deposits and withdrawals remain visible. This is amount confidentiality, not participant anonymity or private native SOL.
| Surface | What the design must account for |
|---|---|
| Public chain | Entry and exit details can create links through addresses, amounts and timing. A shielded design does not erase the public chain. |
| Service providers | Network metadata and submitted requests need an explicit threat model. A relayer is still a server. Public wallet checks through OMIT disclose the requested address to our service and the upstream RPC; direct extension checks disclose the address and your IP to the selected RPC. |
| Your device | Keys and sensitive local data need storage, locking and recovery behavior that can be independently checked. |
| Chosen recipients | Disclosure should show exactly which records a recipient can read before anything is shared. |
The test mint has zero decimals, automatic confidential-account approval and no auditor ElGamal key. Only its own confidential balances can be decrypted by the local owner. No anonymity score is provided.
A smaller window
into your history.
The proposed sharing flow starts with a selection: particular records, assets or a date range. You would review the resulting proof package before giving it to an accountant, counterparty or other recipient.
Shared information stays shared. Removing a hosted link cannot retract data a recipient has already read or copied. Limited sharing must be enforced by the package itself.
Proof packages and independent verification have not been implemented in this release.
Choice, with a way back.
Providers you can inspect
The app can read a selected Solana RPC endpoint's genesis hash, current slot and public wallet data through OMIT's read-only network service. The confidential workspace separately verifies devnet and uses the configured fee sponsor, strict transaction validation and chain-backed account reads. Choosing alternative private providers remains planned.
Local key recovery
The app creates a real local Solana key, encrypts it with your password in browser storage, and supports restoring its OMIT1 recovery code in a fresh browser profile. Save the complete code offline before the encrypted wallet is stored. It contains the unencrypted key; anyone with it can recreate that key. Losing both the code and browser data makes the key unrecoverable.
Can I check a live provider now?
Yes. Public RPC checks work in Providers. In Shield, Send, Receive or Withdraw, Check service verifies the devnet configuration and displays the actual test mint and fee sponsor. The relayer sponsors fees; an account index reads actual chain records without learning decrypted balances.
Should I enter an existing wallet recovery phrase?
No. OMIT does not import another wallet’s seed phrase. Its Local wallet card accepts only its own OMIT1 recovery format. The browser companion remains read-only and stores no private keys.
The same product.
A closer surface.
The Manifest V3 companion saves a public address, selected network, connection route and theme locally. On an explicit check it reads the network identity, native SOL balance and five recent public signatures. It cannot sign transactions or access private keys.
OMIT for your browser
Available for manual installation. It requests local storage and access only to OMIT's network service and the two public Solana RPC hosts. Not published in the Chrome Web Store.
Installation and permissions ↗ · Download unpacked extension ↓
A precise release status.
The devnet workspace operates on a dedicated Token-2022 test mint. Use test tokens only. Mainnet native SOL and USDC privacy operations are not enabled.
- Website, app & docs
- Live
- Confidential deposits, sends & withdrawals
- Active on devnet
- Protocol & cryptography
- Browser proofs + onchain verification
- Local Solana wallet
- Encrypted key + reviewed signatures
- Independent security audit
- External review pending
- Browser extension
- Manual install + public wallet checks
- Public RPC connectivity check
- Live mainnet + devnet reads
- Devnet relayer & account index
- Configured devnet service
Verified through the web wallet
Two fresh local wallets completed the full app flow: configure, deposit 100 test units, apply pending, transfer 25 confidentially, receive, and withdraw 25. All 15 transactions finalized on Solana devnet, with 25 explicit wallet approvals and no page or HTTP errors. The final source balance was 75 confidential units; the destination held 25 public units.
The browser SDK test independently completed the same flow. A separate public-RPC check confirmed all 30 receipts. These are test tokens; participants and accounts remain public. This does not establish private SOL, mainnet readiness or an independent audit.
Deposit ↗ · Confidential transfer ↗ · Withdrawal ↗ · Browser and UI receipts ↗
The local wallet locks when hidden, on navigation and after five minutes idle. Its key has not been independently audited. Restoring the same OMIT1 key lets the official SDK derive the same confidential viewing keys after your approval. Decrypted balances stay local; onchain token accounts remain public.
Before mainnet
Mainnet privacy requires a separately validated protocol, independent security review, operating budgets and deployment evidence. The current confidential test token does not make existing SOL or USDC private. No independent audit of OMIT is claimed.
Can I submit real devnet transactions?
Yes. Open Shield, create or unlock a local wallet, connect the account, obtain test funds, unlock the confidential view and configure the account. Deposit test units, apply the pending balance, transfer to another configured account, then withdraw. Every signature requires a review. These operations use devnet test tokens only.