Content
@
https://warpcast.com/~/channel/arrow
0 reply
0 recast
0 reaction
Frey tradesđ©đ
@freymon.eth
Hey @naaate, Been following along and just wanted to sayâthis all feels really good. The direction youâre taking with Arrowheads stands out in a space that often feels loud and performative. Thereâs a calm confidence in this approach that I really appreciate. so iâll try to do this in a criticâsuggestion type of way first would be the mini-app/product direction 1. Progress Verification: Consider modular proof-of-progress tools (e.g., screenshots, Figma links, GitHub commits) built into update posts. This doesnât need to be trustlessâjust structured enough to make updates feel concrete and legible to backers. 2. Community-as-co-builder: Allow projects to embed calls for help (e.g., need a designer, need meme support) right in their updates. This turns the dashboard into more than a trackerâit becomes a public workshop
1 reply
0 recast
3 reactions
Frey tradesđ©đ
@freymon.eth
Cohort Structure + Weekly ETH Pools: Weekly ETH rewards are a great nudge, but over time, thereâs a risk of updates being posted just to check a box. A few creators might treat it like a chore. You might eventually need some way to keep the bar high without making it feel competitive or stressfulâmaybe light curation, or occasional themed prompts (âwhat did you almost give up on this week?â). Optional Transparency Mode: Let creators opt into showing funding levels and deliverable timelines publicly on their dashboard. This creates an aura of accountability-through-pride, rather than shame. Governance + Curation Limiting the initial group makes a ton of sense. Maybe over time you can give each project a âslotâ to vouch for a future builders. Consider on-chain âvouchingâ where each project in the founding cohort can âvouchâ for 1 new entrant. This makes expansion a lil bit slow, but social, and gives early committed builders soft governance powers without full DAO overhead.
1 reply
0 recast
1 reaction
