kyle

gmonad

Docs: docs.monad.xyz/reference/mpp/… If you’re working on something ambitious with payments on Monad, DM me.

Monad now supports the Machine Payments Protocol through our TypeScript SDK. MPP is an open protocol for agentic payments. Charge for API requests, tool calls, or content with a few lines of code.

v0.14.0 of the Monad client has been released. This update includes several key user-facing improvements and bug fixes: - [Feat] Adds a new RPC endpoint eth_fillTransaction that takes an unsigned, partially filled transaction object and returns it with all missing fields populated, ready for signing and broadcasting. - [Perf][Behavioral] eth_getTransactionReceipt and eth_getBlockReceipts are now available at "Proposed" time, making the responses ~400s faster. - [Perf] eth_getLogs calls return faster for recent blocks that are still in memory. - [Perf][Behavioral] newHeads and logs subscriptions (EVM spec) now notify on "Proposed" blocks instead of "Voted", aligning with monadNewHeads and monadLogs. - [Fix] Blocktags in eth_getLogs are fixed. Previously, all of them resolved to the latest block. Now, they resolve to their correct statuses.

Monad is adding support for eth_fillTransaction soon. Without it, you need separate RPC calls for nonce (eth_getTransactionCount), gas limit (eth_estimateGas), and fee params (eth_gasPrice / eth_maxPriorityFeePerGas). eth_fillTransaction collapses that into one call and returns a fully populated unsigned tx ready to sign externally. viem already calls eth_fillTransaction when the node supports it, so this is a free speedup for every viem user on Monad.

Apps using Monad will all get 400 ms faster after MONAD_NINE hard fork (scheduled 3/19). The JSON-RPC behavior changed to use the "proposed" block state, meaning requests read from an earlier block instead of waiting on consensus.

Big news: the Ponder team has joined the Monad Foundation. We’re excited to contribute open-source tooling and standards that help applications take full advantage of Monad's performance and decentralization.

keep building

Today's Ponder release introduces a new indexing mode where each chain runs on a separate worker thread. The new design offers big benefits across indexing & query performance, and paves the way for better caching, reliability, and DX.

Ponder 0.14 → * We redesigned every log line that Ponder emits * Custom database views * Offset pagination in GraphQL * Better performance & reliability across the board

@_jxom Mostly improvements related to the cursor and handling hex vs bytes. This benchmark does do a checksum on the addresses, even though Ponder skips checksums as of the last minor version

@kyscott18 Faster keccak and/or no checksum address?

Latest version of Ponder is faster because of performance improvements in decodeAbiParameters

Ponder now supports WebSockets (eth_subscribe) for new block notifications. Opt-in to improve realtime indexing latency by ~35% and consume fewer RPC credits. S/o @opaquefeldspar for the excellent work on this.

Full blog here: ponder.sh/blog/performan…

Ponder has gotten much faster in the past few months. With features like RPC request speculation and in-memory database logic, we're making progress towards processing 100,000 events per second. Check out our latest blog for the technical details and what's next.

Introducing Marble. Marble is a platform for offchain software, built by the team behind Ponder. We're making it radically easier to build fast & reliable backend systems for crypto apps.

Ponder 0.11 → We shipped a new docs website, made it easier to query Ponder tables directly in Postgres, and eliminated a bunch of RPC endpoint footguns.

Created a new Ponder chat (link below) that includes the full history from the old chat. Come say hi!

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