feat: add Flare protocols and a stream timeout override - #440
Open
tuddman wants to merge 3 commits into
Open
Conversation
BlazeSwap V2 pools simulate as UniswapV2State; SparkDEX V3 and Enosys V3 as UniswapV3State (logs-only indexing). Without these arms the stream builder warn-skips the protocols a self-hosted Flare Tycho indexes.
tycho-client derives the stream timeout from the chain's block time (3x block time for custom-registry chains), which is too tight for indexers that pause during catch-up bursts: flare's 2s blocks derive a 6s timeout that trips missed-block stream errors while the self-hosted indexer backfills. The flag (FYND_STREAM_TIMEOUT_SECS) threads through FyndRPCBuilder/FyndBuilder/TychoFeedConfig to the stream builder's latency_buffer and leaves the derived default in place when unset.
feat: add Flare protocols and a stream timeout override
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds three match arms to
fynd-core/src/feed/protocol_registry.rsso Fynd canserve quotes on Flare (chain id 14) against a self-hosted Tycho indexer:
blazeswap_v2→UniswapV2Statesparkdex_v3→UniswapV3Stateenosys_v3→UniswapV3StateAll three are Uniswap V2/V3 forks. They index on Flare with the existing
ethereum-uniswap-v2andethereum-uniswap-v3-logs-onlysubstreams packages(logs-only, since Flare has no Firehose-instrumented client and runs on the
RPC-poller block model). Factory addresses, verified on-chain:
0x440602f4…e2A60x8A2578d2…E6520x17AA157A…f0deWhy
We run the self-hosted setup from the docs
(
for-solvers/self-hosted-evm-chain) with Flare as a registry-defined customchain via
--chains-config. Indexing works with per-chain manifests of theexisting packages, but
register_exchangeswarn-skips protocol names it doesnot know, so the streamed components never reach the stream builder without
these arms.
Notes
quickswap_v2. No behavior change for any existing chain or protocol; theunknown-protocol fallback is untouched.
registry; these arms only map protocol names to existing simulation states.
protocols;
check.shpasses on the touched crate.