Modeling marketplaces

Tokens and provenance can describe catalog items, batches, ownership, and transformation history. Model listings, offers, escrow, settlement, and expiration as separate state machines with explicit IDs and terminal states. Counters and availability need bounded, merge-safe operations; do not treat a client-side balance check as custody.

For real value, identity, authorization, double-spend prevention, disputes, fees, and final settlement require a trusted service or external ledger. HyperToken's relay is unauthenticated, and CRDT convergence does not establish legal ownership or honest authorship. Use a server-authoritative Engine for admission and settlement, retaining CRDT state for replay or offline drafts if that boundary is useful.

This model is appropriate for game economies, simulations, and auditable prototypes. It is inappropriate as a standalone financial marketplace.