Create the canonical chain adapter interface and registration lifecycle for the whole platform so a new chain enters through one agreed abstraction rather than through feature-by-feature code edits. The contract must define what an adapter must expose for capability support, discovery, execution requirements, asset support, and health signals. Acceptance notes: onboarding docs and code should make it clear that new chains are introduced by implementing this SPI plus registration, not by rewriting feature code.
Imported from backlog CSV.
Project metadata:
- Lane: Provider Platform
- Feature: Chain Onboarding
- EstimateDays: 1
- Status: Backlog
- Priority: High
- Repository: execution-layer
- Labels: multi-chain,adapters,spi
- Source CSV row: 10
Create the canonical chain adapter interface and registration lifecycle for the whole platform so a new chain enters through one agreed abstraction rather than through feature-by-feature code edits. The contract must define what an adapter must expose for capability support, discovery, execution requirements, asset support, and health signals. Acceptance notes: onboarding docs and code should make it clear that new chains are introduced by implementing this SPI plus registration, not by rewriting feature code.
Imported from backlog CSV.
Project metadata: