Evolve the current execution-layer registration model from protocol-only registration toward a chain-aware, capability-aware registration contract that can support zero-rewrite onboarding. Keep the first slice narrow by defining the registration shape, storage model, and compatibility path from the current registerAdapter(protocolId, implementation) design. Acceptance notes: execution-layer registration should no longer assume that one protocol ID alone is enough to describe adapter ownership across future chains.
Imported from backlog CSV.
Project metadata:
- Lane: Execution Layer Contracts
- Feature: Adapter Registration
- EstimateDays: 1
- Status: Backlog
- Priority: High
- Repository: execution-layer
- Labels: contracts,registry,multi-chain
- Source CSV row: 13
Evolve the current execution-layer registration model from protocol-only registration toward a chain-aware, capability-aware registration contract that can support zero-rewrite onboarding. Keep the first slice narrow by defining the registration shape, storage model, and compatibility path from the current
registerAdapter(protocolId, implementation)design. Acceptance notes: execution-layer registration should no longer assume that one protocol ID alone is enough to describe adapter ownership across future chains.Imported from backlog CSV.
Project metadata: