Skip to main content

For attestors

Status: Built, runs on simulator

An attestor reviews assigned evidence and signs a statement whose fields and effect depend on the task.

This section covers registration, quarterly report review, annual corrections, hardship pauses, fallback exchange rates, amendments and extinguishment. The operating guides and the responsibilities page remain unpublished drafts while signing integration and policy questions are resolved. They are not instructions for an available production service.

Evidence, signature and result​

These are separate things to check. Evidence explains the factual basis for a decision. The signature binds a particular message to a registered key. The chain checks that message and its own current state. A case marked signed in the backend is not by itself evidence that a transaction was accepted.

Stage One defines the chain messages. Stage Two now uses those signature messages and separately linked attestor keys. A signed backend row still needs a successful chain submission before it proves an accepted action.

The program reference and contract reference expose the checked interfaces. The event reference records observable results. These are source references, not deployment confirmations.

What the role can see​

The Stage Two data map gives the chosen reviewer access to encrypted tier-three documents and income openings, or to the evidence for an assigned hardship case. It records extinguishment evidence for the two named reviewers. Active indexed registration and the addressed key’s link to the session account control access to that work.

A holder sees public payment information and status records through the corresponding views; the attestor's evidence is not part of those views. Payment amounts are public onchain. The distinction between a restricted evidence view and public financial outputs matters when explaining confidentiality to an issuer.

Eligibility to serve and compensation remain undecided under Q-043. Registration describes a technical permission; it does not settle those professional arrangements.

What can go wrong​

Reviewing the right evidence is not enough if a signature binds the wrong statement or is prepared for a different signing system. Conversely, a correctly encoded signature does not establish that its evidence is complete. The draft guides keep both questions visible.