Developers
Deployments
Where the contracts are deployed, and how each is configured.
Copy Markdown
Deployed on Robinhood Chain
| Contract | Address |
|---|---|
OpaquePool | 0x388c7Cf4Ce9616E63c2A454B762d5EbFA25081AD |
$OPA token | 0x01f7748d1a3543ad3f9e71b2fbdc10c00688e7f5 |
What gets deployed
| Contract | Role |
|---|---|
OpaquePool | The $OPA pool and note tree |
Poseidon2Hasher | The hash used by the tree and by note commitments |
| Verifier | Checks proofs of the transact circuit (generated, not yet in the repository) |
| Fee harvester | Collects the trade fee and buys $OPA for the vault (not built) |
Constructor of OpaquePool
Every value is fixed forever at deployment.
| Parameter | Meaning |
|---|---|
hasher_ | The Poseidon2 hasher |
verifier_ | The proof verifier |
token_ | The $OPA token |
guardian_ | The address that can pause new shrouds |
exitFee_ | Flat unshroud fee, in $OPA wei. It stays in the pool |
cap | Deposit schedule for $OPA |
A schedule has an initial cap, a step amount, a step interval in seconds and a ceiling.