Skip to content

[WIP] Solidity Implementation of mvs_manager.cairo#20

Closed
Copilot wants to merge 1 commit intoupgrade/scarb-2.11.4from
copilot/fix-50e2bf6b-78aa-4ec7-8ffa-4c9d9a4c702f
Closed

[WIP] Solidity Implementation of mvs_manager.cairo#20
Copilot wants to merge 1 commit intoupgrade/scarb-2.11.4from
copilot/fix-50e2bf6b-78aa-4ec7-8ffa-4c9d9a4c702f

Conversation

Copy link

Copilot AI commented Aug 2, 2025

Coding agent has begun work on Solidity Implementation of mvs_manager.cairo and will replace this description as work progresses.

See problem context

TITLE: Solidity Implementation of mvs_manager.cairo

USER INTENT: The user aims to create a Solidity version of the mvs_manager.cairo file, ensuring it supports multiple extensions and adheres to specific operational requirements.

TASK DESCRIPTION: The user requires the development of a Solidity contract located in solidity/src that functions as an ERC4626 compatible vault. This contract should manage multiple IMVSSubExtension contracts, such as LeverageVault.sol. The total assets should be calculated as the balance of the manager contract plus the total assets of each extension, all denominated in the manager's asset. The contract should include a rebalance function for complex push/pull operations, which should be configurable rather than hardcoded.

EXISTING: The user has specified the repository as strkfarm-core and outlined the requirements for the Solidity implementation of the manager contract.

PENDING: The user is awaiting the creation of the Solidity contract that meets the outlined specifications, particularly focusing on the ERC4626 compatibility and the configurable rebalance operations.

CODE STATE:

  • The user has not provided any specific code snippets or diffs yet, but they have referenced the need to create a new Solidity file based on the existing Cairo implementation.

RELEVANT CODE/DOCUMENTATION SNIPPETS:

  • The user referenced the need for the manager to be an ERC4626 compatible vault and to manage total assets effectively.

OTHER NOTES: The user has emphasized the importance of allowing configurable operations for the rebalance function, indicating a preference for flexibility in the contract's functionality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants