ChainRoute-Forge

ChainRoute-Forge

Anchor provenance chains on Polygon in 127 bytes. No smart contracts. No tokens. Just data.

Try the ProtocolVerify a Chain

The 127-byte payload

Genesis Hash
32 B
Prev Hash
32 B
Arweave ID
43 B
Delegate
20 B
Genesis Hash — Chain root ID (zeros for genesis tx)
Prev Hash — Previous Polygon tx hash
Arweave ID — Permanent JSON blob on Arweave
Delegate — Next authorized signer address

Total: 127 bytes stored in the data field of a zero-value Polygon tx

How it works

1

Genesis

Create the root anchor. A zero-value transaction to yourself with the 127-byte payload. The tx hash becomes the chain's unique ID.

2

Chain Events

Each new anchor references the genesis hash and the previous tx hash, forming an immutable linked chain on Polygon.

3

Delegate

Every anchor names the next authorized signer. Pass signing authority to another wallet for multi-party provenance.

Arweave data layer

The 43-byte arweaveId field links each anchor to a permanent JSON blob on Arweave containing event metadata, timestamps, and references to support files (images, PDFs, etc). Arweave provides the immutable data storage that complements Polygon's immutable chaining — together they form the two pillars of ChainRoute. The demo below lets you explore the chaining protocol without needing AR tokens.

See a real chain verified on Polygon Mainnet:

Verify the HypotheticalPainting example