Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: update devnet config for EC members #10251

Merged
merged 1 commit into from
Oct 11, 2024

Conversation

rabi-siddique
Copy link
Contributor

@rabi-siddique rabi-siddique commented Oct 10, 2024

refs: #10194

Description

The PR updates the DEVNET config in the builder script of replace electorate core eval, which is identical for all testnets. It includes the wallet address of the new EC committee member and adds this address to the high-priority senders list.

Scaling Considerations

n/a

Upgrade Considerations

out of scope of this PR; see an upcoming issue

Security / Documentation / Testing Considerations

These accounts are for testing. The usual key management considerations apply. The relevant private keys are shared on a need-to-know basis for testing.

@rabi-siddique rabi-siddique requested a review from a team as a code owner October 10, 2024 04:01
Copy link
Member

@dckc dckc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I need help reading this

voterAddresses: {
gov1: 'agoric1ldmtatp24qlllgxmrsjzcpe20fvlkp448zcuce',
gov2: 'agoric140dmkrz2e42ergjj7gyvejhzmjzurvqeq82ang',
gov3: 'agoric1f0h5zgxyg3euxsqzs0506uj4cmu56y30pqx46s',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's gov4, isn't it?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, gov3 is actually gov4 in my sequential numbering. Sorry for any confusion! Do you suggest naming it gov4?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, please!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Comment on lines +64 to 65
addressesToAdd: ['agoric1f0h5zgxyg3euxsqzs0506uj4cmu56y30pqx46s'],
addressesToRemove: ['agoric1w8wktaur4zf8qmmtn3n7x3r0jhsjkjntcm3u6h'],
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how do we remove ...u6h? I don't see it listed in voterAddresses.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The voterAddresses map includes the addresses that will be invited to join the new committee and charter. The lists addressesToAdd and addressesToRemove are linked to highPrioritySenders. The new member ...x46s, has been added to addressesToAdd. An outgoing member from the previous committee, ...u6h, has been placed in addressesToRemove.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok... I recognize ...u6h as gov3 now, and I see it's in the devnet highPrioritySenders.

@dckc
Copy link
Member

dckc commented Oct 10, 2024

Again, this can't be in service to #10209 ; that issue is for post code complete testing; that is: stuff that happens after all git commits.

I think the relevant issue here is:

@rabi-siddique
Copy link
Contributor Author

rabi-siddique commented Oct 11, 2024

Again, this can't be in service to #10209 ; that issue is for post code complete testing; that is: stuff that happens after all git commits.

I think the relevant issue here is:

@dckc Made the update in PR description.

@rabi-siddique rabi-siddique requested a review from dckc October 11, 2024 11:49
Copy link

cloudflare-workers-and-pages bot commented Oct 11, 2024

Deploying agoric-sdk with  Cloudflare Pages  Cloudflare Pages

Latest commit: 7a4395b
Status: ✅  Deploy successful!
Preview URL: https://e1bbb074.agoric-sdk.pages.dev
Branch Preview URL: https://rs-update-replaceelectorate.agoric-sdk.pages.dev

View logs

@dckc
Copy link
Member

dckc commented Oct 11, 2024

Upgrade considerations are actually non-trivial. I think we're running this core-eval as part of a chain-halting upgrade, so we need to make sure it's hooked into the go upgrade handler. IOU an issue, I suppose. I suggest changing "n/a" to "out of scope of this PR; see an upcoming issue".

I suggest combining Security Considerations, Documentation Considerations and Testing Considerations into one section:

Security / Documentation / Testing Considerations

These accounts are for testing. The usual key management considerations apply. The relevant private keys are shared on a need-to-know basis for testing.

Copy link
Member

@dckc dckc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good, presuming an update to the PR description

@rabi-siddique rabi-siddique force-pushed the rs-update-replaceElectorate-config branch from 831ab04 to a97a07d Compare October 11, 2024 12:55
@rabi-siddique rabi-siddique added the automerge:rebase Automatically rebase updates, then merge label Oct 11, 2024
@rabi-siddique rabi-siddique force-pushed the rs-update-replaceElectorate-config branch from a97a07d to 7a4395b Compare October 11, 2024 13:11
@mergify mergify bot merged commit 9ede17d into master Oct 11, 2024
80 checks passed
@mergify mergify bot deleted the rs-update-replaceElectorate-config branch October 11, 2024 13:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge:rebase Automatically rebase updates, then merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants