How about UTXOs no smaller than the blockheight you intend to spend your Bitcoin at

Ordinals are an arbitrary ownership scheme with little to do with Bitcoin, you're referring to inscriptions here which can be defined as transactions which escapes arbitrary data into the witness portion of a transaction

What do you mean by valid? Inscriptions are Bitcoin transactions that circumvent Bitcoin "spam" filters which are put into place to encourage users to make transactions in ways to not bloat the UTXO set. It takes a mechanism (witness discount) meant to encourage users to utilize multiple utxos more efficiently into a mechanism where it generates unprunable dust outputs. Arbitrary data on Bitcoin is valid (hence OP_Return is offered), but having it unprunable and not paid-for-in-full is a harm on the network because it puts a cost on node operators and outbids for non-arbitrary data storage-use for blockspace. As an attack it's actually pretty smart (not stupid) to hide behind people like Mr bailey and the silly dancing wizards 🤔

But whose to say what is spam as long as someone's having fun? People are free to create whatever transactions they want, and the mechanism of used in inscriptions is just one method -- there likely will be more methods in the future. Oh heavens, a never ending cat and mouse game, the horror🤦 Is it already time to do nothing?

Every class of Bitcoiner gets to ask the question: "should users be encouraged to spam/scam the network?" then do something about it (even nothing!)

As fun as it would be, wouldn't that kind of defeat the purpose of liquid confidential transactions 😅

.... confidential squirts 💦🫣

Recommend anyone to take some time to build Bitcoin with these commits. Works fine over here

The thread is also worth a read 🤓 Whether you care about ordinals or not, being able to build Bitcoin from source on your own and apply the patches you want is a good skill to have 👍

https://github.com/Bitcoin/Bitcoin/pull/28408

Ah, found what I was looking for

Been messing around with my node (Core v26.0),

setting datacarrier=0 doesn't do anything to filter out the taproot inscription transactions in my mempool nor does setting datacarriersize (I set it to 48)

datacarrier in Core only catches OP_Return right?

Is there a setting to set in v26.0 to ignore relaying inscriptions or is the only solution at the moment to use Knots? I see that Knots adds some additional policies (MaybeReject) that are not in Core

Looking to explain the CVE and mempool policy at nostr:npub1yvt22y0mkehu9n2fr50wlxg3rg0zjfrcezpeat352shjkjd9l8jqgxz9q9 this week, any help or relevant resources to study would be appreciated

#asknostr

SO HUMBLE WE SIT ON THE FLOOR

WE SIT WHEN THE CHAIRS ARE ON THE MOON

WE RUN OUR NODES

I WILL GIVE IT MY BEST TOO, CAPTAIN CAPSLOCK 🫡

I recognize this painting! I saw it at the Chimei Museum in Tainan, Taiwan

It's a wonderful museum, come visit and see this painting in person 🥳

My VPN provider should be using that government cash to make my speeds better then 😤

👀🤙

すごい 💯

CAN'T BLOCK US EITHER

Gm ☕🍩! Great advice

🤯

i gave this a shot, the DHT crawler is impressive. It was able to index like 700K torrents in just a few days (for reference the database for the now-defunct RARBG only has like 1.1 million torrents in the archive)

however a lot of the content on DHT is a bit....... explicit 🤭

I use the command-line utility qrencode, it's available in most package managers.

https://github.com/fukuchi/libqrencode

If it is just for one-off stuff these days most browsers let you share links in QR code format, when you pull up the qrcode you can modify the text box as you see fit

If looking to customize qr codes, toss in "styled qr code" into GitHub and I'm sure a few WebApps will pop up

Just goes to show that other mammals suck at making cheese 🤷

Taiwan lost 0:1 , 失敗有榮 time to eat potstickers at 四海遊龍 as consolation 😞