Polymarket is pushing ahead with a new Rust-based central limit order book, or CLOB, as part of its latest DeFi migration plan, according to Josh Stevens, the platform’s head of development. Stevens said the current CLOB sits at the center of many of the issues the team is dealing with, making the replacement a key technical priority.
The roadmap starts in October, when Polymarket plans to run a full end-to-end order lifecycle in a test environment. That scope includes trading, settlement, onchain interactions, the indexer, and engine notifications. In November, the team plans to mirror all production traffic to the new trading cluster and compare the results with the existing system, while also opening test access to market makers.
Stevens said Polymarket aims to finalize its cutover plan in November and complete two full rehearsals before the final switch. If development stays on track, the new system will then be released. He added that the migration is designed to minimize changes for market makers and developers: request and response interfaces are expected to stay the same, with only some additional fields and the deprecation of one field, and any deprecation will be announced in advance.
Polymarket is building a new Rust-based central limit order book, or CLOB, and has laid out the latest migration plan for Polymarket DeFi, according to Josh Stevens, the platform’s head of development.
Stevens said the existing CLOB is seen as the core source of many of the platform’s current problems.
October testing will cover the full order lifecycle
Under the plan, Polymarket will complete an end-to-end run in a test environment in October. The work will cover the full order lifecycle, including trading, settlement, onchain interactions, the indexer, and engine notifications.
November will bring production traffic mirroring and market-maker access
In November, the team plans to mirror all production traffic to the new trading cluster and compare the results with the current system. Test access will also be opened to market makers during that phase.
Cutover plan and rehearsals are scheduled before release
Stevens said the team expects to finalize the migration cutover plan in November and complete two full rehearsals before the live switch. If progress goes smoothly, the new system will be released after that.
Interfaces are expected to remain unchanged
He added that the migration is being designed to keep required changes for market makers and developers to a minimum. Request and response interfaces are expected to remain the same. The update may add some fields and deprecate one field, and any deprecation will be announced ahead of time.
This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan. Disclaimer:
The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.
Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.
