Multi-chain configuration #7

New issue

Closed

opened 2026-08-03 04:10:52 +00:00 by scheerenkevin · 1 comment

scheerenkevin commented

2026-08-03 04:10:52 +00:00

(Migrated from github.com)

Why

KeeperOS operates across Base (primary), Ethereum, Arbitrum, Optimism, Polygon, BNB Chain, and Avalanche C-Chain, all via Alchemy RPC.

Scope

Chain registry: chain IDs + per-chain Alchemy RPC URL templates for Base, Ethereum, Arbitrum, Optimism, Polygon, BNB Chain, Avalanche C-Chain
Helper to build a chain-specific client/transport (bundler + gas manager URLs typically differ per chain in Alchemy's URL scheme)

Acceptance criteria

Chain enum/registry with the 7 target chains and correct chain IDs
Unit tests verify correct URL construction per chain (no live calls)

## Why KeeperOS operates across Base (primary), Ethereum, Arbitrum, Optimism, Polygon, BNB Chain, and Avalanche C-Chain, all via Alchemy RPC. ## Scope - Chain registry: chain IDs + per-chain Alchemy RPC URL templates for Base, Ethereum, Arbitrum, Optimism, Polygon, BNB Chain, Avalanche C-Chain - Helper to build a chain-specific client/transport (bundler + gas manager URLs typically differ per chain in Alchemy's URL scheme) ## Acceptance criteria - [ ] `Chain` enum/registry with the 7 target chains and correct chain IDs - [ ] Unit tests verify correct URL construction per chain (no live calls)

scheerenkevin commented

2026-08-03 04:34:07 +00:00

(Migrated from github.com)

Merged into develop via #17.

kevin added the

status: done

label

2026-08-05 11:43:20 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

kevin/alchemy-wallet-client#7

No description provided.

Rows
Columns