Tribute DAO Community Call #2

[fforbeck]

Tribute DAO Community Call 2

Agenda

• Dev updates & Audit status
• Grant DAO notes for Community Call 2/8/22 #495
• Suggestions:
  • P&D: Efficient Airdrop Strategies

When

• Date: February 8th, 2022 at 2:30 pm EST.

Where

• Discord: https://discord.gg/jq4K7qw45Q

Notes

Dev Updates

• Integration with Hardhat

  • helped to solve the rate limit issues with Infura and Alchemy APIs.
  • faster compilation.
  • implemented a custom hardhat plugin that uses Google KMS to sign & pay for the transactions created in the deployment.

• Tribute-UI was integrated with Tribute Contracts v2.3.5

  • It is available on our DEMO website: https://demo.tributedao.com/
  • The tutorial will be updated to v2.3.5 in the next few days.

• Audit status

  • We are working with Sigma Prime
  • They have found some medium & high priority issues that were fixed, and a major one related to an impersonation issue in the DAO extensions. All those fixes are in the release v2.3.5.
  • In addition to the audit report, we will also get a testing framework focused on the security of the contracts, and we can add to our CI.

• Deployment REST API

  • The MVP is in progress, and the idea is to post all the DAO configs to the API endpoint, which will trigger the tribute contracts deployment.
  • All the transactions will be signed and paid by an account that is hosted on Google KMS.

Grants

• On TributeDAO Community Call #1 #491 we talked about how we could structure the grants program, what kind of grants we could create, and how we should handle that.
  • One of the ideas was to get some inputs from @tankbottoms and his team since they are doing an amazing job on tribute contracts.
  • @tankbottoms
    • Shared a couple of ideas for grants here: Grant DAO notes for Community Call 2/8/22 #495
    • Noted that it would be great to have an open roadmap with the feature set that we plan to build for Tribute DAO Framework. This way we can coordinate with the community who will work on what, and the community can even fund some grants on their side without the need to spin up a DAO or add more friction to the contribution process.
    • TributeLabs team will prepare the roadmap for the next community call.
  • @adridadou
    • Ideally, the grants will be categorized into three big buckets:
      • 1. Dev Experience - tribute SDK, easy to use and build, etc;
      • 2. Governance - voting strategies;
      • 3. Operations - tooling to maintain the existing DAOs, and improve the DAO members' experience, tools that help to automate day-to-day tasks in the existing DAOs.

P&D: Efficient Airdrop Strategies

• The idea was originated from the NFT community, where we noted that most people don't want to burn money to redeem tokens. It is expensive, creates friction, and it kills community activity.
• So the key thing is to improve the user experience, and for that, we have this idea where:
  • each of the ERC20/ERC721/ERC1155 standards used in the airdrop will have custom typed data based on EIP712
  • the typed data will describe the airdrop (will contain the token info and beneficiary)
  • if we hash that we can use it to build the Merkle Tree for the airdrop, and the root of the Merkle Tree is published to the community (similar to Merkle Airdrops - but we are just using different data to build the leaves)
  • with that in place we can easily check if signed data by the token beneficiary exists in the tree. So the member doesn't need to redeem the token, because we can prove that the account owns a particular token in the airdrop contract.
  • we can expand this idea to the DAO Governance, and allow members that have tokens in the airdrop to vote on proposals without even minting tokens.

To Do

• Open Roadmap (TributeLabs team)