pub struct V2VerifyRequest {Show 15 fields
pub bundle: Vec<u8>,
pub expected: Option<ExpectedChallengeV2>,
pub context_policy: Option<V2ContextPolicy>,
pub required_scope: String,
pub verifier_namespace: String,
pub replay_epoch: i64,
pub verifier_id: String,
pub now: i64,
pub max_challenge_age_seconds: i64,
pub future_skew_seconds: i64,
pub context: ConstraintContextV2,
pub tzdb_version: String,
pub status_keys: BTreeMap<String, V2StatusKeyConfig>,
pub status_policy: RevocationStatusPolicyV2,
pub constraint_evaluators: Option<ConstraintEvaluatorRegistryV2>,
}Expand description
One live verification. context_policy: None means the verifier
explicitly configured no context policy; the terminal result can then
never be allow (SPEC-v2 §6.7). now is the caller’s clock and is used
only for the pre-claim freshness check; every post-claim time-sensitive
check uses the claim store’s authoritative time.
Fields§
§bundle: Vec<u8>§expected: Option<ExpectedChallengeV2>§context_policy: Option<V2ContextPolicy>§required_scope: String§verifier_namespace: String§replay_epoch: i64§verifier_id: StringThe caller-authenticated verifier key ID (SPEC-v2 §2.4, §6.1).
Required: an empty or non-canonical value is configuration_invalid
before the ExpectedChallenge is examined, and both the
ExpectedChallenge and the proof bundle must name it
(verifier_id_mismatch otherwise).
now: i64§max_challenge_age_seconds: i64§future_skew_seconds: i64§context: ConstraintContextV2§tzdb_version: StringThe configured IANA tzdata release for time_window; it must equal
super::TZDB_VERSION_V2.
status_keys: BTreeMap<String, V2StatusKeyConfig>§status_policy: RevocationStatusPolicyV2§constraint_evaluators: Option<ConstraintEvaluatorRegistryV2>The caller-authenticated extension evaluator registry; None
registers none, so every extension type is constraint_unknown.