Powered byTroptions
Donkai · LPS-1 · xxxiii.io
Author IP · Verification

LPS-1 Edition Verification

Five-layer provenance stack

  1. Source files — canonical order in order.json
  2. Git history — reproducible build context (optional for verify)
  3. SHA-256 hashing — CRLF-normalized content hashes
  4. Merkle trees — four category roots → edition root
  5. IPFS + chain anchor — CID pin and optional contract record

Edition root definition

editionRoot = SHA-256(manuscriptRoot + artifactRoot + imageRoot + promptRoot)

Concatenation order is fixed. Any file change in any category produces a different edition root.

Five smart contracts

LiteraryAnchor.solProof-of-origin anchor
PublishingKernel.solEdition management, Merkle roots, licenses
PublishingKernelV2.solECDSA enforcement, timelock, freeze
RoyaltyRouter.solRevenue splits, recoupment waterfall
AuthorIdentity.solIdentity declaration, bibliography

Verification procedure

  1. Clone the reference repository and install dependencies (npm install).
  2. Obtain the edition source files (or use bundled example-work/).
  3. Run the deterministic pipeline: npm run build (compile → hash → merkle → manifest).
  4. Run the independent verifier against the work directory.
  5. Compare computed edition root to the published/on-chain record.
git clone https://github.com/FTHTrading/LPS-1-Reference-Implementation.git cd LPS-1-Reference-Implementation npm install npm run build npm run verify # or: node verifier/cli.js --path example-work

The verifier checks: file hashes match recorded values; Merkle roots recompute; edition root matches; compiled manuscript hash matches; all Merkle proofs verify.

GMIIE integration

Published intelligence on xxxiii.io registers LPS-1 metadata on the Authors provenance stack and the XXXIII property registry. Full per-article Polygon anchoring is PARTIAL — page-level SHA-256 and IPFS snapshots are live today.

Powered byTroptions