pull down to refresh
2 sats \ 9 replies \ @petertodd 9 Feb 2023 \ parent \ on: Is the Bitcoin network starting a UASF over this inscription stuff? bitcoin
Nope. Nothing was done to discourage it.
If I'm wrong, point me to the git commit that censored it
I think I found it: https://github.com/bitcoin/bitcoin/commit/8de9bb53af32f7f6b09c06f831f2c0a7b4e95303
That git commit is called "Define dust transaction outputs, and make them non-standard"
Because of that code change (made in May 2013), Bitcoin Core began censoring transactions from the mempool if they contained very small outputs. The change was made with this comment:
"Dust" is defined in terms of MIN_RELAY_TX_FEE, which has units satoshis-per-kilobyte. If you'd pay more than 1/3 in fees to spend something, then we consider it dust. A typical txout is 32 bytes big, and will need a CTxIn of at least 148 bytes to spend, so dust is a txout less than 54 uBTC (5400 satoshis)
The minimum relay fee at the time was higher than it is now, later it was lowered by a factor of 10 and the dust limit went down to 540 sats.
reply
No, I'm aware of the dust limit. 5400sats wasn't much money back then, and they could just take it out of the bet up front making it revenue neutral. That's not why Satoshi Dice died.
reply
am I also wrong in saying Gregory Maxwell created a dust limit patch explicitly to avoid relaying satoshi dice transactions? That's how it looks to me from reading that old bitcoin talk thread. If that was the purpose of Greg's dust limit, and a dust limit became the default policy two months later, it seems unlikely that those two things happened independently. Am I missing something?
reply
What I think you're missing is that the dust limit doesn't stop a service like Satoshi Dice from existing. It just forces the service to operate in a less harmful way, by ensuring that UTXOs crated by it can be profitably spent.
The timing is just coincidental.
reply
To provide a bit of context, in March 2013 Gregory Maxwell wrote a patch for bitcoin core that censored satoshidice transactions by refusing to relay or mine transactions with outputs less than 10k sats. https://bitcointalk.org/index.php?topic=149668.msg1598216#msg1598216
This patch was explicitly called out as censorship by people in that thread (see the post by OneMiner at the top of that thread) but within a few months bitcoin merged a code change that implemented a less severe form of the same thing, making the dust limit 5400 sats. Satoshi Dice relied on its ability to create utxos below that dust limit as a way to alert users of the service if they lost. But once that change went into place, the number of dust transactions fell drastically.
In other words, censorship works. I'd like to use it once again and "dust" off this reliable old tool from our tool belt.
reply
I'm not sure it's 100% accurate to say it blocking dust transactions directly killed SatoshiDice. SatoshiDice could have keep running, it would have just cost more (min 10k sats) for each of their "alert transactions". The BTC price going up significatly in 2013 also undermined the SatoshiDice business model.
I think a similar things will happen with inscriptions, as fees rise. Looking at mempool.space, a inscription transaction costs $75+ while a simple payment transaction costs something like $0.25. If the BTC price quadruples (or the sat/B fee rate quadruples) then inscriptions become expensive quickly, while transactions remain perfectly viable for everything more expensive than a coffee.
reply
SatoshiDice could have keep running, it would have just cost more (min 10k sats) for each of their "alert transactions".
Even that isn't true. It's not a real cost. Just money they have to take out of the bet that they're giving back to the user in a few seconds when the bet completes.
reply
Thanks the clarification, I'm not an expert on the specifics. But from what I remember from around that time, is that SatoshiDice was basically "priced out" of using the Bitcoin blockchain as the transaction fees rose above a fraction of a penny.
reply
Fees rising probably killed them indeed. Also, people get bored of novel things eventually too.
reply