Michael Gingras (lilfrog) on Warpcast

Content pfp

0 reply

0 recast

0 reaction

rocketman pfp

Nounish software 🤓 🖥️ We fund people who build software that makes Nouns more accessible, useful, and fun. Help us expand the game of Nouns so more people can meaningfully play it! Payment Structure - Each approved project gets at least ~$100 USDC per month - Extra rewards for exceptional impact and adoption - Payments stream automatically every second while requirements are met How to Apply - Write an application with: - Your name, contact information, and social handle(s) - Description of the software you'll build or maintain - How it makes Nouns more accessible, useful, or fun - Links to previous relevant work/contributions - Github/deployment links if existing project - Initial development roadmap - How you'll measure impact and adoption - Pay an application fee (returned if you meet requirements)

1 reply

0 recast

3 reactions

rocketman pfp

Ongoing Requirements - Make consistent progress on your software - Share updates twice monthly with screenshots/video demos - Engage with community for feedback - Fix critical bugs promptly - Maintain clear documentation - Keep code open source when possible - Post updates on Farcaster in /nouns or /flows channel Best Practices 1. **Open Source First**: Keep code public, documented, and accessible to all 2. **User-Centric Design**: Build for accessibility and ease of use 3. **Security Priority**: Follow best practices, conduct regular audits 4. **Community Driven**: Listen to and incorporate user feedback 5. **Clear Documentation**: Write guides that anyone can understand 6. **Test Everything**: Thorough testing before deploying 7. **Quick Response**: Address issues and support requests promptly 8. **Build Together**: Collaborate with other Nouns builders 9. **Stay Transparent**: Share progress and challenges openly 10. **Focus on Impact**: Solve real user needs and measure results

1 reply

0 recast

1 reaction

rocketman pfp

How to Post Updates Twice monthly on Farcaster in /nouns or /flows: - Development progress - Screenshots/demos of new features - Bugs fixed and challenges addressed - Community feedback incorporated - Upcoming plans Verification Methods - Code repository review - Deployment logs - Community testing feedback - User adoption metrics - Bug report responsiveness - Documentation quality - Community engagement - Impact measurement

1 reply

0 recast

0 reaction

rocketman pfp

How to Keep Your Funding - Regular development activity - Timely issue resolution - Maintain documentation - Engage with users/community - Follow security best practices - Show growing impact/adoption - Uphold Nounish values What Gets You Removed - Abandoning development without explanation - Unresponsive to critical bugs over a long time frame (1+ week) - Security vulnerabilities left unaddressed - Missing regular updates - Harmful changes to users - Code/documentation neglect - Misrepresenting metrics - Plagiarizing others' work

1 reply

0 recast

1 reaction

rocketman pfp

Gaming Rules - No plagiarism of code or content - Be transparent about development - No malicious or exploitative features - Community helps monitor integrity - Regular reviews of alignment with goals Remember: We're looking for builders who make Nouns more accessible, useful, and fun for everyone. Your software should lower barriers to entry, enhance user experiences, and inspire others to join and participate in our onchain society. For Curators - Do not accept new applications if doing so will put the baseline minimum salary below $100 a month - Note: It is fine if the baseline salary falls below $100 from new budgets/voting, but don't accept new applications then - Consider removing underperforming builders if new applicants show greater promise/impact - Value meaningful impact in expanding the game of Nouns over feature count - Prioritize accessibility and user experience - Monitor for alignment with Nounish values

1 reply

0 recast

0 reaction

rocketman pfp

What do we think for these requirements for Nounish software?? cc @krel @wiz @spencerperkins.eth @coleperkins @wojciech @nickd @seneca @frog @noun40

2 replies

0 recast

3 reactions

Michael Gingras (lilfrog) pfp

Michael Gingras (lilfrog)

I really like the idea of nounish software being a funding target. However, for 100 a month, I feel like this is best for fixing small bugs, or general upkeep on things like nouns.wtf (if it's not sunset 😀) or other open source nouns public goods I can't imagine anyone wanting to build meaningful new software for that price, but it's definitely interesting from the perspective of encouraging general upkeep, and at 100 a month it's low enough that we could reward folks with a track record of maintaining open source nounish repos something like a list of bugs or requests for folks to go through could be nice as well, so people have visibility into what the community wants to prioritize or has noted as needing fixing

1 reply

0 recast

1 reaction

rocketman pfp

yea ideally we can scale this to 10x just figured it'd be a good one to add in general with the hope we can scale it up

2 replies

0 recast

1 reaction

Michael Gingras (lilfrog) pfp

Michael Gingras (lilfrog)

makes sense, I like it! It's worth experimenting with different stream targets to see what sticks, Personal bias but I'd like software as a category. traits could be cool too -- I know theres some fatigue lately around funding new traits but I think most of that comes from people not thinking its worth spending 3ETH or a noun on a trait. Maybe if we got some stream sent to artists who make new traits and waive rights to add them as official traits then we can streamline how art is funded. would still take a proposal to add the new traits but would maybe help some of the fatigue around paying high premiums for it

1 reply

0 recast

1 reaction

rocketman pfp

how do people currently pay high premiums for traits? i like that idea though

1 reply

0 recast

0 reaction