Live receipt·Public synthetic data·Signed on request
Does the stated trigger follow from the supplied signed receipts?
14 of 14 reported top-level checks passed. Hive operates this verifier and signs the synthetic demo receipts. This is Hive-operated verification, not independent outside witnessing.
This synthetic demo links a trigger receipt to a supplied performance attestation and budget. Hive checks the signed records and recomputes the trigger from their declared inputs. That checks authenticity and internal consistency, not whether the measurements are true or a real insured event occurred.
| Verifier operator | Hive (hive-verifier-api) |
|---|---|
| Declared measuring party | did:hive:public-demo-measuring-party (recorded role: third party) |
| Signature key ID | did:hive:typed-receipts-v2 |
| Declared model identity | hive-public-model, provider hive-public-provider |
| Declared measurement dimension | latency ms total (ms) |
| Declared measurement window | 2026-10-11 10:57:13 UTC to 2026-10-11 12:57:13 UTC |
| Recomputed trigger state | satisfied |
| Verification result | valid |
These names come from verification.gates. Verification stops at the first failing top-level check; later checks are not reported as passed. Editing a signed body without a matching digest and signature fails verification.
This describes the implementation, not additional pass results. The count above includes only the reported top-level checks. Nested checks run in the same Hive-operated service and are summarized by ATTESTATION_INTEGRITY.
Schema and signed bytes. SCHEMA validates the trigger envelope against parametric-trigger-v1. ISSUER_KEY_MATCH resolves its key ID in Hive's configured keyring. PAYLOAD_DIGEST recomputes the signed body SHA-256, RECEIPT_ID checks the receipt type, and SIGNATURE with SIGNER_IDENTITY checks Ed25519 against the registered key. This authenticates signed bytes relative to that keyring, not source truth or organizational authority.
Supplied receipt links. ATTESTATION_LINK matches the supplied attestation's receipt ID and recomputed body digest to the trigger reference. BUDGET_CONSISTENCY compares the trigger and attestation budget references. TENANT_MATCH compares their tenant IDs.
Stated time ordering. PRECOMMITMENT_ORDER checks policy committed_at <= budget declared_at <= measurement window opens_at. This demo signs on request with synthetic historical budget times. It does not prove a real policy or budget was committed before observation.
Nested receipt checks. ATTESTATION_INTEGRITY calls verifyBondedPerformanceAttestation. Its BUDGET_RECEIPT and ATTESTATION_RECEIPT checks run schema, digest, receipt type, Ed25519 signature and registered-key checks on the supplied budget and attestation. BUDGET_WINDOW, DECLARED_BEFORE_WINDOW, OBSERVED_WINDOW, UNIT_DIMENSION, SCHEMA_VERSION_FLOOR and RATIO_RANGE check stated windows, unit/schema compatibility and ratio ranges where applicable.
Nested pair consistency. BUDGET_LINK, PARTY_MATCH, SUBJECT_MATCH, DIMENSION_MATCH, WINDOW_CONTAINMENT, DECLARED_BEFORE_MEASUREMENT and ATTESTED_AFTER_WINDOW compare the supplied pair's budget reference, tenant/run/key IDs, model/provider/cohort, dimension/unit and stated times.
Formula consistency. COMPARISON_RECOMPUTE, SAMPLE_SUFFICIENCY and OUTCOME_RECOMPUTE check threshold comparisons and the outcome using the declared distribution and sample count. INDETERMINATE_PROPAGATION and TRIGGER_RECOMPUTE check trigger_state against the attestation outcome and condition.requires_outcome. They do not verify the underlying measurements.
Observation-reference limits. RESPONSE_BINDING, inside ATTESTATION_RECEIPT, checks the presence and allowed kind of response_binding and the 64-character lowercase hexadecimal form of manifest_sha256. The attestation schema checks reference fields, and its signature binds those declared fields. No manifest is fetched, no manifest digest is recomputed from source material, and no referenced external observation receipt is verified. Reference binding is not source-truth verification.
Limited policy-text screening. NO_POLICY_LEAK checks policy digest form and rejects recognized currency-amount patterns in other signed values. It does not verify policy terms, match the digest to an actual policy, or guarantee that no sensitive text appears.
The measuring party's third_party role is declared data, not a verified role or outside witness. Result booleans such as valid, signature_valid, signer_verified, outcome_verified and budget_linked do not establish additional upstream checks or independent witnessing.
This command downloads the supplied receipt chain and posts it to the same Hive-operated verifier. It requires no account or API credential, but it still relies on Hive running the code and configuring its trusted keys. Running this command is not outside witnessing.
curl -s https://thehiveryiq.com/v1/demo/parametric-trigger | jq '{receipt: .receipt, attestation: .attestation, budget: .budget}' | curl -s -X POST https://thehiveryiq.com/v1/verify/parametric-trigger -H 'content-type: application/json' -d @-
Prefer the raw data? View the signed JSON. That is what a verifier consumes.
This receipt attests that a named parametric condition was evaluated against one specific Bonded Performance Attestation, that the policy terms digest was committed at or before the governing budget was declared and the budget was declared at or before its measurement window opened, and that trigger_state was recomputed by this service from the referenced attestation rather than supplied by the caller. It does not create, confirm, price, underwrite, or interpret any insurance policy, and this service never receives the policy terms. It does not establish that any claim is payable, does not effect or authorise any payment, and does not attest that the measured outputs were correct or that any loss occurred. The measuring party is recorded as declared and is not verified here. Whether this trigger state entitles any party to payment is determined solely by the parties' own contract.
This generic trigger demo uses the parametric.trigger verifier and its supplied performance pair. Other receipt types have their own checks and limits.
Evidence for underwriters Verify a receipt How the attestation works