Exaion
Wiping and Proofs

Proof statuses

Every status a proof goes through, what it means and whether you need to act.

From the moment it reaches the portal, a proof goes through a series of statuses. Most proofs go from Received to Certified on their own, in a few moments.

Processing statuses

These statuses follow one another automatically. You have nothing to do.

StatusMeaning
ReceivedThe proof is stored and waiting to be processed.
ValidatingThe portal checks the signature of the agent, that the proof belongs to your organization, and its content.
Generating PDFThe certificate PDF is being produced.
SigningThe certificate is being signed.
AnchoringThe certificate fingerprint is being recorded on the blockchain.

Final statuses

StatusMeaning
CertifiedThe certificate is issued and anchored on the blockchain. Open it from the proof page.
Certified (no anchor)The certificate is issued and signed, without a blockchain anchor (your instance does not anchor, or anchoring is off). It is just as valid, and it uses licenses like any certificate.
RejectedThe proof is refused for good: it is not valid, or not for your organization. The page gives the reason.
AbandonedThe proof was abandoned by support, at your request and with a reason. No certificate will be issued.

Statuses that wait for something

These three families are kept apart on purpose: they do not have the same cause, and they do not call for the same action.

StatusWhyWhat to do
Awaiting licenseThe proof is valid but your organization has no license left.Nothing is lost. The proof is certified automatically once licenses are available. See Awaiting license.
Pending reviewThe agent could not tell what kind of machine it erased.Set the machine type on the proof page. See Pending review.
FailedA temporary problem on the portal side interrupted the processing.The portal retries on its own. If it keeps failing, a client admin can retry by hand. See Failed.

The proof page

Click View on a proof to open its page. It shows:

  • the source (AGENT or MANUAL), the date received and who submitted it;
  • the SHA-256 of the DER: the fingerprint of the file as received, handy to match a proof with the file you hold;
  • the reason, when the proof was rejected or failed;
  • a link to the certificate, once it is issued.

While the proof is being processed, the page refreshes its status every few seconds.

Contents