Replying to Avatar Dr. Bitcoin, MD

The whole op return thing is all about having one or more transaction relay networks. If you don’t want to relay some transactions but do want to know meta data about them for accurate fee estimation, go ahead and connect to a libre node and drop any tx you don’t want to relay after noting its size and fee rate.

Libre nodes will relay enough shunned transactions to save bitcoin mining centralization from slipstream type OoB payment pressure.

I think I’ll run a libre node on this principle. It shouldn’t take too many to bypass nodes participating in transaction shunning… nostr:npub1ej493cmun8y9h3082spg5uvt63jgtewneve526g7e2urca2afrxqm3ndrm has a good head about these things.
6b
OneNostrich 3mo ago 💬 1

Core team introduced Inscriptions bug being exploited by spammers, refused to fix it, and then use the resulting UXTO bloat as leverage to argue for a very spam friendly "fix" (100k payload plus subsat fees).

Reply to this note

Please Login to reply.

Discussion

Avatar
Dr. Bitcoin, MD 3mo ago

I hear people saying that as if it were true and meaningful. I don’t deny there is a new place to stuff data and it’s easier from a mental perspective, but it’s not like there weren’t other places to stuff data before en masse.

Thinking about ways to discourage OoB payments to preserve the utility of transaction shunning…reputational damage might be the only way.

Something like “miner xyz just included a nonstandard transaction paid for out of band and shame on them…”

We need something to make slipstream unprofitable, otherwise shunning based on standardness criteria is doomed to fail.