Verify an evidence packet

Verify selected evidence on this device. No sign-in, AI credential, file upload or wallet action is required. Signature, private replay, hardware identity, conditional inference timing, source association and independent destination observation are separate claims.

Portable packet v1

Evidence packetJSON up to 40960 KB. Selected files stay local.Separately reviewed signer, deployment and financial expectationsJSON up to 98 KB. Selected files stay local.Revalidate public hardware reports through the official NEAR SDK. Intel/NVIDIA collateral, attestation services and SDK proxy endpoints may receive public quote/GPU evidence. Current verification does not prove original execution time or plaintext.Authorize historical NEAR lookups for this packet's public contract/payment references.

Optional sensitive private replay

Enable local replay against independently reviewed plaintext digests. This does not establish hardware trust, invoice truth or payment authority.

Separate inference chain anchors

Requires the original packet's encrypted wire bodies plus separate razor.inference-anchor-evidence/trust v1. Independently choose contract/code, recorder, model measurements, context, original Gateway SPKI and maximum interval. The block producer can predict its random seed; the conditional interval never becomes an unconditional wall-clock proof.

Final challenge and response-commitment evidenceJSON up to 64 KB. Selected files stay local.Independently reviewed anchor trustJSON up to 64 KB. Selected files stay local.Authorize bounded archival NEAR lookups for both finalized anchors, historical code/keys, receipts and execution timestamps.Authorize official hardware/collateral verification for the exact chain nonce and retained wire/report commitments. Public evidence may leave this device; current collateral does not prove its historical validity.

Standalone destination transfer observation

Strict NEP141, ERC20 or legacy SPL references. A real transfer, address/amount match or matching packet IDs does not establish payment association. Unsupported finality, fee extensions, Token-2022 and missing archive data remain unavailable.

Destination evidenceJSON up to 98 KB. Selected files stay local.Independent exact destination and token behavior expectationsJSON up to 98 KB. Selected files stay local.Authorize this destination's public references to my selected RPC.

Separate payment settlement association

Separate razor.settlement-link-evidence/trust v1 supports one exact native treasury execution or an explicitly authorized reporter's structured statement committed on NEAR. Reporter association and destination observation are separate. Old free-text, partial, expired or redacted receipts cannot be reconstructed into proof.

Settlement-link evidenceJSON up to 64 KB. Selected files stay local.Independent source, payment/route/version, reporter and destination trustJSON up to 64 KB. Selected files stay local.Authorize historical NEAR source action, code, frozen terms and receipt lookup.Separately authorize destination RPC observation. This does not convert a reporter statement into trustless bridge causality.

Clearing discards local references and invalidates late results. Public network requests you already authorized may finish; no background request starts from selecting a file.

Independent trust must come from a source you reviewed, never an exporter-provided allowlist. No signature or plaintext match proves invoice accuracy, model honesty, legal discharge or settlement outside the exact reported verification class. Downloaded disclosures cannot be revoked remotely.

Local command and input schemas

node --max-old-space-size=512 --import tsx scripts/verify-evidence.ts --help

Portable packet: razor.portable-evidence v1 and razor.verifier-trust v1. Destination: razor.destination-evidence/trust v1. Private replay: razor.private-inference-replay-keys and razor.private-inference-replay-expectations v1. Anchors: razor.inference-anchor-evidence/trust v1. Settlement: razor.settlement-link-evidence/trust v1. The command is offline by default, requires --acknowledge-replay-key-disclosure for owner-only key files, prints no keys/plaintext and exits 1 for invalid/failed or 2 for incomplete claims.