Verification Methods | Traceport

Verification Methods

Traceport's four-layer verification system ensures your records are authentic, accurately represented, and permanently recorded on the blockchain.

đź“‹ How Verification Works

Public Proof

Verifications 1–3

Anyone can confirm a record exists, when it was created, who signed it, and which organization issued it—without seeing the underlying data.

On-Demand Verification

Verification 4

When you need to prove what the record contains—for audits, disputes, or compliance—you provide the original data. Anyone can then verify it matches the blockchain proof exactly.

1

Proof of Existence

Publicly verifiable
What it proves: Your record was permanently recorded on the Bitcoin blockchain at a specific time and block. It's like having a timestamp from thousands of independent witnesses around the world—providing permanent, public proof that your record exists and can never be deleted.

Technical Process

Validates the complete Merkle path from the transaction to the blockchain's Merkle root using BUMP (BSV Unified Merkle Path) protocol defined in BRC-74. Verification requires computing the Merkle root from the BUMP data, then validating that computed root against actual blockchain headers.

Why it matters

Provides immutable, timestamped proof that data existed at a specific point in time. Cannot be backdated, modified, or deleted. The blockchain provides mathematical certainty.

Verification steps

  • Parse BUMP binary format containing block height and Merkle path data
  • Calculate Merkle root using transaction hash and provided BUMP path
  • Query block-headers service to validate computed root against actual blockchain
  • Verification passes only if root exists at specified block height
2

Cryptographic Signature

Publicly verifiable
What it proves: Traceport cryptographically signed this specific record using our unique digital signature. Only Traceport possesses the private key that could create this signature for this specific data—it's mathematically impossible to forge.

Technical Process

Uses Elliptic Curve Digital Signature Algorithm (ECDSA) to verify that Traceport's private key signed the data hash. The signature is mathematically verified using the corresponding public key embedded in the blockchain transaction.

Why it matters

Provides cryptographic proof of authenticity and non-repudiation. Anyone can verify the signature came from Traceport—no trust required, just mathematics.

Verification steps

  • Extract signature and public key from blockchain transaction
  • Apply ECDSA signature verification algorithm
  • Confirm signature mathematically matches the data hash
  • Verification is deterministic—same inputs always produce same result
3

Organization Identity

Publicly verifiable
What it proves: The record was created by a specific organization using their unique cryptographic identity—not by someone else, and not by Traceport pretending to be them. Each organization has a mathematically isolated keyspace that only they can use.

Technical Process

Uses hierarchical key derivation (BRC-42/43) to create cryptographically isolated keyspaces per organization. Each organization's keys are mathematically derived from their unique identifier, making cross-organization impersonation impossible.

Why it matters

Proves organizational ownership with mathematical certainty. Even Traceport cannot create records that appear to come from a different organization—the cryptography enforces isolation.

Verification steps

  • Extract organization identifier and derivation path from attestation
  • Regenerate expected public key using hierarchical derivation
  • Verify transaction signature matches organization's derived keyspace
  • Confirm attestation originated from claimed organization
4

Data Integrity

Verifiable on demand
What it proves: The original data you're presenting exactly matches what was recorded on the blockchain. If even a single character was changed, the verification would fail immediately—providing tamper-evident proof of the record's contents.

Technical Process

The original data is hashed using SHA-256 and compared against the hash stored on the blockchain. This verification requires access to the original data—which you control and provide only when needed.

Why it matters

Proves exactly what was attested without storing sensitive data on the blockchain. Your data stays private until you choose to share it. When you do share it, anyone can verify it matches the proof.

Verification steps

  • Organization provides original data for verification
  • Apply SHA-256 hash algorithm to provided data
  • Compare resulting hash with blockchain-stored hash
  • Verification passes only if hashes match exactly
Your control: This verification only happens when you provide the original data. The blockchain proves something exists—you decide when to reveal what it contains.

Why Four Layers?

Each verification serves a different purpose. Together they create a complete trust framework that anyone can verify independently—no trust in Traceport or the record creator required.

Publicly verifiable
Proof of Existence
Immutable timestamp proving the record exists
Publicly verifiable
Cryptographic Signature
Mathematical proof of authenticity
Publicly verifiable
Organization Identity
Proves which organization created it
Verifiable on demand
Data Integrity
Proves the contents when you choose to share

The Verification Layer for Any Record

Your data. Your control. Cryptographic certainty.

Unlike traditional record-keeping, every Traceport attestation can be independently verified by anyone using public blockchain tools. No database access required. No trust required. Just mathematics.