Proposal 255 (Q129)
From Nouns Dev
A Nouns proposal.
| Language | Label | Description | Also known as |
|---|---|---|---|
| English | Proposal 255 |
A Nouns proposal. |
Statements
96
0 references
Nouns Wallet Service
0 references
255
0 references
36
0 references
17 March 2023
0 references
38
Doesnt seem like it has demand, not sure its focused and clear, and the maintenance costs implied ongoing are high.
0 references
Enabling mobile push-notifications for token holders is interesting, but I wonder how many Nouners would use this specific tool or even want these on-chain events appearing as notifications on their phone. There isnt enough obvious utility for me here. The prop also talks about Nouns lacking a simple real-time communication layer but doesnt seem to offer any further communication tools, like messaging. Poolsuites work is fun and significantly Nounish, happy to have them present and proposing. Im voting no on this prop but definitely encourage them to come back with more proposals.
0 references
Imagine a world where voting does not exist. In this world, we would have no need for rules or principles. But in our world, voting is a reality. So we have a simple rule: we only vote against. We use a “Squad Vote” for each proposal. If more people vote against than vote for or abstain, we vote against on-chain. Otherwise, we abstain. This is our rule. According to the “squad vote” result for proposal 255, which is 1 for, 17 against and 6 abstain, we choose to vote against.The viewpoints of our different members are as follows (source not listed): Opposing views on the proposal: 1. The community wallet product originated from a private social club similar to FWB, which is more suitable for closed community scenarios and not applicable to open Nouns. However, it may be adopted by subDAOs of Nouns. 2. Why should Nouns pay 120 ETH for an integrated service? The proposal for NounsWallet is different from Prop House and House Of Nouns building products from scratch for Nouns. The product was not adopted in FWB, and now they are applying for funding in Nouns to do integration, which is extremely unreasonable. Nouns provides both users and funds to integrate a product service. 3. There is insufficient confidence in timely delivery of the product. This is PoolSuite teams first proposal at Noun. In the past, the team has delayed delivery of products such as https://grandleisure.org/. Supporting views on the proposal: 1. The proposer of Proposal 255, PoolSuite, is a talented team with excellent aesthetics in their FM magazine products etc., even if there have been delays in delivery we are willing to wait for them to produce results.
0 references
I am skeptical about the efficacy of financing software for external communities as a method of proliferating Nouns, and I doubt our ability to accurately assess their requirements. Instead, I advocate for supporting the development of tools that address the needs of Nouns DAO, as numerous other communities are likely to share these needs, allowing us to disseminate our tools and principles. Regrettably, this proposal appears to be geared towards funding a tool for other communities, whose demand for it remains uncertain.
0 references
large ask while the primary use case(s) dont feel particularly compelling/applicable to nouns
0 references
Thanks to the team for putting together this prop! I think this is a cool idea, and is a fun theme to experiment with, but I think the ask is too high for the amount of work and the need being met here. I am also concerned about the longevity of this design: who maintains the systems that send these notifications, how are they funded and organized, etc. Would be up for a smaller grant to fund some experimentation here. Thanks again for your time on this!
0 references
Very strong yes from me. Not only are the folks are Poolsuite excellent, but I see this as a great opportunity for Nouns to be a leader in building public infrastructure for all of web3. Nouns Wallet Service can accompany tools like Prop House, Agora, and House of Nouns as software that any community can use to serve its own needs. The only question Id have is what the plans are after the 1y of Poolsuite development/maintenance is up, and who would take that over per se. Im confident that can be figured out though when the time comes.
0 references
This sounds super useful and is a great public good for the ecosystem. The Poolsuite team has proven they can ship high quality product. This is a yes from me!
0 references
Reasons given in my newsletter: https://paragraph.xyz/@thebower/active-governance-noun-582-4
0 references
A great team and a useful tool validated by their community is a great combination. This could be really valuable for Nouns and the ecosystem.
0 references
108
0 references
Poolsuite
0 references
17 March 2023
0 references
Poll failed to meet vote threshold. **FOR - 21 VOTES** **Classic_Craig** | *this feels like a potential on ramp experience for folks* **AGAINST - 26 VOTES** **nonodynamo** | *This seems like a centralized notification system to me.* **Sasquatch** | *Please come back with another proposal. Poolsuite is amazing!*
0 references
10
0 references
1
0 references
120
0 references
120
0 references
The Nouns Wallet Service is a proposed tool that would allow users to add any NFT or ERC-20 into their Apple/Android wallet. This would enable web3 communities to send push notification s to token holders and open up a range of future use cases.
0 references
unlocking the ability for web3 communities to send push notifications to token holders and a wealth of powerful future use cases. --1. How would Nouns send notifications to users who had this?-2. Do you need to own the NFT to put it in your Wallet?
1. Nouns would send notifications to users who had this by giving all members/collectors a wallet pass and then sending direct messages to them. The holders don't need to enter their email or join a telegram/discord, they just add the pass (push notifications are turned on by default).-2. It is not explicitly mentioned whether you need to own the NFT to put it in your Wallet.
0 references
what is the breakdown of design/build/maintenance costs?
The breakdown of design/build/maintenance costs is roughly design 20% — build 50% — maintenance/onboarding/support 30%.
0 references
