Content
@
0 reply
0 recast
0 reaction
rocketman
@rocketman
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
@rocketman
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
@rocketman
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
@rocketman
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
