Replace Aptos addresses during DON setup #19060
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
friedemannf
requested review from
KodeyThomas,
asoliman92,
b-gopalswami,
dimkouv,
makramkd,
matYang and
winder
product-security-plaid-test
bot
requested review from
CL-Eric,
DimitriosNaikopoulos,
ajaskolski,
bytesizedroll,
giogam,
graham-chainlink,
jkongie and
securejavier
KodeyThomas
approved these changes
Aug 21, 2025
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Due to missing support in Operator UI, when submitting Aptos as a supported chain to JD, the nodes will currently only submit their account addresses, when for the DON config we actually need the public keys.
This adds a hardcoded mapping of some addresses -> pubkeys in order to set the correct values.
We have a potential fix for Operator UI ready here: smartcontractkit/operator-ui#105
Once that's been released we'll be able to use the correctly submitted public key instead.