Skip to content

Add a numeric chain-id validation scheme as an alternative to free-text src_chain #133

Description

@james2177

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

  1. Fork the repo and create a branch
    git checkout -b docs/chain-id-vs-string-comparison
    
  2. Prototype the chain-ID approach and compare ergonomics against the string enum
  3. 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)

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programcross-chainCross-chain integration workhigh (200 pts)Drips Wave complexity: high, 200 points

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions