Menoid docs · V1 Mainnet

Menoid V1

The compliance-friendly multichain privacy layer, live on Monad and Base. Mask, send, swap and unmask privately from your browser — and show your history with a viewing key, only when you choose.

Live on MonadLive on BaseProofs made in your browserKeys never leave your device
01

V1 Mainnet · Start here

What V1 is

Menoid V1 is the mainnet release of Menoid: a private app that runs in your browser at app.menoid.xyz. You connect the wallet you already use, sign one message, and that signature becomes your private keys. Your funds then live in a shielded pool as notes only you can open — and every move is checked by a zero-knowledge proof instead of a public balance.

No new app to install, no second seed phrase, no second address. People pay you at your normal address; the pool does the rest.

What’s live today

Mainnets

Monad (143) · Base (8453)

Private actions

Mask · Send · Swap · Unmask

Tokens

28 on Monad · 50 on Base

Memecoins

14 on Monad · 20 on Base

Swap venues

Uniswap V3 · Capricorn (Monad)

Compliance

Full viewing keys

Proofs

Groth16, made in your browser

Testnets

testnet.menoid.xyz, separate keys

How the pieces fit

Your wallet

MetaMask, Phantom…

signs once

one signature

Menoid app

in your browser

keys · proofs · decryption

proven calls

Relayer

submits private txs

pays their gas

transactions

NoidPool

one per chain

verifies · holds funds

Keys and proofs stay in your browser. The relayer only carries finished, proven transactions — it can refuse one, never change one.
  • The app, in your browser, derives your keys, finds your notes by decrypting the pool’s events, and builds every proof locally. Menoid’s backend serves only public data: the pool’s events, prices, swap quotes and the relayer’s fee.
  • The relayer submits sends, swaps and unmasks from its own address and pays their gas, so your address never appears on them. It is paid with a private fee note, in the token you spend.
  • NoidPool is one contract per chain. It holds every token in one pool, keeps the Merkle tree of notes, verifies the proofs and refuses any note that was already spent.

Contracts

Both chains were deployed from the same key, so a few addresses repeat across chains with different roles (Monad’s withdraw verifier and Base’s pool share one). That is expected, not a typo.

What the chain sees

On-chain, anyone can see

  • That an address registered for Menoid
  • Masks: who masked which token, and how much
  • Unmasks: which token, how much, and the receiving address
  • Swaps: the token pair and both amounts
  • Commitments, nullifiers and Merkle roots — opaque numbers
  • Encrypted notes — unreadable without a viewing key

Stays private

  • Who sent a private payment, and who received it
  • How much was sent, and in which token
  • Your private balance
  • Which mask paid for which unmask
  • Who made a swap, and where its output went
  • Your keys — they never leave your browser