H33
Last updated2026-07-02Page version1.0Methodologyrev 1

Home › Proof › Public verification examples

Public verification

Sample H33 artifacts on Solana. Verify without an H33 account.

Every artifact class H33 emits has a public anchor on Solana. Any block explorer resolves it. Any auditor reproduces it. No H33 attestation needed. The samples below are illustrative — real customer artifacts appear here as the public receipt viewer ships.

○ Sample anchors · real per-customer artifacts land with public receipt viewer

Which artifact classes land on chain
· document notarization
· identity verification
· wallet + cross-border
· AI provenance
· audit-log Merkle roots
· payment authorization chains
· beneficiary payments

Directory

Eight artifact classes · one Solana anchor each.

Click Solana ↗ to open the sample anchor in an external block explorer. Real per-customer artifacts follow the same shape.

Capability & anchor kind Sample hash Verify
Document Notarization
Solana document NFT
 5x7pB6MHc4vN8kQz2mXn3rY1hR9fJ4kL7wD6bE Solana ↗
Digital Identity Verification
Soulbound identity NFT
 7Xz1n6QwqCB4uNRDp3TfhE5wM8bLK2xVzP9jHr Solana ↗
Wallet Send / Receive
Solana transaction
 3nZfMHkK1v9pBQrX4hN2yLDcW7RaTt8gEUj6VP Solana ↗
Cross-Border Payments
Solana transaction (multi-hop settlement)
 9bkD2fQpX8jY1hMcNwR5vTt7L4aGKm3zXPUV6E Solana ↗
AI Verification & Provenance
Signed provenance record (AI Agent Authorization artifact)
 4TmB7pQzN3vX8jY1hMcNwR5vTt7L4aGKm3zXPU Solana ↗
Audit Logs (spot-check anchor)
Solana anchor for audit-log Merkle root
 6vHnQKp3fJ2yLDcW7RaTt8gEUj6VPzXP4hMcNw Solana ↗
Payment Authorization Chain
Signed authority chain (multi-approver)
 2xzRpQ9bkD2fQpX8jY1hMcNwR5vTt7L4aGKm3z Solana ↗
Beneficiary Payments
Solana transaction (dormancy-triggered)
 8QwqCB4uNRDp3TfhE5wM8bLK2xVzP9jHr7Xz1n Solana ↗

Solana was chosen for its transaction cost profile ($0.00025 average · sub-second finality) which makes per-action anchoring economically viable. H33 does not depend on chain uptime — receipts remain valid off-chain; the anchor is redundant third-party proof.

How this composes

Three layers of proof, stacked.

Layer 1 · in-Vault

Signed receipt at emit

Every action produces a receipt signed with ML-DSA-65. Kept in the Vault activity log.

Layer 2 · Object-Locked

Immutable at rest

Audit trail written to S3 with Object Lock Compliance retention. Cannot be deleted by anyone.

Layer 3 · on-chain

Solana anchor

Selected artifact classes (or periodic Merkle roots) anchor to Solana as third-party time proof.

Trust status

Every artifact is publicly checkable.

Solana anchors listed above · verify without an H33 account.

Runs today

  • Vault workflows running in production
  • Cryptographic receipts emitted per action
  • Immutable audit trail · Object-Locked
  • Auth1 · Wallet · Document · Audit APIs
  • Post-quantum primitives (Dilithium + Kyber)
  • Benchmark v12 · 2,293,766 auth/sec

Coming next

  • Public /verify// receipt viewer
  • Public /replay// decision viewer
  • docs.h33.you developer documentation
  • SOC 2 Type II Certified
  • Payment Requests + Rewards adapters

Every artifact class has an anchor.

Check the samples on Solana above. Real per-customer artifacts follow the same shape.

Start free Back to Proof