Description
As a more solver-bot-friendly alternative (or complement) to a string-based allowlist, consider validating src_chain against standard numeric chain IDs (e.g. EVM chain IDs), which are less ambiguous for programmatic matching than free-text names like "ethereum".
Requirements and context
- Weigh this against the string-based enum approach in the other src-chain issues -- these are alternative designs, not both meant to ship
Suggested execution
- Fork the repo and create a branch
git checkout -b docs/chain-id-vs-string-comparison
- Prototype the chain-ID approach and compare ergonomics against the string enum
- Bring the comparison back to whichever src-chain issue is picked up first for a final decision
Example commit message
feat: add a numeric chain-id validation scheme as an alternative t
Guidelines
- Assignment required before starting -- comment on the issue to claim it
- PR description must include:
Closes #<this issue's number>
- Complexity: High (200 points)
Description
As a more solver-bot-friendly alternative (or complement) to a string-based allowlist, consider validating src_chain against standard numeric chain IDs (e.g. EVM chain IDs), which are less ambiguous for programmatic matching than free-text names like "ethereum".
Requirements and context
Suggested execution
Example commit message
feat: add a numeric chain-id validation scheme as an alternative tGuidelines
Closes #<this issue's number>