Verifiable Privacy
User-controlled privacy with legally grounded regulatory oversight.
Users control what to reveal (counterparties, amounts, asset types) on a per-transaction basis, and regulators access data within limits defined by law — a design that satisfies privacy and compliance at once.
The execution layer of this model is live on chain: the privacy precompile at 0x1000…000b handles shielded-pool deposits, transfers, and withdrawals verified by zero-knowledge proofs, and every state-changing privacy call passes PCL policy evaluation. The concrete mechanisms are documented in this section's concept pages and the IPrivacy API reference.
Selective Disclosure
Unlike traditional public chains where everything is visible, Maroo lets users and enterprises shield sensitive transaction details from the general public. Today this runs as a shielded pool: a deposit leaves only a commitment on chain, and transfers and withdrawals are verified with zero-knowledge proofs. The full design is covered in
privacy-precompile-overview.Observer Nodes
The regulatory-access model set out in the litepaper: authorized entities (such as financial regulators) operate Observer Nodes whose cryptographic keys can decrypt specific transaction data, usable only within their legal authority. This disclosure protocol is not yet implemented on chain — the regulatory control running today is PCL policy evaluation applied to every privacy call, covered in
privacy-policy-aware-precompile.