Ponder

Ponder 0.10

This release speeds up large factories and contract reads, adds a new `event­.id` property, and fixes several reliability issues →

Ponder's factory pattern collects a list of addresses from decoded event logs, then plugs that list anywhere in your config.

Before this release, the address list was built on-the-fly and filtering ran in SQL. This didn't scale well.

Building ponder.sh. EVM, TypeScript, open-source enjoyer.

The new `event.­id` property is a globally unique ID for a log, transaction, block, or trace that works across all chains.

For tables that don't have a logical unique constraint, `event.­id` is a good option for primary key values.

We also improved the behavior around a common RPC provider bug where eth_call requests incorrectly return `0x` near tip. While this is a "success" response, it's best to retry it a few times.

The latest addition to a long list of RPC quirks we've found and handled.

Before you upgrade, *please* read the migration guide. This release includes a database migration to the `ponder_sync` schema that can lead to downtime.

That's it - enjoy!

Migration guide: https://ponder.sh/docs/migration-guide#010
GitHub: https://github.com/ponder-sh/ponder
Chat: https://t.me/ponder_sh

In 0.10, filtering runs entirely in-memory, with the address list cached in the database to avoid refetching.

Our Uniswap V3 factory benchmark got 3.6x faster with this release. Now, there's ~zero overhead to indexing huge factories - very happy with where we landed.