Your video had a good start. Yes, sidechains are a big deal, the "Holy Grail" of Bitcoin technology --
bitcoinmagazine.com/technica… -- so the reaction should be big. Very big.
Your video then says: "sometimes there are unforeseen consequences", so we should go slow.
Here is my history of promoting Drivechain, slowly:
Sept 2015 -- wrote "Measuring Decentralization" essay, about why it is important to be able to run a node -- (differential node costs idea is key to understanding drivechain) --
truthcoin.info/blog/measurin…
Nov 2015 -- wrote "Drivechain" protocol --
truthcoin.info/blog/drivecha…
Dec 2015 -- Gave quick Drivechain talk, during lunch, at Scaling Bitcoin II [not recorded]
[ numerous conferences, meetings, emails, etc]
May 2016 -- Gave a 70-minute talk responding to feedback from gmaxwell etc --
piped.video/watch?v=0goYH2sD…
(!) Sept 2016 -- Gave a 5 hour, 161-slide presentation on "Sidechain Risks -- The Case Against Worrying" --
piped.video/watch?v=xGu0o8HH…
Oct 2016 - Presented "Sidechain Scaling" at Scaling Bitcoin III --
piped.video/watch?v=Gzg_u9gH…
Jan 2017 -- After technical feedback from the community, wrote "Mirage of Miner Centralization", "Mining - Threat Model and Equilibrium Analysis", and invented "Blind Merged Mining" --
truthcoin.info/blog/mirage-m… ,
truthcoin.info/blog/mining-t… ,
truthcoin.info/blog/blind-me…
Jan 2018 -- Collected all criticisms and replied to them in this 2 hr "Misconceptions" presentation --
piped.video/watch?v=gUbGT70w…
July 2018 -- Presented "Consensus and Dissent," at Building on Bitcoin --
piped.video/watch?v=15lBZQTN…
July 2019 -- Presented on interchain combat, at TabConf --
piped.video/watch?v=15lBZQTN…
After those technical discussions, I started to collaborate with other Bitcoin developers to make some software:
Jan 2019 -- first (barely usable) version
Oct 2019 -- first version w/ decent GUI
Mar 2021 -- first successful clone (of zCash) --
piped.video/watch?v=N33iJK2F…
Oct 2022 -- new cloning method, successful clone of Eth --
drivechain.info/blog/ethside…
After proving the theoretical and technical challenges could be met, I decided to start LayerTwo Labs. L2L will survive just fine, if Bip300 never activates on BTC -- the Bip300 advocacy is ironically something of a loss leader. We are funded by Bitcoin OGs with 10+ years Bitcoin experience. Most $ came from "Bitcoin Maximalists". Some expressed frustration with slow progress on BTC, and concern about Ethereum having more fees (
cryptofees.info). "Better safe than sorry", one said.|
L2L works on other non-Drivechain projects, including some designed to further decentralized mining. We hired Luke-Jr to work on the DC pull request, because anything merged into Bitcoin must be of the highest quality.
Only last month, did I talk to Miners for the first time. I went to Mining Disrupt in Miami. They all seemed interested and supportive. One asked about the security model -- I said it would be better for greedy miners to play by the rules. How much better? I did some envelope math, in front of him: "with today's altcoin fees, complying with Bip300 could increase miner hardware by NPV of .. $40 billion dollars". (More careful math here:
nitter.app/Truthcoin/status… ). People were astounded. Even me -- I had never done the math before, in all these years. I'd just assumed that this was "Satoshi's vision" and that it would probably work. Plus the revenues would grow over time.
I personally have never bullied anyone, nor "threatened to use miner support as a cudgel"...
...what I have done is tweet about how/why miners might activate a soft fork unilaterally. I often tweet or write about such activation paradoxes -- see Nov 2017
truthcoin.info/blog/uasf-con… truthcoin.info/blog/mahf-and… I say: forewarned is forearmed! The sinister thing would be to pass this knowledge only to the miners, and otherwise keep it secret.
----
> Isn't the most important thing, that we not screw up Bitcoin?
Drivechain poses no risk to Bitcoin. Drivechain claims the unused OP NOP 5, and basically uses it to count up to 13,150. That's it.
github.com/bitcoin/bips/blob… . If there are problems, then OP NOP 5 can be disabled (via soft fork) -- restoring things to exactly the way they were. It would just be cntrl + z on drivechain.
"Bip300" can actually already be done, today, without a soft fork — it's just much worse for everyone:
nitter.app/Truthcoin/status… For example, large pools could make a federated sidechain -- that idea has more overt collusion among miners. And gives "more power" to pools, and makes them harder to fire. It isn't a great idea at all. Yet it is allowed under today's Bitcoin rules. Bip300 is better, for everyone, and has no downside.
> How does drivechain help us avoid screwing up Bitcoin?
There is now so much new "blockchain tech" coming out, that it is impossible for one person to be aware of it all. Most of it is junk. But not all of it will be. The smart thing — the safe thing — is to always be able to copy/paste their tech into a Bitcoin L2, at the drop of a hat. It is enormously reckless to bet that we have today the optimal tech stack, especially given the limitations of lightning
piped.video/watch?v=BjFjK-f9… —
piped.video/watch?v=LnG5H62I… —
piped.video/watch?v=eCWTTY1e… . Lightning is powerful but it is not the scaling panacea and cannot be the final frontier of Bitcoin innovation. Our competitors' wildest fantasy, is that we rest on our laurels; and their greatest fear is that we will be able to freely imitate any strategy they uncover.
On top of that -- if we can obtain whatever we desire via L2 drivechain, then what legitimate reason would anyone have for changing L1? Almost none.
R&D made Bitcoin what it is today. Without R&D, we would not have HD wallets, seed phrases, multisig, RBF or Lightning (which relied on BIP 141, in the same way that drivechains rely on BIP 300).
teddit.net/r/Bitcoin/com… We have slowed down our R&D, not by choice, but because of SegWit2x trauma. Bip300 suffers from that same miner-phobia trauma. Fortunately, if activated, it also ends this trauma, and restores innovation to what it was during 2009-2017.
----
> What of "the effect on mining incentives"?
Drivechain is comparable to RIOT's use of "power curtailment credits".
riotplatforms.com/bitcoin-mi… It is just a new way for miners to make money. When I'm asked: "does drivechain affect miner incentives?" I say "no". Perhaps this is a mistake on my part? I personally lived through the invention of: FPGAs/ASICs, heat-reuse, stranded natgas flaring, curtailment credits, and a whole lot else. Merged mining was invented by Satoshi in 2010, and is already in continuous use --
truthcoin.info/blog/security… . So, to someone like me, getting revenues from merged mining doesn't even register as a change. It's just business as usual.
> What if the govt puts pressure on Foundry, as in zndtoshi's example?
It doesn't matter. What does matter, is this yes/no question: "Is it in the best interest of Foundry's clients, to support Bip300 withdrawals honestly?" If NO: then the govt pressure is a moot point. If YES: then Foundry will be a ghost town, moments after it stabs its clients in the back. Switching pools is as easy as navigating to a different website. If pools ever start making trouble, it will get easier still. (That is why pools have never made trouble.)
> Didn't SegWit2x prove that nodes > miners?
No, you have confused the similarly-named "Segwit UASF" and "SegWit2x".
The former, proved that nodes can force miners to ACTIVATE a soft fork (& a blocksize increase at that). The latter, proved that miners alone cannot force nodes to activate a HARD fork. Activating a hard fork is always hard (requires 2 of 2 votes), but activating a soft fork is always easy (requires just 1 of 2 votes). Ironically, the people now panicking unnecessarily, and calling for a node update to block OP NOP 5, will be hardforking themselves without miner support — they will be taking the losing side in the SegWit2x story.
----
Everyone who takes the time to understand Drivechain, will appreciate it for what it is: a benign attempt to improve Bitcoin.
----
It is pronounced "Storts" but you are free to call me Paul if you like.
drivechain.info
LayerTwoLabs.com