Dynamic Project Minimum Quorum

[jac18281828]

Dynamic quorum is likely not a requirement for any single vote, however token projects will have varying numbers of tokens and therefore a type of dynamic minimum quorum is probably required at the project and community level

• Currently supporting fixed quorum: the quorum is settable on every proposal. Dynamic quorum is a feature addition
• Dynamic quorum for the project would be based on the token contract implementing ERC721Enumerable and therefore optional and not always present.
• Consider having fixed quorum for each vote but the minimum project quorum being calculated dynamically if the token is based on ERC721Enumerable -- specifically totalSupply is required
• For strictly ERC-721 tokens, an alternative path can be provided for the project owner to “increase only” minimum quorum for the contract.

[jac18281828]

https://docs.openzeppelin.com/contracts/3.x/api/token/erc721#IERC721Enumerable-totalSupply--

[rocketman-21]

I think having a quorum set to a percentage of the total token base is necessary.

when I refer to dynamic quorum I mainly mean something like this based on percentage of against votes.

for now the former is definitely enough imo