Status Checking

Once you submit a Proof Request, a Proof ID will be generated and displayed. You can then check the status using:

PROOF_ID=id

fermah-seek proof check -k dev --key ecdsa.seeker --id $PROOF_ID

Valid for Testnet.

Status Lifecycle

Proof requests follow a specific lifecycle from creation to completion. Understanding these status codes will help you track your request through the system.

Status Codes

pub enum ProofStatus {
    /// Was just created in the system
    Created,
    /// Passed most basic checks like signature
    Accepted,

    /// Closed, primarily due to PRer returning their funds
    Cancelled,
    /// Rejected with explanation
    /// - Eligible for payment
    Rejected(String),

    /// Assigned to a specific prover
    Assigned(OperatorId),
    /// Solid assigned state. Prover confirmed the assignment.
    AcknowledgedAssignment(OperatorId),

    /// Received proof, but test is not complete
    ProofBeingTested(Proof),

    /// Proved
    /// - Eligible for payment
    Proven(Proof),
}

Status Codes for Proof Requests

Status Code	Meaning
CREATED	Matchmaker has received the Proof Request.
ACCEPTED	Seeker has escrowed enough funds.
ASSIGNED	Matchmaker has assigned the Proof Request to an available Operator.
ACKNOWLEDGED_ASSIGNMENT	Operator has sent an acknowledgement message to Matchmaker.
PROOF_BEING_TESTED	Operator has sent a proof to Matchmaker.
PROVEN	Matchmaker has verified the proof, and it is valid.
REJECTED	Proof was rejected for one of the following reasons: Seeker didn't escrow enough funds. Operator wasn't able to compute the proof for any reason, including: Failure to download the prover image Image not having the expected hash Ill-formed Proof Request Matchmaker tried to verify the proof, but it is invalid.

React Flow