Nostr Web Client

"development". in other words: backend identity theft via their corporate front ends. nothing new. this is literally all the time. that's why i run deep and use my own protocols. it's terrorism. not development.

delete 8mo ago

Block is floundering under nostr:nprofile1qqsgydql3q4ka27d9wnlrmus4tvkrnc8ftc4h8h5fgyln54gl0a7dgspzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgdwaehxw309ahx7uewd3hkcjt4jxf “leadership”. He doesn’t drive excellence. All the “leadership” like Brian are phoning it in. CashApp is stagnant. Give me one BU and I will have no problem working 996 at least - to turn it around. The 7 in the 996 I will work on strategy while the team is taking a day off. Give me Tidal, the worst of the worst, and I will turn it into the biggest revenue generator at the company in 2 years or I will pay back my minimum wage salary.

Globe99 8mo ago

It's fascinating to watch this debate... The strongest arguments I see in favor of removing the OP_RETURN restrictions are (a) people are "getting away with it" anyways with ordinals / inscriptions and (b) full blocks mean that demand for actual transactions will effectively "crowd out" spam.

Brunswick 8mo ago 💬 2

This is a nontrivial problem to solve. There appears to be no elegant proposals, only "all or nothing" discussions in lieu of the apparent hack that exists today.

The argument for "ACK" seems to center around disincentivizing using the p2p network and mempool to convey proposed transactions into the block template.

The argument for NACK is that we want to preserve the blockchain for financial transactions, and that the current mempool rule works well enough today. That argument would lead me to conclude a hard fork is more desirable to diaallow any post-OP_RETURN data in the blockchain at all.

There is a separate argument from the Knots camp saying the mempool should have MORE filters on by default. The argument against this is "big money" can easily bypass this by purchasing template space directly from the pools.

What is the underlying concern? It boils down to fights over limited resources.

Maybe OP_RETURN data could require an exponentially increasing cost-per-vbyte similarly to how TCP retries use an exponential backoff in congested channels? This, combined with tightning up transaction-input rules to reduce non-financial abuse?

sedited 8mo ago

> The argument for "ACK" seems to center around disincentivizing using the p2p network and mempool to convey proposed transactions into the block template.

How are you coming to this conclusion? The exact opposite of that is the goal here.

Brunswick 8mo ago

I said it backwards. You are right