All episodes
Episode 72

Adam Back: Bitcoin's Past and Future

February 20, 202089 min

Dr. Adam Back is a cypherpunk pioneer. His work on hashcash is cited in the Bitcoin whitepaper and, lesser known among bitcoiners, but just as cool, his work on telescoping circuits is cited in the TOR white-paper. These are among many more contributions to the field of applied cryptography. In this episode we discuss cypherpunk history, bitcoin’s history and future, bitcoin privacy and Adam gives us an overview of the state of bitcoin tech. This was a great one, hope you all enjoy it.

Transcript

About this transcript

Transcribed from the original recording with word-level timing. Automated transcription may contain errors; the audio is the source of truth. Speaker names are not inferred.

Welcome to the Citizen Bitcoin Podcast. I'm Brady and I'm sharing my journey learning Bitcoin, hoping it makes yours a bit easier. How's it going out there, my Bitcoiners? Thanks for joining me again today here at the dawn of the Bitcoin Renaissance. This week we're sitting down with Dr. Adam Back, co-founder and CEO of Blockstream, one of the original cypherpunks and the inventor of Hashcash, the proof of work system adapted by Satoshi for Bitcoin.

Adam is a straight up Bitcoin legend. Really excited to get into this one with you. But first, an update from Swan. The March launch is coming quickly. The app is looking beautiful.

Swan will make Bitcoin investing easy with automatic buys every week, month, or paycheck.

It will steadily convert your dollars into Bitcoin savings and build your stack.

You'll be able to set automatic withdraws when a certain amount of Bitcoin is reached. I am really looking forward to having the Swan web app out there and hearing what you all think about it. It's going to be pretty exciting.

Thanks as always to the Let's Talk Bitcoin Network for including the pod in their feed. Give them a follow at LTB Network on Bitcoin Twitter. And check out the LTBN feed in your podcast app for the other great Bitcoin podcasts included there.

The Bitcoin 2020 conference is coming up quick. Just a little over a month away now. In these episodes, I'm in the midst of recording with Bitcoiners who will be speaking at the conference, including Dr. Adam Back. It's going to be even more big than last year.

Definitely recommend making your way out to SF for this one March 27th and 28th. A lot of satellite events and parties around those dates. Alright, let's dive in.

Dr. Adam Back is a cypherpunk pioneer. His work on hash cash is cited in the Bitcoin white paper, and lesser known among Bitcoiners, but just as cool. His work on telescoping circuits is cited in the Tor white paper. These among many more contributions to the field of applied cryptography.

In this episode, we discuss cypunk history, Bitcoin's history and future, Bitcoin privacy, and Adam gives us an overview of the state of Bitcoin tech. This was a great one, a real honor. Hope you all enjoy it. Here we go.

It's an honor to welcome one of the world's preeminent cypherpunks, a true Bitcoin OG, Dr. Adam Back to the podcast. Adam, how's it going? Pretty good. Thanks for having me on. Absolutely. I really appreciate you making the time. Whenever I get a chance to speak with one of the pioneers of Bitcoin, I'd love to just go back and hear some personal history and obviously talk about York's, you know, history with Bitcoin.

Let's just talk about your, you know, early days of getting into computing and the internet. What what was your first computer? It was a Sinclair ZX81, which also sold as a Timex brand in other countries. So it was ZHE based processor.

8-bit microprocessor with 16 kilobytes of RAM and some ROM. So it's kind of slow by today's standards. The I.O. Was a tape drive, like a cassette tape drive, and the screen was analog TV, basically. So that was that's where I started.

So I taught myself to program on that thing. What was early coding project that you're most nostalgic about when you think back? I guess I got interested in I mean it it had a programming language in it, a version of BASIC in the ROM, and so I kind of wanted to do more things with it, and there was no so I wanted to learn a assembly basically, so I bought a reference manual, but I didn't have a disassembler to look at the ROM because there's a lot a lot of example code in the ROM effectively.

So I wrote a disassembler in BASIC so that I could more easily reverse engineer what the ROM did. So that was kind of fun and novel thing to do. And then I didn't have an assembler, so to write programs you'd have to enter hex values, so I probably still to this day remember a few of the instruction machine code numbers and things.

That was fun. Then how did you become interested in cryptography? So I did so when I when I got this AT, I was teenager, like 13, maybe a bit younger, something like that. And so I taught myself basic program and Z80 programming, and then there was no computer science at college, which is age 16 to 18.

I went to college in the UK. So I taught myself they had some computers, so I taught myself Pascal on those. And then I when I finished that, I thought, well, I'm interested in computers, so I'll do computer science degree. So I did that at university. And then went on to do a PhD.

And during that, a friend of mine who was doing a master's degree was doing some research on distributed systems. So arrays of low-powered compute sort of CPUs connected by high-speed interconnect, and the challenge is to you know, collectively these CPUs have a lot of power, but individually they're quite weak.

So the challenge is to divide up your work so that you get decent performance out of all these computers. And he was trying to parallelize the RSA encryption algorithm. So he explained to me what it was, and I got interested in the mathematical tricks to subdivide the problem.

And so when PGP came out, I guess you know, sometime after that, I recognized the use of RSA, so I got interested in what PGP does. And the interesting thing to me was that it was advanced technology that has a positive social impact.

So it empowered individuals, increased, so it changed the balance of power between governments and media and sort of the military industrial complex and the individual rights in a positive way. So I got interested in that, and then wanted to find out, you know, wanted to get involved in more discussions about technology like that, and that that's where I found the Cypherpunks list, which had been formed around that time.

And what time was this roughly?

Probably around 92, 93.

So right around the birth of the web. Yeah. Early, early internet web pages. I mean. Why do you think that cryptographic solutions like hash cache solutions to the spam problem never garnered wide use? I think it had a couple of problems.

So one problem was a check-in and egg problem. So there are many technologies like this where you could see that if something was widely deployed, it would have an effect. But to create incentive structure for people to deploy it is difficult because the early adopters don't get much value. So I think it suffered from that.

And there was a fear as well when I started it, you know, when I when I came up with the idea, which was actually about reducing spam issues for remailers, which were I was running a remailer that provided a way to email anonymously and to participate in Usenet sort of distributed discussion groups anonymously.

And people would spam through those. So I started from that direction rather than just email, but it works for email as well.

So I think, you know, it's difficult to sort of bootstrap it.

One approach that was used that you know I arrived at to try and bootstrap it was to integrate it into anti-spam systems, and one of those is a system called Spam Assassin, which somebody integrated it into that, and Spam Assassin is used by ISPs and companies running mail servers that have you know a lot of resources used by spam.

I mean, bear in mind at this time spam was probably more than 50% of internet email, consuming a lot of bandwidth at that time relative to total internet bandwidth. So it tends to overload servers, and the idea there to try and get incremental value so you get benefit from adopting it unilaterally for the network effective growth was that the hash cache stamps that the sender would put on an email would reduce the chance of their email being incorrectly categorized as spam.

