Substreams running without a specific tier2 (with default substreams-client-endpoint=<empty>) will now expose tier2 service sf.substreams.internal.v2.Substreams so it can be used internally.
CHANGED
flag substreams-client-endpoint now defaults to empty string, which will make a 'tier1' service act also as a 'tier2', serving its own requests. Make sure that you don't expose sf.substreams.internal.v2.Substreams to the public, via an HTTP-aware firewall.
flag substreams-partial-mode-enabled renamed to substreams-tier2
FIXED
substreams-client-endpoint=<empty>
) will now expose tier2 servicesf.substreams.internal.v2.Substreams
so it can be used internally.CHANGED
substreams-client-endpoint
now defaults to empty string, which will make a 'tier1' service act also as a 'tier2', serving its own requests. Make sure that you don't exposesf.substreams.internal.v2.Substreams
to the public, via an HTTP-aware firewall.substreams-partial-mode-enabled
renamed tosubstreams-tier2