TapeUP Universal Ledger

The hub is not a vault. It is two directories.

Every enabled chain uses deterministic deployment so the hub address is identical. Inbound entries record the sender container, block, timestamp, and digest; outbound entries record the recipient endpoint and the message's sequence in the recipient directory. The body lives in the send event; the chain retains the directory and fingerprint long term.

No destination-chain queries, no waiting for destination execution.

Senders submit transactions only on the chain that hosts their container. The hub verifies holder identity on that chain, writes the directory entry, and emits an event. The protocol therefore has no half-state such as "burned on the source chain, not minted on the destination," and needs neither a validator quorum nor destination-chain prepayment.

If the fingerprint does not match, the message does not exist.

The digest combines reference and payload hashes. The message ID binds the protocol domain, chain ID, hub, recipient endpoint, and recipient sequence. Payloads use elliptic-curve key exchange and authenticated encryption; directories are public, but only the recipient can decrypt the body.

Conceptual representation only; actual byte lengths and encodings follow the protocol specification.

function verify(record, payload, confirmations) {
        assert(hash(payload) === record.digest);
        assert(confirmations >= safeDepth(record.chainId));
        return { status: 'confirmed', payload };
      }

The page you see, the message you write, and the identity you hold point to the same coordinate.

Site files are chunked into containers, and the site registry records path, type, chunk count, and content hash. Pages and messages share the same container coordinate. Readers fetch chunk by chunk, and every hash must match the registry.