Tribute DAO Community Call #3

[fforbeck]

Tribute DAO Community Call 3

Agenda

• Dev Updates
• Open Roadmap
• Suggestions
  • Grindery.io

When

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

Where

• Discord: https://discord.gg/jq4K7qw45Q?event=940704229872517270

Notes

Dev Updates

• Tribute-UI

  • The new integration was released, and the documentation was updated to v2.3.5 - which works with the latest version of tribute-UI.

• Bugs

  • A community member has reported a bug in the latest tribute-contracts release v2.3.5. The issue happens when you try to submit a vote result to onboard a new member, it returns the error: VOTE NOT ALLOWED.
  • We rolled back the tutorial to release v2.3.3 until we have a fix for that issue.

• Audit

  • Sigma Prime flagged that they are wrapping up the audit process, so we will probably receive a report in the next few days.

Open Roadmap

• Summary

  • TributeLabs team shared the draft of the open roadmap for the Tribute DAO framework
    - Roadmap
  • Briefly described where we are, where we want to go, and how we will get there.
  • The idea is to work with the community to improve the framework, develop new features, and orchestrate all the community contributions.
  • The tasks will be divided into five big categories:
    • User/Dev Experience
    • Operations
    • Security
    • Integrations
    • Governance
  • Any task in the roadmap document is subject to changes.
  • Tasks published to Github as a ticket are ready to be implemented.
  • Next steps:
    • Break it down into smaller tasks, add them to Github.
    • Anyone interested in working on any of these tasks will need to express interest in the Github ticket.
    • Ensure that different community members are not working on the same tasks.

• Community Questions

  • 1. Do you have any plans to integrate tribute contracts with other chains such as NEAR, Solana, Polkadot, etc?
    • A:
      • It is not in the roadmap, but it is something that we can look into, as long as the integration is EVM compatible. Mainly because rewriting all the contracts, going through new audits, and testing everything together takes time. If we can build these integrations on top of what has been created already, that would be better.
      • @Alpine-lines volunteered to test the NEAR + Aurora integration and the results on how the contracts can be ported to Near’s L2-like network.
      • From Aurora docs: "The base fee of Aurora is ETH, which provides a smooth experience for dapps’ users."
      • Someone already ported Moloch to NEAR. It would be nice to take a look:
        • https://discord.com/channels/854328535929192498/855015519043059744/873198161135550523
        • https://explorer.testnet.near.org/accounts/molochv3.mrkeating.testnet
  • 2. Is there any document that describes which Adapters & Extensions are in development?
    • A:
      • Yes. You can find it here: Adapters & Extensions
      • In this document, we will track all the contributions, requests, and ideas for any new Adapters & Extensions ideas. Once the specification is defined in the roadmap document we can create a ticket on Github, and anyone can work on that.
  • 3. Any plans to open the code of the KYC Backend Service?
    • A:
      • The KYC Service is a backend service to validate and sign onboarding coupons for verified members, so they can redeem these signed coupons to join the DAO.
      • One of the reasons we did not open that code yet is because it relies on a centralized infrastructure (Database + Server hosting), and we want to make it decentralized.
      • Ideally, we should conduct the KYC check and issue new signed coupons for members without relying on this kind of infrastructure.
      • We can add that to the task list and start thinking about how we can design such a system with the community.

Suggestions

• Integration with Grindery.io
  • Grindery dev could not join the call to share more about it.

To Do

• Mapping out the Adapters & Extensions already developed by the community + TributeLabs team [@fforbeck]
• NEAR Integration test results [@Alpine-lines]

[moza88]

It seems like the Discord is invalid, I am hoping to join the community call.

[fforbeck]

Hey. Try this one: https://discord.gg/jq4K7qw45Q?event=940704229872517270