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

Method in the Gateway to adopt and return the last accumulated validator set #208

Closed
Tracked by #211
aakoshh opened this issue Sep 7, 2023 · 1 comment
Closed
Tracked by #211
Assignees

Comments

@aakoshh
Copy link
Contributor

aakoshh commented Sep 7, 2023

As the Fendermint interpreter, during the checkpointing period I want to hand cross messages to the Gateway and expect it to accumulate validator set changes without adopting them immediately.

At the end of the checkpointing period, I want to call a method on the Gateway which returns to me the next validator set to adopt in the upcoming blocks, that is, the last finalized validator set in the parent, including its Configuration Number and the power table. I want the contract to remember and adopt this as the current validator set from now on.

@dnkolegov dnkolegov changed the title Method in the Gateway to adopt and return the last accumulated validator Method in the Gateway to adopt and return the last accumulated validator set Sep 13, 2023
@dnkolegov
Copy link
Contributor

dnkolegov commented Sep 15, 2023

Implemented here - https://github.com/consensus-shipyard/ipc-solidity-actors/tree/membership

You can use

  • newMembership(uint64 n, FvmAddress[] memory validators, uint256[] memory weights) to adopt a new membership (validator set) explicitly under SYSTEM actor privileges if needed
  • commitParentFinality(ParentFinality calldata finality, uint64 n, FvmAddress[] calldata validators, uint256[] calldata weights to adopt a new membership along with a parent finality message under SYSTEM actor
  • getLastMembership to return the last adopted membership

@jsoares jsoares transferred this issue from consensus-shipyard/fendermint Dec 19, 2023
@jsoares jsoares closed this as not planned Won't fix, can't repro, duplicate, stale Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants