Authority anchors
Verifier-controlled backend selection and explicit finality/revocation evidence.
oas-resolve::LineageAnchor is the backend seam for authority evidence. The SDK's anchor-policy module is gated by the resolve feature. Documents may name anchor references; the verifier chooses which schemes it trusts.
Configure the policy
AnchorPolicy::default() trusts Sigil. AnchorPolicy::sigil_then_eas() prefers Sigil and permits EAS fallback. AnchorPolicy::trusting accepts an explicit ordered nonempty scheme list. Register the corresponding backend implementations in AnchorBackends.
VerifyWithAnchorRequest carries the policy, available backends, expected authority-path kind, required scopes and an optional minimum finalized block. These are verifier-controlled values, not privileges supplied by the document itself.
Confirmation flow
The configured source checks relevant revocation, root-anchor presence, status and finality before confirming authority. An unsupported or missing backend cannot confirm trust. If no trusted backend confirms the required authority, the privileged operation must fail closed.
A syntax-valid anchor reference is not inclusion/finality evidence. An adapter in source does not establish a live configured backend or make every foreign chain trusted. Inspect metadata commitments and other requirements of the actual implementation.
Backends
Sigil is the reference/default policy. oas-anchor-eas and the TypeScript EAS adapter supply a separate implementation seam. Configure chain, contract, endpoint and finality policy and verify the deployment before using it as authority.
Read anchor policy arguments and results, anchored resolver types, and EAS source modules. Local lineage checks remain a separate step.