Glossary
Definitions for Opertus protocol, cryptography, and transaction terms.
Terms are grouped by the part of the system they describe. Exact constructions are in keys and notes.
Protocol
Commitment
A Poseidon hash of a note's token, value, one-time owner public key,
randomness, and blind. Commitments are public Merkle-tree leaves; their
openings remain private.
Deposit
A public transfer of assets into the pool that creates one note commitment.
Deposits do not use the transfer circuit. The pool inserts the note only when
the measured net amount equals the declared note value.
External data hash
A public field element derived from proof-bound transaction data. It binds a
proof to the chain, pool, encrypted notes, and either the transfer or unshield
payload.
Meta-address
Opertus's custom Base58Check address containing the recipient's BabyJubJub
spend public key, secp256k1 view public key, and nullifier image N. It is not
an Ethereum account address and is not ERC-5564.
Note
Private ownership data for one token and value. A note includes a one-time
owner key, randomness, and blinding material. The pool stores its commitment,
not its plaintext.
Nullifier
A hash of the nullifier key and a note's commitment. Publishing it marks a note spent without publicly
linking it to its commitment. The pool permanently rejects reuse.
Pool
The contract that holds public assets, verifies proofs, tracks roots and
nullifiers, inserts commitments, accounts for fees, and processes unshields.
Public amount
The gross value removed from private notes during an unshield or external call.
It is zero for a private transfer. The circuit enforces
sum(inputs) = sum(outputs) + publicAmount.
Return note
A note created from assets that arrive back at the pool after an external call.
Its measured value is public. A call may request up to four distinct returned
tokens.
Shield / unshield
Shielding moves public assets into a private note. Unshielding spends private
notes and moves a public amount out of the pool, either to a recipient or
through one external call.
Keys and privacy
Blind
A hash of the nullifier image and fresh blinding, included in a commitment. The sender knows public N
and fresh private blinding but not the recipient's nullifier key.
Note key (K)
The 32-byte XChaCha20-Poly1305 key of one note. The recipient derives it from
its view key, the sender from its outgoing key. Sharing it discloses that note
only.
Nullifier image (N)
A hash of the nullifier key. It is published in the meta-address and lets a sender construct
the note blind without learning nk.
Nullifier key (nk)
A secret derived from the viewing key. It lets a wallet compute nullifiers for
notes it can view, but it is not the BabyJubJub spend scalar.
One-time owner key
A stealth BabyJubJub key unique to a note. The circuit checks knowledge of its
secret when the note is spent.
Outgoing key (ovk)
sha256("opertus/ovk" || viewPriv). Seals the outgoing record and derives a
sending wallet's note ephemerals, so the sender can rebuild what it sent.
Receipt
A JSON document disclosing one note: its log position, note key, and either the
recipient meta-address or the blind. Anyone verifies it against the pool log.
Spend key
The BabyJubJub master scalar used to derive note-specific spend secrets. It does
not decrypt notes.
Stealth tweak (t)
Poseidon(S) mod l, where S is the stealth shared point. The one-time owner
point is the spend public key plus t · Base8, so revealing t proves which
spend key can spend a note.
View key
The secp256k1 private key used to decrypt matching notes and derive the
nullifier key and outgoing key. Possession reveals received and sent note
activity but does not by itself authorize a spend.
View tag
The first two bytes of a hashed ECDH shared point. It cheaply filters notes
before authenticated decryption. It is not authentication and can collide.
Proofs and trees
Groth16
The zero-knowledge proof system used by Opertus. Its small proofs are efficient
to verify on Ethereum, but each circuit requires a trusted setup.
Merkle path
The sibling hashes (at most 32), their count, and their direction bits that show
a commitment belongs under a root. A LeanIMT level without a right child has no
sibling. Membership does not prove ownership; the circuit checks both.
Root
The Poseidon Merkle-tree digest representing accepted commitments. Opertus
retains every inserted root; nullifiers prevent replay against old roots.
Trusted setup / ceremony
The process that generates Groth16 proving and verifying keys. Soundness
requires at least one participant to destroy their secret contribution.
Witness
The private and public values supplied to the circuit, including note openings,
spend secrets, Merkle paths, nullifiers, outputs, and public transaction data.
Execution and fees
Clone
A minimal contract used by the executor for one external call or a persistent
position. Salt zero selects the shared clone; a valid nonzero salt derives a
repeatable user-specific CREATE2 address.
Clone salt
A public circuit input. Zero needs no preimage. A nonzero salt must be opened
inside the proof from the spend scalar and a diversifier.
Executor
The contract component that runs one external call from a clone and returns
listed assets to the pool. The pool funds the clone directly; the executor holds
nothing.
Protocol fee
A basis-point fee charged on deposits and unshields. Accrued fees are later
claimed by the configured treasury. Private transfers do not incur this fee.
Relayer fee
An ordinary private output note intended to compensate a submitter. The pool
does not calculate or transfer it.
Perpetuals
Claimable
USDC the perpetual vault owes a clone from a close, refund, or liquidation. The
vault never pays a clone directly; the clone collects with claim(). See
trading.
Hedge gap
The difference between users' net position in the vault and the vault's
HyperCore position, szi. Valued at the mark, it is capped by
maxUnhedgedUsdc for any open that adds risk.
IOC order
An immediate-or-cancel order: it fills what it can at once and cancels the
rest, so nothing rests on the book. Every HyperCore order the vault sends is
IOC.
Mark price
Hyperliquid's reference price for a perpetual. The vault fills every request at
the mark of the executing block, plus or minus the spread.
Protocol equity
What the perpetual vault owns after paying users what it owes them. It bounds
open interest and must stay above minInsuranceBufferUsdc for opens. See
risk controls.