HLP — Hash-Linked Proof

L7-HLP · 1. What HLP is

1. What HLP is

This is product legal copy for Wrooms and L7 Chain. It is not legal advice, not a securities prospectus, and not a registration statement. Wrooms is the Service and the contracting party. The Wrooms App is hosted at wrooms.ai. Wrooms AI is the house desks inside the Wrooms App. L7 Chain (also L7) is the public settlement ledger of the Service, readable at l7c.ai. Its purpose is to seal economic events — buys, sends, swaps, issues, wraps, and pieces — so a later record cannot quietly replace an earlier one. L7C is the layer-one coin of L7 Chain. WRO is the native layer-two token of Wrooms, isolated on L7 Chain. The Wrooms User Agreement remains the binding terms of use. The Token Sale Agreement is the binding purchase terms for L7C and WRO sold on the Wrooms book.

The wrap rule on L7 Chain is the Aggregated Hash-Linked Protocol (AHLP). In the book, the explorer, and product copy it is HLP (Hash-Linked Proof). Both names refer to the same instrument. The current field is HLP-2: 22 records, L7C first, then every rail spine including USDC, USDT (Tether), and DAI. A wrap produces a hash-link: one SHA-256 digest of those live heads at that instant. Hash linking — aggregate hash linking — is the act of folding those heads. The Hash Link Protocol is that same bind. Short form on a seal: HLP. Short HLP on a seal: H1S.

When you wrap a buyable rail onto L7 Chain — Bitcoin, Ether, Solana, USDC, USDT, or any other buyable rail — the seal is a cryptographic validation hash that attests a transaction has been sealed across multiple blockchains over the public internet. It does not stamp one foreign block. It commits the entire live field. Occupancy cannot print past the live wallet. A failed seal produces no state change and no asset movement.

L7-HLP · 2026.08.22-10 · p. 3 / 9

L7-HLP · 2. History of HLP

2. History of HLP

HLP was developed because a wrap that stamps one foreign tip is a screenshot. L7 Chain watches many rails at once. Occupancy is 1:1 against native locked in a published vault. The bind had to answer one question at lock time: while this native was locked, what did every watched chain look like? That answer is a cryptographic validation hash that attests a transaction has been sealed across multiple blockchains over the public internet — a hash-link — not a dashboard of someone else’s chain.

The blueprint did not change. Five planes, data only down: Wallet → Vault → Field → Hash-link → Book. A failed plane aborts. What changed is the field, the names, and how stables enter the digest.

Stable-coin implementation. A stable is not an L1 and not an L2. HLP-2 puts USDC, USDT, and DAI in the field as aggregated host binds without inventing a USDC chain. HLP-3 and HLP-4 do not reopen that field. HLP-4 is the live generation that writes and verifies those 22 slots, scores field health, and seals Short HLP v3.

Founding     postulate
Protocol     ALHP / AHLP / HLP named
HLP-1        19 slots. Stables ride hosts
Short HLP    H1S projection
HLP-2        22 slots. DAI · USDC · USDT aggregated host binds
HLP-3        prior generation. Same 22-slot HLP-2 digest. Dual-gen verify. H1S v2. Field health.
HLP-4        live generation. Same 22-slot HLP-2 digest. Quad-gen verify. H1S v3. G4 memo stamps.

Planes (unchanged)
0 Wallet → 1 Vault → 2 Field → 3 Hash-link → 4 Book

HLP-1 seals still verify under the 19-slot grammar. HLP-2, HLP-3, and HLP-4 wraps use the 22-slot grammar. The digest namespace is HLP-2. A further change to field membership or record grammar is HLP-5 and a new digest namespace.

L7-HLP · 2026.08.22-10 · p. 4 / 9

L7-HLP · 3. The live field

3. The live field

