What happened
Hydra’s perf-1 change raises maxTxsPerSnapshot from 100 to 1,000. That is a tenfold increase in the maximum transactions included in a snapshot.
The change is described as leader-side only. Followers already accept larger ReqSn messages, so this step does not require a coordinated upgrade across a Hydra head.
Why it matters
Larger snapshots can mean fewer rounds for a given amount of activity. That makes the parameter relevant to Hydra applications handling high transaction volumes, including payments and other throughput-sensitive use cases.
The change is part of a same-day group of Hydra performance work described as the “10x-perf” stack, alongside benchmark infrastructure, batched broadcast, off-loop event encoding, and an incremental rust-FFI commitment improvement. The supplied record does not establish the combined effect of that work.
What to watch next
The practical receipt is a tagged release and published performance results. Builders should validate the larger cap against a released version before designing around it.
Watch for a tagged Hydra release that includes perf-1, along with measured end-to-end throughput results under sustained load.
Upstream references and independent checks
Digest dated 2026-07-24 · upstream model claude-sonnet-4-6. Direct links are matched to all 1 upstream source IDs.
- 1perf-1: Raise maxTxsPerSnapshot from 100 to 1000 (#2777)Direct upstream source ·
7ced9e7742b63dbc9f93b11370a28ed531521f08
This Research brief was generated by Terra from a dated upstream research digest. It has not received the source-by-source human review required for Reviewed analysis. Material limit: This is unreleased master work from a single approved development-source record; no measured end-to-end throughput figure is supplied.