So other than spam being a nuisance, you also have another problem, which is genuine email gets miscategorized by automated systems, and then you know you failed to communicate your email ended up in the spam folder. That's still a problem to this day. But it didn't seem to be quite enough. I guess the other problem is that you need integration in mail software, and while there are a number of plugins, it wasn't directly integrated in that much mail software.

Although Microsoft did do make their own version of Hashcash, so slightly different format, but the same kind of proof of work system. That was integrated in a number of different Microsoft platforms, but it was incompatible as well. So I think that also didn't really I don't know.

It got integrated, so you know, and Spam Assassin still has the support today, so it's you know, there are people who use it. Oh, yeah, I had no idea about that. So you started working on Hash cache to kind of solve this problem. Did you think did you have the idea that it could be used for in some way for e-money?

I mean it seemed to occur to people pretty immediately that it could be interesting for that purpose. So within like a day or so, multiple people observed that it was a form of digital scarcity or likened it to digital gold, and then got interested to try and work out the details, one issue being how to do it in a decentralized way, another being how to control the inflation.

Because if you have the ability to you know mine some coins using a computer, and you're you're making money on that, people will do a lot of it and the supply will inflate. This discussion was on this the cyberpunks list primarily. So you know, I think it's curious, but I think that money is something that is independently reinventable by humans.

So I think that people just generally look for something that is scarce or rare and hard to reproduce, and will use the best money technology available at the time, and that's evolved over time.

So you think about Bitcoin as the next evolution in that. But you know, then there was a sequence of ideas around how to build a reusable money, a respendable money. Hashcash itself wasn't respendable because it's kind of postage stamp that is not reusable.

So it convinces you that the sender spent some cost incrementally in CPU time and electricity, but you can't turn around and respend it because of the mechanism it uses.

So the hashcash was posted, like implementation and so on, on the cypherpunks list in 1997. And by 1998, there were two proposals about how to go about decentralizing it. And they weren't complete systems,

They weren't implemented, but they were there were ideas described in some detail. And those were B Money by Wei Dai and BitGold by Nick Szabo. And you know, so I think the main thing they lacked was some aspects were sort of federated or using supernodes, so they weren't fully decentralized in their design, or they involved humans doing market activity to sort of control inflation in the case of B-Gold.

Sorry, BitGold. And the a later variant was a thing called RPAW, reusable proof of work by Halfinny. So BMoney and Bitcold were somewhat decentralized, and RPAW was actually not decentralized, but used a different technology.

So it used the trustworthy computing equipment so that you could have a centralized server that you could verify what code it was running, and so you could get some trust despite the fact that it's centralized. And you know, the before hashcash there were other electronic cash systems, academic and deployed, and the most sort of widely known one that was deployed was digicash using a protocol by David Chum, and that one was also centralized because the previous electronic cash systems, the cryptography was in a

Centralized trusted server assumption that you would you would start by assuming that there's a trusted central server that could be trusted not to inflate the supply.

Hal Finney's RPOW

Was a way to get beyond that and proof that the supply couldn't be inflated, provided the hardware hadn't been tampered with. So RPAW and the Digicache that came before it had solved some problems, they had better privacy, but they weren't very survivable.

You know, when the central server goes away, you can no longer verify coins and the system stops working and you can't resume it on another server. So BMoney and Bitcoin were a bit more decentralized from the point of view of trying to survive central central server shutdown issues.

So I think Bitcoin kind of solved the combined problem of being more decentralized in the way it solves for inflation and having a novel insight, which is that you don't try to control the supply or the price. Sorry, you don't try to control the price, but use you control the supply.

So if Bitcoin has a defined rate of supply that tapers off over time to 21 million coins, but it doesn't try to do anything about the price of the price set by the market. And you know, we've seen the a rate of adoption and price speculation that has over, I guess, any two-year period in its 11 years of operation, made it deflationary in the sense of the price going up.

But there is there is supply inflation. I mean, there are new coins being created at any time. It's just that they're limited in total number and the rate of adoption is exceeded on average the rate of production of new coins. So I think the Bitcoin approach is quite interesting in mirroring physical gold mining in a way.

You know, there's something which behaves similar to gold, but with actually more rigid supply guarantees. With gold, if the price is higher, people will produce more gold per day, per week, per year, and taper it off if the price goes down. Whereas Bitcoin adapts mathematically so that the rate of supply is fairly constant, regardless of market conditions.

Why do you think that Satoshi designed Bitcoin to have that four-year halving cycle instead of a smooth linear decrease in the supply? I don't know.

I mean, I think it's an interesting feature. I mean, I don't know why he he decided to do it that way, but it does seem to create some kind of economic cycle within Bitcoin, which maybe beneficial.

Certainly it could have been designed with a smooth supply curve, or it could even be changed in a soft fork, softworkable way, so a backwards compatible way to be made smooth, but I think people like the halvings at this point. And for the last couple of halvings, they haven't proven to be an issue.

Like they haven't created an economic shock of negative repercussions. Generally the prices adapted around the halving, and the hash rate has continued to provide you know continuous operation for the halving with not much impact on speed of transaction processing and things like that.

So we'll we'll see how the halving coming up in a few months goes. But yeah, so far it's been an interesting artifact of the Bitcoin economic system. Yeah, it's very interesting. What do you think were the key innovations then that solve the digital scarcity problem? You were getting at this idea some of the deficiencies in terms of decentralization of the precursors to Bitcoin.

So, what were the key innovations then that solved that problem, the decentralization of scarce digital scarcity? I think that one I mean the first factor was to you know to have proof of work. So technically, proof of work existed before Hashcash with with different names.

I wasn't aware of it at the time, but there's earlier paper by Dwarker Nayor, called which uses CPU pricing functions, which is another another word to describe proof of work. There and they actually had the same application in mind as and in terms of spam control, coincidentally.

But the way that they approached the proof of work was to make weakened signature algorithms. And so those algorithms are kind of less elegant in a way. They result in bigger proofs of work, and the proofs get larger as the work increases and become more expensive to verify.

And they're also not randomized. And it's important for Bitcoin mining that the proof of book be randomized to avoid centralization. So with the Dwark, there are three different proof of works in the paper, and I think it's clear for two of them that if you were to use that proof of work, whoever had the fastest processor would get all the coins.

And there'll be a race to build the fastest processor. The other one is a bit ambiguous. It does have some randomness,

But we don't know if there was a strong incentive whether there might be slightly slower but non-randomized algorithms that would create the same problem as the previous two.

So the way Hashcash works is it's a Poisson process. So it's randomized. So there's no progress.

So that means that you know somebody with 0.1% of the hash rate gets the same you know benefit pro rata as somebody with 1% or 10% of the hash rate by having more equipment. So it's kind of like buying lottery tickets. The person who buys one lottery ticket has their one in a million chance of winning, and the person who buys a hundred has their one in ten thousand chance of winning.

So so that's one aspect of it. I think that one of the lessons people drew from the previous systems failing is that central points of failure were a problem for survivability of a system and for the permissionless of a system permissionlessness of a system.

