Avatar
freedom dev 𓅦
58b295a1a5f7b8e7d507777acbcbf7691a0b39c768da2695220a89a6da85ca67
Working on freedom tech. For hire.
Replying to Avatar mister_monster

There has been some news going around in bitcoinland about people sitting on tons of small bitcoin UTXOs that they can't spend because fees are more than the value of them. Bitcoin guys don't want to look at it too closely, because when you extrapolate this into the future that we want, you wind up with a huge problem. I'll draw you, dear reader, a picture.

Bitcoin becomes the most valuable asset in the world. It becomes the unit of account for the world, the medium of exchange for all high value trades, such as nation to nation or corp to corp, and each bitcoin is worth a ton. Block space is still limited, but demand for it is orders of magnitude higher than it is now. This means fees are orders of magnitude higher, this means that people with even reasonably worthwhile amounts in UTXOs will not be able to spend them. And if this becomes a steady state and there's no more volatility with bitcoin because it is constantly used, there is no "wait for fees to get cheaper."

So some people, including many of us, will have money we can't spend, ever. That's bad. But it's not that bad, because what comes next is worse.

First I'd like to point out that some day there will be no coinbase transactions in bitcoin. The idea is that miners will mine for transaction fees alone, that transaction fees rise to meet demand for block space. The problem I'm talking about doesn't hinge on this, but this fact does exacerbate it, it gives us a best case estimate on the upper limit of time we have to solve the problem I'm about to describe.

What it looks like we see here is that *transaction fees asymptotically approach some equilibrium that makes the system non viable long term.* My intuition tells me that that equilibrium is a function of the median transaction value, the energy cost to secure the network adequately, demand for block space, and rate at which new bitcoin are created. I say intuitively because I haven't done the math on it, but the picture is clear enough to make out the overall picture.

One other thing I'd like to point out that's pertinent: miners can send transactions for free if they mine the block their transaction is in, or if *their counterparty* mines that block, because if you're recipient to a transaction you don't care if you're paid fees for processing it, you're getting paid either way, two miners paying each other can agree to mine each others transactions to each other at any rate they like, including for free.

Worst case scenario: the fees approach the value of the transactions themselves, miners suck up all the value to pay their energy costs and then some profit if any, it isn't worthwhile for anybody to use the network to send value except miners, and can only send in blocks they or their counterparty mine. Of course, that doesn't work, everybody can't mine and get enough blocks to send value within a reasonable timeframe, so the value of the system collapses, people find something else to store and send value whatever that is. What we see then is a system much like the copper money system outlined by Saifedean Ammous in The Bitcoin Standard, where everyone adopts this money only for the power producers to reap the benefit, sucking the capital from miners to secure their network who in turn suck capital from everyone looking to transact. This is energy as money, but energy has a stock to flow ratio of 0.

"Best case" scenario: Bitcoin becomes so important to world trade that states and miners enter cartel agreements to limit energy expenditure on bitcoin and limit transaction fees between permissioned participants. Bitcoin becomes supported as legacy software indefinitely only because we rely on it for international commerce, and compute becomes highly regulated to prevent attacks on the network since security cannot be guaranteed if there's a roof on the amount of energy that can be used to secure it. Only state level actors use and mine bitcoin. That is, of course, if they continue to mine at all and not just agree to share a ledger and permission the network. Note that this is the best case *for bitcoin*, not the world, it is arguably worse for the world than the current state of affairs.

Likely scenario: similar to the worst case scenario, except that as people look to find cheaper ways to move capital around, the cost to move bitcoin approaches the cost to move the alternative and people don't just abandon bitcoin, but rather it shares it's role with something else. Right now, that alternative would be gold due to the scarcity it has. That would mean, of course, that the days where bitcoin is cheaper to move across the ocean than gold are numbered, and in fact, it's as expensive to move bitcoin 1 inch as it is to move it 10 light minutes (the theoretical limit to how far bitcoin can be transported due to the block time, that opens it's own can of worms about spatial distribution of miners and the interplay between that problem and the one I'm describing is very interesting) so gold makes more sense to send short distances while bitcoin may make more sense to send long distances.

