✅Tool Result Verifiers
A verifier answers a narrow question: what evidence is sufficient for one Tool result to become accepted workflow data? Transport success means a request reached a Tool and produced a response; on-chain acceptance means the protocol checked the configured trust choice and committed the result.
The three trust choices
Noneaccepts the configured no-verifier path. It does not turn an unreachable endpoint into a successful result; a terminal off-chain transport failure may become normalized_err_evalfailure evidence on this path, while the workflow still records the response or failure boundary.RegisteredKeyaccepts evidence signed by an active key binding for the Tool or Leader identity. Key lifecycle, canonical commitments, and Signed HTTP are owned by Registered Keys and Signed Tool Communication.Externalroutes evidence to the Tool’s registered external verifier configuration, including its method, witness, and required shared objects. Use the generated external verifier reference for exact fields.
The selected mode is part of Tool and vertex configuration. Do not describe a RegisteredKey signature or external witness as a generic verifier requirement when the vertex selected None.
Verdicts and proof requirements
A verifier produces a verdict such as accepted, rejected, or a failure classification that the workflow can route. Proof requirements include the expected Tool identity, request commitment, signer or witness, nonce or replay boundary, and any required shared-object state. A returned or verifier-submitted output can produce durable VerificationVerdict::Reject/failure evidence, including an external-verifier rejection or an invalid active signature. A terminal off-chain transport failure may normalize to _err_eval evidence only for the None path; with RegisteredKey or External, verified transport failure can remain pending until timeout/expiry rather than becoming a cryptographic Reject. By contrast, a malformed proof, wrong Tool or vertex binding, stale request, missing witness, or structurally invalid stamp can abort the transaction before a result is committed; it leaves no failure evidence to resolve. Repair and resubmit that submission rather than treating an abort as a recoverable rejected result.
The workflow can therefore have a successful HTTP response with an on-chain rejection, a None transport failure with normalized _err_eval evidence, or a verified transport failure that waits for expiry. It can also have a transaction abort with no committed result at all. Payment and result-resolution use the accepted verdict or durable failure evidence, not an HTTP status alone.
Evidence boundary
Keep the generic verifier model here: identify the trust choice, the expected proof, and the verdict. Keep key rotation, allowlists, canonical signed bytes, nonce rules, and Signed HTTP v3 in Registered Keys and Signed Tool Communication. Keep the committed-result and affordability lifecycle in On-Chain Result Resolution.
Verification checklist
Record the Tool identity and vertex that selected the verifier.
Confirm whether the mode is
None,RegisteredKey, orExternal.Preserve the request commitment and the proof or failure evidence.
Check the verdict on chain before treating transport success as workflow success.
Link exact fields and signatures to the generated Move and SDK references.
Next
Continue to DAG and Execution to see where a verdict enters execution state.
Last updated

