Apparently this cycle's supercycloooooor is developing from a theory that corporate bitcoin treasury adoption will somehow break the cycle.

I expect this will be proven to be delusional hopium, like previous supercycle theories.

Looks like devs are gonna need to stop dicking around and find a spam solution.

I don't think you're allowed to do that

We're living through 3 incredibly interesting technology advancements/adoptions.

1) Bitcoin

2) AI

3) UAPs

While these are incredibly interesting, I like to focus on actionable things surrounding them.

For Bitcoin, I can Stack Sats

For AI I can experiment with new tools

What actionable step is there for me regarding UAPs?

yes that what i thought... but don't you find that at odds with how easy shitcoiners come up with new coins?

i think there is clearly a lack of incentives beside altruism

Because a 'client' is not something you do on a whim. It is a serious software project because it involves peoples money and capital

Don't let the bad actors trick you into thinking Bitcoin Core 30 allows you to re-enable the datacarrier limit:

1) Along with unlimiting the default, they also broke it further. datacarriersize=83 now (as of Core 30) allows for 83 outputs totalling 830 bytes of spam, instead of just 92 bytes of spam (9 bytes of which couldn't be arbitrary) as in Core 29 and earlier.

2) datacarriersize is marked as deprecated, and explicitly planned to be removed in a future release (likely silently, since "it's already deprecated").

3) Core never fixed the Inscription exploits (CVE-2023-50428 and CVE-2024-34149) which allow spammers to bypass the datacarriersize limit.

The only way forward now is a mass migration to Knots. Not the way I wanted things to go, but Core has given us no other choice. Once this is resolved, we should avoid putting all our eggs in one basket, and encourage the creation and use of multiple clients.