So that you know, people wanted to have a kind of user-adopted technology. Digicash particularly had a banking interface, so they were assuming a banking relationship where you deposit Euros or US dollars into a bank account and you get coins, and you could deposit the coins and convert them back into Euros, US dollars, and they would maintain bank balances behind it, kind of like today's stable coins.

And so that was you know, a point of permission. You would have to find a partnership with a bank, and if the bank changed their minds, then you would be out of business again, or the coins would be unredeemable. So Bitcoin solves that kind of problem, and that was the attraction for the previous systems, like I mean, Hashcash itself actually did it it wanted to avoid needing a banking relationship, but wasn't respendable.

Digicash, sorry, VMoney and Bitcold were also attracted to the idea that by doing mining, then you wouldn't need a banking relationship. So that's kind of decentralization factor. And as I said, you know, in in 97 people immediately hit on the idea, bearing in mind that most people had on the Cypherbanks list had not heard about the previous anti-spam system by Dwarken Ayore.

So they were looking at it afresh, and it wasn't until later that somebody you know found a paper and drew people's attention, the DORC paper and drew people's attention to it. So on a on a Hashcash discussion, people hit on the idea that this could be interesting for avoiding bank permission in operating a decentralized version of digicash.

And people were already thinking about how could they decentralize electronic cash system. So proof of work helped that because it it avoided one of the centralization points, the way to get money into it. So you could just mine the coins from scratch and then you'd have money in it. So you wouldn't need you know a banking partner to get money in.

And once you had money, you could have secondary markets, so people could you know trade the mined coins peer-to-peer or on after aftermarket or secondary market or in-person exchanges. So I think that that's where the digital scarcity came into the picture and the decentralization, so it's also about so it's a combination of being about a way to get money into the system and a way to have a decentralized system so that it's more survivable.

It doesn't get shut down if a central party goes up business. And more recently, I became aware that some of the people involved in electronic cash, namely Nick Szabo and I think Halfin were also interested in monetary reform. So they were interested in you know, switching to a gold back to a gold standard or something like that, or a digital version of it.

And so, in thinking about an electronic cash system, they were thinking they wanted one that had monetary reform, so that had gold-like properties, basically. So that's why I presumed that Nick Szabo called his proposal BitGold because he was interested in monetary reform.

So people were interested for different reasons. Some people were maybe interested in the ability to transact without permission and with strong privacy. And others were interested in a monetary form and return to a gold standard or a digital gold standard, because the digital gold standard would be more convenient.

You know, you'd be able to transact at a distance. So,

But you know, Bitcoin has aspects of both, in fact. Digital gold and electronic cash, permissionlessness and some privacy. Do you think that the kind of the advent of peer-to-peer technology, which was kind of happening around the same time that Hashcash was released, kind of late 90s, Napster, etc., and then BitTorrent by Bram Cohen came in the early 2000s.

Was that idea around before? Like were you guys talking about that stuff on the cyberpunks list as a feature to use to solve this digital scarcity problem? And if not, do you think that you know later for Satoshi looking back and saying, hey, this peer-to-peer technology could really be used to help decentralized the operation of nodes became a feat like a reason for the decentralization or a way to make sure ensure the decentralization of the network?

Not actually sure. So Wikipedia here is saying that file sharing, I'm just trying to think about when did the term peer to peer arise? So the concept was popularized by file sharing systems such as Music Sharing NAPS that are released in 99.

So I think that the actual terminology peer to peer came slightly after Hashcash. But the and like focused on file sharing initially.

But I think the idea about making decentralized systems predated that and arose from the recognition that individually run software is hard to shut down because it's run, let's say, by volunteers or it's too decentralized so that if you were to succeed in shutting down one node, it wouldn't really impact the system's behavior.

So you could see other decentralized systems in play, which were kind of peer-to-peer, right?

Which is, for example, the anonymous remailers, which are about providing privacy for email. And they were inter there was interested in peer-to-peer, like censorship resistant web service, for example, or file distribu distribution service.

And I'd proposed a system called Eternity. Well, I implemented a sort of prototype of it.

There was a paper by Ross Anderson called, by the same name,

And that was about being able to publish things and have it be hard to censor because it was recognized that websites could be shut down because a hosting provider could be pressured into removing content.

I also proposed something else, which was a way to

Decentralize DNS names. So the name you type in for a website gets translated into an IP address, and the name services is hierarchical, so also a bit vulnerable to domain seizures by establishment by courts, and the administrators of the name service are ISPs and things, so they're they're prone to follow those orders, even though it's international and different countries, there were dispute resolution processes, and like a copyright holder can sometimes seize a domain, even if some individual with the with a legitimate use

For the name got there first. So I thought that was another centralization point. So I think the cypherpunks are kind of hit upon decentralization as a way to retain sort of more permissionless systems, harder to censor systems, they were interested in privacy and anti-censorship and further moving the balance of power towards the individual in publishing and communication and also financially, you know, with electronic cash.

Sure. When did you start running your first Bitcoin node? I think probably in 2013. I probably downloaded the software before then, but I maybe didn't run it for very long. I was running Bitcoin Core or Bitcoin QT.

I think it changed names at some point, so I would have been running a full node because that was the primary software at the time, and later installed various different smartphone wallets. And actually, I think I didn't have a smartphone at the time, so I bought a smartphone in order to be able to run a Bitcoin wallet.

So did you ever get involved in mining then around that time? Or were you ever curious about getting involved? At least? Yeah, I did a little bit of mining on GPUs, and then I bought a couple different ASIC miners, some butterfly miners, and another another generation of butterfly miners which kind of arrived late and I was supposed to get a refund, but I didn't didn't get a full refund.

So that was a little disappointing. But I think a lot of people had that kind of experience in the early mining space. There were you know, the companies producing the mining equipment were underfunded, so they expected the buyer to fray the technical risk, so they'd get you to pre-pay for the equipment, and then if they ran into technical risk, you'd get the equipment late or it wouldn't work as advertised, or you know, in some cases they offered refunds, but as I say, I never got the refund.

And I think you know there were other things going on as well. You know, some of the manufacturers were strongly suspected to be succumbing to greed and mining the equipment instead of providing it to the users. So they you know they'd manufacture a money printing machine with user funding, and then they'd mine it and make excuses about it, technical risk, which were false, and they were just profiting, and then they'd send you used equipment later because people could see that the equipment being run after the fact, like they forgot to reset the configuration or it looked extremely worn.

So the early mining was a bit of a wild west. I've I've been doing some more, I mean more mining more recently. I bought some you know silicon equipment a few years ago and some micro BT equipment more recently. So what do you think are the most pressing challenges that Bitcoin faces right now and is going to be looking at over the next decade or so?

Do you think Bitcoin's sort of at a fragile place right now, or has it gotten to the point where it can't be fully stopped anymore? I mean, there are there are a number of things about Bitcoin that could use improving, and it is something that undergoes continual improvements. I would say that it's improvement processes both proactive in terms of people recognizing issues and working to improve them and also reactive in the in the same way that aircrafts get more reliable and safer over time because when there are issues,

People do postmortems and really try to understand and characterize the problem and prevent further problems of that class. So that kind of thinking goes into the Bitcoin software and issues that come up every you know, once in a while, maybe every two, three years or something, there will be some bug, and I think the bug rate, you know, the major bug rate has definitely decreased over time.

