memoscan

0xea9f…4e9c

All memos sent from and to 0xea9f…4e9c.
0xea9ff038…4e9csent to0x4976fb03…ba41·#22,369,446·0x86b8ff96…bae420
nouns.bioin the age before ease, before comfort dulled the hands of builders, three rose from the dust: olli and his two companions. they did not ask permission. they did not seek approval. with bare hands and stubborn hearts, they carved camp out of the void — a place where spirit could live unbroken, where craft could breathe free. the nights were long, and the world vast and hostile. still they built, stone upon stone, code upon code, until camp stood — not as a shelter, but as a fortress against mediocrity itself. the people came in silence at first, then in waves. they came not because they were invited, but because something ancient stirred in the walls of camp, something that called to all who still remembered what it meant to build truly. and though the world outside may wither, though kingdoms fall and memory fade, camp will endure — because it was not made for the world. it was made for those who would dare to make a new one.
0xea9ff038…4e9csent to0x6f3e6272…223d·#22,247,923·0x6cedfb75…4f02a8
@0x39a7...aBc0 👌 > > > If this prop pass, #NounsBreakEvenMovement will start vote down all props with any spending in the next 3-4 month until we become net positive again. > > If that is what the community wants. I can make it pass using my vote, but are you ready for what's coming next? > +1 > @0x2897...c84F > > > increasing flows budget, I'd love to. I think flows is easily the highest impact way for Nouns to spend money. Just unsure given current treasury size if people are willing to stomach more than $50k a month. > > I think increasing the flows budget is a simpler pathway to growing the pie right now, and a safer bet for the DAO. And there's already a pathway, although less explicit, for Builders to grow the pie: it's via proliferating Nouns and referring new people back to the DAO > > Flows is the best experiment for reliably doing good things in the world and realizing the purpose of the DAO I've seen yet. We should double down on it. > > But I don't think it's time to make considerable changes to the protocol. It has been operating for only 6 months, and this is too soon to get an accurate read on the current strategy. > > I'm also not confident we really know what's happening inside flows right now. We need better data and better dashboards. > > My feeling is we're overwhelmingly relying on AIs to oversee the whole operation, and I see little action from curators. I doubt that strategy works in the long term because as builders learn how to optimize those automated metrics they become meaningless (Goodhart's Law). > > I think before we step up the protocol, we need to establish a culture of due diligence and ensure we're funding the things we should be funding. Curators are the only sustainable way of keeping a high bar on the impact of funded builders, so we've got to ensure there are enough of them and that they're active. > > Can you share data on curator activity across all flows? I think we're missing that data, and it would tell us a lot about the current state of the protocol. > > important metrics: > - curator diversity/vote concentration per flow > - number of votes per flow > - overall distribution of flow scores (histogram) > - how many flows have been challenged. how many continued vs were cancelled > - how is this data trending historically? are we consistently attracting more builders, more curators? > > I'm very supportive of Flows, but not convinced of the plan laid out in this proposal yet. That data might convince me. > > > > @0x7f64...d6d2 > > > > We've mostly seen builders collab / share resources when it's explicitly incentivized eg: in the Builder Kits flow. Outside of that, there's been competition because flows is zero sum, everyone is fighting over fixed budget / attention from nouners for votes. > > > > That's what we're trying to solve with this prop. The structure of flows doesn't incentivize anyone to work together, because there's no way to grow the pie. It's hard to get any quantitative data for you given that fact. I'll let @jango chime in on revnets in general > > > > re: increasing flows budget, I'd love to. I think flows is easily the highest impact way for Nouns to spend money. Just unsure given current treasury size if people are willing to stomach more than $50k a month. > > > > > > > > > > > "Builders earn revnet tokens and matching-pool bonuses when they put their revenue into the revnet tree. Launching a revnet will require splitting project tokens with the broader Flows network, ensuring continuous collective growth. Basically, builders put revenue into their revnets because it’s financially smarter to grow together, aligning everyone's incentives around collective success rather than isolated effort." > > > > > > > > > - Any examples or evidence of similar behavior exhibited by any of the flows participants today? Actual hard numbers will be good to know. This currently feels hypothetical. > > > > > > - Ideally you would want to get a sliver of qualitative or even better quantitative data regarding demand for such, before introducing such a fundamental upgrade to the protocol. > > > > > > Given Nouns is main funding body for flows, currently its grant-making mechanism only utilised by Nouns. > > > Why not just increase Flows operating budget (more than 40k$/month) in the interim while you prove out this demand. > > > > > > > > > > > > > > > > +1 > > > "Builders earn revnet tokens and matching-pool bonuses when they put their revenue into the revnet tree. Launching a revnet will require splitting project tokens with the broader Flows network, ensuring continuous collective growth. Basically, builders put revenue into their revnets because it’s financially smarter to grow together, aligning everyone's incentives around collective success rather than isolated effort." > > > > > > - Any examples or evidence of similar behavior exhibited by any of the flows participants today? Actual hard numbers will be good to know. This currently feels hypothetical. > > > > - Ideally you would want to get a sliver of qualitative or even better quantitative data regarding demand for such, before introducing such a fundamental upgrade to the protocol. > > > > Given Nouns is main funding body for flows, currently its grant-making mechanism only utilised by Nouns. > > Why not just increase Flows operating budget (more than 40k$/month) in the interim while you prove out this demand.
0xea9ff038…4e9csent to0xf790a5f5…1365·#21,836,320·0x4d71a4d2…62529b
# Temp-check: Re-propose TokenBuyerV2 audit Hey everyone! I'd like to do an informal sentiment check on re-proposing the [TokenBuyerV2 audit](https://www.nouns.camp/proposals/723), and explore options. **Quick issue recap**: We're facing an ongoing liquidity problem where we don’t have enough ETH in the treasury to reliably convert (via the Payer/TokenBuyer contracts) and pay out grants in USDC. This results in the DAO racking up debt to successful proposers without the ability to pay out funds until the TokenBuyer is funded by another proposal. Having read through the discourse on the recent the [unstaking](https://www.nouns.camp/proposals/639), [claim](https://www.nouns.camp/proposals/644), and audit proposals, my sense is that the DAO is pretty aligned on that we should prioritize staked ETH, and a solution where stETH is converted on a need basis is a good way forward. The main pushback seems to be that grantees should request stETH directly, which I feel underestimates how inaccessible that could be for someone outside the crypto-native sphere. Thoughts on re-proposing the audit? Also happy to hear other ideas. 🙏🙇‍♂️temp-check:-re-propose-tokenbuyerv2-audit
0xea9ff038…4e9csent to0xf790a5f5…1365·#21,775,039·0x1522ae32…2be781
introducing-topicsJust to be extra clear: there is no new tech underlying this, just a different form factor on the already existing data contract APIs. A topic will display as a regular proposal candidate on other governance clients, so comments here aren’t limited to Camp.
0xea9ff038…4e9csent to0xf790a5f5…1365·#18,785,790·0x8f649725…bb22be
@brennen all code is and will remain fully OS, no exceptions. We saved months of work by piggybacking on nouns.wtf and Agora, and hopefully others will be able to do the same by looking at Camp. https://github.com/obvious-inc/frontend-monorepo/tree/main/apps/nouns-camp