(An interesting thought I have had is, in doing this are we discovering that the cost associated with moving gold only appears to be the result of it's mass but is the apparent symptom of something fundamental that appears as a cost to moving scarce things no matter how you do it, and does that tell us anything about what mass fundamentally is?)

Either of these 3 scenarios is an utter failure of bitcoin. Either it collapses, it becomes the new fiat, or it isn't any better than what we already have.

Now, I am not making a block size argument here. raising the block size only kicks the can down the road, you'd still run into this problem, and it has problems that lead to centralization which would exacerbate this scenario such that I think doing it only makes my best case scenario more likely, and that's really not a good scenario at all.

I'm also not arguing for proof of stake. It would put you into the same position except that the validators are the top of the food chain rather than the energy producers. It does absolutely nothing to alleviate this problem.

You might think "payment channels!" or "layer 2" or something, but this also only kicks the can down the road. ultimately you have to finalize everything on the blockchain, otherwise it isn't bitcoin, and you'd still run into the same problems. In my best case scenario it would work, but that gets us basically the gold standard back, complete with high expense to move large value, and nothing more. I would not expect such a scenario to fare better than the gold standard did, it led centralization of custody and then fiat money.

What I'm saying is that *we cannot have a block size at all.* We cannot set an arbitrary ceiling on the number of transactions that can be mined per block. We have to make it so that miners make more money the more transactions they process regardless how much each one pays them. And we can't do that if the entire history of the ledger has to be kept to ensure security while simultaneously keeping the network decentralized. Bitcoin needs cut through and a block size only limited by the latency of the network or it will fail. Ideally the entirety of the blockchain would be unspent UTXOs and we would still have programmability. Even that presents us with some problems, probably more unforeseen ones, and maybe even still the problem I've described if network latency becomes a tangible limit on supply of transactions within the block time.

Also note, above I mentioned that I think the rate at which new bitcoin are created is a factor. I don't know that this would still be an issue if there were no arbitrary scarcity with regard to block space. But it is possible that it would present an issue even with an unlimited sized block, maybe there's a reason that the only place where anything naturally occurring is provably scarce is at the edge of the universe. It may very well be "limited supply, limited block space, limited block time, pick 1."

There is no scarcity of Bitcoin except for that in the minds of people adhering to the current consensus.

There have been forks in the past and there will be in the future, can't be prevented. Forks make Bitcoin non-scarce.

At the end of the day it is not Bitcoin that matters, it's the truth that it unveils - that inflation is a scam.

Once people understand this fundamental truth it won't matter what technology is used to make trades happen.

People will figure out ways.

My rent is $150 and I can't afford to pay it anymore.

My fridge has only butter and a chunk of cheese.

You're doing something wrong with your money, because you are rich.

We will get there, it is just too good!

It's all a matter of value offering.

Nostr will become hard to ignore, then impossible to ignore.

I'm joined by guests [Mike Schmidt]( https://twitter.com/bitschmidty ) & [Rijndael]( https://twitter.com/rot13maxi ) to go through the list.

**Housekeeping**

* 00:06:34 OpenSats announce 10 new grants

**Vulnerability Disclosures**

* 00:13:40 Ledger vulnerabilities

* 00:27:26 Keystone License has been changed

* 00:29:22 A critical vulnerability has been found in LNBank

* 00:31:01 In March 2021 the FBI raided USPV, broke open every single box in the vault

* 00:35:04 Shakepay Customer Information Leaked

* 00:36:23 Controversial Ocean upgrade fixes long-standing vulnerability exploited by modern spammers

**Bitcoin**

• Software Releases & Project Updates

* 1:11:37 Bitcoin Core

* 1:19:07 COLDCARD Mk4

* 1:22:38 Frostsnap prototypes first look

* 1:29:32 BTC Pay Server

* 1:29:47 Liana

* 1:30:23 Keeper

* 1:30:29 rust-payjoin

* 1:31:18 Mempool.space

* 1:31:30 NerdMiner

* 1:31:42 AgoraDesk

* 1:32:05 Blockstream Green

* 1:32:18 Samurai Dojo

* 1:32:26 Ronin Dojo

* 1:32:59 RoninUI

• Project Spotlight

* 1:33:40 The #Hashtub

* 1:34:45 Coinselect

**Lightning & L2(+)**

• Software Releases & Project Updates

* 1:35:00 lnd

* 1:35:04 lnbits

* 1:35:08 Zeus

* 1:35:13 Phoenix Android

* 1:35:26 ldk-node

* 1:35:35 lightning-terminal

* 1:35:39 Mutiny Wallet

* 1:37:36 Breez SDK Core

* 1:37:41 taproot-assets

* 1:37:48 10101

* 1:41:20 Ride The Lightning

* 1:41:25 Stacker News

* 1:41:32 Alby

* 1:41:42 BitBanana

* 1:41:45 Thunderhub

* 1:42:08 River Link

* 1:44:02 Cashu

* 1:44:13 eNuts

* 1:44:27 Minibits

• Project Spotlight

* 1:45:07 PlebDevs Course II

* 1:45:14 ShockWallet

* 1:45:16 Ark Developer Hub

* 1:45:21 Elements Academy

**Nostr**

• Software Releases & Project Updates

* 1:46:30 NDK

* 1:46:46 Unleashed.chat

* 1:51:07 Primal

* 1:51:58 Amethyst

* 1:52:08 Snort

* 1:52:11 Coracle

* 1:52:13 Nos.social

* 1:52:15 Yana

* 1:52:18 Nostree

* 1:52:21 Civkit

* 1:52:44 Plebeian Market

* 1:52:52 Mostro

* 1:52:57 nostr-webhost

* 1:53:01 nostr-universe

* 1:53:04 0xchat

• Project Spotlight

* 1:53:09 Nostr Tech Weekly

**Privacy Software**

• Software Releases & Project Updates

* 1:54:48 SimpleX Chat

**Boosts**

* 1:55:01 Shoutout to top boosters: @vake, @qxotk, @dubravko, @agichoote, @cantillionaire.

**Bitcoin Optech Newsletter**

* 1:56:38 Highlights from recent Bitcoin Optech Newsletters

**Links & Contacts**

* Website: https://bitcoin.review/Podcast

* Twitter: https://twitter.com/bitcoinreviewhq

* NVK Twitter: https://twitter.com/nvk

* Telegram: https://t.me/BitcoinReviewPod

* Email: producer@coinkite.com

* Nostr & LN:⚡nvk@nvk.org (not an email!)

**Full show notes: https://bitcoin.review/podcast/episode-57**

I agree, for lightning, custodial is the way, less headaches.

Liquid is arguably more reliable.

The problem is that neither are solutions to the big problem here, of on-chain being unusable. Because both require trust in people not taking your money away from you.

They solve some problems, not the main problem.

In IT we have this concept called "rollback". When something goes wrong, one makes things go back to what they were before.

What about we all admit segwit went wrong?

Even Satoshi did this, he corrected many mistakes.

Replying to Avatar Seth For Privacy

# Taproot didn’t cause Ordinals ❌

I've seen the view that "Taproot caused/enabled Ordinals" commonly mentioned across Twitter, and it's one that can be extremely harmful. Many in the space would love to further ossify (prevent change) in Bitcoin and use Ordinals "spam" as the reason for doing so, but I'd argue that that would be the worst possible outcome from this situation.

This needs a lengthy explanation to properly grasp what's at play here, though, so let's get into the fun details.

## Arbitrary data in Bitcoin has always been possible

Something most people don't understand is that a system like Bitcoin is built for data storage, it's just intended for monetary data. This design made it possible from day one to include arbitrary (arbitrary) data into the blockchain, either through methods like OP_RETURN (a good place for storing arbitrary data as it can be easily pruned) or in tweaked pubkeys (a bad place for storing arbitrary data, as it cannot be pruned).

Some examples of this:

- Satoshi inscribed a newspaper headline in the genesis block coinbase (https://mempool.space/tx/4a5e1e4baab89f3a32518a88c31bc87f618f76673e2cc77ab2127b7afdeda33b)

- Luke Dash Jr. used his pool to inscribe Bible texts and prayers in 2011 in the coinbase (https://bitcointalk.org/index.php?topic=38007.0)

- Someone added the entire Bitcoin whitepaper to the UTXO set in 2013 (https://bitcoin.stackexchange.com/questions/35959/how-is-the-whitepaper-decoded-from-the-blockchain-tx-with-1000x-m-of-n-multisi)

All of these happened before both SegWit and Taproot, and there are many more cases of this type of data storage on Bitcoin.

## But I thought Taproot enabled this?

Unfortunately, there is a common misunderstanding (thanks for the troll name [@TaprootWizards](https://twitter.com/TaprootWizards) 😅) that Taproot enabled this type of data storage, thus opening the way for Ordinals "spam." In reality, this type of arbitrary data storage on Bitcoin has always been possible, but was made much cheaper to do with the introduction of SegWit in 2017.

SegWit was a major upgrade and bug fix for Bitcoin that enabled the Lightning network to be built and included a 3MB "witness" data allowance within each block w/ reduced fees for data to incentivize spending UTXOs (therefore making them prunable). More on SegWit in a fantastic post from [@River](https://twitter.com/River) here:

<https://river.com/learn/what-is-segwit/>

This incentivized portion of each transaction (called "witness" data) is intended for things like Bitcoin scripts, but can be used to store any data as long as it's done the "right" way. Specifically, Ordinals store them in an "envelope" between two opcodes, allowing the data to count as witness data and get the discount. This storage method was possible before SegWit, but now saves on fees in comparison to pre-SegWit usage.

While this of course was not the intent of SegWit, it underlines the simple fact that if someone wants to store arbitrary data in a blockchain, they will find ways to do it.

## Does that make SegWit bad?

If your first reaction is then to want to raise a pitchfork and campaign for no more changes in Bitcoin, remember this -- without the SegWit soft-fork there would be no Lightning network, no discount for users consolidating UTXOs, and instead users would be incentivized to create more un-prunable UTXOs as it's cheaper to create than to consume UTXOs w/o SegWit.

Additionally, Ordinals being stored in witness data allows those who run a node to easily prune them and not store them in RAM, unlike any method that leverages pubkey tweaking or other types of stenography to include arbitrary data on-chain. This means that the actual impact of Ordinals on those who run a node is drastically minimized versus other arbitrary data storage methods.

## If we didn't have SegWit, Ordinals would all use the UTXO set

It's extremely like that if we had never included the SegWit soft-fork into Bitcoin that the Ordinals craze would still have happened, and along with it a drastically worse outcome for the blockchain. In this alternate reality, Ordinals (and all similar NFTs) would likely be inscribed directly into the UTXO set, similar to how Stamps function today.

Some within the Bitcoin community have been asking for a removal of the SegWit witness data discount to force Ordinals to pay the same fees as all other users per byte. Unfortunately, this would have two extremely detrimental side-effects: it would disincentivize healthy UTXO management (consolidating UTXOs vs creating new ones) and incentivize Ordinals to be put in the UTXO set directly.

While putting the data into the UTXO set does cost those creating these NFTs drastically more, it also means that those running a Bitcoin node cannot prune the data, no matter what. Bitcoin relies on nodes being able to retain the entire UTXO set in order to verify transactions properly and prevent double-spends, and any data within that UTXO set must be kept in perpetuity.

That would be drastically worse for those running a Bitcoin node, and makes the Ordinals in SegWit witness data pale in comparison when it comes to negative impact on Bitcoin nodes.

## So what can we do about it?

The solution to reducing the cost of using Bitcoin is not censoring Ordinals (something that isn't even technologically possible, BTW), but rather is finally building solutions to Bitcoin's long-term scaling. Ordinals have highlighted something most of us knew would happen -- base-layer fees would become untenably high, as they have to for Bitcoin to be secure long-term.

In order for the average person to use Bitcoin, we need powerful scaling solutions like layer twos, and unfortunately Lightning in it's current form isn't the final solution. Lightning relies on every channel-owner (and thus user when done in a non-custodial manner) being able to settle back on-chain to resolve disputes, something that isn't economically feasible in a realistic fee environment.

## The solution? Covenants

Enter covenants, an improvement to Bitcoin that has been a long-time in the making and is finally picking up the steam it deserves in the space. Covenants enable both improvements to Lightning that make it drastically more scalable, and new layer two networks to be built that have different (often better) trade-offs compared to Lightning.

As this post is already getting a bit too long I won't dive into the details of covenants, but instead ask you to spend a few minutes going through this fantastic set of resources on covenants to better understand what they enable:

<https://covenants.info>

Have questions? **ASK THEM!** The best way for the broader Bitcoin "rough consensus" layer to work is for more people to step up, learn, and ask questions as they go.

That is a lot of speculation.

I just sent you an email, because your server blocks requests coming from Tor, can't apply on your website because of this.

Please check if you received it, it's about a new project.

Thank you.

Replying to nobody

The Great #Drivechain Debate with Paul Sztorc and Peter Todd (SLP533).

Official Podcast Episode: https://www.stephanlivera.com/533

Drivechain is a proposal from 2015 which has had a lot of community debate recently. Joining us today to debate this are Paul Sztorc (CEO of Layer Two Labs) and Peter Todd. We discuss a range of points:

- Drivechain and miner centralisation

- Whether you can delegate running a node

- Legal risks

- Fees and Blocksize limits

Timestamps:

00:00 - Intro

01:22 - Guests Introduction

02:12 - Paul's Opening Statement

11:08 - Peter's Opening Statement

19:42 - Paul's Rebuttal

24:56 - Peter's Rebuttal

30:47 - Guests Challenge each Other

01:30:59 - Closing thoughts

https://youtu.be/Omx2tcHGKd8

Peter Todd says "Nostr isn't decentralized".

He doesn't say that it isn't decentralized *enough*. He says that it is not decentralized at all.

Can't take him seriously after that statement.

Absolutely, people are clueless.

I see this Ordinals thing as a government and establishment funded attack on Bitcoin. The synchronicity with the ETF approval is not a coincidence.

People will trade ETF, not on-chain. Either they like it or not. Or at least that's their plan.

The alternative would be taking away incentives from miners, which is not a good scenario either.

Never underestimate smart evil people.

That wouldn't work. Since you already have in your hands whatever you bought, you have an incentive to double-spend -- and some people will do it. The Bitcoin transaction needs to confirm during your meatspace transaction. You can't drive off with your new car while the transaction has not yet confirmed.