So I think that risk is receding of a technical, you know, large scale technical issue. Now another another way to look at it is would Bitcoin would it be possible for the establishment, let's say a major country to significantly impact Bitcoin or shut it down?

And I think the answer at this point is largely no. So and that's because you know it's international and it's operated by ultimately individuals, if it has to be, you know. I mean, there's certainly some companies doing mining these days, but if they were prevented from doing so, there are individuals that would continue to mine.

And the mining is, you know, it can be decentralized, people can run a few kilowatts in their garage and things like that. So that kind of thing's hard to shut down, and there's a financial interest and a philosophical interest to operate it. And I mean, the other the other sort of sense some somewhat permission centralized risk is the cryptocurrency exchanges.

So a few different variants of cryptocurrency exchange, but the ones that you know have banking wire transfers are probably at risk of losing banking service. So if there were, you know, let's say that hypothetically banking service was disrupted, would that prevent Bitcoin being used?

And I think the answer again is no, because you know, firstly, there are decentralized exchanges where people are swapping cryptocurrencies or swapping stable coins for cryptocurrencies. So the stable coins could also be impacted, they also rely on banks. And the last kind of even more decentralized approach is things like local bitcoins.

So the idea that there are enough people with an interest in Bitcoin and people interested to trade it, that ultimately it could be traded person to person, and the adoption level is sufficient at this point that you know, in any any moderate sized town, there are multiple people who would participate in local trade, or you could that you could ask a friend and you know, use use network social networks, in-person social networks to find somebody who'd be interested to trade with you to buy or sell Bitcoin.

So I think you know, from that kind of adoption level, it's it's bootstrapped in a way that it would be hard to put the genie back in a bowl. Now, of course, you know, major political attacks on Bitcoin might impact the price.

Historically that's been the case. You know, there's this period where China was kind of on the fence, they were gonna ban Bitcoin, and then they soften their stance and they weren't banning it, and you know, each time they did that the price fell and then it recovered, and over time people stopped believing it.

So, you know, when China would steer the tune tune their regulations towards tightening controls on Bitcoin or cryptocurrency, you know, towards the end the price would actually go up because people just like didn't believe it anymore or or didn't think it mattered, and the volume diversified into more countries at some point as well.

So it's a kind of preview. I think there's also a balance where again with China, when they would you know talk about banning cryptocurrency exchanges operated in China, what what would happen is the unofficial ways to trade Bitcoin would see an enormous increase in volume.

So local Bitcoin's volume would spike, and there were other things like that in China. So where there's an economic interest to do things, many cultures will you know continue to do them if they're grey market, or maybe do them more if they're gray market because they're attracted to the gray market or something. And so you could see there's a balance there for the governments that if they for financial surveillance, that if they were to tighten up the controls too much, they'd lose visibility into cryptocurrency because you know an exchange would have identity and be able to provide information to the authorities

If there was a theft or something like that. And by tightening controls too much, they would lose that visibility. So I think that that ended up being a balance in China where they could see that tightening controls actually made things worse to the you know to the financial surveillance part of the government, to their perspective. So you were talking earlier about Nigzabo and others wanting to return to a gold standard being mainly concerned about the monetary changes that something like Bitcoin could bring about.

When did you when did you first develop an understanding of the problems created by the centralized control of money? I mean, I studied economics when I was do in college, which is 16 to 18. So I have an economics A level, which is you know it's not a degree level qualification, but I was through that I became interested in sort of free markets and developed a more capitalist free market outlook.

Where my view was that the free market was a better way to achieve services and social outcomes than government or you know, incre increasing the size and scope of the government. So I was like, minimize the government, the private sector can do a better job of that in general.

And you know, so the it's something that's less well known that inflation erodes your erodes your capital, erodes your wealth, and is a form of taxation. So people don't take money for granted. But I was you know interested in investing and would look at you know headline inflation rates and interest rates you could achieve by skipping around doing different savings or long-run return on investment you could take by taking different risk profiles by stock trading and things like

That. So yeah, I was aware about it being that inflation was a i indirectly a form of taxation because you're you're you'll be trying to target achieving a higher rate of return than inflation, and inflation itself, you know, there's there's ongoing discontent in countries, even the UK, which I was I was living did my study in the UK, where the you know the rate of inflation is not that high.

Central bank was targeting I think two percent inflation rate, but they used their own definition of inflation, the consumer price index, and there's discontent that that was manipulated, you know, that it didn't reflect the true spending habits of the average consumer or the average market participant.

For example, they excluded housing, which in the UK is relatively expensive due to a very controlled market. I mean, it's planning is restrictive, so house prices tend to be overvalued. So, you know, it and that the basket of goods was being manipulated over time, so that they were keeping the headline inflation rate low while the real inflation rate was high.

So, you know, I will I did at some point own some gold ETF stocks for as a as a hedge against this kind of thing. But I think it's fair to say there were other people that were maybe, you know, I think people on Cypherpunk's list were interested in all kinds of things, and tends to be free market libertarian types of people.

I mean, I wouldn't necessarily identify myself as libertarian or member of Austrian economics or anything specific, but more that I would be interested to analyze the situation and understand my version of it for myself. So more independent thinking viewpoint. But it certainly seems that people were interested in both the permissionless anonymous electronic cash for the kind of reducing government control on them on the flow of money and you know, avoiding monitoring of personal spending habits, because in the physical world, if you walk into a store and paid with

Cash, you would have quite a high degree of privacy, and in the online world, people could see that that was being eroded rapidly because of the payment mechanisms available. And then people were also interested in another aspect of control, which is the government sort of political control of the money supply, so that money itself had degraded from the gold standard into being a form of political control or a way to have a hidden tax, a tax that's not visible to many people, though it's you know it's measurable and observable and estimatable.

There's a debate that's going on right now in Bitcoin, Bitcoin, it's been going on for a couple years. Are you in favor of trying to increase privacy on Bitcoin's base layer? Or do you prefer a more layered approach using protocols like Lightning and Liquid on top of the base layer to improve privacy?

I'm in favor of both. And actually historically, that's how I got more actively involved in Bitcoin is that I could see that the base layer privacy wasn't as good as the previous electronic cache systems, and that could be you know that was suboptimal, didn't give it as much fundamental or utility value, and I think was presumably born out of you know technical limitations more than a design feature.

I think if it was easy to have strong privacy in a base layer, Bitcoin would have had that. Now it is relatively easy to have strong privacy in a centralized base layer, which is what the you know Digicache and other protocols such as Stefan Brand's electronic cash protocol, they have very strong privacy, but they're centralized.

So it turns out the cryptography is hard to make work in a decentralized system. So that's still a kind of open research problem, if you like. So now I mean you can build privacy in layer two, but I think you know there are reasons to use the layer one.

So we have a couple of problems. So one is that now I saw this when I proposed confidential transactions. I called it something else, homomorphic encrypted value on the Bitcoin Talk Forum in 2013, which became confidential transactions, and Greg Maxwell optimized and invented some more things to make that work efficiently in practice, and that's what got implemented into Elements and Liquid.

