Add rebased Aptos CRE common and loop support#1896
Conversation
(cherry picked from commit 8aa26f1)
(cherry picked from commit 331a1e5)
…op adapters (cherry picked from commit ffa37f1)
(cherry picked from commit 7fda75d)
(cherry picked from commit d263db3)
(cherry picked from commit 7e47b5e)
(cherry picked from commit 13d99da)
(cherry picked from commit 7f43bb2)
(cherry picked from commit 1a13fdc)
(cherry picked from commit e835cb9)
(cherry picked from commit a2589e6)
(cherry picked from commit c991b6f)
(cherry picked from commit 7a83532)
(cherry picked from commit ca31c54)
(cherry picked from commit 79d6350)
(cherry picked from commit f59b6dc)
(cherry picked from commit 1eac473)
|
Summary
What changed
LedgerVersionsupport used by the Aptos read flowWhy
The Aptos local CRE stack needs the common Aptos loop/service surface from the earlier read-capability work, plus the shared compatibility pieces consumed by the write path. This PR keeps that layer narrow so downstream repos do not need to reach around
chainlink-common.Testing
go test ./pkg/types/chains/aptos ./pkg/loop/internal/relayer ./pkg/loop/internal/relayerset ./pkg/loop/internal/core/services/capability -count=1