Skip to main content

Reporting Dashboards

All dashboards source data from the backoffice and the decryption service (for encrypted mint/burn amounts). Only mint/burn transactions can be decrypted — arbitrary transfers between users cannot.


Mint/Burn Dashboard (required)

Primary source of truth for on-chain supply. Used by Treasury Officer, Compliance Officer, and Supply Signers.

Headline figures

  • Public supply — plaintext ERC-20 tokens in circulation
  • Encrypted supply — FHE-encrypted tokens (decrypted value from decryption service)
  • Total supply — public + encrypted

Mint/burn history

Chronological log of all mint and burn transactions with decrypted amounts. Each entry shows:

  • Tx hash and block number
  • Timestamp
  • Type (mint or burn)
  • Amount (decrypted)
  • Public or encrypted
  • Linked backoffice request ID
  • On-chain status (finalized?)

Filterable by date range, type (mint/burn), and public/encrypted. Exportable as CSV.

Point-in-time query

Look up total minted supply as of any historical timestamp.

Supply chart (nice to have)

Supply trend over time — total, public, and encrypted plotted separately.


Validation History (required)

Log of all Reserve Validation runs.

Each entry shows:

  • Validation ID — unique identifier
  • Date — validation timestamp
  • Fiat balance — Treasury-provided reserve figure
  • Reserve location — free-form note on where reserves are held (MiCA Art. 30 requirement)
  • On-chain total — dashboard-pulled supply
  • Public supply — plaintext ERC-20 minted
  • Encrypted supply — encrypted minted (FHE-decrypted value)
  • Result — PASS / FAIL
  • Multisig verified — Yes / No — whether the 2-of-3 Supply Multisig co-sign completed on the publication decision (No for closed_failed and closed_not_published). Expand to see the individual signers.
  • End stateclosed_published, closed_not_published, closed_failed
  • Failed checks — which checks failed (if any)

Useful for auditors, regulatory submissions, and tracking published supply figures over time.


Incoming Transfers & Returns (required)

Operational view of the shared custodial redemption address. Used by Supply Signers to attribute incoming transfers and manually return funds when needed.

Each incoming transfer shows:

  • Tx hash and block number
  • Timestamp
  • Sender address
  • Amount
  • Attribution — matched redemption request ID, or unattributed if the sender does not match any open request
  • Status — pending_compliance, queued_for_burn, burned, return_required, returned, compliance_hold

Actions:

  • Return — initiates an ERC-20 transfer back to the sender address. Used for unattributed transfers and for compliance-rejected requests (Step 4a). Executed by a Supply Signer signing from the custodial wallet.
  • View request — jumps to the linked redemption request for attributed transfers.

Filterable by status, date range, and sender address.


Mint/Burn Volume Reporting (nice to have)

Derived from the mint/burn history. No additional data source needed.

Metrics

  • Daily mint volume — total minted (public + encrypted) per day
  • Daily burn volume — total burned (public + encrypted) per day
  • Net issuance — mints minus burns per day
  • Mint/burn count — number of transactions per day
  • Rolling averages — 7-day and 30-day rolling mint/burn volume

Available as a dashboard view and as a filterable CSV export (by date range, public/encrypted, mint/burn).

Use cases: compliance trend reporting, regulator submissions, early detection of unusual redemption spikes.