My motivation for doing that was about privacy, but when I looked at how would you go about integrating that into Bitcoin, it became obvious that it's hard to make complex changes to the Bitcoin base layer because it it has already, you know, in 2013, already a high amount of value, so you have to be careful very careful about changes.

And so that turned my focus to say tackle a precursor problem, which is Bitcoin modularity. So it seemed to me, well, if it's hard to add desirable features to the base layer, maybe we can find a way to make Bitcoin more modular so that you can have different opt-in like security boundaries where you could have different features, and that's where the two-way sidechain concept came from.

And other people had had similar ideas about sidechains driven from different directions. So Greg Maxwell had one driven from the recent at that time recent SNARK inventioning in having cryptographic proofs about software execution, a kind of signature of execution.

I think that the reason that it would be desirable to have fungibility and privacy in the base layer is that we don't have a way to fully provide the same layer of level of security to sidechains.

So there's there's some kind of security trade-off inherent in sidechains today that might be fixable in the future with more technology. So and the other reason is that for you can use layer twos like Lightning and Liquid, but they make security trade-offs. So while you can get enhanced privacy in those layers, you would want that in the base layer because for the best censorship resistance, the best cold storage security, base layer is the best option available today.

And so, you know, you'd want the best privacy and fungibility for that use case too. You know, it makes pretty good sense to have different layers for to optimize different use cases, but today they have to make trade-offs to do it. So Lightning, you know, it makes some security trade-offs in terms of hot wallet risk.

So people tend to use that for lower value transactions. They have other advantages, like they're more private and they're more instant, more instantly final. It also has kind of channel capacity and routing complications, which also push towards lower value transactions.

And liquid is optimized for trading, so people who want to do exchange trading, move assets between a trading wallet and exchange or move move only between one exchange and another and to trade different assets. So it adds confidentiality, but it does so in a way that makes most sense to people who are trying to improve the situation of being able to trade without having full custody risk in an individual exchange.

But still for long-term storage, the main chain is the better option. So I mean, I you know there has been a some evidence of features being validated and tested on the layer twos, making their way into the main chain.

So, for example, there was a malleability fix with an effect similar to SegWit, tried first in the open source platform that Liquid uses, which is called Elements. So if you like a SegWit precursor was first tested in a side chain, and also Schnorr signatures were first tested in Elements in 2015, 16, that kind of time frame, and are now being proposed for inclusion in Bitcoin.

And Schnorr signatures improve some aspects of privacy, they reduce fingerprinting of wallets and use cases by making more types of transactions look identical to people who are trying to do open source intelligence on on a blockchain. So I would I would be interested to see strong privacy in the main chain.

Now, obviously, some people I think if you ask users if they want it, most users want that. But some users who are using Bitcoin for its store of value worry that adding stronger privacy into the base layer might put at risk it may make it more difficult for exchanges to maintain banking relationships or you know, make them less able to answer questions about where funds move from or to and things like that.

So I would say today that's already ambiguous in the sense that if you are careful and methodical, you can get quite strong privacy in the Bitcoin main chain. But technology could make that better. I mean, the thing is, you know, in the absence of a kind of silver bullet privacy tech for the main chain, the main chain has been making progress on privacy.

So in each major release, there are usually some incremental privacy improvements. The most recent being the Schnorr and Taproot proposal, which adds some privacy. But there have been previous things to do with making it less obvious which IP address originated transaction.

So other than being able to look at the history of coins, some people who are trying to analyze the network for risk scoring that exchanges use, or for more Nefirus users to try and identify IP addresses that have coins and try to then maybe figure out where they are physically located and perhaps burgle a property or something like that.

We don't know exactly what people are doing, but probably some hackers are looking at you know, hackers with malicious intent looking at that. So you know, there is an interest from a self-def self-defensive perspective to hide the IP address that you're originating transactions for.

So that's why some wallets integrate Tor.

And for example, Blockstream has a smartphone and desktop wallet called Green. It used to be called Green Address. And we've integrated Tor into the iOS and Android versions of that. And Bitcoin Core also makes it easy for you to connect with Tor. So I think that's defensively a good idea.

So that at least keeps your IP address out of things. But there are risks with wallets that you can accidentally correlate transactions in wallets by because you know you're you might make a payment that combines two coins that were used from different sources, and that would show the observer that you know they're probably from the same spender.

It is a bit ambiguous because there are multi multi-party spends like Coinjoins, and probably different types of trading activity, like some of the peer-to-peer exchanges might involve multi-party spends. But you know, it it if you're not careful, it can rival correlations.

Yeah, so I think more privacy would be good personally, and I think it would be a much more interesting debate than you know the block size trade-off, which I thought was you know technically a clear direction that layer two scaling at layer two was a better computer science trade-off.

But I think the set of people arguing on that trade-off will be split in a different way between when when it comes to arguing about privacy on the base layer. So I think the lowest you know, the closest to deployable incremental privacy tech for the main chain would actually be confidential transactions in a way.

You know, the more advanced things than that that further remove linkage are less scalable. I mean, they are involve more experimental cryptography or are less less computationally efficient or space efficient. So it may be that confidential transactions makes the leap from sidechain to main chain following you know the SegWit precursor and Schnorr signatures.

It's worth bearing in mind that that confidential transactions is is also another incremental change. It doesn't change as such the ability to look at which coins are spent to which other addresses, because you can still explore where coins are spent in terms of the sending address and receiving address on a block explorer are be running a full node.

There's a distinction is that you can no longer inspect the value of the transaction, how many bitcoins are transacted, and so it becomes harder to distinguish change from the spending transaction. And I think that's you know, there are many good reasons to do this. Certainly when we at Blockstream released the first version of Elements and Liquid, there was appreciation and you know, welcoming reaction to confidential transactions from multiple audiences, and both the technical audience who found it you know very interesting and counterintuitive to understand this new technology, and from end users

Who who you know valued the privacy and security from not divulging wallet balances by accident when you make a spend. And actually from the finance sector, so the different banks that were you know involved with their own blockchain labs found it important because one drawback of public blockchains is they're too transparent.

And many businesses and financial institutions don't want to reveal pricing information or trading strategies for the world to see because people will analyze that and trade against you. So in some ways Bitcoin has less privacy than normal stock markets or banking privacy, because while the banks internally and potentially regulators get visibility into that in in some circumstances, the average person can't do open source intelligence on it, which is the case for Bitcoin and other cryptocurrencies.

So you could see that the financial world actually likes confidential transactions too. So it's it's an interesting trade-off because it doesn't remove linkability as such, but it improves a different different aspect of privacy, namely how much money's changing hands and the pricing of transactions and trades that are happening.

So I think that's generally good for individual security as well. And not, you know, if you if you make a high value transaction from an IP address, now people know that they can geolocate the IP address and perhaps try to burgle the house when you're on holiday or something like that. Of course you'd want to keep your backups outside of your house, let's say you're in a safety deposit box or something, but it's still a risk that you're taking.

