Nostr Web Client

I tend to fall into this camp. For me, Bitcoin is money. I believe that's where the focus should be. My problem is with censorship/cancellation/omission.

Jamin ☦️🏴󠁧󠁢󠁥󠁮󠁧󠁿 8mo ago

Yep, bitcoin is money as the white paper stated, and that is the intention of the protocol.

Censorship and spam filtration are not the same thing.

Censorship is X node/wallet/address cannot broadcast transactions to my mempool.

Spam filtration is I will not include non financial transactions in my mempool, even if they are otherwise protocol compliant.

The irony is with knots you can do whatever you like because it's completely configurable. You could set mempool policy to only include non-financial transactions if that was your desire.

Reply to this note

Please Login to reply.

Discussion

Zaikaboy 8mo ago 💬 2

Yes that is irony. My beliefs say you should be allowed to do what you want but I'm a little torn. Why reinvent the wheel? My head is hurting, its like I'm letting my teenage son drive my classic car!

Jamin ☦️🏴󠁧󠁢󠁥󠁮󠁧󠁿 8mo ago

The way I see it, the only thing that needs to happen is to add nostr:nprofile1qqs0m40g76hqmwqhhc9hrk3qfxxpsp5k3k9xgk24nsjf7v305u6xffcpp4mhxue69uhkyunz9e5k7tcpzemhxue69uhk2er9dchxummnw3ezumrpdejz7l3vw43's anti inscriptions filter. This is essentially a bug that was introduced as a result of changes that were needed for lightning to work and it makes sense the fix the bug.

Once that is done I think bitcoin should ossify as much as possible and the innovation should happen higher in the protocol stack.

Zaikaboy 8mo ago 💬 2

I can see that argument but I'm not sold. Filter seems anti for me. I like lightning but if it/taproot has damaged the base layer... As I have said, my head hurts

Jamin ☦️🏴󠁧󠁢󠁥󠁮󠁧󠁿 8mo ago 💬 2

I get it, it's a huge topic. I've watched a lot of what nostr:nprofile1qqs8fl79rnpsz5x00xmvkvtd8g2u7ve2k2dr3lkfadyy4v24r4k3s4sppemhxue69uhkummn9ekx7mp0qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshscy566r has had to say about it on his YouTube channel and I think he lays it all out very honestly and makes an iron clad case.

Ultimately, spam filters have always been a part of bitcoin, but in changing bitcoin for lightning a bug was introduced that allowed a new way to spam. We should just add a filter to cover that too.

Zaikaboy 8mo ago 💬 1

https://x.com/boomer_btc/status/1918320027192664349

This is quite good.

Jamin ☦️🏴󠁧󠁢󠁥󠁮󠁧󠁿 8mo ago

Yeah Bob is a legend

jon doe 8mo ago

Has anyone noticed that Bitvmv2 has been putting abritary data into the UTXO set rather than OP Return like Casey and his ordinals. Not a fan of Lukes 83 byte cap limit filters as this introduces "permission" into a permissionless network. But can't help but wonder why everyone are so focused on arbitary data on the OP Return when recent activity has mainly been Bitvmv2. These arguments are best had at bitdevs 🧡

The real concern IMHO as stated by LaurentMT:

"Concerns about jpeg and ordinals spamming the Bitcoin blockchain are a distraction.

You should be concerned about a state-backed usd coin using the Bitcoin blockchain as its data availability layer and outpricing the monetary use of bitcoin."

🤗

jon doe 8mo ago

If people look at blocks. Most ordinals activity are like 0.00000400 BTC at the moment. Not really a concern? 🤷