Content pfp
Content
@
https://opensea.io/collection/nouns
0 reply
1 recast
1 reaction

Noun 40 pfp
Noun 40
@noun40
@rocketman looking for thoughts on what the top level buckets should be for the new flows funding mechanic everyone please share your thoughts!
2 replies
1 recast
9 reactions

rocketman pfp
rocketman
@rocketman
Off the top of my head: - Open source software Stuff like viem/wagmi/software that helps propel crypto - Nounish software Software that expands the game of Nouns, or otherwise builds on the protocol in a useful way. (rounds/camp/flows/wand/nounswap) - Local spaces improvement Cleanup / improve local public spaces - Nounish athletes Folks that are nounish athletes and are looking for a new footing - Nounish Animators - Nounish Illustrators Generally should be things that require continuous work since this is a stream
2 replies
0 recast
1 reaction

leoclark.base.eth.⌐◨-◨🎩 pfp
leoclark.base.eth.⌐◨-◨🎩
@leoclark.eth
- Nounish content creators (eg. posting photos/videos everyday)
1 reply
0 recast
0 reaction

rocketman pfp
rocketman
@rocketman
Might need to be a bit more specific tbh eg: what kind of content/posts?
1 reply
0 recast
0 reaction

leoclark.base.eth.⌐◨-◨🎩 pfp
leoclark.base.eth.⌐◨-◨🎩
@leoclark.eth
My first thought was someone going around the world posting selfies wearing noggles on iconic places. But it could be anything really. Isn't that the idea of the buckets/categories? So if you have the content creator stream, someone could potentially apply with something like "I will post daily recipes/cooking videos wearing noggles". Makes sense?
1 reply
0 recast
0 reaction

rocketman pfp
rocketman
@rocketman
yea for sure makes sense, qualifier in this case is "nounish" content so eg: TNS podcast, @jackwyldes.eth content, nouns documentaries etc.
2 replies
0 recast
1 reaction

rocketman pfp
rocketman
@rocketman
there's just tricky balance to strike between being overly specific, and ensuring the flow list curators have something concrete to work off of is all this one sounds great though
2 replies
0 recast
1 reaction

rocketman pfp
rocketman
@rocketman
one parameter to adjust is baseline vs. bonus pool rates baseline is the salary everyone splits, bonus is what nouner votes determine for certain categories, if they aren't specific enough (eg: long form nouns content vs. Nounish content in general) it will make more sense to have a lower baseline salary w/larger bonus so eg: posting selfies every once in awhile can earn you $20 a month, but nouns documentaries can still earn $200 a month. if they're in the same category this becomes trickier is all, but not impossible, just relies more on voters. which is why it's better to be overly specific about type of content imho, make sense?
2 replies
0 recast
1 reaction

leoclark.base.eth.⌐◨-◨🎩 pfp
leoclark.base.eth.⌐◨-◨🎩
@leoclark.eth
Got it! Yes, it does. So, in short, the bucket/category has to be adjusted to the size/budget/time of a project/initiative. So if a voter chooses to allocate to your example above, they had to be on 2 separate categories, otherwise both would get $20 or $200 and it would not be fair. Is that right?
1 reply
0 recast
0 reaction

rocketman pfp
rocketman
@rocketman
i would say that's a good way to think about it! this is all pretty new territory, it's sort of like prompting an AI except we're prompting TCR curators with guidelines/requirements and they'll adjust the list accordingly (Assuming incentives work out) and not necessarily. what i'm saying, is if we created a general "nounish content" category, where the time required for different projects was vastly different (eg: 1 selfie a month vs. weekly 5 min edited videos), and for some reason we decided to allow these in the same budget, i'd recommend putting the baseline pool relatively low (eg: so it works out to the minimum work permitted let's say $20 for selfies), and then the bonus pool a relatively high proportion of the rest of the flow. then, voters would come in and vote for the higher effort content ideally, and it'd be able to earn $200 but that relies on voters voting based on effort / not popularity, and confuses the mechanism a bit. i'd recommend just being more specific and making 2 buckets
2 replies
0 recast
1 reaction

rocketman pfp
rocketman
@rocketman
to clarify, putting hugely different work / time required projects in the same category means either salaries will be very similar for vastly different classes of effort, or we have to put the baseline pool (the min salary everyone gets) way lower, and rely on voters to allocate to higher effort projects naturally (not good thing to rely on imo)
1 reply
0 recast
1 reaction

leoclark.base.eth.⌐◨-◨🎩 pfp
leoclark.base.eth.⌐◨-◨🎩
@leoclark.eth
Got it. I guess initially I did not understand the bonus part. So, yes, agree on the separate buckets.
1 reply
0 recast
0 reaction