So confidential transactions reduces that risk because now nobody who's not involved in the transaction knows how much how much trading hands that's good for security. Right. What one of the concerns that I hear about potential privacy solutions like confidential transactions is that it might compromise the ability to audit the supply, and there might be a supply, like an inflation ability to inflate the supply.

Does confidential transactions not compromise or threaten the ability to audit the total supply of the of Bitcoin? That's an interesting question. So I would say the of confidential transactions acceptance criteria, there are two issues.

One being the size, they tend to be a bit larger. And now arguably they are more powerful transactions, so they often replace multiple individual transactions when people break up value into lots of small coins. So I think that probably is winnable argument on balance, and the other one being the argument about whether it's harder to know that the guarantee about no inflation is slightly weaker.

And so in principle there is a mathematical guarantee of no inflation, but the details get a little tricky around the edges. So the two broadly two versions of confidential transactions.

One is

That I mean there's there's generally a range proof, so it's it's proven by induction kind of. So while you can't have visibility by adding up all the coin values because they're all communicated between transacting parties, you know the clear text value of the freshly mined coins, and then as they're transacted, they go confidential.

But you do have a mathematical proof that each transaction, the inputs add up to the outputs plus the fee, and so you know by induction that no inflation has occurred anywhere because all the miners and all the full nodes are verifying each and every transaction adds up correctly. Now the question arises with the quantum computing debate that well, what if in the far future, many decades into the future, I would suspect a powerful enough quantum supercomputer is

Developed to break discrete log to be able to compute discrete logs fast enough to attack Bitcoin. And in that case, somebody would be able to for this for this type of perfectly hiding or perfectly anonymous sort of well, it's not really anonymous, but but perfectly value hiding confidential transaction.

There are two variants. So this this variant would suffer inflation at that point, that a you know quantum supercomputer would be able to inflate value, and you wouldn't be able to tell. And that's basically because the confidential transaction is making a pedicine commitment, sort of a special type of hash that is has a randomizing blinding value, and then the actual amount.

If you can break discrete log, you can compute different blinding values that look like valid commitments to incorrect values, and you can create value that still looks like it adds up, but actually introduces fake value. So so that would be a problem, but there's another variant which is perfectly binding, and in the event of you know the quantum supercomputer arriving, they fail in a different way, which is you lose your privacy, but no coins can be inflated.

So you have to make a choice really which one do you want? There's there's some fairly compelling mathematical argument that you can't have both properties. Umthough one of the applied crypto researchers who's now at Blockstream, Tim Ruffing is a PhD applied crypto guy, made an interesting proposal which is called switch commitments, where you start with the perfectly private version and you commit but don't reveal the full version, and then you switch later, hence the switch commitment.

So you start with perfect privacy, and if it looks like you know quantum supercomputers might happen within a decade, then you start switching to the other one, or you start introducing a new crypto scheme with you know post-quantum cryptography and different kinds of proofs and things, which will probably I mean that's an active area of research in itself.

So there are post-quantum, there are cryptographic signatures and proof systems, zero knowledge proof systems that work even if there are quantum computers, they just use different types of cryptography, but they're active areas of research, so it's difficult to adopt them now because they're vastly inefficient.

They have huge signatures and proofs. So, you know, one formula that might work is to use switch commitments so that we have good privacy now, and we can swap the crypto systems long in advance of quantum computers becoming a reality to different proof systems that provide still the strong privacy guarantees even as the quantum computers arise.

And so that way we could have perpetual privacy.

The privacy you get from the first version is extremely robust in the sense that even with infinite computing resources in the very far future, looking back at a history of early confidential Bitcoin transactions in the short-term future, you wouldn't be able to decrypt the values.

And that's because it's the same reason that they become emplayable, which is basically you can forge anything if you have a fast enough computer. So that means that if we if we if we keep that perfectly anonymous version today and then we switch to a different one in the future that is post-quantum secure, the quantum computers looking back at old transactions won't be able to tell what their values were.

Yeah, I was gonna ask that question. Would the privacy compromise be retroactive in the future if if we had a quantum break of the particular kind of cryptography we're using? So in the case of the first type, which are have perfect privacy, then no, they wouldn't be able to learn anything.

But the second type, which is preemptively today immune to quantum supercomputers in the far future, we know what's going to happen with those, that all of the transactions of that type that happened you know, in this decade, would lose their privacy in the future.

So it would be a reach back in time and like see the values that were exchanged. So for some use cases, maybe that's okay because you know the trading strategy is not financially relevant anymore, or the pricing for commercial contracts is not relevant anymore. But for individual privacy, maybe that's that's not a good trade off.

So I think you know, a lot of people are quite attracted to the switch commitment idea. So you know, the quantum attack is not very concrete at this time. It's probably gonna take decades before we see anything threatening to the kind of discrete log cryptography that Bitcoin uses. And a switch commitment gives you a way to switch over to new crypto systems in the future without ever giving up on on a privacy.

And that's that's the version we've used in we haven't used switch commitments, but we've used the fully private version in Liquid. Of course liquid is not so much used for cold storage, so you know we have the opportunity for people to transact with it and benefit from that privacy and for the system to be upgraded in future years.

It can it can keep the privacy going forwards. So I think obviously people are more defensive about long term cold storage because they want to know that inflation will be protected for a coin that hasn't moved in five years, for example, because there are coins around like that. You mentioned the privacy improvements from Schnorr and Taproot, the Snor Schnorr signatures will be able to make different types of transactions look the same in the signature on the blockchain, and I believe Taproot is improving privacy because you could have like a rather complex script and you only have to reveal one kind

Of path of that script and not the entire thing. What other innovations can we look forward to from the implementation of Schnorr and Taproot besides the privacy improvements? I think it's also more efficient because

You're not, you know, the most of these scripts are set up so that there's a collaborative close. So you know, with Lightning Channel, both parties agree to close the channel, and then there's a non-collaborative close where one party tries to make a hostile close and you have to counteract it, or one party goes away, so you have to override it.

And so the assumption is that 99% of the time you'll have a collaborative close, and that will be very small and efficient. So it will save space.

We'll see what it brings,

But it does probably open the doors for larger smart contracts, more complicated smart contracts, more interesting effects, because you can largely rely on the economic incentive to do a collaborative close, because if there's some kind of complicated script that will be able to use the Bitcoin blockchain as an arbitrator in the event that somebody tries to do something, you know, close it in a hostile way, they can override it.

And so then there's no incentive to try to hostile close because you won't benefit from it.

So that kind of top level,

You know, we close it collaboratively, or we go to the Bitcoin blockchain as the adjudicator, and he's gonna decide in a mathematically defined way, is interesting. I mean, it gives it gives an efficiency benefit to the Bitcoin model.

The Taproot contains also MAST, which is less talks about, but it's a way to have multiple branches. So the top level tap root only gives you one if branch, but inside that you can optionally have multiple branches with different scripts to use in different scenarios.

So beyond Schnorr and Taproot, which seem to be sort of the next two improvements that are likely to be merged into the base layer, what are some other upgrades on the horizon that those of us who aren't kind of following the mailing list and other forums like IRC and stuff where this stuff's being hashed out, what are what are yeah, what are some that are on the horizon that we might not know about?

