MARKETPLACE
Each collection is an append-only, hash-chained, signature-sealed ledger — verifiable by anyone, anchored on-chain when you choose.
A game item used to be a row in a database an operator could quietly edit. Now it is an append-only event chain whose history cannot be rewritten without visibly breaking the hashes downstream.
Legacy · before
Now · live in dev
A collection is a per-collection, append-only chain of events — Mint, Transfer, Burn and the rest. Each event carries a BLAKE3 hash of the one before it and a server signature in a crypto-agile envelope, so the whole history is verifiable without a blockchain and without gas.
01 · Event chain
An item’s life is a sequence of events appended to its collection’s chain. Nothing is mutated in place; a correction is a new event, so the full provenance is always present.
Mechanism: append-only per-collection event log.
02 · Hash linkage
Every event includes a BLAKE3 hash of its predecessor, chaining them together. Altering any past event changes its hash and breaks every hash that follows — visibly, not silently.
Mechanism: BLAKE3 hash of the previous event.
03 · Signed envelope
Each event is signed in a crypto-agile envelope (a hybrid with ML-DSA-65), and the collection’s genesis page anchors the minimum trusted scheme — so signatures can be strengthened without losing verifiability or being negotiated down.
Mechanism: hybrid signature + genesis trust-anchor.
This is the same hash-chain mechanic the asset-ledger runs on. Tamper with any block and watch every downstream hash break — the tamper-evidence is structural, not a claim. Reset to restore the chain.
↑ Click any block (except genesis) to tamper. Downstream hashes break — visibly.
Identical to the engine audit chain — tamper-evidence you can trigger.
Buying and selling items settles the money side on the exchange ledger through the same two-phase escrow as P2P — a hold that releases or refunds, never both. This is in build.
01 · Escrow settlement
A trade places the funds in a pending escrow transfer on the exchange ledger; it posts to the seller on completion or refunds the buyer on cancellation — the same single-resolution guarantee P2P uses.
02 · Provenance follows
On settlement, the item’s Transfer event is appended to its collection chain and signed — so the new owner is recorded in the same verifiable history, not a separate ledger that could drift.
A Game SDK lets a studio move items between a player’s marketplace inventory and the game itself — issuing, returning and reading items — against the same verifiable asset-ledger. This is in build.
01 · Items in and out
A studio can move an item from the player’s inventory into the game and back, with each movement recorded as a signed event on the collection chain rather than a private side-record.
02 · Read the provenance
The SDK lets a game read an item’s provenance from the asset-ledger, so the game can trust what a player owns without taking the marketplace’s word for it.
For collections that want a public checkpoint, a later option anchors the collection’s Merkle root on-chain (ERC-721) — a published commitment to the off-chain history, without paying gas on every single trade. This is planned.
01 · Merkle-root anchor
The collection’s Merkle root can be published on-chain as a tamper-proof checkpoint of its history — one anchor for the whole collection, rather than gas on every transfer.
02 · Opt-in ERC-721
The anchor is opt-in for collections that need a public, on-chain reference point — the verifiable ledger stands on its own, and the anchor adds a blockchain hook on top.
How this differs from NFTs, whether the exchange can edit your item, what trading costs, and what the Game SDK actually does.
It is a centralized registry with cryptographic verifiability rather than a public blockchain. Items live on an append-only, hash-chained, server-signed asset-ledger that anyone can verify — so you get provable provenance and tamper-evidence without paying gas per trade. An on-chain anchor (ERC-721) is an option for collections that want a public reference point, not a requirement.
No — not without it showing. Each event hashes the previous one, so altering any past record changes its hash and breaks every hash that follows. Run the verifier over the collection chain and a tamper shows up as a broken cascade. The demo on this page lets you trigger exactly that.
No. The asset-ledger is off-chain, so appending events and trading items costs no gas. The only time a blockchain is involved is the optional on-chain anchor, where a collection’s Merkle root is published as a single checkpoint — not a per-trade fee.
It lets a studio move items between a player’s marketplace inventory and the game — issuing items into the game and returning them — and read an item’s verifiable provenance from the asset-ledger. Each movement is recorded as a signed event on the collection chain, so a game can trust what a player owns without trusting the marketplace blindly.
The asset-ledger borrows the platform’s signatures and settlement: post-quantum covers the crypto, P2P the escrow, and transparency the proof.