---
# System prepended metadata

title: 'Tribute DAO Community Call #1'

---

# Tribute DAO Community Call #1

## Agenda
- AMA: Tech questions about the Tribute DAO Framework
- AMA: The future of Tribute DAO Framework (Vision & Community)
- Grants program

## When
- Date: February 1st, 2022 at 2:30 pm EST.

## Where
- Discord: https://discord.gg/jq4K7qw45Q


## Notes

- AMA: Tech questions about the Tribute DAO Framework
    - Major updates
        - The audit is in progress
            - audited version: v2.3.1
            - issues are being fixed and pushed to the master branch
        - Tribute UI
            - Removed the subgraph dependency, it is possible to use it but now by default the dApp talks to the chain directly
            - Integrated with Tribute Contracts v2
        - Tribute Contracts
            - The migration to hardhat is in progress, it helped to reduce the number of requests sent to the network provider during the deployment
            - It will be possible to run deployments using an external signer account such as Google KMS, so you don't need to manage any private keys 
        - Governance
            - Introduced the GovernanceHelper.sol, a helper contract that allows external tokens (ERC20 and ERC721) to be used as governance tokens, so we can use that to limit who can vote on what. For instance, only members holding token X are allowed to vote on DAO Configuration proposals
            - We have plans to improve that by using storage proof because right now it uses the historical balance of the member which is a bit gas-consuming.
        - Lend NFT
            - A new adapter was developed to allow members to stake any ERC-721 and ERC-1155 tokens in exchange for any amount of DAO internal tokens (in this case it mints UNITS always). The tokens are then vested. If the new member takes the NFT back before the vesting period, the tokens are being burnt. The Lend NFT adapter is similar to the TributeNFT adapter in that both allow for joining the DAO (or increasing a stake in the DAO) through the exchange of contributed assets for DAO internal tokens. The key difference is that the NFT is merely lent, not given to the DAO
        - CLI
            - The Tribute CLI tool was integrated with Tribute Contracts v2, and it allows DAO maintainers to upgrade existing DAOs
            - The upgrades include 1) Managing proposals to change adapters and/or extensions of a DAO, 2) Configuration proposals to change DAO settings such as voting periods, unit prices, the maximum number of members, etc
         - SDK
            - The plan is to build an SDK to make it easier for other devs to create and deploy new adapters and extensions without the need to fully understand the framework

- AMA: The future of Tribute DAO Framework (Vision & Community)
	- User Experience
		- Improve the experience on both sides: Dev and User
		- Dev
            - It needs to be easy as possible for a dev to use the framework and extend it
            - Open Source & Collaborative Work FTW
            - Research & Development
                - Storage proofs & Cost-Effective Airdrops
                - L2 & Sidechain integrations
        - User
            - Reimbursements 
			    - A new helper contract was developed to allow user interaction without the need to hold eth. Any DAO operation will be reimbursed to the member
	- Tribute DAO Framework as a set of operations
		- Using the existing DAO tooling to automate and orchestrate daily tasks related to the DAO operation
	- Snapshot-Hub
		- We currently have our Snapshot-Hub version but eventually will migrate it to the official one

- Grants program
	- Build a DAO around TributeDAO Framework
		- Creating a community to curate and create the grants for people to add more value to the framework
		- It needs to be sustainable 
            - Ideally, the DAO will be financing the grants  
		- First iteration
		    - Start with a safe wallet, open GitHub discussions about the proposed grants, vote on them, and decided what needs to be done and what will be accepted
		    - Still need to define what we will consider as done/implemented, and who should be allowed to vote and choose which grants needs to be done
			- Once all the rules and governance are aligned we can translate them into code
		- Grants Ideas
		    - paying people to maintain different implementations in different chains, e.g: near, Solana, Polkadot
		    - improving the DAO tooling
		    - independent auditors
		    - bug bounties
		    - L2 integrations

