Skip to content

dxdao-contracts v2.0.0

Latest
Compare
Choose a tag to compare
@AugustoL AugustoL released this 15 Mar 15:10
9dc284c

Short Changelog

  • Remove daostack contracts, the daostack contracts folder, and all daostack references had been removed, this is the final effort to detach completely from legacy code written by daostack, its been very helpful in the past three years, but it is time to move on.
  • New DaoAvatar smart contract that only does "avatar calls", this calls can be executed only by the owner which is the DAOController contract.
  • New DAOController contract that keeps track of the registered schemes, their permissions, and voting parameters hash. This smart contract owns the avatar and connects the schemes with the avatar, allowing schemes to make avatar calls, register and unregister schemes, and mint/burn dao reputation.
  • New DAOReputation smart contract that is basically an ERC20SnapshotRep (a non-transferable token that is minted/burned by the owner), this smart contract is also used by ERC20Guilds, the DAOReputation is owned by the controller, and as owner, the controller is the only contract that can mint and burn rep.
  • The WalletScheme was refactored as well, now we have an abstract contract called Scheme and from it we have AvatarScheme and WalletScheme, AvatarScheme is designed to make avatar calls and mint/burn rep. And WalletScheme is designed to register/unregister schemes and execute calls from itself.
  • The AvatarScheme is used to manage avatar funds and mint/burn reputation.
  • The WalletScheme is used for scheme management and wallet schemes that can hold balance themselves.
  • The DXDVotingMachine was refactored to VotingMachine where the voting parameters were changed and the redeem function simplified.
  • Automated documentation generation added with docify
  • Solidity v0.8 used in all contracts.
  • GH test action happens on every branch.

Full Changelog

New Contributors

Full Changelog: v1.0.0...v2.0.0