Skip to main content

Compliance Enforcement Dashboard

Backoffice view for managing compliance enforcement actions (freeze, seize). Used primarily by Compliance Officer. Must support both EVM addresses and ZK (shielded) addresses.

Active Enforcement (required)​

All addresses currently frozen and/or oracle-sanctioned. Derived from on-chain state. Searchable by address. Seize is a one-time event, not an ongoing state — see Enforcement History below.

Each entry shows:

  • Address — the restricted address (EVM or ZK)
  • Frozen? — Yes / No — manual freeze in effect (blocks both inbound and outbound)
  • Oracle-sanctioned? — Yes / No — Chainalysis sanctions oracle (live query, EVM only)
  • Since — date the freeze was executed on-chain
  • Known entity? — whether this address belongs to a known partner or has prior redemption/issuance history; opens the full Known Addresses lookup

Sortable by date.

Pending Actions (required)​

Enforcement requests awaiting decryption or on-chain execution (status = awaiting_decryption or awaiting_execution). Compliance Officer and the relevant multisig use this view to see what is in flight.

Each entry shows:

  • Address — target address
  • Action — freeze, unfreeze, seize
  • Status — awaiting_decryption (ZK seize, before TRC response) or awaiting_execution
  • Signs with — Compliance Multisig (freeze/unfreeze) or Seize Multisig (seize)
  • Amount — for seize: amount to move. Blank for freeze/unfreeze, or for ZK seize still in awaiting_decryption.
  • Destination — for seize: destination address and kind (emi_segregated, case_designated). Blank for freeze/unfreeze.
  • Decryption record — for ZK seize: link to the child decryption request (status, response amount once recorded, response reference)
  • Requested by — Compliance Officer
  • Requested at — timestamp

Enforcement History (required)​

Full log of all enforcement requests — executed and dismissed. Searchable by address, filterable by action type and date range. Exportable as CSV for audit purposes.

Each entry shows:

  • Date — timestamp of the request
  • Address — target address
  • Action — freeze, unfreeze, seize
  • Amount — for seize: amount moved. Blank for freeze/unfreeze.
  • Destination — for seize: destination address and kind. Blank for freeze/unfreeze.
  • Legal-ground tag — the cited legal basis (e.g. aml_art_16_2, court_mica_94_3_f)
  • Signed by — Compliance Multisig or Seize Multisig (for executed actions)
  • End state — closed_executed or closed_dismissed
  • Rationale — Compliance Officer's documented reason
  • Tx hash — on-chain transaction hash (for executed actions)
  • Decryption record (ZK seize only) — expandable: target_epk, committee_response_amount, responded_at, response_reference

Oracle Address Lookup (nice to have)​

Ad-hoc lookup against the Chainalysis sanctions oracle — check whether a given address is flagged. Useful during investigations and compliance reviews. No liveness monitoring needed.

  • Oracle contract address — on-chain address of the sanctions oracle
  • Chain — Base (L2)
  • Address check — manual "check address" input that queries the oracle directly and returns the current flagged state