Closed
Conversation
|
Cursor Agent can help with this pull request. Just |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Integrate LayerZero oVault components to enable cross-chain functionality for the Chamber vault, preserving existing governance and transaction logic.
The core Chamber contract's governance model, stake-weighted leaderboard, and director-gated transaction flow remain unchanged. This PR introduces LayerZero submodules, remappings, and new adapter/composer contracts (
ChamberOVaultComposer,ChamberAssetOFTAdapter,ChamberShareOFTAdapter) to wrap the Chamber's vault operations for oVault compatibility.