Registry-local bonds
Bond metadata, validation, and the external settlement boundary.
What is implemented
The registry stores bond records and validates optional bondReference metadata. Operators provision bonds through the admin API. Bond requirements depend on entry type and operator policy; root entries can be exempt.
BondAmount is a fixed-point domain type. Follow the generated bond schemas; do not encode amounts as display strings such as 5 MINTS in arbitrary fields. Publisher-owned bondReference is included in the signing payload.
What a bond record does not prove
The current bond port is registry-local. It does not provide a live Mints escrow adapter or establish an on-chain wallet debit, automatic slash, or timed refund. Types for slashing and distribution describe the contract, not a verified external settlement.
Operator workflow
Use provision bond with admin capability and idempotency, then read bond. Keep policy enforcement and any separately operated economic settlement explicit.
Source authority
This page describes the checked-in implementation, not the availability of a public registry.
mars-server/src/bond.rsmars-protocol/src/bonds.rsmars-server/src/api/rest.rs