-
Notifications
You must be signed in to change notification settings - Fork 217
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
feat!: make Network and IBC vats durable #8721
Merged
Merged
Conversation
This file contains 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
iomekam
force-pushed
the
iomekam-ibc-network-durability
branch
from
January 12, 2024 04:04
1f00929
to
01c575a
Compare
iomekam
force-pushed
the
iomekam-ibc-network-durability
branch
from
January 18, 2024 17:27
01c575a
to
3194369
Compare
This reverts commit cc7626d.
iomekam
force-pushed
the
iomekam-ibc-network-durability
branch
2 times, most recently
from
January 19, 2024 03:30
d5a31c5
to
953e352
Compare
iomekam
force-pushed
the
iomekam-ibc-network-durability
branch
from
January 22, 2024 22:30
4ea3b4a
to
24e45e9
Compare
iomekam
force-pushed
the
iomekam-ibc-network-durability
branch
from
January 25, 2024 16:47
d6bf33b
to
fe6ca1f
Compare
- check types.js: optional args - Vow$(S) is S or Vow<S> - names for remotables plus Endpoint, Data, Bytes
3 tasks
michaelfig
force-pushed
the
mfig-whenable
branch
3 times, most recently
from
February 23, 2024 02:58
ecbc34d
to
4d9371c
Compare
…mekam-ibc-network-durability
…mekam-ibc-network-durability
…mekam-ibc-network-durability
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
fixes #8950
fixes #5696
fixes #8319
refs #8742
Description
As part of the Calypso work, we need to be able to upgrade both the IBC and Network vats. Making this upgradable entails moving a lot of our
Far
objects to exo classes to make them durable. This PR includes all the work to move towards the durable pattern leveraging Zones. Given that IBC and Network are pretty intertwined, this PR makes both changes.Security Considerations
We intend to run this through both first-party and third-party security reviews.
Scaling Considerations
We are now leveraging Zones to make these vats durable. Doing so means that we'll be taking advantage of on-chain storage to storage the various objects in the network and ibc vats.
Documentation Considerations
We'll be creating extensive documentation, including READMEs, diagram, code flows, etc.
Testing Considerations
There are multiple unit and integration tests that we've been leveraging to test this change. The green CI is a big win for testing, but we are also planning on creating a A3P test that will simulate an actual upgrade so we can confirm that handlers still work and data is still flowing between upgrades.
Upgrade Considerations