Mints (Maxy Mint) / Reference
Mint contracts
The contracts behind a mint, on Robinhood Chain, chain 4663, and what you rely on the issuer for. The SDK compiles these in.
| Contract | Address |
|---|---|
| Mint contract | 0xb2b8dAB207810586e2b8cf8daEfFbe0D92990A9d |
| Token (BTC.R; on-chain symbol MAXYBTCb, 18 decimals) | 0xA32Ec9e411aCF2ea403233e5e7f2f8366CC0d6C8 |
| Redemption contract | 0x9B21339E641bA89DfC1Fda27684D009B15b64D8A |
| Verifier | 0xDbA3FaD120aE7bBBD42a39eAB65D2A41E030e29A |
The operator key, returned by the mint contract's operator(), is 0x1AA9B5542Ec1fd6221935dE1CF7BA612aFe17c58.
What enforces each promise
| In direct custody | Enforced by |
|---|---|
| A mint needs a proven Bitcoin payment of the exact amount | Mint contract and verifier |
| Only an operator-signed assignment registers | Mint contract |
| A refund goes only to the signed address | The issuer, against the signed order |
What you rely on.
- The issuer holds the Bitcoin once the payment confirms.
- The issuer's service submits the proof and pays refunds and redemptions.
- The operator key signs only valid assignments.
Tell users this plainly. Report a problem to your Maxy contact. Failure cases and the planned HTLC model: Maxy Mint documentation (PDF).
Interfaces and parameters: Maxy Mint documentation (PDF).