First Emerald Console Contract operations

Operations console

Every action below is signed by the role that would perform it in production: the registrar records, the custodian confirms, the auditor attests, the oracle publishes. The console holds no powers of its own.

Demonstration environment. The keys are the deterministic ones from the development node. In production they live on an HSM or a multisig and this interface never sees them.

Demonstration walkthroughs

Ready-made sequences to run in front of a subscriber. Each ends with a readable verification.

1The constraint holds

Attempts to issue one token beyond the reserve ceiling. It must fail at the contract level.

2The reserve grows

Adds a stone, places it in custody, re-attests: the ceiling rises on its own.

3The reserve breaks

Suspends a stone without re-attesting: registry and attestation diverge, the ceiling drops to zero.

4From SAFT to token

Enables issuance and lets subscribers exercise their entitlements. This is the post-approval scenario.

5The KYC perimeter

Attempts a transfer to a wallet that was never verified.

6Collateralised lending (phase 2)

Funds the isolated market, deposits FEX as collateral and draws liquidity. Requires walkthrough 4.

Individual actions

Record a stone

Publish the index

Moves the token reference value and the collateral value on the lending market.

Re-attest the reserve

The auditor realigns the attestation with the current registry.

Record a SAFT

Ready.