MARKETPLACE PROTOCOL
Infrastructure as an on-chain primitive.
How a resource order is expressed, constrained and settled — the mechanics beneath every market.
01 · ONE PRIMITIVE, NOT ONE MARKET
One primitive, not one market
Kronex is designed as an infrastructure marketplace rather than a marketplace for one specific resource. The network can support multiple specialized markets operating simultaneously.
02 · WHAT AN ORDER CARRIES
What an order carries
Orders can contain execution requirements instead of simply transferring value.
This transforms an ordinary transaction into a programmable infrastructure request.
03 · ANATOMY OF AN ORDER
Anatomy of an order
Eight fields, and the stage each one governs. Every field is a constraint on what the network may do next.
No field governs execution. The protocol coordinates it; a provider performs it off-chain.
04 · WHY ONE PRIMITIVE SERVES MANY MARKETS
Why one primitive serves many markets
The order carries no assumption about what is being bought. Resource is a field, not a type, so a new market needs new providers and new verification methods rather than a new chain. The protocol's job is to constrain, route and settle — none of which depends on the resource named.
05 · WHAT EXISTS TODAY
What exists today
The Kronex testnet settles ordinary value transfers and EVM contract calls. Programmable orders are not implemented, and nothing on this page is available on the chain running now.
Related