v4 moved the matching engine into validator memory
v3 settled perpetual trades through Ethereum contracts while an operator ran the orderbook and matcher. v4 chose a dedicated Cosmos chain: short-term orders travel through validator memory, a proposer selects matches and consensus commits fills.
That does not place every pending order in permanent state. Node books can differ, and official slashing documentation identifies censorship, reordering and MEV without a protocol-level remedy. Anyone may run the open-source indexer or front end, while each hosted deployment retains access control.