I mean, some of them are actually not consensus changes, but kind of key management and signature coordination protocols that are for passing messages between wallets. So there's one something called PSBT, which is partially signed Bitcoin transactions, and that's pretty interesting in making it easier for different wallets to interoperate and participate in multi sigs.

So one of the challenges today is that if you if you make a multi signature wallet, and blockstream has one of those in in the green address, I think it's the first smartphone wallet with multi-signature, for example, dating back to I think 2012, 2013, is that if you introduce a new smart contract and you want other wallets to interoperate with it, you have to collaborate on that.

Each wallet that's able to participate in a new script template has to be written with that script template in mind. So it makes it hard to innovate because you need a lot of coordination between the different wallets, and there are multiple wallets on the market. So PSPT partly overcomes that in a clever way, which is that it makes a general format for passing signature requests so that you can have you know two or three people co-sign something, and it does it in a way that a wallet can contribute to a signature without having been written with a specific template in mind.

So it's able to parse a signature request and figure out how to co-sign something that was maybe constructed as a specific script template by a power user or a different wallet after the wallet you're about to sign with was written. So it has no foreknowledge of it, but it's able to generically sign whatever parts of it it can sign.

So obviously, with you know more nuanced or advanced use cases, they'll still need to be wallet understanding, but for general kind of multi signature, that's pretty interesting. And so I think we'll see more and more wallets switch over to the PSBT. Another non consensus thing is descriptors and MIDIScript.

So let's start with miniscript. So MiniScript is a way to so Peter Will did this work with somebody at Blockstream and intern. And they

The idea there is that there's a script format that translates into Bitcoin script. So the other person who worked on it is Andrew Pulstra and Sankrit Ken Jacar, who was an intern at the time at Blockstream.

So there are multiple people that worked on this. But the idea is that you can write Bitcoin script in a in an easier to read, more descriptive language and have it translate into Bitcoin script. So it does it in an efficient way, so it kind of brute forces and finds the most efficient representation of the way you've expressed a script.

So it saves a little bit of space quite often. And it's it's decompilable, so you can take a Bitcoin script and decompile it into this miniscript language, which makes it easier to understand what a Bitcoin script is doing. So because Bitcoin script is a fourth like stack machine language, it can be a little bit hard to understand what moderately complicated Bitcoin script is actually trying to do.

So Miniscript makes that a lot easier to read. So the idea is really just to improve the ease of writing scripts and things like that.

And the last thing I mentioned there was descriptors.

So today there's some aspect about how wallets are written where you know there are seeds, a couple of different seed standards, but they can be used for different types of wallets with different multi-sigs and so on. And so when you put a seed into a wallet, it has to kind of brute force different types of seed format and derivation paths, so ways that the keys are derived, and see if there are any funds on them to figure out what kind of wallet this came from.

And you know, the compatibility is not always perfect, too. So maybe it doesn't find the wallet because it doesn't have that newer type of wallet or something. Where what descriptors are is a way to explicitly describe in a machine readable compact format exactly what this wallet is doing. So then when you back up a wallet seed, you can also back up the descriptor, and then that can be imported into wallets, and they can tell you either you know they know exactly what to do, and they don't have to brute force to guess what type of wallet it is, or if it's a dis if it's a descriptor type that they don't support, they can tell you so, so you know to go find another wallet or upgrade

The wallet. So I think descriptors are a pretty good innovation in sort of standardizing and avoiding the guesswork in wallet interoperability, because there are more sort of formats and types of wallets that might be useful to create in the future.

And it also helps people who want to create kind of power users who want to create a customized multi-sig with some extra rules in it, that there should be a way for their wallet to be told about that and for you to back that in information up. Because otherwise you could run into an issue where you got too creative in creating a customized wallet and you forgot the exact format of the wallet.

So even though you've got the seed, you don't know how to recover the files. So descriptors would help with that. And then on more consensus like things, there are some other things going on. So there are some new versions of Lightning that people are analyzing and considering to implement that require more soft forks.

So recalling that Lightning itself needed a malleability fix, and SegWit was the method used for that. And also CSV was beneficial for Lightning. So that was another soft fork that was introduced in the past. So there are more things like that basically for new and more efficient versions of Lightning.

So one aspect of Lightning at the moment is that if you there's a punishment transaction. So if you if you do a hostile close and the other party is able to override it, you can lose money in the process.

And you might say that's desirable because it disincentivizes hostile closes.

However, in practice, there are sometimes accidental hostile closes or accidental closes that look hostile but actually are not. They are backup failures and mistakes. And it's suspected that most of the most of what look like hostile closes are actually accidental closes.

So eltoo, which is a proposed new version of Lightning, avoids that so that if you do an accident or close, it's just corrected with no penalty. But to do that and to make some other aspects of it

A bit more efficient. They need something called SIGHASH_NOINPUT, which is another signature flag. And there is also another version of Lightning called L3, which is a pun on like version three. And that needs actually different different changes.

So it's a little bit ambiguous at this point. Which change is preferable, you know, if if we get soft forks for both versions, or if L2 is implemented or L3 is implemented instead as being slightly slightly better. There's another kind of software called check template verify, which is a kind of simplified covenant.

So it's a way to commit to transactions without sending them. So normally a Bitcoin transaction has a set of inputs and a set of addresses or script pub keys that the coins are being spent to, which are the scripts that enable them to be spent in them in the future. Typically they're hashed.

So they're like pay to public key hash or pay to script hash. But this check template verify, what it does is it doesn't disclose all of the outputs, it just hashes a set of outputs, and so it makes the it makes it more possible to have a transaction that has a large number amount of outputs and reveal them later, which can you know it enables some different types of protocol where maybe you have a layer two system that subdivides

Outputs or wants to be able to close lots of channels at the same time and avoid having a problem with fees if it needs to close hundreds of transactions at once because they can be kind of committed to in a small transaction and then spent later by revealing more of the details at time spent.

So that's an idea.

I'm not sure how the priority between these different soft forks stacks up. It partly depends on people's level of interest and interest in the use cases they enable.

Another sort of more long-term thing we could talk about is simplicity, which is kind of even more next-gen script system for Bitcoin, on the most concept.

I really appreciate that overview on what's going on. I think it'll be very appreciated by the listeners out there. So to close up, I know you're gonna be at the Bitcoin 2020 conference. I saw you there last year as well. Can you give us a little preview of what you'll be talking about, if you know at this point at the conference? Yeah, so I as I mentioned simplicity is something else on the horizon, and this is a sort of ground up redesign of Bitcoin scripts by somebody called Russell O'Connor.

There's another PhD computer science guy who's working at Blockstream now, but when he initially proposed Simplicity, this was pre Blockstream, I think, 2012, as so he has a PhD in formal language security, so things like proof assistance and being able to prove things about programming languages and programs written in those languages.

So the idea with Simplicity is to make Bitcoin self-extensible. So do it in a security-first way using techniques from formal proof systems. So he has a kind of actually very low-level script language where you do simple operations involving combinators.

