v2.0.4

Substreams

• Fix an issue preventing proper detection of gzip compression when multiple headers are set (ex: python grpc client)
• Fix an issue preventing some tier2 requests on last-stage from correctly generating stores. This could lead to some missing "backfilling" jobs and slower time to first block on reconnection.
• Fix a thread leak on cursor resolution resulting in bad counter for active connections
• Add support for zstd encoding on server

v1.5.9

Substreams

• Fix an issue preventing proper detection of gzip compression when multiple headers are set (ex: python grpc client)
• Fix an issue preventing some tier2 requests on last-stage from correctly generating stores. This could lead to some missing "backfilling" jobs and slower time to first block on reconnection.
• Fix a thread leak on cursor resolution resulting in bad counter for active connections
• Add support for zstd encoding on server

v2.0.3

v2.0.3

Note

This release will reject connections from clients that don't support GZIP compression. Use --substreams-tier1-enforce-compression=false to keep previous behavior, then check the logs for incoming Substreams Blocks request logs with the value compressed: false to track users who are not using compressed HTTP connections.

• Substreams: add --substreams-tier1-enforce-compression to reject connections from clients that do not support GZIP compression
• Substreams performance: reduced the number of mallocs (patching some third-party libraries)
• Substreams performance: removed heavy tracing (that wasn't exposed to the client)
• Fixed reader-node-line-buffer-size flag that was not being respected in reader-node-stdin app
• firehose-grpc-listen-addr and substreams-tier1-grpc-listen-addr flags now accepts comma-separated addresses (allows listening as plaintext and snakeoil-ssl at the same time or on specific ip addresses)
• removed old RegisterServiceExtension implementation (not used anywhere anymore)

v1.5.8

v1.5.8

Note

This release will reject connections from clients that don't support GZIP compression. Use --substreams-tier1-enforce-compression=false to keep previous behavior, then check the logs for incoming Substreams Blocks request logs with the value compressed: false to track users who are not using compressed HTTP connections.

• Substreams: add --substreams-tier1-enforce-compression to reject connections from clients that do not support GZIP compression
• Substreams performance: reduced the number of mallocs (patching some third-party libraries)
• Substreams performance: removed heavy tracing (that wasn't exposed to the client)
• Fixed reader-node-line-buffer-size flag that was not being respected in reader-node-stdin app
• firehose-grpc-listen-addr and substreams-tier1-grpc-listen-addr flags now accepts comma-separated addresses (allows listening as plaintext and snakeoil-ssl at the same time or on specific ip addresses)
• removed old RegisterServiceExtension implementation (not used anywhere anymore)

v2.0.2

Substreams

• Include outputModuleHash in metering events.

v1.5.7

Substreams

• Include outputModuleHash in metering events.

v2.0.1

What's Changed

• create README.md to fix substreams.yaml by @fschoell in #162
• update readme by @fschoell in #163
• fix int overflow in ReadByteArray() by @fschoell in #164

Full Changelog: v1.5.5...v2.0.1

v1.5.6

What's Changed

• create README.md to fix substreams.yaml by @fschoell in #162
• update readme by @fschoell in #163
• fix int overflow in ReadByteArray() by @fschoell in #164

Full Changelog: v1.5.5...v1.5.6

v2.0.0

v2.0.0

Production release for Antelope Spring nodes. For Antelope Leap please stay on the v1 releases.

v2.0.0-rc.9

Substreams fixes

Note All caches for stores using the updatePolicy set_sum (added in substreams v1.7.0) and modules that depend on them will need to be deleted, since they may contain bad data.

• Fix bad data in stores using set_sum policy: squashing of store segments incorrectly "summed" some values that should have been "set" if the last event for a key on this segment was a "sum"
• Fix small bug making some requests in development-mode slow to start (when starting close to the module initialBlock with a store that doesn't start on a boundary)