Latest / The Bitcoin Way Podcast / BIP 110 Explained: Bitcoin's Biggest Battle
Transcript
- 0:00During this signaling period and the BIP 110 movement happening, we might see a chain split.
- 0:06If you're listening to this and you are not running a node, then you should ask yourself a question.
- 0:10You truly have control.
- 0:12Running NOTS alone doesn't prevent these transactions being broadcast throughout the network,
- 0:16but it might be a way to signal discontent with what Core has done.
- 0:20There's transactions, Bitcoin transactions happening every day.
- 0:22If more people would do that, then BlockSpace would be utilized for monetary use.
- 0:27whether you're for BIP110 or against it, at least you can see at the end of the day,
- 0:31I'm making my own decision based off my own interpretation.
- 0:45Today on the show, I have two of our very own at the Bitcoin way, Bert and Kyle. These two fall
- 0:51on different sides of the Nats versus Core BIP110 debate, but agree on many of the fundamentals.
- 0:56We are all Bitcoin monetary maximalists, so you don't have to worry about any of us being
- 1:00spammers or scammers.
- 1:02But this is the most cordial discussion and most entertaining and informative discussion
- 1:06of this debate I think anyone has ever put out.
- 1:09So make sure you tune in, pay close attention.
- 1:11You're going to learn a lot.
- 1:12And hopefully at the end, you have the information you need to decide what implementation do you
- 1:17want to run.
- 1:18And of course, most importantly, make sure that you're running a node.
- 1:21Enjoy my conversation with Bert and Kyle.
- 1:23Hey, everyone.
- 1:24And like I said in the intro, I have Bert and Kyle here.
- 1:26Gents, this is going to be a fun conversation.
- 1:29I'm going to navigate this as well as I can.
- 1:31It's going to be a little complicated, a little bit messy.
- 1:34But the goal of this, as we've discussed offline, is really just for this to be an incredible educational resource for many people who are trying to figure out what do I do moving forward?
- 1:43Run core knots.
- 1:44What about BIP 110?
- 1:45What does all of it mean?
- 1:46So we're going to try to make this as non-technical as possible.
- 1:48I did say in the intro, but I'm going to reiterate, we are all Bitcoin monetary maximalists here.
- 1:54So this is not like we, none of us are spam apologists or anything like that.
- 1:58But we want to take a nuanced perspective as we look at this stuff.
- 2:02So Kyle, you have done a lot of the background work on this episode here.
- 2:07Why don't you walk us through how we got to this op return debate, the core versus nots, all the fighting that we see online.
- 2:15Where did this all begin?
- 2:16First, I think we should talk about Upperturn and how that came about, because that leads into this conversation with BIP110.
- 2:24So Upperturn was first introduced in 2014 with a 40-byte limit.
- 2:30And the whole purpose of this was to mark an output as unspendable.
- 2:34And so because it's unspendable, the nodes can throw it away and prune it.
- 2:37And so it was created as a small, safe place to put non-monetary data so people can store data into the UTXO set.
- 2:45because the UTXO set is basically a giant database of all the unspent coins.
- 2:50And if there's transactions in there that are stored in your RAM that bloated up,
- 2:56it means your node has to store more and more data.
- 2:58And so if that data cannot be pruned or that transaction cannot be pruned because of that data,
- 3:04then the database that your node has to hold keeps growing forever.
- 3:08So the whole purpose is to keep unnecessary data out of the UTXO set.
- 3:14And then a year later in 2015, it was raised to 80 bytes.
- 3:18And then in 2016, it was raised to 83 bytes.
- 3:21And so since 2016, we've had pretty much a standard where the default was 83 bytes.
- 3:28And then that allowed node operators to, if they wanted to, they could always change that setting and restrict that to a lower amount or increase it to a higher amount if they wanted to.
- 3:42So that worked fine for a decade, pretty much, until inscriptions arrived in late 2022.
- 3:49So that's when the ordinals came around.
- 3:52That's when we had inscriptions, and they bypassed OpRoturn entirely.
- 3:57Because instead of putting that data into the prunable output, the OpRoturn,
- 4:02it started to stuff arbitrary things like images, videos, text, into the taproot witness.
- 4:08And so that piece of the transaction holds a proof of what you're authorized to spend, like signatures and scripts.
- 4:15And that was introduced by SegWit in 2017.
- 4:18But I think an important thing to mention here is that witness data gets a 75% fee discount because of SegWit.
- 4:26So for every byte of data or witness data, it costs a quarter to put it in.
- 4:33And that discount was designed to encourage moving the signatures and scripts into the witness, not to make it cheap to store images or videos and things like that.
- 4:44So, for example, if you had a four megabyte witness block, that would cost the same in fees as a one megabyte of normal data.
- 4:51But it takes four times as much data on the node operators.
- 4:56So the inscriptions basically exploit that.
- 4:59And there have been people that have talked about this for a while.
- 5:02this has been a debate for quite some bit. For example, Blockstream's director of research,
- 5:07Andrew Folstra, he posted to the Bitcoin dev mailing list and he said data storage is toxic
- 5:13to the network. But he didn't see that there was a technical way to stop that. And with the data
- 5:21carrier size of being able to limit or change how much the operator is for your specific node,
- 5:28in mid-2023, it was basically deprecated.
- 5:33So they added a code change to basically say that it only covers script pubkey, which basically
- 5:40excludes witness data.
- 5:42And before that change, you could say that that setting covered all data.
- 5:47But after that, it says that it only covers for operator.
- 5:50That's basically the main story from the data carrier size and how we got to that point
- 5:56up until around 2023, 2025 and 2024, that period.
- 6:03Bert, do you want to chime in on what happened after that?
- 6:05Yeah, I think it's first very important to distinguish between consensus,
- 6:11so what is possible on the nodes itself versus mempool policy.
- 6:16So if you look at mempool policy, which is basically if you transact
- 6:22and you send a transaction out onto the network,
- 6:26it goes into this basically waiting pool of transactions
- 6:31that's going to be mined.
- 6:33And what gets into the pool
- 6:35that is determined by all the nodes on the network.
- 6:40But there are also consensus rules
- 6:43and that's what's actually possible to get into the block.
- 6:46So those are two different things.
- 6:48You've got the space where you're waiting
- 6:50for something to get into the block
- 6:51and you've got what is actually going to get into the block.
- 6:56And there's consensus rules for what can get into the block.
- 6:59And there is, let's say, rules that you can determine on your own node
- 7:04with regards to what you want to be in the waiting area before it hits the block.
- 7:09And that's a very, very important thing to distinguish here
- 7:13because in the discussions that we had, let's say,
- 7:18up until we are now here in this BIP 110 area,
- 7:21was mostly about the mempool policy part where indeed, you know, there was a relaxation of the limit,
- 7:30what can actually be in this waiting ground.
- 7:32And the reason for this is because people can actually put something straight into the blocks,
- 7:39going straight to miners.
- 7:41And that is already happening at mass scale.
- 7:43We've got some very, let's say, not so nice miners, in my opinion, in the US,
- 7:49they are letting people just side load stuff within the consensus limits onto the Bitcoin blockchain.
- 7:57And that's purely a terminal consensus.
- 8:00Okay, so maybe if I could simplify, well, I want you guys to correct me where I might be wrong,
- 8:05because I am by far the least technical person on this call.
- 8:08So when you send a Bitcoin transaction, there are different places where you can place data,
- 8:13as maybe a simplified way of thinking of it.
- 8:15The UTXO set, though, is required for you to run a node.
- 8:18And that lives in memory and eventually you run out of space. And so you need to be able to verify spendable transactions very quickly. And so if arbitrary data, we'll call it images, videos, to Kyle's point, are bloating the UTXO set, then you have this problem that you run out of space, it becomes harder to run a node.
- 8:39Op return is sort of a compromise.
- 8:41We know people are going to have metadata or something that they might want to put into a transaction that you can then prune from your node.
- 8:49So it's not bloating the UTXO set.
- 8:51It's not taking up that space.
- 8:52I'm sure something I said, was that directionally correct, even if maybe I spoke about it in a less technical way?
- 8:59Is that a fair way of framing it?
- 9:01It's very important to, again, distinguish between what you are relaying and holding into the mempool.
- 9:08so into the pool that's going to be mined versus what is going into the set block set that are mined.
- 9:15You are always relaying in the current situation the nodes that have actually been mined,
- 9:22and that is based on consensus rules.
- 9:25Then mempool policy, you can just set freely yourself what you want to relay in your own mempool.
- 9:30And that determines, of course, on the miner side, what they are actually mining.
- 9:35So the node that the mining pool or the individual solo miner is actually running determines in their specific mempool what is going to get into the block when they mine a block.
- 9:47What is very important here is with this whole discussion, again, when you come back to the op return, the op return consensus was already on a max cap.
- 9:57There was no cap limit there.
- 9:59So if you would have a direct connection with the miners or you would be mining yourself and you have sufficient hash rate, you could just very easily fill your block with up returns, of course, very, very large transactions.
- 10:13And in the consensus rules itself, there are limits to what can be in the block.
- 10:18Now, if we would all be using Bitcoin properly, you know, as monetary maximalists, so just going back to what we initially were introduced to, I make transactions every day.
- 10:31I run a shop also.
- 10:33There's transactions, Bitcoin transactions happening every day.
- 10:36If more people would do that, then BlockSpace would be utilized for monetary use.
- 10:43Currently, there are so little use of Bitcoin that there are indeed, as Kyle is saying, very cheap transactions being able to put into, let's say, scripts on a cheaper way that can fill this space that is limited, that is kept by consensus.
- 11:02And that is actually being filled up at the moment.
- 11:05And a lot of people see this as an issue.
- 11:07But it might be the main issue that we currently have is that not enough people are using Bitcoin and that we should actually, you know, especially if we look at our clients, which are at the moment thousands, they should do more transactions, test transactions, you know, try to do some transaction on the network itself.
- 11:25Because if sufficient people do this, it will crowd out the entire problem, which is, let's say, misuse of the Bitcoin network.
- 11:35And the main thing that we can focus on with regards to using Bitcoin more is that when everyone is actually paying for actual transactions, is that these very small extra things that are added, which we see as malicious, will be crowded out directly.
- 11:57Now, I think we should go back indeed to Kyle's point.
- 12:01He was trying to set the timeline of the op-return.
- 12:05So let's say last year it was changed.
- 12:10The op-return discussion was changed a bit.
- 12:13And we went into a discussion with regards to, okay, we can set mempool policy, but that's very easily routed around, right?
- 12:20Because there are still nodes that are, you know, running different mempool policies.
- 12:25These minor operators are still allowing everything in.
- 12:29So we need to change on the consensus level.
- 12:33I think that's when I want to give it back to Kyle to talk more on the consensus level.
- 12:37I think an important point before you even get to that part is during those periods, the years before they made the change,
- 12:46which really sparked this whole debate of Bit.10 and caused it to spark that proposal for Bit.10, is the Core v30.
- 12:55And the core V30 basically before that the default for the operator was 83 bytes on the nodes So you could think that majority of nodes people that are not checking their configuration
- 13:10they just run it as whatever the defaults are, they get 83 bytes.
- 13:14And then with Core V30, that changed it to the, as Bert said,
- 13:19that it is possible to make your upper turn limit basically unlimited.
- 13:23And so they basically in v30 changed it so that the default is unlimited.
- 13:28And so we can think that the most people that when they upgrade to v30, they're not going to change the configuration.
- 13:36Let's say most people would not if they're just going to run the defaults.
- 13:40And so those nodes are running with this uncapped version where basically anything can be stored on their mempool.
- 13:48So images or whatever that gets stored.
- 13:50And obviously, as Bert was saying, that the filters get routed around.
- 13:56And because, you know, let's say I have a very conservative node, Michael has a conservative node, but Bert and some other people don't.
- 14:03They have a more liberal mempool policy.
- 14:06Then maybe I don't get in my mempool images or whatever, but maybe Bert does.
- 14:11or even in the case like Bert was saying about certain miners,
- 14:14you can just submit the transaction straight to the miner
- 14:17and bypass the nodes in general in terms of relaying that transaction
- 14:23and get it into a block.
- 14:25And so the whole purpose of BIP-110 is basically saying,
- 14:28okay, well, if the filters are just going to get routed around,
- 14:31then we will just have to implement it into consensus.
- 14:34And that's really where the whole debate came from.
- 14:37And one thing I'd say that I think is really important
- 14:40is that the miner just gets paid once,
- 14:43but the node operator,
- 14:44everyone has to store that data forever.
- 14:47And so if we don't make a stand of,
- 14:49you know, in terms of
- 14:50what are we willing to store on our nodes,
- 14:53because it's our property,
- 14:54and in 20, 30 years,
- 14:56will it become prohibitively expensive,
- 14:59both from a hardware cost
- 15:01and just from data costs and all that,
- 15:04for people to run their own full nodes,
- 15:06full archival nodes?
- 15:07And are people going to have to be forced to use,
- 15:09you know, like,
- 15:10a prune node or trust someone else's node to give them the blockchain state.
- 15:16Yeah, I see that a little bit differently because we have this consensus limit already
- 15:20where we have this four megabyte block size.
- 15:24So already there is a cap limit that is already hard enforced.
- 15:28And indeed, what we are really discussing here on the consensus changes,
- 15:32what can actually get into the node.
- 15:35And just to come back one second to the mempool, you mentioned,
- 15:38if you're on the mempool policy running different policies,
- 15:42you're actually not storing it yet.
- 15:44You're just temporarily holding that on your node.
- 15:48And then when the block is actually mined,
- 15:51that is what actually settled.
- 15:52So we did a very nice thing, Kyle,
- 15:55if you remember where you were running nodes,
- 15:57I was running core.
- 15:59And core is actually capable of doing
- 16:01sub one set per virtual byte transactions.
- 16:05So if Kyle looks at his mempool, you can see it live and very nicely visualized.
- 16:11If you run a node, you can see exactly what is waiting to be mined on your node itself.
- 16:17And if you run nodes, that's a very empty mempool.
- 16:20And if you run core and you have relaxed limits and you run basically a very free node where you accept everything, you will see a lot of transactions there.
- 16:29And you can also go sub one.
- 16:32so lower than one Satoshi per virtual byte on that core
- 16:36and then relay it through the network.
- 16:39And once that block is actually mined with the sub one,
- 16:43it will actually also be embedded on Kyle's node,
- 16:47which is the nodes node.
- 16:48And that's currently the case.
- 16:50Now, when you start to go on the consensus level,
- 16:53which Bit.1.10 is, there are a lot of transactions
- 16:56that are currently being embedded in the blockchain on core
- 17:01that Kyle is not going to accept even on his node, on his hardware itself.
- 17:07And that's basically where BIP-110 starts to come in,
- 17:10where you do a consensus change and you say,
- 17:12okay, I don't actually really don't want this on my node itself.
- 17:17And that is where we are heading for now.
- 17:19Okay, so we're going to talk more about BIP-110 and what it changes,
- 17:23but just to make sure that the remainder of the history is discussed.
- 17:27So in June 25, Core V30, or I guess it was proposed that they're going to blow out the OpReturn relay limit from 83 to 100,000 bytes.
- 17:37So basically, you can put almost anything that you want in OpReturn.
- 17:41That was when really the vocal opposition heated up.
- 17:45We saw many people begin running NOTS nodes.
- 17:49It's not perfectly, by the way, for all of our listeners, it is not perfectly verifiable if these are real individuals,
- 17:55if these are virtual machines, bots, you can't know that for certain.
- 18:01One comment I'll make is it seems to be something of a grassroots movement.
- 18:05I had Matt Hill on the podcast recently, or his episode might be coming out after this, actually.
- 18:11But one of the things he talked about was actually showing some of their revenues.
- 18:14They started selling a lot of nodes afterwards, indicating that there were a lot of people who maybe were discontented with the core move to blow out the op return limit
- 18:23in order to start running a node for maybe the first time
- 18:26and presumably to some degree running not.
- 18:28So his point was a lot more nodes actually are coming online.
- 18:32It doesn't seem evident that it's at least not all virtual machines.
- 18:36Any comments on the controversy around the op return limit being removed?
- 18:40And then I guess that took effect.
- 18:42Was that the October 10th?
- 18:45That was the big move.
- 18:47Core V30 came out.
- 18:48Everyone blamed the price crash.
- 18:50October 10th was when V30 came out,
- 18:52But the actual PR that you're mentioning, where it moved from 83 bytes to 100,000, was in June.
- 18:59And there was a lot of community backlash.
- 19:01Because in that PR as well, they basically deprecated data carrier size.
- 19:07So it doesn't really matter whether you choose to restrict it or not.
- 19:11Because now the default would be basically uncapped.
- 19:14And so when you're sending it through the network, and there's other nodes that just accept the uncapped version,
- 19:21then it doesn't really matter because they can either do that or they could just send it to the
- 19:26miner and then the miner can just put it in the block and then you have to store it forever.
- 19:31And so the other thing I think is also important to mention is that this bit.10 is temporary. So it
- 19:36only lasts for one year and then it expires automatically. So I'm not, and I don't think
- 19:41any other people within the spec itself of bit.10, it doesn't stop spam. It doesn't, this isn't like
- 19:48the end goal. But it's a way to give us time to figure out from a long-term perspective,
- 19:53how are we going to solve this problem? So would it be fair to say then running
- 19:58knots is a philosophical stance because those transactions with the arbitrary data are still
- 20:06going to be routed either directly to a miner, something like Slipstream, for example, or
- 20:10through the peer-to-peer network, because many people are going to be running
- 20:14Core v30 or have changed data carrier size to allow these larger op return transactions.
- 20:21And so running NOTS alone doesn't prevent these transactions from being broadcast throughout
- 20:27the network and for a miner getting them into the block.
- 20:29But it might be a way to signal discontent with what Core has done.
- 20:34Is that a fair way of framing for folks who are currently running NOTS or considering it?
- 20:39That's currently the case, Michael, exactly as you're saying.
- 20:42But now, of course, during this signaling period and the BIP 110 movement happening, especially during this period, we might see a chain split.
- 20:53And that's becoming very interesting because if we are going to see a chain split, I think that's very exciting for a lot of Bitcoiners because it's a very interesting time.
- 21:03We haven't seen a chain split for almost nine years, right?
- 21:07It's 2017 when we saw the user activated software.
- 21:12And that was totally different in comparison with what we are going to see at this specific activation period.
- 21:19So currently, you could see NOTs and the NOTs until 29.3.1 came about, see it as being some kind of discontent movement with core.
- 21:32And I agree, you know, it should have been taken more seriously with regards to doing a change on the mempool policy.
- 21:42There should have been more insight with regards to governance structure on the core side and what you actually are doing on the core side.
- 21:52I think it's in that sense a poor management, let's say.
- 21:56But the current direction where we see NOLS slash BitPunk 10, where we basically have a single person controlling that implementation, a single person who has the merge access, is also a huge risk.
- 22:11And I think it's very nice that Kyle is saying, yeah, it's temporary and we just need to figure it out.
- 22:16Yes, I think we need to figure out how we want to continue on Bitcoin in and by itself.
- 22:20but the current direction has risks.
- 22:23And that's something that I think we really have to talk about
- 22:26with regards to if a chain split occurs,
- 22:29that you know what you are doing,
- 22:31what are you actually running,
- 22:33and what could the impact be.
- 22:35Okay, so this is where the rift lies between the two of you.
- 22:40You guys, I think it would be fair to say
- 22:43you agree on the history of what's happened.
- 22:45You both have your own issues
- 22:47with the way things have played out thus far.
- 22:49and where you seem to part ways is specifically on running knots.
- 22:55So Barrett, I'm going to let Kyle sort of run with this first,
- 22:58and I want you to respond to him.
- 22:59But running knots, but then maybe more significantly, BIP-110.
- 23:04So Kyle, why don't you describe what BIP-110 is?
- 23:08What does it do for this approximately a year?
- 23:12And why is it something that you find appealing?
- 23:16And then Bert, you get to explain what some of those risks are that you believe exist.
- 23:21Sure. And I just want to mention something on what Bert said about the chain split risk is that it is a risk with any user activated software.
- 23:29So I don't think it's something specific to BIP-110.
- 23:31And if we look in the past, like SegWit, BIP-148 was actually much more new in terms of what it was doing was much different from today with BIP-110, which is actually just constricting to what we had a year ago.
- 23:48But yes, it is also temporary.
- 23:51So there are obviously differences with that.
- 23:54But I think the other thing is that the miner revenue with the inscriptions of what they would lose, let's say, in this year period, if Bit.10 is activated, then I don't really see why a miner would sustain a chain split over a tiny percent of spam revenue.
- 24:10I'm not sure, Bert, if you disagree with that.
- 24:12Yeah, so now this is becoming a bit difficult, I think, for the listener to understand.
- 24:17There is, let's say, a chain split risk on both sides.
- 24:23Let's say yes.
- 24:24Explain the concept of a chain split.
- 24:26Explain what that means exactly.
- 24:27I mean, I think it seems self-evident to us probably, but for someone who's listening.
- 24:32Yeah, so you have very much restrictions on BIP-110, what it accepts on its own nodes.
- 24:39So the people that are running BIP-110 will say when a miner was running Core or Libre Relay or one of the other Bitcoin node types, a block which doesn't fulfill the consensus of these NOTs BIP-110 nodes.
- 24:56That block will actually not be accepted on the NOTs nodes with the BIP-110 activation.
- 25:03So at that point, they will only build forward on their own block that was or has to be mined by a BIP-110 signaling miner that is actually running BIP-110 and only accepting the blocks under the accordance of the BIP-110 consensus rules.
- 25:25Now, the expectation is that not the majority of miners might go along with running BIP-110 and heavy restrictions on their blocks that they are mining.
- 25:39So what could then occur is that there are some miners that do, some miners that don't, and then the BIP-110 miners will only build forward on their restrictive blocks.
- 25:51while the ore or Libre Relay or other miners that are much more liberal and much more open to mine everything will just build forward on everything They have no restrictions so they will build forward And then the question is
- 26:08who is going to be the majority? And that is what a split basically means. We will get
- 26:15two Bitcoin networks where either one of them, let's say, wins the race of having the most
- 26:23proof of work and most blocks at the end of a certain period.
- 26:28And at the end of that period, it is determined if it's either Bit.1.10 or the current situation
- 26:35where we are.
- 26:37And that split could mean that if you are on a Bit.1.10 node and you're actually doing
- 26:43transactions where blocks are only built on the conservative side, that you are actually
- 26:49splitting off the actual Bitcoin network and you're in a different split of the network and
- 26:55you reside there with your transaction. So that's why in general, I think that's what both Kyle and
- 27:02I, but also the broad technical team within the Bitcoin way has concluded, it might be wise if
- 27:09you're not very tech savvy to maybe not do a transaction during the activation period if you're,
- 27:15for example, running bit.10, but also if you're running core, again, it might not be the best
- 27:23period to do transactions because there might be some chaos with regards to this split.
- 27:29And in general, it might then make sense to think twice about what you are actually running and what
- 27:39is actually happening. And I think we need to supply us with some really nice resources that
- 27:43we already discussed before this recording, where you can actually see what happens with
- 27:49what percentage of mining rate is actually signaling a certain direction.
- 27:56And this will give you more clarity of what might happen.
- 28:00But we don't know.
- 28:01Kyle doesn't know.
- 28:02I don't know.
- 28:03And the entire Bitcoin way team doesn't actually know.
- 28:07And I think that is very important for us to emphasize that we can see a little bit of
- 28:12chaos in August, and people need to be aware of that.
- 28:16Yeah, and I also say that if we look at Segwit, for example, for a long time, there wasn't
- 28:20signaling until the last period.
- 28:22So I agree with Bert that we shouldn't assume anything until we get closer to the activation
- 28:29date and then figuring out from there what to do, because we don't know what's going
- 28:33to happen.
- 28:34And signaling can happen very quickly from the miner side.
- 28:37But one thing I also think is worth mentioning, if the chain does split, people should not
- 28:42be afraid in the sense that they're not going to lose your Bitcoin. You're going to have the coins
- 28:47or the keys to control the coins on both sides of the chain. So nobody is losing any ownership of
- 28:52the Bitcoin that you already have. And just to be a little bit attached to that. So in my specific
- 28:59personal situation, I run a Lightning node. And let's say that that chain split does occur and I
- 29:05would be running BIP110 with my Lightning node. I might indeed be in the chain split of BIP110
- 29:11and then I basically disconnect with my peers
- 29:16that are still on the other network.
- 29:18That means that you get forced closures on your Lightning node
- 29:21and that costs quite some money.
- 29:25So there are some risks for the more advanced users,
- 29:28but we expect them to be the people that understand this risk anyway
- 29:32and would be careful with regards to this split risk.
- 29:37So it would now be a good time.
- 29:39I pulled this up on my screen.
- 29:40these different scenarios for how this could play out. So scenario A is BIP-110 activates with
- 29:46majority hash rate. Kyle, do you want to walk through what all this means and maybe talk through
- 29:51what people might anticipate? So if BIP-110 activates with majority hash rate, then obviously
- 29:56if you are running NOTS with the RDTS, RDTS is a synonym for BIP-110. It stands for reduced data
- 30:03temporary software. That's just the name of what BIP-110 is. So in the case that BIP-110 activates
- 30:09with majority hash rate.
- 30:11We're looking here at the risks.
- 30:13If you're running NOTS and the BIP-110,
- 30:16then there's pretty much no risk there.
- 30:19You are basically enforcing all of the BIP-110 rules
- 30:22and then you would be on the longest chain.
- 30:24And so if you're using 29.3 core or core V30
- 30:28or NOTS without BIP-110,
- 30:31then basically it would be recommended
- 30:34that you upgrade your node.
- 30:36And you basically, if you don't upgrade your node,
- 30:38then you're basically trusting the miners.
- 30:41If on that chain they're producing, for example, an invalid block,
- 30:46you would be able to see, let's say, an invalid transaction on your node, for example,
- 30:51that is not actually there because you're not on the right chain effectively.
- 30:56Okay. And then if you're running an earlier version of Core, Core v30,
- 31:02maybe just kind of describe some of these, or Barrett, if you have any comments.
- 31:07If you're running core 29.3 or B30 or NOTs before without BIP110, then your node is just following the longest chain.
- 31:15So you're just trusting the miners and your node is not enforcing the rules.
- 31:18The whole purpose of running a node is to enforce the rules.
- 31:21So your node basically cannot confirm from a consensus perspective what those rules are.
- 31:27And so you're just trusting what the miners are giving you effectively on your node.
- 31:31One very important detail here, you see that at the top, BIP110 activates with majority hash rate. If it doesn't activate with majority hash rate, there is much more risk. And that's the next page, where indeed, if you're then running BIP110, then you get into a fork. And that's the chain split, which we were basically discussing.
- 31:53Right. And I think also the whole bet behind Bit.10 is that the miners will not sustain a chain split for a tiny percentage of the revenue, which is driven by spam and these JPEGs and ordinals and things like that.
- 32:09And so the idea would be that, let's say it activates without majority hash rate, that if you think about an economic node, people that are using Bitcoin, paying with Bitcoin, receiving Bitcoin with their own nodes, that they would end up moving over to that BIP110 chain because there's no point to go on the other chain.
- 32:29and like i said before that this is a temporary activation so it's not something that would last
- 32:34forever but it is something that that is a trade-off if you are going to run knots with
- 32:39bit 110 you need to understand that in the event there is a chain split you are basically betting
- 32:45that there's going to be people moving over to that chain and if that doesn't happen then you're
- 32:49basically on a minority fork effectively and then that goes back to bird's points that you should
- 32:54understand the risks associated with that okay and that and that's the user activated soft fork
- 32:59is that migration. Is that correct?
- 33:03Right.
- 33:03And then obviously if it activates without majority hash rate,
- 33:08all of these other older versions of Core, Core v30,
- 33:11you're on the majority chain.
- 33:13There's really nothing problematic about that.
- 33:16And so the big question is, which is it going to do?
- 33:19And are you going to be prepared?
- 33:21Could maybe you guys talk a little bit about if you're a node runner,
- 33:24let's say you're running NOTS, you're signaling BIP 110,
- 33:27and BIP-110 does not activate with majority hash rate
- 33:33or it activates without majority hash rate,
- 33:36what do you do?
- 33:37Is there like a period of time that you waited out to see?
- 33:39To Baird's point earlier,
- 33:41you don't send transactions during this period.
- 33:44What should people be thinking about here?
- 33:47So I think it's wise to not upgrade,
- 33:51let's say to the latest version of Core.
- 33:54It's not wise to upgrade to the latest version of Nots.
- 33:57that's actually running Bit.10 because you can just wait this out.
- 34:01So you can be the Switzerland, let's say, in the wars, right?
- 34:05So you can just sit back, relax, and enjoy the show
- 34:09and see whatever is going to happen.
- 34:11And for sure, your Bitcoin is just sitting, let's say, in self-custody.
- 34:18You are running a node.
- 34:19You might be signaling either an earlier version of nodes
- 34:23or signaling an earlier version of core.
- 34:26But during this period, if you don't do much, then there is no real risk in any fashion because you're not transacting.
- 34:35So you're not in any of the blocks where some of this chaos ensues.
- 34:39Now, if you want to be at the forefront of the Bit110 and you want to signal and you still want to use your Bitcoin lavishly during this period, there is this little risk of being in this chain split.
- 34:54and then of course again your bitcoin will be in this chain split and then you might be able to call
- 35:03us at the end you know i'm in this chain split and i don't know what to do if you're not technical
- 35:09so we prefer that not to happen we prefer people to just remain on a conservative stance watch what
- 35:18happens. And then when that period is over, it's a signaling period that will take a couple of
- 35:24weeks. When that is over, then you can upgrade if you like. But being conservative has always been
- 35:31one of the best ways if you're just a hodler and not a very active participant in the network,
- 35:38which currently most of our clients are. They are mostly hodlers, not people that are daily
- 35:42transacting on the Bitcoin and on the Bitcoin blockchain itself.
- 35:47Yeah, I think if you're going to be running, for example,
- 35:51the older versions of Core or the older version of Nuts without the Bit.10,
- 35:54if Bit.10 activates with majority hash rate, you will still be on the same chain.
- 35:59If Bit.10 doesn't activate without majority hash rate,
- 36:03then obviously you'd still be on the majority chain.
- 36:06So there's no real change from the status quo.
- 36:08I think if you want to make the choice,
- 36:10Obviously, I think everyone should just do their own due diligence and education on what they want to choose.
- 36:16But ultimately, if you do choose to run NOTS with BIP 110, then the whole thesis is that if BIP 110 activates with minority hash rate, that your bet is that the miners are going to follow the economic activity.
- 36:31So merchants, users, exchanges would move to that chain and use that.
- 36:36So the node operators are basically forcing the miners to comply by threatening to reject any non-signaling blocks that they produce.
- 36:44And I think that's, at the end of the day, the decision that people have to make.
- 36:48And like Bert said, if you don't understand this stuff, if you think that this is too complicated, then it's best focus on being neutral.
- 36:57Don't do something that you're not really sure of.
- 36:59So I think that's the main thing that if you're watching this and you're still not sure, it's better to be neutral than to run something that you don't really understand and then be in a situation where you need help and you don't know what's going on.
- 37:14And then you're in an uncomfortable situation.
- 37:16So just to spell it out, the most neutral you could be might be something like running Core v29, where you're not indicating support for Core v30, but you're not taking on the risk that Baird outlined, which, by the way, I want to dig into more of being on an implementation with effectively a single maintainer.
- 37:37That's what you would define as like the most, that's plain Switzerland, is running something like Core v28, Core v29. Is that correct?
- 37:44Yeah, and that's the conservative approach and you just see what happens.
- 37:50And coming back to the beginning, I think it's very important that if we really want to, let's say, kill the spam and get rid of all this stuff that is basically polluting the network, we need to start doing this.
- 38:05I grabbed this specifically, which is called a coin join.
- 38:10And people should start to dig into that because if sufficient people start to run coin joins and to anonymize, even though it's a little part maybe of their stack, it's active use for Bitcoin.
- 38:22So you constantly basically mix coins and you create a growing anonymization set of coins on the network.
- 38:29And if that group of anonymized coins is large enough, it becomes almost impossible for analysis companies to actually, you know, get back to tracing who's actually holding which coins, which is currently the majority with regards to all the KYC policies, especially where I'm from in Europe, but also in the US.
- 38:50And the amazing thing is if we actually focus on that part you know privacy security and using Bitcoin in and by itself then we are for sure going to win And that something that I really missing We are really diverting into a discussion which sounds quite you know like oh there an emergency on Bitcoin
- 39:13It's not an emergency.
- 39:14That's not how I see it.
- 39:15I think the real emergency that we have is that we're not using it enough and we could use it very, very nicely by doing coin joins,
- 39:24doing anonymization with our transactions and then using the network properly and therefore
- 39:31pushing the fees up a little bit and crowding out all the stuff that we don't like to see there.
- 39:38I agree. Definitely use your Bitcoin. Okay, so guys, I've got a question for you. I'm reluctant
- 39:42to ask this because I don't want anyone to take away like that we're putting odds on anything. But
- 39:49if you were to bet based on what you're seeing in terms of signaling, activation, growth of knots,
- 39:56online discourse, all of these variables, what do you think is going to happen during this
- 40:01activation period? And no one should take this as like, you know, a crystal ball, but I'm curious
- 40:07if you guys have any. I don't know. I don't know. This is the amazing thing. I don't know. And you
- 40:13have to be honest if you don't know right like i'm also just trying to put it in the right words
- 40:19so for the general public and i think kyle is doing it exactly the same from his perspective
- 40:25i'm doing it from my perspective but in general i i don't know what exactly is going to happen
- 40:31and that's also why i think it's wise to not be at the forefront uh with maybe some transactions
- 40:38going into a chain split.
- 40:40If you are not 100% sure what is going to happen there.
- 40:43And I think the people that are saying,
- 40:46I know 100% sure what's going to happen,
- 40:49you have to be careful with that kind of stuff.
- 40:52We've seen a lot of people promising a lot of stuff in Bitcoin before.
- 40:56And that turned out in general quite risky.
- 41:00Yeah, I agree.
- 41:00I think, like you said, I don't think anybody knows.
- 41:03And I think for sure, both on the side of if you're overconfident on BIP 110, but also on the other side, if you're overconfident that BIP 110, that it will just go away.
- 41:14This is similar to how we got here in the first place, where when they merge these changes, these controversial changes, and they just think, you know, people are just going to have to deal with it.
- 41:25And then it turns out, well, no, people are not just going to deal with it.
- 41:28They're going to come up with solutions to that problem, which maybe are not perfect, but there is a significant amount of people who are not just going to go along with it.
- 41:37But I agree completely that nobody really knows what's going to happen.
- 41:42I see a lot of times people look at the signaling numbers, but SegWit had near zero signaling for months before there was a big change right beforehand.
- 41:51And then that caused BIP-148 to go through.
- 41:54And I think personally that the temporary nature of BIP110 limits the downside in both directions.
- 42:00So that if for whatever reason, this is not the path forward, then it out of expires in one year.
- 42:09And to me, I personally run BIP110 because I think Bitcoin is money and it should only be used for money.
- 42:16And we should make a stand for that.
- 42:18but I definitely understand
- 42:20Bert's point of view
- 42:21and other people that are skeptical
- 42:23or do not want to run
- 42:25Notts or BIP 110
- 42:27and another thing
- 42:29I also just wanted to mention
- 42:30just for clarification
- 42:30is that from let's say
- 42:32a call a neutral perspective
- 42:33if you're not
- 42:34if you don't want to run BIP 110
- 42:36you don't necessarily have to run
- 42:37core like the older versions
- 42:39you could also run
- 42:40an older version of Notts
- 42:41if you still have
- 42:42that philosophical understanding
- 42:44of I want to
- 42:45I don't want to store spam on my node
- 42:47But I also don't want to bring it at a consensus level.
- 42:51And I think it goes back to Michael's question about philosophically, if you're running NOTS, you are basically saying, I don't want to store spam mascot on my node.
- 43:02And BIP-110 is just going a step further and saying, I don't think at a network level, at least for a year, there should be anyone, any node storing this data.
- 43:11So we've been talking a lot about BIP-110 and the possibility of activation.
- 43:17Let's dig in a little bit further on what exactly it does at the consensus level.
- 43:22Kyle, you shared seven rules would change at the consensus level if BIP-110 were to activate.
- 43:28Could you walk through as I'm looking at these and I'm like, okay, I can sit down and think about this really hard, maybe kind of grasp it, but try to make this as non-technical as possible.
- 43:38Could you walk through these and then interject throughout as you, you know, and by the way, so I know.
- 43:43So as someone who is signaling BIP-110, Kyle, you're going to probably frame these in a more positive light.
- 43:50Barrett, you've got concerns about this not being the solution.
- 43:53So maybe you interject with some of your issues with any of these.
- 43:58Yeah, sure. We'll just go through one by one.
- 44:00So BIP-110, like Michael said, it adds seven restrictions at the consensus level.
- 44:05Obviously, this means that these are rules that determine which blocks are valid.
- 44:09So this is very different from mempool policy relay rules, which just control what your node passes along the network.
- 44:18So any blocks during this period of BIP-110 of activation, any blocks that violate these seven consensus rules will be rejected by nodes that are running BIP-110.
- 44:29They're not just filtered by individual nodes.
- 44:32They're actually just blocked and they cannot be added to the blockchain.
- 44:37So the first rule is the output size cap basically limits upper turn to 83 bytes.
- 44:45And this goes back to what Bitcoin was a year ago and over 10 years was at just 83 bytes.
- 44:52And this is at a consensus level limiting upper turn.
- 44:56So basically what your node can store from a data perspective, not only from the node perspective, but also from a block perspective.
- 45:04if there are any transactions that have up return over 83 bytes will be blocked.
- 45:09And so any monetary transaction of Bitcoin will be accepted.
- 45:14But if you're storing large amounts of data, videos, text, and so on,
- 45:18this basically gets blocked from being added to the blockchain during this one year period.
- 45:23Bert, do you have anything to add for this one?
- 45:25Yeah, I always have a problem with images and videos stored on.
- 45:32That sounds like you basically have videos and images stored on Bitcoin.
- 45:40Either way, everything is in that sense interpretations of ones and zeros, which I really, really have problems with.
- 45:47And this comes back to a specific part where letters were sent out to the mining pools, large mining operators by, let's say, Ocean slash Luke with regards to the whole CSAM debate, which we saw before BIP.10 actually came about.
- 46:05And the risk here is that this path that we are taking with regards to Bit.10 is that we see restrictions on the consensus level, where we also open a box of Pandora with regards to legal framing.
- 46:20When you say, oh, there are people that are running certain hardware that can store information that is illegal and that can be shut down.
- 46:30Now, this can, of course, extend.
- 46:32Now, it's up return and some of the other things that Kyle is going to walk through.
- 46:37But it can also extend into other areas where you can think of the fungibility of Bitcoin in and by itself, where we're talking about certain people or certain countries having certain amounts of Bitcoin on addresses where you could go in that direction, which I find very risky in and by itself.
- 46:56Well, one thing I think is important to mention as part of BIP 110 is that any UTXOs before the activation date are grandfathered in.
- 47:05So they're still spendable.
- 47:07But any transactions that want to occur in the future or during that BIP 110 period of one year, those are going to be blocked by these rules.
- 47:17So if, for example, there is some entity that has one of these UTXOs that let's call it would be blocked or transactions that would be blocked during the one year period, if they add the UTXO before the activation height, then that will still be spendable.
- 47:34Going to rule number two, this is the data push and witness element cap of 256 bytes.
- 47:40So this is a pretty big one.
- 47:41This is basically saying that it limits any individual piece of data in the witness, which is primarily where these ordinals and inscriptions were stored, to 256 bytes.
- 47:52And that's more than enough for multi-sig, for any type of legitimate Bitcoin transaction, but not for embedding an image in one continuous piece.
- 48:02And so that goes back to what Bert was saying about what are we willing to store on our nodes.
- 48:08And I think one of the main things in the spec of BIP 110 is that this is not going to stop spam.
- 48:15It's not going to stop steganography and ways of putting bad stuff on the chain.
- 48:20That's still going to happen.
- 48:22But if I'm running a node, and not only from a legal perspective, because if I don't care about the legality about it,
- 48:28Or if I live in a jurisdiction where maybe the laws are more liberal, that might not matter.
- 48:33But just as an ethical and a moral perspective, if I know that I have to store certain data that I don't want to on my node just to download the Bitcoin blockchain so I can validate it myself, that's going to cause people like me and others to not run a node because I don't want to store that data.
- 48:50I find that abhorrent.
- 48:52And so if that becomes the case where there's this bad data on the chain, let's say images or videos that I don't want to see or I find are morally not good, and I have to store that to run my own node, that's going to stop people from running it.
- 49:09And that's just from a moral and ethical perspective.
- 49:11If there are jurisdictions that have legal ramifications for holding certain of this data, for example, CSAM, then it could become something where the law could go after you.
- 49:23And obviously, there is no court cases that we've seen in the past about this.
- 49:27But there is data, CSAM data on the chain already.
- 49:30They've done investigations on that.
- 49:33But it's not something that's contiguous in your note.
- 49:37So you would have to use a separate tool to put that together.
- 49:40And now if you're in your node, there's contiguous data of this videos or whatever, it becomes a lot more trickier from that perspective.
- 49:48So what I think is very important in what you just explained, the witness data is then basically capped.
- 49:54So it's becoming less wide.
- 49:56So, of course, if malicious actors still want to embed a lot of data, they will just cut it into smaller pieces and still, you know, use Bitcoin with regards to using this specific type, but just the smaller chunks.
- 50:10So the real problem is it's very easily circumvented.
- 50:14And the other issue you have here is that you are actually stopping some operators from using some of the functionality that they are using currently.
- 50:23So specifically, for example, Anchor Watch, but also some very advanced features with regards to Taproot Miniscript, where I've personally also worked on, is where, for example, Liana, which is also a wallet that very tech-savvy people might use, is that you can build certain setups where you can obfuscate your key structure.
- 50:45So the key structure is not public.
- 50:48That's the new privacy features that are actually enabled by Taproot.
- 50:53And you are not revealing all of your signers when you do a transaction.
- 50:57This not only increases privacy, but this also creates less weight in the actual larger multi-sig transactions.
- 51:05And this is specifically interesting for larger holders that want to be very private about how many keys there actually are and how they transact.
- 51:18And this is all working in practice.
- 51:20And this will not work anymore when Bit110 activates.
- 51:23And that's why some people say this is a very niche scenario.
- 51:26And, of course, it's still niche because exactly as one, we are testing all these features.
- 51:32There's just a few wallets that are actually capable of doing this, but we expect this to be rolled out more broad.
- 51:40And this will bring a huge privacy increase on holders with large sums, with complex setups in and by itself.
- 51:49So this witness part is, in my opinion, it's debatable and it's questionable if you want to actually do this.
- 51:58But just to be clear, are you are you referring to the the you said
- 52:02mini script? Are you talking about like the no? No?
- 52:04for like the tap leaf construction?
- 52:08No, just the data itself.
- 52:11So the size when you go through larger setups.
- 52:15Like a larger multi-sig setup?
- 52:17Yes, correct.
- 52:18Okay.
- 52:19Yeah, that's basically above eight keys.
- 52:23Correct.
- 52:24But anything below that seven keys, three of six,
- 52:27three of five, two of three, multi-sig still works.
- 52:29So that is true.
- 52:30There are some more advanced setups.
- 52:32I think AnchorWatch is one of them using 10 keys.
- 52:34And that would be 243 bytes.
- 52:37That would be above the 256 byte limit that Bit.10 would be constraining.
- 52:41But obviously, this is only temporary.
- 52:44And hopefully, we can figure out a solution to be able to stop this spam debate without needing these rules for a longer period of time.
- 52:54Okay.
- 52:55Number three, what do you got, Kyle?
- 52:57No spending undefined witness versions.
- 53:00Bitcoin has different versions of how witnesses work.
- 53:03Version zero is SegWit.
- 53:04version one is taproot. Versions beyond that are undefined and reserved for future upgrades.
- 53:10Right now, they have no rules on their data, meaning they could be abused for unlimited data
- 53:14storage. BIP 110 blocks spending from these undefined versions during the temporary period.
- 53:19Any future upgrade would need more than a year of coordination anyway. So this doesn't block
- 53:23anything real. I think that that's more of a minor one. I'm not sure, Bert, if you have anything
- 53:28to say about that. I'll let you finish the list first. That's good. For rule number four,
- 53:33no taproot annex. The annex is an extra data field in taproot transactions with unlimited size
- 53:38reserved for future use. And so this is blocked since there's no legitimate use for this today.
- 53:44Rule number five, control block cap. Taproot lets you set up multiple spending conditions
- 53:50organizing a tree structure. So this is basically limiting the conditions for certain complex
- 53:58transactions. So this can be limiting for projects like Bitfm, which is working on advanced computation
- 54:06on Bitcoin. But there's no real world transactions on Bitcoin today of Bitfm, at least that I'm aware
- 54:12of. And so that one year expiry means that limitation would end before Bitfm is likely to
- 54:17launch. For rule number six, we have no Ops, Access and Taproot scripts. These are placeholder
- 54:22instructions reserved for future upgrades, no legitimate use today. So those are blocked.
- 54:26And then the last one, rule number seven, I think this one is an interesting one.
- 54:31No op-if or op-not-if in Taproot scripts.
- 54:36So op-if lets a script choose between two different code paths based on a condition.
- 54:41This is useful in older Bitcoin scripts, but Taproot was specifically designed to replace it.
- 54:47So in Taproot, each condition gets its own branch in the tree, and only the branch you actually use is revealed on the blockchain.
- 54:53Using op-if inside a Taproot script is redundant because you're publishing code that never runs,
- 54:58which is exactly what Taproot was built to eliminate.
- 55:00Op-if in Taproot scripts is commonly abused to embed data that gets skipped during execution.
- 55:05Now, I actually put up a PR in the Rust miniscript that got merged by Andrew Polstra.
- 55:13And basically, it adds a fix whereby if you currently use op-if in a Taproot script,
- 55:19it allows you to compile these conditions into separate branches automatically.
- 55:25So it gives you the same wallet functionality you would have before Bit.110
- 55:30and allows you to do so where you don't need OpF.
- 55:35So for any developers that currently use OpF in their Taproot scripts
- 55:38and they're looking to see how can they continue to have the same functionality
- 55:42during the Bit.110 period,
- 55:44they can just use that new functionality in a mini script.
- 55:48But those are the seven rules.
- 55:50You have anything to add, Bert?
- 55:52Yeah, so you mentioned a couple of times,
- 55:54these are temporary solutions.
- 55:57And I think it's very important to come back to that.
- 56:04It's seen, I think, if you look at it,
- 56:07how it pushed how many fast updates we saw when the first Bit docs were starting to be released There were also some serious very serious Bitcoiners looking at it
- 56:20And there was quite some quick iterations there.
- 56:24But most people that are, let's say, on a longer timescale,
- 56:30trying to be as serious as possible with regards to a more than $1 trillion network,
- 56:36don't like to see temporary solutions that are almost like a hip-shoot solution
- 56:43to something that will not kill Bitcoin.
- 56:47I don't know how you look at it, Kyle, but if Bit.110 does not activate,
- 56:51will Bitcoin die in any short term?
- 56:55No, I don't think so.
- 56:56But I think the use case of Bitcoin as money is going to take a hit from that perspective
- 57:03because then it says there is a legitimate use case
- 57:06for storing data on nodes.
- 57:09And if you're running an IPFS or something else,
- 57:11some other data storage, decentralized data storage protocol,
- 57:15you can delete or you can remove certain data
- 57:18from that node you're running.
- 57:19But with Bitcoin, you cannot.
- 57:21Every single person in the future will have to store this data
- 57:24that could be morally apprehensive.
- 57:28And what if we start to use Bitcoin more,
- 57:30as I mentioned a couple of times already,
- 57:33I certainly don't disagree with that. I mean, I think everyone should be using Bitcoin more, but I don't see how that would affect Bit.110.
- 57:40But in the short term, as you mentioned, it will not kill Bitcoin. And I think it's very important that we get to a solid solution for the long term.
- 57:48And we all need to work on that.
- 57:52And I think, indeed, we both agree that core is not a very nice path that has been taken there.
- 57:59But also not for sure, as I mentioned before, with a single person that has merge access is an insane risk, too.
- 58:09So we have to really think about...
- 58:13There's a lot to work on, basically.
- 58:14There's a lot of improvements to make all around.
- 58:16And I think something very telling is that this issue has been around for many years.
- 58:22And only now in December, this BIP 110 was proposed and accepted in the BIPs repo.
- 58:28And we've had six months or more now.
- 58:31And even before the BIP 110, the proposal was added into the BIPs repo and accepted.
- 58:37This debate has been going on for far longer than that.
- 58:40And we still don't have anybody else really coming out and saying, this is our solution.
- 58:46We've seen some other node implementations talked about, for example, production ready, although they don't have a client that you can run.
- 58:53There are obviously governance structural issues with core, as you mentioned, and other people have said the same thing.
- 58:59Same with NOTS, with Luke being the only maintainer there.
- 59:03But ultimately, I think at the end of the day, and also the fact that it's temporary, is that this is not the end result.
- 59:10We need to figure out how do we solve these issues.
- 59:13We need to move forward and basically figure out how do we solve this from a long-term perspective?
- 59:20How do we fix these issues?
- 59:23And I think more Node implementations are clearly better than just having everyone corralled into core and then they make a change that everyone has to accept.
- 59:31I love that you say corral into core.
- 59:33So I think it's very important here.
- 59:35There are some other Node implementations.
- 59:37You already mentioned production-ready, but it's not production-ready.
- 59:40And the nice thing is that you actually have Libitcoin, which has been under development for over a decade, which looks really, really solid.
- 59:49And we need more people to actually also work on that and focus on that.
- 59:53We need multiple implementations where there's more effort being put in so that we don't see the current binary choice of like you either run NOTS or you run Core, but there's nothing else.
- 1:00:04we would like to see much more than that publicly available and easily accessible for node runners,
- 1:00:11which will open up basically people being able to participate in the network even more easily And I think that the most positive node in that sense because everyone is now getting aware of how important it is to run a node and that you actually can become fully sovereign when you run a node
- 1:00:35And that's why I'm wearing this little pin, which says node runners will inherit the earth.
- 1:00:39In the end, if you're not a participant, you are relying on someone else.
- 1:00:44And that's not what the goal of Bitcoin is.
- 1:00:47The goal of Bitcoin is to become sovereign.
- 1:00:50And that's what this whole discussion in the end will also make sure that you all become because whatever path is being taken, Bitcoin will get stronger and we will see more adoption of Bitcoin through it.
- 1:01:04Yeah, one thing I'll add before you go, Michael, is just we're all having this conversation about nodes and all this stuff.
- 1:01:11But I think what's really important is if you're listening to this and you are not running a node, then you should ask yourself a question of do you truly have control over what you see on your wallet, for example.
- 1:01:23And if you're just trusting someone else, then maybe they go core, maybe they go nuts, maybe they have bit.10, maybe they don't.
- 1:01:29But you have no say if you don't run your own node.
- 1:01:31So I think that's really important to come out of this conversation. If you're not running a node, ask yourself why not, because that's the whole purpose of Bitcoin, not to trust someone else, not to give them control over your actions.
- 1:01:43Yes, completely. I think we can all agree we need more nodes online. If you want to be a sovereign individual, you need to run a node. And hopefully we've given you some takeaways here to consider what you might run.
- 1:01:54So quick question for you, Kyle. So if you were to frame the objective of BIP-110, do you view it as a solution, a tactic designed to give us more runway to find a solution, or just maybe a year-long period to keep some of the scammers or spammers, however you want to define them or describe them, away that they go chase some other cryptocurrency and go
- 1:02:24know, dump on their projects or whatever?
- 1:02:26Or is it some combination of those things?
- 1:02:29I think it's a combination of those things.
- 1:02:33Ultimately, it exists because filters are going to get routed around.
- 1:02:36And so if we want to figure out a long term solution, we at least have to cap the potential
- 1:02:42gap that has now been brought about by v30.
- 1:02:47So that means we have to do at a consensus level, because I think if BIP 110 came out
- 1:02:51and said, we're going to do this permanently, which again, some skeptics are like, why is it
- 1:02:56temporary? If it became permanent at the consensus level, I think that would, I mean, we're already
- 1:03:01having a lot of debate and controversy around Bit.10. But if it was permanent, I think it would
- 1:03:05be way worse. And I think it would have less, much less support. But the fact that it is temporary,
- 1:03:10that it does out or expire, in my head, it's not a permanent solution. It's not the long term
- 1:03:15solution. But it is something, even if it's not perfect, we need something to make a stand that
- 1:03:21Bitcoin is money. We've been having this conversation for many years, and it seems like
- 1:03:25nobody wants to listen to us from the core side. And obviously, NOTS is not the most,
- 1:03:31from a governance perspective, just like core is. There's issues there, obviously. But
- 1:03:36the idea that a miner gets paid once and then every node operator has to store that data forever
- 1:03:42is very dangerous, in my opinion. And I think more people need to run nodes. And if we keep trying to
- 1:03:49make it easier to run nodes, then I think that's a win for Bitcoin. And that's why I believe that
- 1:03:55Bit.10 will succeed in the end. By the way, Barrett, if you want to double down,
- 1:04:01we want to avoid anything ad hominem, slanderous. But one of your concerns you expressed offline was
- 1:04:08you've got Luke sort of sitting at the center of a lot of this. He's the single maintainer for
- 1:04:13He didn't initially, I don't think, release the PR for VIP 110,
- 1:04:19but he was noted as a contributor.
- 1:04:21I'm sure he was heavily involved in that.
- 1:04:23That's been one of your concerns as well,
- 1:04:25is just the mechanics sort of underlying the issuance of these PRs and these proposals Could you maybe touch on that a little bit Yeah I haven named any person in our current talk and I like to keep it that way
- 1:04:40I think it's best for people to just do deep research on people involved in general with regards to implementations.
- 1:04:48We've seen a very nice article come about the corruption within core.
- 1:04:53It's heavily shared and talked about a lot.
- 1:04:56but I think the other side should also be heavily investigated and checked upon
- 1:05:01because there is also a lot of question marks over there.
- 1:05:05And then we come back to let's be conservative, run something conservatively,
- 1:05:11and let's build on something that actually lasts for the long-term future
- 1:05:15because the kids depend on it, Michael.
- 1:05:19Perfect.
- 1:05:21Okay, I'm looking through some of these notes that we have here.
- 1:05:24What, Kyle, what have we not gotten to, if anything, that you were hoping to discuss?
- 1:05:30I think we covered everything.
- 1:05:33I'm not sure there was anything else.
- 1:05:36I think it seems to me like we've done a pretty good job.
- 1:05:39I think at the end of the day, what I've really enjoyed about this, guys, is that there's just so much division, tribalism.
- 1:05:47If you look at X and see the debate unfolding, I think this is hopefully much more educational and constructive.
- 1:05:54for people, probably a little bit technical. I think you can only keep it high level for so long
- 1:05:59before you have to get into the weeds a little bit. Tell me if I'm missing anything here. I think
- 1:06:02the big takeaways are run a node. You need to be running a node regardless of implementation.
- 1:06:09Try to take some of what you've learned listening to this chat and make an informed determination.
- 1:06:14Go do your own research. Don't trust verify. And then be ready for this activation period.
- 1:06:19Make sure you're thoughtful about should you be sending transactions, you know, depending on what you choose to do.
- 1:06:26Maybe there are some other considerations.
- 1:06:27Am I missing anything?
- 1:06:28Like, what do you guys want to make sure that people hear as a result of this episode?
- 1:06:33Learn to CoinJoin, not your node, not your code.
- 1:06:36I agree with that.
- 1:06:36And the big one, verify, don't trust.
- 1:06:39Not even us, not anybody.
- 1:06:41Do your own research.
- 1:06:43Make your own decision.
- 1:06:44Don't ever be in a situation where you're like, oh, well, somebody told me.
- 1:06:47or, oh, I'm going to trust someone else,
- 1:06:50or maybe I'm not running a node.
- 1:06:51I'm just going to have whatever they choose for me.
- 1:06:55That's like a sheep mentality.
- 1:06:57And in Bitcoin, we're not sheep.
- 1:06:59We need to focus on educating yourself, being sovereign.
- 1:07:04And that means taking action on your own,
- 1:07:06whether you want to be neutral,
- 1:07:07whether you're for Bit.10 or against it.
- 1:07:11At least you can see at the end of the day,
- 1:07:13I'm making my own decision based off my own interpretation.
- 1:07:17Well said. Guys, I think that's a good place to wrap up. Thank you both for doing this. Kyle,
- 1:07:21I know you in particular put a lot of time into pulling some notes together. And Barrett,
- 1:07:25I know you were going back and finding lots of resources. So this has been incredibly helpful
- 1:07:30for me, hopefully helpful for our viewers. And I'm really grateful for both of your time.
- 1:07:34Thank you.
- 1:07:35Cheers, guys.
- 1:07:36And that's a wrap. Again, hope you enjoyed this discussion. I thought this was incredibly helpful,
- 1:07:41very enlightening for me, especially as someone who is not a developer.
- 1:07:44and hope you learned a lot and are now ready to go run your node and make a determination about
- 1:07:49how you want to proceed, what implementation you want to run. But again, the most important thing
- 1:07:53is take self-custody, run a node. If you need help doing that, go to thebitcoinway.com slash
- 1:07:58podcast. You can schedule a free 30-minute consult with a member of our team. It could also help you
- 1:08:03with online privacy, setting up a privacy phone. We have an awesome plan B residency option in
- 1:08:08Panama too. Again, it's thebitcoinway.com slash podcast. If you stuck around this long, do me a
- 1:08:14huge favor, like and subscribe to the channel. We'd really appreciate that. Share it with someone,
- 1:08:18anything you could do to help feed the algorithm. We would really, really appreciate. Go follow us
- 1:08:23on X. We're at the Bitcoin way underscore. I'm there as well at the other M Jordan. And until
- 1:08:29next time, stay safe, stay sovereign. And remember the yield on Bitcoin is freedom.