0xc27bff1d…1a06sent to0x2a019853…277f·#16,743,278·view on Etherscan
Our principle is to only vote against currently :)
The rule is that for each proposal we will conduct an "Squad Vote".When the "against" votes are greater than the "for" votes + "abstain" votes, we will choose to vote against on-chain; otherwise we will abstain.
"Squad Vote" result: Approval:Opposition:Abstention = 16:5:3.
The proposal was approved by all of us to provide an open database for the Nounish ecosystem. NounsDAO will benefit greatly from it. It will enhance the overall daotool development of the Nounish ecosystem. We support the team in exploring the path of data composability for Nounish. Infrastructure exploration is highly risky and uncertain. It is harder than imagined. But the team has a good track record to prove that they have a deep understanding and patience for it.
Our opposition mainly comes from:
1. Is it too early to do it now?
Nounish Dataverse may be like Web3 Social projects, unable to find Builders to develop products/tools that everyone needs, infrastructure but running applications that no one uses on top.
There is no information indicating that applications currently in demand (Prop House, Nouns Agora, House of Nouns, Nouns.Build, Dune Dashboard..) would consider using Ceramic as their data backend. It is much more difficult for applications to be demanded than to do underlying infrastructure. Holding a Prop House Round as mentioned in the proposal does not solve this problem.
2. The proposal delivers too much content
The Nounish Dataverse proposal promises a decentralized database based on Ceramic, developer documentation, ID system integration application… A single proposal combines too many things to do. We recognize 30% of what’s in the proposal but 70% is over-committed.