HLP-2 always covers L7C plus every live rail spine, including USDC, USDT (Tether), and DAI as field members — 22 records in a fixed order. A stable’s record is the aggregated bind of its hosts: height is the sum of those host tips; hash is SHA-256 of those host records. USDC rides Ethereum, Robinhood Chain, and Base. USDT rides Ethereum, TRON, and BNB. DAI rides Ethereum, Arbitrum, and Base. Those hosts also keep their own slots. Arbitrum, Optimism, Base, and Robinhood Chain are Ethereum L2 spines, not coins you buy. HLP-1 was the 19-spine field without the three stables. A further change to field membership is HLP-3.

The home cluster of a planet is L7C plus the spines of networks where that coin can actually be bought. The protocol still maxes the bind: every wrap commits the full L7C-and-rails field.

L7-HLP · 2026.08.22-10 · p. 5 / 9

L7-HLP · 4. Digest, memo, and the book

4. Digest, memo, and the book

The protocol does not encrypt the live field. It fingerprints it. SHA-256 takes the exact UTF-8 bytes of the payload and returns 256 bits written as sixty-four lowercase hex characters. That string is the wrap’s live hash. There is no HMAC and no salt.

One record is emitted for each of the twenty-two field members, in HLP-2 order, with L7C first. Records join on U+007C. Missing spines occupy their slot as ASSET:0: with an empty hash. Order is part of the digest.

USDC, USDT, and DAI are aggregated host binds. Height is the sum of host tips. Hash is SHA-256 of those host records. Hosts remain in the field on their own slots.

The memo carries HLP, the sixty-four hex characters, Short HLP, and the readable heights, then HLP_PAYLOAD and the exact string that was hashed. Seals that still say ALHP are the same protocol. An HLP-1 seal without USDC, USDT, or DAI slots still verifies if it carries HLP_PAYLOAD under the nineteen-slot grammar. Open /tx/{hash} to watch the explorer pass or fail that comparison in public.

L7-HLP · 2026.08.22-10 · p. 6 / 9

L7-HLP · 5. Short HLP

5. Short HLP

Short HLP gives the bind a line a person can read aloud. Tagged H1S, it is twenty Crockford Base32 characters, grouped H1S-XXXXX-XXXXX-XXXXX-XXXXX. The packing is version, a twenty-two-bit live mask, a fifty-six-bit braid-fold of the digest with every slot’s height, head, and ticker, and a CRC-8. I, L, O, and U are excluded from the alphabet so a mistype is likelier to fail the checksum than to name another wrap.

The sixty-four hex characters remain the bind. Short HLP is a projection computed after SHA-256. A reviewer who decodes H1S, checks the CRC, and recomputes the fold from HLP_PAYLOAD is checking that projection, and must still match SHA-256 of the payload to the stored digest. Mapping I or L to 1, or O to 0, only normalizes paste. A code that fails CRC is not a wrap. Short HLP is printed on the rails board, on the explorer, and on the wrap memo so it can be copied without copying the entire preimage. Every seal on the book also carries a locator tagged L7B, packed from that line’s height and hash. L7B names the seal. H1S names the wrap bind. A send, a buy, and a pulse do not become wraps by wearing a short code.

L7-HLP · 2026.08.22-10 · p. 7 / 9

L7-HLP · 6. What HLP is not

6. What HLP is not

• Not a screenshot of one tip.
• Not a price feed.
• Not a combined count of stored blocks.
• Not a wrap of Base, Arbitrum, Optimism, or Robinhood as coins — those L2s are spines under ETH.
• Not a truncation of SHA-256. Short HLP is a braided projection with a checksum. The 64-hex digest is still required.
• Not a security, share, or claim on Wrooms.
• Not a substitute for the Token Sale Agreement. Wraps are 1:1 occupancy of a foreign asset you already hold, not a sale of L7C or WRO.

L7-HLP · 2026.08.22-10 · p. 8 / 9

L7-HLP · 7. Binding place

7. Binding place

AHLP / HLP is a protocol of L7 Chain described in User Agreement §7. The current field is HLP-2. The technical specification and blueprint are at /hlp-spec. This page is product legal copy for users, auditors, and reviewers on l7c.ai. It is not legal advice. Questions: [email protected].

L7-HLP · 2026.08.22-10 · p. 9 / 9