Polymarket moves blockchain indexing in-house, citing faster onchain data for trades and balances

Polymarket has moved its primary blockchain indexing infrastructure in-house, a change its vice president of engineering said lets the prediction market platform surface some onchain events up to 14 blocks — roughly 28 seconds — faster than before.

Josh Stevens announced the change in a post on X dated September 15, 2026, writing that Polymarket had “built our Polymarket indexing systems in-house, powered by rindexer in Rust.”

What Polymarket says changed

According to Stevens, the internally operated system can index data within 0 to 10 milliseconds of a block being broadcast. “We now see onchain data events up to 14 blocks (28 seconds) faster, and we index within 0-10ms of block broadcasting, making it nearly instant,” he wrote, adding that the change means “trades, positions, and balances will update much faster.”

The performance figures are Stevens’s own characterization of the new infrastructure; Polymarket has not published independent benchmarks alongside the announcement.

The announcement also reshapes Polymarket’s relationship with Goldsky, a blockchain data infrastructure provider. Stevens said Polymarket “will use Goldsky as a data backup, but we now primarily run on our own indexing infrastructure.” According to reporting by crypto.news, Goldsky previously handled important parts of the platform’s real-time blockchain data pipeline.

Why indexing speed matters for a trading platform

Blockchains record activity in sequential blocks of transactions, but raw chain data is not organized in a way applications can query efficiently. Indexing software solves that problem: it reads onchain events as blocks are produced and organizes them into structured data that an application can retrieve quickly.

For a prediction market, the indexed information includes the data behind trades, user positions and balances. The gap between an event being confirmed onchain and that event appearing in the platform’s interface is therefore a direct function of indexing latency. Stevens’s claim is that the in-house system shrinks that gap to near zero — within 0 to 10 milliseconds of a block broadcast, by his account — compared with a previous lag of up to roughly 28 seconds on some events.

About rindexer

The tool at the center of the shift is rindexer, an open-source indexing toolset written in the Rust programming language. According to its project repository on GitHub, rindexer is designed for compatibility with any EVM chain — the family of blockchains compatible with the Ethereum Virtual Machine — and allows developers to index chain events using a YAML configuration file “requiring no additional coding” for basic deployments.

The repository describes the tool as extendable for more advanced needs, enabling developers to build custom indexing pipelines, and says it provides a built-in GraphQL API for querying indexed data. It also supports custom chains by adding an RPC URL and chain ID to the configuration file, with no code changes required, and offers Docker images and a Helm chart for deployment in containerized and Kubernetes environments.

Stevens’s post did not detail how Polymarket configured or extended rindexer for its production systems, nor did it specify which chains or contracts the in-house indexer covers.

What remains outside the announcement

The September 15 statement addresses infrastructure rather than any change to Polymarket’s products, fees or market offerings. It does not announce new markets or features for users; the practical effect Stevens described is faster updating of the trade, position and balance data the platform already displays.

Whether the claimed latency improvements hold under heavy trading load, and how the in-house stack performs relative to the backup arrangement with Goldsky over time, remain to be seen. Polymarket has not published technical documentation of the deployment beyond Stevens’s post.