gitcoinbot
commented
2 years ago Issue Status: 1. Open 2. Started 3. Submitted 4. Done
Work has been started.
These users each claimed they can complete the work by 7 hours from now. Please review their action plans below:
1) oschleic has started work.
- new vault status of deprecated added after open
- new mapping created for (vault address => metadata)
- getVaults, getFilteredProductionVaults and getProductionVaults all now return a second array of metadata strings, the metadata array aligns with the other returned vault array (equal/reflective index).
- new two way mapping for keys: mapping(string => address) public addresses; mapping(address => string) public keys;
- Get key address with getAddress(string memory key) and get key from address with getKey(address keyAddress)
- Delete key with deleteKey(string memory key), note that a separate function could be created to delete key by address
- Tests reformatted and new ones added to test new key and guild features
Discord: ToastyOwen#5179 Email: oschleic@asu.edu 2) ufe-pr has started work.
I'll be improving the Badger registry smart contract. 3) alexni245 has started work.
I will work on the new registry contract 4) mohamad1371 has started work.
I'll do my best to solve this problem 5) ssgums has started work.
The new version of Badger Registry for GR13 Hackathon. 6) jack-the-pug has started work.
A new version of the Badger Registry. 7) koksymaglo has started work.
Grants round13 Hackathon 8) recep9227 has started work.
Kazanç ve ödül için
Learn more on the Gitcoin Issue Details page.
koksymaglo
Context
Badger, in its constant seek of further decentralization of its ecosystem, developed the Badger Registry. This Smart Contract, allows for a single source of truth of all Badger related contracts in a decentralized fashion. The Badger-Registry currently host a list of keyed smart contract addresses that includes all infrastructure and actors within the Badger infrastructure for each chain that Badger is on. Additionally, the registry hosts a list of all the vaults existing on each chain, keyed by their strategist (account that adds them to the registry) and mapped to their version type (v1 or v2) and to the stage at which they are at (experimental, guarded and production).
The current registry is deterministically deployed at the following address for all chains: 0xFda7eB6f8b7a9e9fCFd348042ae675d1d652454f
As Badger pushes for further decentralization and systematic efficiency, new requirements have come up for the Registry to the point where a new version is required.
Requirements
A new version of the Registry Smart Contract must be developed based on the existing one linked above. The new version should include the following changes:
strategistGuildmultisig account parameter. This actor should now be in charge solely of the promotion of vaults (changing vault status). This address should be modifiable from governance. Vault promotion should still be doable from the Registry's governance.registry.add(Vault_address, "v1", "DCA-BTC-CVX")). The metadata should be returned along with the vaults when calling the vaults view functions (getVaults,getFilteredProductionVaultsandgetProductionVaults).A brownie project is also required around the Smart Contract that includes:
Submissions will not be accepted if they don't compile or if they don't include tests.
Post Bounty Offers
We may pursue the few developers that are able to undertake this challenge and succeed by offering 1-1 tailored bounties with the goal of onboarding them into Core Tech at BadgerDAO (Full time Contributor Positions).
Dev-Discord
Feel free to join us on our Dev Discord: https://discord.gg/Tf2PucrXcE