v0.5.0

• Bumped substreams to v0.11.1

v0.4.2

• Bumped substreams to v1.10.3
• Add support for new manifest attributes like 'protobuf.excludePaths'

v0.4.1

• Add NoopMode, enables to avoid live processing while requesting tier1.

v0.4.0

• Bumped substreams to v1.7.3
• Enable gzip compression on substreams data on the wire

v0.3.5

• Fix another case where 'infinite-retry' would not work and the program would stop on an error.
• Enable multiple substreams authentication methods (API key, JWT), using flags --api-key-envvar and --api-token-envvar.
• Deprecates the use of SF_API_TOKEN environment variable, now use default SUBSTREAMS_API_TOKEN or set your own using --api-token-envvar

v0.3.4

• Fixed spurious error reporting when the sinker is terminating or has been canceled.

• Updated substreams dependency to latest version v1.3.7.

v0.3.3

• Improved substreams stream stats log line but now using substreams_sink_progress_message_total_processed_blocks for progress_block_rate replacing the progress_msg_rate which wasn't meaningful anymore (and broken because the metric was never updated).

• Fixed a crash when providing a single block argument for block range if it's the same as the Substreams' start block.

• Added --network flag and handling proper handling.

v0.3.2

• It's now possible to define on your handler the method HandleBlockRangeCompletion(ctx context.Context, cursor *sink.Cursor) error which will be called back when the sink.Sinker instance fully completed the request block range (infinite streaming or terminate because of an error does not trigger it).

v0.3.1

Substreams Progress Messages

• Bumped substreams to v1.1.12 to support the new progress message format. Progression now relates to stages instead of modules. You can get stage information using the substreams info command starting at version v1.1.12.

Changed Prometheus Metrics

• substreams_sink_progress_message removed in favor of substreams_sink_progress_message_total_processed_blocks
• substreams_sink_progress_message_last_end_block removed in favor of substreams_sink_progress_message_last_block (per stage)

Added Prometheus Metrics

• added substreams_sink_progress_message_last_contiguous_block (per stage)
• added substreams_sink_progress_message_running_jobs(per stage)

Other changes

• Added manifest path in error message when failing to read it.
• When back off limit expires, the returned error now also contains the last retryable error unwrapped received.

v0.3.0

Changed

CLI

• Breaking Flag shorthand -p for --plaintext has been re-assigned to Substreams params definition, to align with substreams run/gui on that aspect. There is no shorthand anymore for --plaintext.

  If you were using before -p, please convert to --plaintext.

  Note We expect that this is affecting very few users as --plaintext is usually used only on developers machine.

Library

• gRPC InvalidArgument error(s) are not retried anymore like specifying and invalid start block or argument in your request.

• Breaking ReadManifestAndModule signature changed to add params []string, this is required for proper computation of module's output hash, upgrade by passing nil for this parameter.

• Breaking ReadManifestAndModuleAndBlockRange signature changed to add params []string, this is required for proper computation of module's output hash, upgrade by passing nil for this parameter.

Added

• Added support for --params, -p (can be repeated multiple times) on the form -p <module>=<value>.

• Added logging of new Session received values (linear_handoff_block, max_parallel_workers and resolved_start_block).

• Added --header, -H (can be repeated multiple times) flag to pass extra headers to the server.

• Added ClientConfig on sink.Sinker instance to retrieve Substreams client configuration easily.

• Added ReadManifestAndModuleAndBlockRange as a convenience for ReadManifestAndModule and ReadBlockRange.

• Added ReadBlockRange so that it's possible to easily read a block range argument against a Substreams parsed module.

Fixed

• The stop_block for infinite streaming passed to the server is now 0, it seems MaxUint64 was causing some issues on the server, should result normally in better startup performance now.