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

IPC: Set membership from information in the parent #235

Closed
adlrocha opened this issue Jul 20, 2023 · 1 comment
Closed

IPC: Set membership from information in the parent #235

adlrocha opened this issue Jul 20, 2023 · 1 comment
Assignees

Comments

@adlrocha
Copy link
Contributor

adlrocha commented Jul 20, 2023

Related to #237
Probably depends on #236

In order for IPC actors to have information about the membership set on-chain, every time a reconfiguration is triggered by Fendermint (after reading some change in the parent through the agent), this reconfiguration should trigger through a config message that calles set_membership in the gateway to update the membership set of the subnet on-chain. set_membership can't be called by external actors and it is executed through an implicit message.

Update (after sync CoLo)

  • Every time the membership set changes in the parent a new top-down message will be triggered with the information about the membership change.
  • This message will be propagated as any other top-down message (State tree / app state garbage collection #154)
  • Its execution in the child will trigger the reconfiguration in the child subnet membership.
@adlrocha
Copy link
Contributor Author

adlrocha commented Oct 4, 2023

Being tackled in consensus-shipyard/fendermint#272

@adlrocha adlrocha closed this as completed Oct 4, 2023
@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
No open projects
Status: Done
Development

No branches or pull requests

3 participants