Typewriter is a fresh take on application-specific sequencing - the (technical) benefits of an appchain/L2, with less complexity, better composability, and fewer trust assumptions Once again, Kyle has cooked

Thanks! Got back to you on the forum. forum.monad.xyz/t/mip-16-jso…

Thanks - appreciate your bug reports / feature requests to ponder over the years 🫡

Good callout, trace_filter does indeed support fromAddress and toAddress filtering. But it still suffers from the same pagination issues as eth_getLogs. And yes, these methods require clients to maintain new indexes - more to share soon on the impl side

Latest benchmarks of the Monad implementation are roughly ~10-100ms for typical requests More benchmarks coming as we finalize the spec / API

Will follow up soon with an RPC URL you can test out For some applications, these methods could indeed eliminate the need for an indexer. But, they are also designed to make indexers faster, more efficient, and easier to build.

> an open standard that any EVM chain can adopt 🤷‍♂️

Very long indeed. Would love feedback to ensure the proposed API will satisfy their requirements. github.com/monad-crypto/MIPs…

End of an era

I was curious about this question too - here's a subset of popular etherscan-style API endpoints & which ones could be replaced by these methods. These methods can also probably be composed with other standard methods to replace more endpoints.

We’re looking for feedback from application developers, RPC providers, data analysts, and client developers working on other EVM chains – get in touch.

I’m particularly excited about traces and native transfers, which are prohibitively expensive to fetch and index over JSON-RPC today. With the proposed methods, developers can filter, join, and query these objects just like logs. PR: github.com/monad-crypto/MIPs…

Example: fetch every USDC transfer to an account, including the parent block timestamp. This returns the full transfer history (256 transfers spanning 68M blocks) in *one request* on an experimental Monad Mainnet endpoint.

These proposed methods address all of these limitations and more. Each request accepts a filter, related objects to include, fields to return, and an optional block range. The cursor pagination design is efficient, reorg-friendly, and eliminates “block range exceeded” errors.

Ethereum’s JSON-RPC standard has well-known limitations for reading chain history: - No filtering for txs and traces (only logs) - Field selection isn't supported - Native transfers are not available - N+1 requests to fetch related objects Discussion: forum.monad.xyz/t/draft-mip-…

Excited to propose five new JSON-RPC methods to fetch EVM blockchain history: blocks, transactions, logs, traces, and native transfers. These methods address longstanding Ethereum data problems at the protocol layer, through an open standard that any EVM chain can adopt.

I bet there's a clever way to solve this problem using clickhouse which gives you "perfect" prices (price of latest swap during or before target timestamp) at a reasonable cost. You might not need that, but if you did, worth checking out clickhouse!

clickhouse?

We indeed had a gap in maintenance earlier this year as we settled into our new roles, but we're back at it and did a release last week which fixed several bugs. github.com/ponder-sh/ponder/…