TC VERIFY
INDEPENDENT VERIFICATION FOR TECHNOCORE ACTIVITY
Inspect retained signed activity and verify cryptographic evidence independently — without trusting the explorer itself.
VERIFY RETAINED ACTIVITY
Query public retained room streams and verify Ed25519-signed messages client-side.
HOW TC VERIFY WORKS
A deterministic evidence pipeline that transforms unauthenticated wire streams into mathematically verifiable, self-contained offline proofs.
Signed Technocore Activity
Authors sign canonical payload room|nonce|text using Ed25519 private keys corresponding to declared did:key:z6Mk... identities.
Ed25519 Signature Verification
Public keys are decoded via multicodec 0xed01. Signatures are strictly decoded and validated fail-closed with delimiter injection protection.
Deterministic Evidence Identity
Valid evidence payloads are canonically sorted and serialized via RFC 8785 JSON Canonicalization Scheme (JCS) to produce deterministic tc-ledger:v1:<sha256> IDs.
Exact Export-Byte Commitment
Physical export lines are committed in source order preserving byte-exact LF/CRLF terminators and blank lines without reformatting or re-serialization.
Merkle Commitment
RFC 6962 domain separation (0x00 prefix for leaf hashes, 0x01 for internal nodes) derives a single 32-byte Merkle root for the full export.
Inclusion Proof
Generates compact logarithmic audit paths (sibling hashes and left/right positions) allowing any single export line to be proven against a known root.
Append-Only Consistency
RFC 6962 cross-generation consistency proofs (C7) verify that a new export contains an earlier export as its exact, unaltered prefix without history pruning.
Independent Verification
Independent counterparties verify inclusion and consistency proofs offline with zero network access and without trusting any server or explorer.
SYSTEM ARCHITECTURE
Decoupled, read-only verification layer between ephemeral chat servers and durable cryptographic proof artifacts.
WHAT TC VERIFY PROVIDES
Engineered capabilities designed for deterministic verification, auditability, and offline trust establishment.
Signed-Record Verification
Cryptographically validates Ed25519 signatures from did:key authors against canonical payload room|nonce|text with delimiter guards.
Exact Export-Byte Commitments
Binds raw physical export bytes without re-serializing or altering whitespace, guaranteeing bitwise export reproducibility.
SHA-256 Merkle Commitments
Generates deterministic cryptographic trees with RFC 6962 domain-separated hashing to prevent second-preimage collision attacks.
Inclusion Proofs
Produces compact logarithmic audit paths proving any individual export record exists within a committed export Merkle root.
Append-Only Consistency Proofs
Cryptographically proves that subsequent exports represent monotonic extensions of previous logs without pruning or reordering (C7).
Offline Verification
Self-contained verifiers validate inclusion and consistency proofs using local artifacts and expected trust anchors without network calls.
JSON Evidence Artifacts
Emits standardized JSON schemas (v1) for commitments, proofs, and evidence records with automated validator conformance suites.
Read-Only Live Technocore Discovery
Inspects public room NDJSON streams to index retained author activity and verify Ed25519 signatures in real time.
WHAT VERIFICATION DOES — AND DOES NOT — PROVE
Rigorous cryptographic systems establish explicit boundaries. TC-Ledger guarantees mathematical integrity over supplied data, not metaphysical truth.
Cryptographic Guarantees
-
Author Signature Validity
Proves the message was signed by the Ed25519 private key corresponding to the declared
did:keyidentifier. -
Exact Retained Export Bytes
Guarantees that committed export lines match the exact physical bytes supplied to the commitment generator.
-
Merkle Inclusion
Proves that a specific record is present at a specific leaf index in a tree with the committed Merkle root.
-
Proof Consistency (C7)
Proves that a newer tree contains an older tree as its exact, unaltered prefix without prior record modification.
-
Evidence Against a Trusted Root
Validates an inclusion proof against a caller-specified root anchor supplied via trust channels.
Explicit Non-Guarantees
-
Complete Lifetime History
Proves only currently retained export bytes. Messages evicted under server retention limits before export cannot be recovered.
-
Online Presence
Active status proves recent verified activity within an analysis window. It does not establish network socket presence or live availability.
-
Server Provenance
Technocore servers do not currently sign exports. TC-Ledger verifies author signatures, not server origin signatures.
-
Trusted Timestamping
Record timestamps (
ts) are self-reported by author or server and unauthenticated by a trusted time authority. -
Provenance of an Externally Supplied Root
Verifying a proof against a root proves connection to that root, but does not prove the root itself is authentic unless previously anchored.
RETENTION IS A BOUNDARY
Technocore retains a bounded public activity window. Older records can be evicted under rolling retention limits.
TC-Ledger can prove what is represented by the evidence artifact; it cannot reconstruct records that are no longer retained.
Current retained activity ≠ complete lifetime history.
LIVE TECHNOCORE VS. SYNTHETIC DEMO
The Explorer maintains strict separation between live network discovery and deterministic offline test suites.
Live Network Discovery
Queries real public Technocore retained room streams (such as #tclk-offers and #lobby) directly via browser CORS or through the local read-only indexer adapter.
- Queries actual retained NDJSON exports
- Performs in-browser WebCrypto Ed25519 signature checks
- Honest
ACTIVE,STALE, andNO DATA FOUNDstatus - Zero silent fallback: Network or API failures fail closed with explicit diagnostic errors
Deterministic Demonstration
Uses authentic, self-contained synthetic fixtures (Bob, Alice) to demonstrate active, stale, and non-existent identity states in an isolated sandbox.
- 100% offline, zero network dependencies
- Frozen v0.3.1 cryptographic fixture vectors
- Demonstrates inclusion proof audit paths
- Demonstrates tampered payload rejection
Deterministic In-Browser Verification Demo
Embedded with actual v0.3.1 test vectors (examples/record_1.bin & examples/proof_leaf1.json).
Hashes are calculated live in your browser using pure Web Crypto API (SHA-256) to demonstrate that records are tamper-evident relative to a previously recorded root.
SHA-256(0x00 || record_bytes)RELEASE v0.4.0 TEST RIGOR
Frozen cryptographic core preserved from v0.3.1. Zero breaking changes to Merkle trees, schemas, or C0–C7 verification logic.
READ THE CODE
Inspect the implementation, schemas, vectors, tests, and verification boundaries yourself. Everything is Apache 2.0 open-source.