feat(config): expand pool registry to 76 mainnet pools + Eden/Rsync builders#121
Merged
Merged
Conversation
…ync builders WS-1.6 / WS-1.7 partial — implements the config-only half of #71. Pool registry: 3 → 76 curated high-TVL Ethereum mainnet pools tiered hot/warm/cold across all 6 supported protocols (UniV2, UniV3, Sushi, Curve, Balancer V2, Bancor V3). Auto-population to the full 5,000+ target tracked separately in #120 (discovery pipeline + per-builder Prometheus metrics). Builders: add Eden + Rsync to builders.yaml using the existing api_key auth pattern. Default to auth_type "none" so executor startup stays clean for default deployments — operators flip to api_key + set EDEN_API_KEY / RSYNC_API_KEY in .env to activate. Tests: relax engine bootstrap_pools assertion from exact-3 to >=3 (anchor USDC/WETH pools) so the test stays robust as pools.toml grows. Update internal/config builders test to expect the four configured builders. Refs: #71, #120
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
Closes part of #71. Splits the code-level refactor into #120.
Summary
config/pools.toml): 3 → 76 curated high-TVL Ethereum mainnet pools across all 6 supported protocols (UniV2, UniV3, Sushi, Curve, Balancer V2, Bancor V3), tiered hot/warm/cold. The original WS-1.6 target of 500+ is scoped down here to a manually-verifiable seed set; auto-population to the CLAUDE.md 5,000+ target is tracked in Pool discovery pipeline + per-builder Prometheus metrics #120 (on-chain discovery pipeline).config/builders.yaml): add Eden + Rsync entries using the existingapi_keyauth pattern. They default toauth_type: "none"so executor startup stays clean for default deployments. Operators setEDEN_API_KEY/RSYNC_API_KEYin.envand flipauth_type: "api_key"to activate..env.example: document the three optional builder API key vars.crates/grpc-server/src/engine.rs—bootstrap_poolstest relaxed from exact-3 to>= 3(anchor USDC/WETH pools), so it stays robust as pools.toml grows.internal/config/loader_test.go—TestLoadBuildersConfig_ValidFileupdated to expect the four configured builders.Why these scope decisions
The original #71 mixed config-only changes (deterministic, easy to review) with code-level changes (new discovery binary, per-builder Prometheus metrics with inclusion polling). This PR delivers the config half so the executor can fan out to four builders today and reads richer pool state. The code half landed in #120 for a focused review pass.
Test plan
cargo test -p aether-grpc-server --bin aether-rust— 83 passedgo test ./cmd/executor/... ./internal/config/... -race— all greenEDEN_API_KEY+RSYNC_API_KEYset, flip auth_type to api_key, verify fan-out reaches all 4 relays in stagingaether-rust, confirm RSS stays well below the 2 GB target (current 3-pool RSS is the floor)Out of scope (tracked elsewhere)