So there are nine combinators, which are things like string concatenation and logical operators. And to illustrate how low-level that is, you can't, you know, you can't even add two 32-bit numbers together in this language, or even you can't even add up two one-bit numbers together.

You have to first implement a one-bit adder using these low-level combinators. So the aspect of this, which is simple, as in Simplicity, the name, where that comes from, is that the semantics of the language are designed to be very easy to understand and to have very clear mathematical formal definitions.

So then even though something like a 32-bit adder is built out of many hundreds of these combinators, it's it be it inherits the formal semantics, and the formal semantics are very needed and useful to be able to make statements about software and verify that they would be true.

So as an example of the direction and power that gives, the simplicity interpreter, so the Bitcoin script has an interpreter. There's a simplicity interpreter. It's implemented in SimpliCity, and there is a formal proof that the simplicity interpreter correctly is able to correctly execute all simplicity programs.

So in other words, any any conceivable simplicity program you could write will be correctly interpreted by this interpreter. So that's a kind of example of the very strong blanket security guarantees you can provide. So other other examples are that you know if you if you write a smart contract, you can you could construct a predicate to say, well, you know, it shouldn't spend money except in this way, or there are no other ways to spend money apart from this scenario, and then you can prove it.

So you can prove predicates about your software, and you can also prove the worst-case runtime, the worst-case memory consumption, that it doesn't overflow any array bounds. You can make proofs of that with mathematical certainty. And the so that that's about the mathematical guarantees, and then about performance because it's an interpreted language.

There's actually a path to being able to formally prove that C implementations of common library functions in simplicity, which are called JETs, to prove that the C implementation is the same as and therefore also correct in all circumstances, as the simplicity implementation of a library function, for example, and he has formal proofs of correctness of, for example, a SHA 256 implementation in C as compared to the simplicity reference implementation.

So we've done a couple of developer releases of this over since August last year, and we have another one coming up in in the next month or so. So for the Bitcoin 2020 conference, I will hope to be able to talk in more detail about this and show examples.

So initially we are targeting elements, which is the open source platform under liquid, and hope to add simplicity to liquid towards the end of this year, so that people will be able to transact value and extend liquid itself.

So as an example, and then and then later that would you know maybe find its way into Bitcoin in the way that previous technologies have been tested in sidechains. Maybe that would also eventually find its way into Bitcoin in some years if people like the flexibility and power that gives with the security guarantees.

So, as an example of the self-extensibility and the power of that, if Bitcoin had simplicity today, then Schnorr and Taproot would not be a software, they could just be implemented using its self extensibility and using an appropriate level of jets or like predefined common functions to you know compute disc compute big numbers, analyptic curve calculations and common serialization and so on, it would be a small enough program, you know, order of dozen bytes kind of thing that you would be able to just run it.

And if there was a more complicated program that introduced something bigger, let's say in like confidential transactions with you know more codes, more lines of code kind of thing, you would also you could still do that as as a program, but you could also then have a mechanism to soft fork in a new opcode or a new library function.

So to introduce a new library function as a soft fork. And the interesting thing there is that the it's not a soft fork in the way that soft forks are done today, in that a Bitcoin full node that didn't have the soft fork upgrade to this new library function, new jet function, would still be fully validating the blockchain.

It would just be slower because it'd be interpreting that part, whereas a soft fork upgraded version would be able to execute that with native code. So that's interesting because today, as soft fork, if you know if you don't upgrade a Bitcoin node after a soft fork has gone through the process, then you're partly SPV.

You're sort of assuming it's correct because you don't understand it, and assuming that other users, their full nodes are verifying it so they would warn you, or that miners are protecting you because they wouldn't want to economically make invalid blocks. So you're you're a sort of elevated risk that miners could fool you effectively by not upgrading.

So in a post-simplicity world, that wouldn't be the case. Your node would just get slower over time until you upgraded. And if you didn't have a strong need, if you had a fast computer or you didn't have a strong need for fast processing of blocks, you know, so minus half reasons to want to process blocks fast.

So if you weren't mining, maybe you wouldn't need to upgrade very frequently. That sounds exciting. I'm looking forward to listening to the talk at the conference. Appreciate the little preview there. Adam, it was truly an honor to have you on the podcast today, the opportunity to speak with you. I really appreciate your contribution to Bitcoin, your continuing contribution to Bitcoin.

Congratulations on the success of Blockstream and you know appreciate the work that Blockstream is doing to support development on the base layer and extending Bitcoin on the second layer with liquid and I you know, like you just mentioned liquid is really useful as well beyond it the use cases that it's found already as a testing ground for potential future Bitcoin technologies.

So I think that's great. Thanks again for making the time. I really appreciate it, and take care. Likewise, thanks and good talking with you. Thanks to Adam for joining me. It was a really cool honor to have the opportunity to speak with him.

Let us know your thoughts about the episode. Adam is at Adam3US. That's ADAM3, the number three US. And I am at Citizen Bitcoin on the Bitcoin Twitter. That is the best way to support the podcast. Share it out on Bitcoin Twitter. You guys have been doing that a lot lately.

It really helped, and it's really fun to see your comments and thoughts about the episodes. You can also share the podcast with your family and friends. It's that time of the cycle where family and friends are going to be coming to you knowing that you're into Bitcoin, asking about how to get into it, how to learn more. You can pass along this podcast among many other great resources that are out there now.

The podcast website is citizenbitcoin.org. Thanks again to Swan Bitcoin for sponsoring this episode and to the Let's Talk Bitcoin Network for including the podcast in their feed. And don't forget to check out Bitcoin 2020 just around the corner. Hope to see you all there.

If you have any questions for me, please feel free to reach out. My DMs are open on Twitter. I'm at Citizen Bitcoin on Telegram and Keybase, and my email address is citizenbitcoin at PM.me.

This week's open source shoutout is Blockstream Green. Blockstream's Bitcoin wallet is open sourced on GitHub. Features include watch-only wallets, fee control, two-factor thresholds make it easier to spend small amounts, and Tor support on Android. It's all wrapped up into a beautiful interface.

Check out Blockstream's Green wallet.

Alright, that's it for this week. Take care out there, Bitcoiners, wherever you happen to be in the world.

FROM THE ORIGINAL EPISODE

Episode notes

Dr. Adam Back is a cypherpunk pioneer. His work on hashcash is cited in the Bitcoin whitepaper and, lesser known among bitcoiners, but just as cool, his work on telescoping circuits is cited in the TOR white-paper. These are among many more contributions to the field of applied cryptography. In this episode we discuss cypherpunk history, bitcoin’s history and future, bitcoin privacy and Adam gives us an overview of the state of bitcoin tech. This was a great one, hope you all enjoy it.

Citizen Bitcoin on Twitter

Citizen Bitcoin Podcast

Citizen Bitcoin Lightning Shop

Citizen Bitcoin Layer One merch collection

Music: Moon in the Sky by Hobotek

Links from the episode:

Adam on Twitter

Blockstream

[Blcokstream Green[(https://blockstream.com/green/)

Downloads