القائمة الرئيسية




[00:00:07] AG: Hello, everyone.

[00:00:09] CK: What's up, Alex? How's it going?

[00:00:11] AG: Going very well today. Very excited about this.

[00:00:15] CK: Me too. Let's get Adam in here and I'll go ping Aaron really quick. Rizzo is going to be a little bit late. He has a bit of a refrigerator emergency, it seems. Yeah. Can we get P up as a co-host, too, Eli? Thank you. Let me go ping Aaron really quick. Gladstein, if you don't mind following up really – Oh, here's Aaron. If you don't mind following up really quickly with Adam, that'd be fantastic. P, I don't know if you want to do some schilling for the conference while we try to get settled in here. Or not. I guess, I could do it. That's fine, too.

[00:00:46] P: I was going to say, yeah, man, we talk about it a lot, but this conference is going to be the best Bitcoin experience you could possibly have. It's going to be a combination of the best thing that's ever happened in your life, and also Disneyland, and also Twitter Spaces/Clubhouse, all the best conversations. There's going to be stuff everywhere. It's going to be the thing where even over two full GA days, you're not going to be able to see all of the amazing stuff that's going on.

Lightning is going to be a major feature. Everything else that you'd expect is going to be there. Everyone you'd expect is going to be there. If you want to buy a ticket, if you haven't already, first of all, shame on you. Then, second of all, you can use the conference code HFSP for have fun staying poor, and that will get you 10% off.

[00:01:27] AG: Okay. Adam's coming in shortly. Aaron, I figure maybe we can steer this conversation together and maybe rotate questions. I think it's important for people listening to know that Aaron is basically a historian of early Bitcoin technology. I've tried to do a little bit of that myself and we're going to have here someone who is essentially, one of the founding fathers of Bitcoin. You could think of it that way. I think, we got to start at with the beginning. Adam's here, so we'll get him up and we'll get going. Adam, welcome.

[00:02:00] AB: Hi. Hello, everyone.

[00:02:02] AG: Thank you so much for being here. We have Aaron from Bitcoin Magazine. I think, Aaron and I will just start to steer a conversation with you, Adam, that takes us from the beginning to today. It's ambitious, but we really want to start at the beginning. Let's go back to the late '80s, early '90s, to the beginnings of the crypto wars and the beginning days of the Cypherpunks.

Would love to hear Adam, if you could just give the audience today some color as to what that was like, and what was the big battle at the time and what intrigued you to start joining the list and contributing?

[00:02:36] AB: Yeah. What intrigued me to join the list, the Cypherpunks List and get interested was the release of PGP, email encryption program. You could use it to encrypt files as well. And the change in the balance of power that brought about that individuals could coordinate online and exchange messages that the establishment and the spy apparatus couldn't decrypt. That caused quite a lot of discussion about the gradual change in the balance of power.

I happen to be aware of that RSE encryption algorithm that PGP is – That's the main building block is this public key cryptography technology that had been invented in the late 70s. Because a friend of mine who's doing a master's degree while I was doing a PhD was trying to implement faster, because CPUs weren’t as fast back then. RSA was CPU-intensive. He was doing it on a distributed system, like a system with communication at work and many cause. We were both working in distributed systems. My PhD was in distributed systems.

Yeah, I thought that was a very interesting and intriguing combination of positive, societal value and mathematical cryptography, computer science. I went to see where people were talking about such things, and find out where people are talking about that and further things you could build on it. I found the Cypherpunks List and certainly, people were interested in a lot of related things, like disk encrypted, anonymity and privacy, so how Finney is well-known in Bitcoin circles, was already active.

At that time, there was a remailer technology that would provide you with anonymity to post, to send emails, or post on the discussion list, basically by sending your email through multiple hops. It didn't have any encryptions. Somebody who had the ability to read everything on the Internet, or a lot of things on Internet, like the NSA and GCHQ. People like that were probably be able to do, would be able to tell where the message came from.

How Finney implemented P2P encryption into that remailer technology, so that it would be a lot harder. We’ll be looking at messages. They would be encrypted. Then there was a batching, so that each remailer would receive, let's say, a batch of 20 or 50 mails, shuffle them and send them out again, so you wouldn't be able to tell which email, in corresponds to which email. I don’t know, if you're watching it as a black box. That technology improved over time to become Mixmaster, which was a way to standardize, to make a fixed size message chunks, so that you couldn't tell which message was which based on the size, which was in case, the original one.

[00:05:24] AG: Adam, it's interesting for us to reflect back on the fact that a lot of the contributors, to what would later become the Bitcoin Project started in the privacy space, and they were obsessed with privacy and intrigued by it. I guess, the background for the audience would be that cryptography used to be the domain of the military and of governments.

As you mentioned, that late '70s, academics in various places, but especially at Stanford came up with this idea of public key cryptography, which about a decade later was actually implemented in a way that made it easy for PC users to exchange private messages beyond the control of spy agencies.

As you mentioned, Hal Finney, who was essentially, the first person to receive a Bitcoin transaction from Satoshi was an early, I think, the second PGP contributor technically. You have a lot of people like yourself working in this space before it became about money. I don't know if Aaron wants to weigh in on that transition as well. Would love to just focus in on this a little bit, this provenance of the people who fought for digital cash and how meaningful it was that they started out as privacy advocates.

[00:06:29] AVW: One of the interesting tie-ins here is that Adam Back just met the remailer system. One of the problems that the remailers were facing was at that time, spam. Anyone who was operating a remailer was essentially doing it as a free service, but that free service was starting to be abused. That's one of the reasons why the Cypherpunks started to look into, how do you make it, so that running such a system, running a remailer is actually incentivized. For that, you might need some digital cash system and a post-its scheme, right? You're paying post-its to whoever – a form of post-its to whoever is running these servers.

That's, at least, one of the reasons why the Cypherpunks started to think about that, including Adam, very specifically, of course, with Hashcash, which was meant to be an anti-spam system to counter exactly that spam that the remailers were facing. Maybe Adam wants to expand on that.

[00:07:27] AB: Yeah. As you said, the remailer’s were volunteer of things and it was not without legal risk. Sometimes people would send something threatening, or obnoxious to the remailers, and the authorities would come to the exit remailer. The last one in the hop that would actually send the email and try to push them to reveal the previous hop. Of course, they wouldn't know because there's no logs and it's encrypted and stuff like that. Nevertheless, I think the EFF maybe ended up helping defend a couple of people in that position, but there were lots of them and when one failed, another one took over. There were 50 to a 100 of them at various times. I operated one for a while, which I rented a shell account from a one-man ISP, basically, that was in Switzerland at a time when I was living in the UK. I had some jurisdictional complexity to it, to make it more difficult to work your way back.

Just figured that I would operate it, until such time as there was a major issue. Then I would shut it down and that would be most likely the end of it. That's actually how it progressed. It ran for a few years, some years. Then the Swiss Federal Police turned up at the fellow whose many ISP it was and demanded to know more. He told me and I switched the remailer off. I don't think either of us heard any more about it. We don't know what threatening email was sent, but it was shut down and it did its job for a number of years. That was the remailer.ch was the domain. I bought a Swiss domain for it as well.

[00:08:56] AG: I was just going to ask Adam, before we get into your practical implementation of — and thinking about how you would address this issue of spam with remailers and improving that, can you give us insight in just the cultural moment, like science fiction authors had started to write about e-cash. You had David Chaum and his team out in Amsterdam around 1990, starting to work on DigiCash. Was there an excitement among privacy advocates about the idea of government of cash beyond the control of governments? Was that something that immediately interested you, or was that only something that came later for you?

[00:09:29] AB: Yeah. That was a were different applied crypto and perhaps, enhancing technologies as they were called. There were a conference series on that. Of course, the Cypherpunks list itself, which was very applied. Now, that'd be more interested in writing code than writing papers.

Apart from disk encryption, email, encryption, anonymous messaging, pseudonymous messaging, so that you could receive a reply, like reply with a remailer, that was another piece of technology they built, various people in the Cypherpunks list. Steganography was another one, so that you could hide an encrypted message in an image and people wouldn't be able to tell, but it was a message, even without the keys.

Electronic cash. I think really, electronic cash was the elusive one. It was the hardest thing to build. It's very difficult to know how you would bootstrap it. Cause people originally assumed that you would need a partnership, or service from a bank to send money in. Then you would have electronic cash tokens that you could transfer between users very anonymously and then convert them in and out of fiat at some point in between. People were very excited about building that, but it was a very difficult thing to build. DigiCash tried to commercialize that. They implemented the technology. Divisional technology dates back to a 1985 paper by David Chaum, called 'About Blind Signatures'.

It's quite elegant and a simple piece of technology, but it started the strongly private electronic cash, which could be both sender and receiver anonymous. It was a centralized protocol. It went through a central server that was your double spend database. There was no way to audit it, so you had to trust that central server to not create more coins than there were fiat in a bank account. They operate a demo server. People try to bootstrap of value actually, because they said that there'll be no more than a million of these currency units. They would email you, somewhat like a Bitcoin to force it. You could email them and they'd send you a few coins. They promised, there'll be no more than a million.

[00:11:32] AVW: Yeah. To be clear, sorry for interrupting, but just to make it clear to the audience, this is basically another – The first one that you just mentioned that essentially had to be backed. Then they also had this demo version, the cyber box, which they just promised, there will only be a million of this. It basically had no value. I think, that was their intention. It was just a demo thing, but they said there will only be a million.

[00:11:54] AG: We're talking about David Chaum’s DigiCash company and the currencies that they were issuing in the early '90s.

[00:12:00] AB: In fact, their thought was, this is like a Bitcoin test net right. Don't place value on these, but you can play with them. We will issue a million of them. I don't know why they thought of that, but it created a scarcity concept. A number of people on the Cypherpunks had a go at selling, but just selling things for them. We figured it's only, like there weren't that many people involved, but it's only a million dollars. If we just treat them only a million units, if we treat them as dollars, as a starting point and just sell things, well, and if enough of us do that, maybe it will bootstrap a value.

People had a go at doing that. I had some t-shirts, which were actually about the export restrictions on encryption software. Had a small implementation of RSA on the t-shirt, which was short enough that you could type it in. That’s the protest at the silliness of that restricted that export restriction from the US.

I was selling those online anyways, so I figured out I'll try selling them for these DigiCash demo coins and other people did similar things. Before we got very far in this rogue, unauthorized experiment, the DigiCash went bankrupt and the double spend database went offline. Now, you wouldn't be able to tell if your coin – you, wouldn't got to prove to somebody else that your coin was valid or not, because the way you spend coins in the system is you send them to the person and they check if they're valid by a redepositing them on the server and getting a fresh coin as all the server was gone. That was the end of that.

[00:13:26] AG: If I'm not mistaken, when you originally released the Hashcash concept, which we'll get into, you mentioned at the time that DigiCash type projects may run into trouble. In the meantime, maybe this could spark some parallel structure that could help, in the meantime. I think, it's also worth noting that the creator of Bit gold, and Nick Szabo, he was also contributing to DigiCash.

It seems like, quite a few of you who ended up contributing to what later would become Bitcoin were intrigued by DigiCash, but then saw the problem with the centralized mint. Then, that was the next great challenge. Is that correct?

[00:13:58] AB: Yeah. I think, this demo server didn't have the banking connection. Then, the fact that it was centralized and failed showed and perfectly to people that this single point of failure was a problem, and it wasn't going to be a very robust electronic cash system, even if they did get a banking service. There wasn't a demo server that was real dollars, or something. That started people thinking about whether you'd be able to distribute it, distribute it, double spend database.

I’m not quite sure of the sequence, but in any case, I was operating this remailer and this is how I came about with Hashcash and then these distributed versions of Hashcash design concepts came about in the next year after that. In ’97, I was operating a remailer and dozens of other people operate similar remailers. There was some systematic spam, which was not commercial spam, like not trying to sell Viagra pills or things like that, with incredibly low success rate, but email is essentially free. These were just nuisance spam. It would just be random numbers and sent to Usenet, which is a very distributed broadcast chat system. That's still around, but less popular. It magnified the denial of service. They could send some random numbers through a remailer, remailer would send it to Usenet, Usenet would broadcast it to thousands and thousands of sites around the world.

Then, the system of administrators of those sites would get annoyed about the spam. I suppose, the people doing it wanted to create a backlash against privacy. They were hostile to privacy. This was our operating theory. The spam was trying to discredit remailers and create a system administrative backlash, so that they would try to block the remailers as exit points, as send us to Usenet or something like that.

It caused me to think about, normally at that time, and still, anti-spam is done by just blocking IP addresses, centers. Of course, you can't do that with anonymous system, because the whole point is you don't know who the center is by design. It caused me to think about it in a different way, which is what's the real problem. The real problem is it's free. It's a pity that DigiCash didn't make it. Credit cards, or credit card processing was difficult and centralized and not everybody has one.

[00:16:10] AVW: There was one more problem, if I can jump in real quick. Because I want to ask, I want to ask if you remembered this. You mentioned the problem of centralization of DigiCash. There was another problem, which was that it was patented. This was a huge source of frustration for the Cypherpunks, including yourself. I've read messages of you, where – because the Cypherpunks had this idea that, you have this really cool technology. The way to improve this, and the way to actually make this work is to let people experiment with it and let people figure out how to make it work better, but that was actually blocked off by these patterns. At one point, you grew so frustrated that you offered on the Cypherpunk list, let's just by this patents then. Do you remember this?

[00:16:50] AB: I'd forgotten that. But it was definitely a point of contention and there was a party when patent expired. It was the first upfront cash patent to expire, because it was so early. It’s where that spiraled sometime after 1985. Around 2000 –

[00:17:04] AVW: I think even earlier, Adam, I think the original paper was 1980.

[00:17:10] AB: Could be. The blind signature paper?

[00:17:11] AVW: The paper that's referenced as Big Brother. I'm not sure. He had a couple, of course. But I think the earliest digital cash proposal by Chaum was 1980.

[00:17:20] AB: Ah, you’re right. Here we go. 1983, blind signatures on untraceable payment. There you go. Yeah. I guess, after the 20 years or whatever the rule was like, that the patent associated with that, which presumably was great sometime after it expired and there was a party for the expiring of it.

Before that time, people were trying to think of different ways of achieving the same result. There was another, actually better scheme by somebody – another cryptographer who was actually David Chaum’s PhD student; a friend of mine, Stefan Brands. He got to discrete local way of doing the same thing, which is more flexible and powerful, but unfortunately, it also patented it.

Yeah. I think, part of the problem with patents is that for Internet protocols, the ITF Internet engineering task force likes to have royalty free and patent technology, because it presents a barrier to adoption. I think, it's actually counterproductive to patent something. Their argument of patenting is well, they can use it to present to investors to raise money, to commercialize and build the technology, but it tends to do the opposite, which is, after DigiCash went bankrupt, it was bought by a large company and put in a big patent portfolio and never used until it expired. That was the end of that.

[00:18:31] AG: Before we get deeper into what the next e-cash projects were, when we spoke, you talked a lot about how you were maybe disenchanted by the mainstream approach to fighting the surveillance state, which started to emerge in the '80s, which said that maybe we should just ask governments to stop it. You basically said, there's this other option, which is we could just seize our rights with code.

Could you talk a little bit about that strategy and how the Cypherpunks, basically, took a different line than others who are also concerned with the surveillance state at the time? Just the two different strategies of lobbying the government and trying to work to make better public money, or better public communications versus creating open-source alternatives?

[00:19:14] AB: Yeah. In a lot of cases, you would actually have right and legal sense, legal and regulatory sense, but they will be ignored, or eroded online. The other thing is, when you want to improve the balance of power for the individual, if you ask permission from the establishment, the answer is going to be no. You're getting mission creep from establishment and government and regulators. It has its own inertia. Typically, the way that things work out in practice is, society reaches a new norm. The archaic laws say, it's illegal to do things, but 90% of the population are doing. Eventually, it’s an egregious test case and they haven’t turned it.

There are various people victimized by these archaic laws in the meantime. You can view the legal landscape as a trailing indicator of society's views and it never – almost never leads. That, from that perspective to affect change, it seems like, society is led by adoption, innovation and just doing things becoming popular, and eventually, the laws will catch up, your regulations will catch up.

On the one hand, a lot of these things, the rights to freedom of association, freedom of speech and things are entrenched in laws and regulations in many countries. Nevertheless, the online trend was actually depriving you of those. The way to raise it up to a certain is to protect them with cryptography. That's what the segments were about. Certainly, this concept of just building it and don't ask permission was something that to me and John Cornwell, who were some of the Cypherpunks co-founders and Eric Hughes wrote about – Eric Hughes wrote a Cypherpunk’s manifesto. I think, it says something pretty much explicit along these lines like, “We don't care what you think we're going to build and do,” or something like that, paraphrase.

Yeah, that's that direction. You can see a more modern version of that. Well, that's old news now. When Skype first started doing online audio and video voiceover IP things, the telecom regulators and the telecom companies, many of which are government-owned, hated it, because it was going to erode their long distance – egregiously expensive, long-distance calling plans. They lobbied against it. Skype didn't try to become a telephony provider and get all the licenses internationally. It just built the app and went for it and dealt with the legal attacks behind their backs. That just became too popular to stop and say, the online use of voice things, effectively, such as we’re doing now, you got to be effectively able to bypass a lot of restrictive telephony rules.

[00:21:44] AG: What was it like to watch the gradual concession, essentially, or defeat of the US government and the Clinton administration with regard to the clipper chip and basically, its plans to try and penalize, or criminalize citizen cryptography, over the decade, over the '90s? What was it like to be a part of that and watch that?

[00:22:04] AB: Yeah, it was interesting, because in principle the restrictions seem laughably pointless, because the fact, too, everybody had all the encryption software they want, and the Internet has no borders. As John Gilmore had observed, actually one of the Cypherpunk co-founders, the Internet view censorship was damaged and routes around it. That's famous quote that he said at some point.

The fact that people were using it using encryption software and encryption libraries, and some of it was written internationally and not in the US – it seemed frustratingly stupid, but I think the pragmatic, kind of what the US national security apparatus, like the NSA and their counterparts in other countries. In some countries, there were also restrictions. Mostly not. Was actually to impede the adoption of encryption. They knew that it wouldn't stop it, cause incident’s porous, but they figured that it would be harder to inter-operate and harder for companies to make encryption related software available for download. It would just slow adoption, and more encrypted things with less control. That's why.

It became an impediment to finance, basically. Eventually, it was overturned, because enough companies lobbied. The US has a strong free speech and anti-censorship, or printed books. For example, some people have printed the PGP source code in some thick books, but some people in Europe scanned. There wasn't really much they could do about it, because they couldn't quite bring themselves to ban a book. That would have been difficult politically. It made a bit of a mockery of the whole situation until they gave up.

[00:23:38] AG: Would you say that the – to whatever extent that US has a free society, relatively speaking, that made a difference then in terms of the courts, the judges vis-a-vis had this happened in China, or some other country. Maybe that did matter.

[00:23:51] AB: I mean, it was certainly a correlation between the civil rights records, independence of courts and the freedom metric – the metrics for countries being civilized places to live in, where you have rights and you can rely on courts. Countries on the worst end of that would be the ones that would have in place a ban on encryption, and some anomalies, like France had one, the US had one. Other places in Europe didn't.

I think, it seemed like the strong precedent for not censoring written and spoken speech in the US health, because people, basically, transferred, they blurred the line between software and speech by printing it in books. In my case, putting it on a t-shirt. There are a few people who've got a tattoo of that program as well, because it was three lines of space optimized pole code, basically. The point was to make it as small as possible to show how silly it was that this could be restricted.

[00:24:47] AG: Aaron. Just going to ask Aaron, if there’s anything else you wanted to hit on that, the crypto wars before we move on to other digital cash projects?

[00:24:54] AVW: No. Let's move on.

[00:24:56] AG: All right. Adam, we have this decade between the failure of DigiCash, or creation of Bitcoin, or little more than a decade. Obviously, you were continuing to work on digital cash projects. You kept looking at your own Hashcash design. We had Wei Dai. We had Nick Szabo and then we had Hal Finney all come out with interesting new concepts. There was still this, again, decade plus gap. Can you talk to us a little bit about this gap and what was happening there and what you were up to on the digital cash front, let's say, from the late '90s, till you got that email from Satoshi?

[00:25:27] AB: I would say that, Hashcash itself was a stop gap, because it wasn't really re-spendable, but it did impose a cost. It had a metering benefit, and it was anonymous, because you could just mine them yourself, like freshly mine Bitcoins anonymous. Hashcash stamps were anonymous, and it was very scalable and distributed, because there's the double-spend databases are tiny ones on the recipients, so if we scale. It was interesting that it seemed like, multiple people recognized almost immediately that Hashcash could be an interesting ingredient in trying to decentralize the electronic cash system, like DigiCash, like that.

People were commenting within the next day, that looks digital gold, it's got some scarcity. There's a cost associated with making it and yet, it's electronic. It started a multi-year conversation about how to on the Cypherpunks list, mostly, about how to control inflation in it. People were worried that if you build a system that was based on it, as computers get faster, you'd get hyperinflation. That people struggled with how Bitcoin solves this is where the difficulty just then, but nobody figured out at the time.

By the next year, so it was ’97. By ’98, there were two proposals by – one by Wei Dai called b-money and one by Nick Szabo called Bit gold, which were candidate solutions for this, which were, somewhat decentralized, but lacking enough detail to implement and involving some human, or market judgment. B-money had basically, supernodes, so people would run servers and vote amongst themselves how many coins would be mined, or the cost of mining coins in the next month or something like that. Nick Szabo had the other idea, which was just, you make stamps and let people make them as fast as they want. If a lot are made in a month, those are not rare. A few are made, they're rare. Then, you assemble a standardized bundle of stamps and that becomes acquaint standardized by total scarcity of it or something.

He envisaged a collectible market, like physical stamp collectors. There are people that specialize in making a fixed value book out of a mixture of scarce and non-scarce stamps. It’s complicate and indirect. Also, in the b-money case, hard for – both cases, hard for a piece of software to automate that, that involves human judgment in both cases. In my mind, that's one of the key things that Bitcoin solved, because if you look at the b-money and Bit gold discussions, particularly Nick Szabo had written about a lot of related things. He'd actually, originated the idea of smart contracts five years before Hashcash, or pria, something like that.

He talks about in a distributed database, by sometime general's problem, the coordination problem and using Hashcash to create stamps and b-money uses Hashcash. Basically, the realization was as Wei Dai put it, you could have an electronic cash system without a banking interface, if you could mine the coins into existence. All of these systems, b-money, Bit gold and Hal Finney’s RPOW used proof of work to mine coins.

I think, the ’98 to 2004, actually, I did try continue to try to find solutions to a lot of these things. In my spare time, I actually worked for zero-knowledge systems in Canada around ’99 to 2001. They had licensed Stefan Brand’s electronic cash system, which is another very private electronic cash system. They made an implementation. There's also a central server model. I tried to find a way to make that offline re-spendable. It turned out that the idea I hit on was actually already discovered by somebody else. Described it to Stefan Brands and he said, “Oh, yeah. There's a footnote in this page of his thesis that describes it.” At least, I found something.

That was still a reactive security model and relied ultimately on a central server. Basically, it was hard and nobody found a solution. Then Hal Finney in 2004, made use of a new technology, which is the trustworthy computing. A lot of people weren't very keen on trustworthy computing, because it meant that there was a hypervisor in your CPU, or connected to your CPU that could run code that you couldn't inspect, or modify. It was intrusive in a way and controlling. You couldn't fully program and control your machine anymore.

Hal Finney found a way to use it to security advantage, because you could make this thing called a remote attestation, which would prove to a third-party what software was running in this hypervisor. That would allow you to trust it, assuming that the hardware vendor hadn't colluded with a server operator to extract the keys from the hardware, and the hardware generated its own keys, a little [inaudible 00:30:07] device. He bought one of these things and implemented RPOW.

Basically, he built a Chaum electronic cash server, where the way you would pay for cleanse, it was not with fiat, but by sending it Hashcash stamps, and then it would send you a Chaum coin and you could re-spend the Chaum coin by giving it to somebody else, who would check if it's valid against the server that he ran. It indirectly solved the inflation trust for the server, because you could be sure that the server wouldn't create more coins than work was done, because you could audit the code and the code would prevent that. That was interesting innovation. Unfortunately, it's also has the centralization.

[00:30:46] AG: Aaron, do you want to just – you've explored and written a lot about this time and these innovations. Do you want to color in some context for the audience on these kinds of success of innovations that built on each other?

[00:30:57] AVW: Let's see. One thing about RPOW that's interesting. It didn't solve the inflation problem that was mentioned. I think, that was something that Hal Finney at that time, just skipped over. You have to double spend inflation in a way, if you double spend, you're creating more coins. Then you have the other type of flip-flaking, which Adam mentioned, which is computers got faster over time. Hal didn’t solve the second. Maybe that was a longer-term plan for him, but that was still a weak spot in RPOW. No, I think Adam gave a very good overview. I'm not sure what else to add to that.

[00:31:29] AG: I guess, what I want to get at here is that you start to see this concept of scarcity come in, and there's been this tension between privacy and scarcity, always. Not just technologically and from an engineering trade-off perspective, but also culturally, because it seems like even today, a lot of the privacy community is hostile to the scarcity component of Bitcoin.

Going from 2004 to 2008, Adam, we have Satoshi reaching out to you, not after a surveillance scandal, but in the middle of the great financial crisis. Indeed, a few months later when he launched, or whoever it was launched the actual software in the Genesis block, there's a critique of a central banking in there. Could you talk a little bit about how Bitcoin merged these two ideas, or communities together, Adam?

[00:32:18] AB: Yeah. I think, actually, maybe Hal Finney and Nick Szabo were a bit interested in hard money, like gold, and I had some interest in a return to a gold standard, that kind of thing. Most of the electronic cash systems, which just assuming previously, that you would connect it to fiat with a bank. Doing the proof of work to get into it, it does create the opportunity that there can be independent scarcity. The system can run under its own steam and it can create scarcity control in the supply curve, and that's what Bitcoin does.

If you make that leap, which nobody did before Satoshi, that you could just control the supply curve of direct production of new coins, and a distributed system could do that all by itself without reference to human concepts. What is a dollar? What's the price, that kind of thing? That can be all outside the system. Instead, it could be all automated. Then, you just see what the market does, right? The market will adapt and that will indirectly control the amount of work that's done, but it weren't very dim out coins that created. There's very interesting concepts.

I think, that certainly, Bitcoin was novel and different to the previous systems in the way that it uses proof of work to solve the race condition tiebreaker of the Byzantine General's problem. Basically, that it's distributed system. There's no one in charge. It's not even clear what is accurate time, what time is it right now? That's not clear. People got to lie. Yet, you have to coordinate which of transactions gets processed and ensure that nothing gets undone and redone.

The way Bitcoin uses proof of – to address that was all new. Bitcoin has a lot less privacy than the previous electronic cash systems, and the security model took getting used to for academic cryptographers. I would say, the first few years of Bitcoin's interaction with academic, like mathematical cryptographers was rough. They thought it was not very good. They thought it wasn't very private, because there was a idealized, mathematical set of assumptions about how electronic cash system should look.

There've been dozens of incremental improvements over the years that included the visibility of clients. Always the same privacy assumption that Chaum and Brands had. Bitcoin didn't have any of that. Each coin is like a pseudonym, so you can link the history of coins a bit, without names attached, but it didn't have this unlinkable payment privacy. The security assumption was also a little different. Looking at it from that time period, people would assume that it's pitting the good guys against the bad guys. If the bad guys had more money, or more hash rate, they could overwhelm the system and undo transactions and steal things, stuff like that.

It took people a while to get used to that, bounce of things. Of course, with Bitcoin itself to have a market price at all, the first few years, there was no price ranges. People are doing it as a hobby, for amusement, and a bootstrap event somewhere on the –

[00:35:22] AG: I think, we'll dive more into the goal of trying to make Bitcoin more private. First, it would be remiss for us to not ask you to reflect on the day you got this email from this person you ended up a few months later being one of the eight citations in the Bitcoin white paper. Obviously, this person thought what you had to say was useful. Can you just walk us through what it was like to get this email? Did you initially ignore it, or downplay it, or were you like, “Huh, this is really interesting”?

[00:35:50] AB: I'm pretty sure that the design and most of the implementation was probably already done at that point. The paper was there. From time to time, people will say that, such and such person helped Satoshi. It seemed like, as far as I know, I'm the first person to get an email and he'd already built it. He did it by himself. As far as anybody knows, it was one person. I wouldn't really claim to having influence design, because the design is already built. What he did cite was Hashcash. Bitcoin uses that as the proof of work mechanism and as the type, as a way to finalize and submit transactions under large amounts of work. To create a finality guarantee and distribution system and a risk condition, a tiebreaker, or things that happened by accident at the same time.

The email thread was really just about – talked about this online. There's a guy called Gwen who has a blog and he's collected some of the emails from Wei Dai and other people from that time. Basically, he was trying to cite things, and so he wanted to know what how he should cite Hashcash, and if I had any comments on the paper, which he linked.

Yeah. I read it enough to realize that it seemed pretty related to b-money, and didn't mention b-money. I was aware of Bit gold, but I think, b-money was published somewhere where I was more active. I remembered that one first. I mentioned that he might want to look at b-money, because it's related. I think, that is what caused Satoshi to add the b-money citation to the paper. Wei Dai has published his email, so it seemed like he turned around and emailed Wei Dai immediately and asked him for a citation for b-money. B-money is it's not like a paper or something. It's like a text, one-page webpage, like a blog entry or something. It's a very interesting idea, but it wasn't formally published. I think it just referred to the URL.

In terms of, again, email, I think, it didn't occur to me that Satoshi was a pseudonym, that that wasn't a real name, or it wasn't a real name of a person. If you have open-source software, or applied crypto, papers or observations online, you get emails from once every month or two from somebody who's got a question about something you did, or is using something and wants you to make you aware of it, so that you might find it interesting to look at it. It just felt like that to me. I think, my view on Bitcoin was that, like other people doing, and I was more of an applied person, but the academic authors and I read all many of the academic papers on this electronic cash topic and implemented some of the protocols in the past, that wow, it's really not very private, is it?

Then you've got these good guys versus bad guys hash rate. Because of the DigiCash experience, it did seem to me that it had one strong advantage, which is it's decentralized. It should be more survivable and slated. It would be interesting to see if it would bootstrap. That's where I got to.

[00:38:41] AG: You said something interesting to me, where you said that there was a paper that came out in ’99 that built on some of the zero knowledge, digital cash experiments. You said actually, in retrospect, you're glad you didn't mention this to Satoshi because by trying to use this privacy technology, it makes transactions much larger and it would have hurt the ability for Bitcoin to be as decentralized as it is. Do you want to just address also this ongoing tension between the size of transactions, privacy and how Bitcoin would ultimately be a system that users could control by running a node at home?

[00:39:13] AB: Yeah. Actually, I sent the Bitcoin system in early 2009 to some former colleagues, who were applied crypto people. I said, “This is interesting. You should have a look at it, kind of thing.” A few of them for my trouble, accused me of being Satoshi. I said, “No, because if I would have done it, I would have used this paper, because it has a privacy solution that still works in a distributed system.” Most of the previous electronic cash systems, the cryptography would only work on a single server, because you'd need the private key to operate it.

This particular system, so sovereign [inaudible 00:39:44] auditable electronic cash, anonymous auditable electronic cash, it has no keys. It's just using zero-knowledge proofs, and of set membership and things like that. It could be used in a distributed system, instead of having a central bulletin board, you can just broadcast it. Immediately, it occurred to me that wow, Bitcoin could have used that and it wouldn't have such bad privacy. I guess, that occurred to me later, like in early 2009. Curiously, other people made that connection later. There's a paper called a Zero Coin by Matthew Green and others.

Some of the old coins today, picked up the technology and used it. Some other academics made more efficient versions of it. They are actually optimizations of that paper indirect. For myself, I would certainly like to see Bitcoin – it's just technically difficult. To find a way to make a scalable and very private solution, like David Chaum’s original protocol, but in a decentralized way. The problem is the crypto is CPU-heavy and makes large proofs that maybe have a log scaling, like they get bigger the more coins there are. The systems which are able to achieve a lot more compact proofs are using very novel, new crypto and create a risk that they end up being proven to be incorrect and have a defect and lose all the money, or suffer unresolvable inflation, or something like that. It's at the bleeding edge of what's possible at the moment.

[00:41:13] AG: This tension is essentially, part of why you created Blockstream and why you got back into Bitcoin is you were like, “I want to find a way to make it more private,” right?

[00:41:22] AB: Yeah. I was working in another startup of early 2009 onwards, from before then, but up until 2013. I got very interested in Bitcoin in 2013. That the usual thing that people do, get down the rabbit hole and realize there's a lot more to this than what I had seen in the original paper. It clearly bootstrapped at that point. It was going somewhere. I tried to read everything there was, to try to understand the details. There wasn't much written at that time, so I ended up finding the Bitcoin Wizards IRC, and just peppering them with questions and they were very helpful.

It enabled me to catch up with more than was written down and look at the source code and things. What I was interested to do, so okay, it looks like it's bootstrapped. There's really not very much privacy, but this is my background, right? I've implemented electronic cash papers. I'm very familiar with privacy and hops technology, electronic cash protocols. I'm like, surely, there's some way to improve it after the fact, retroactively fit a linkable privacy, or some forms of confidentiality into it. I found a way to do what later became known as confidential transactions. that doesn't hide the history, but it hides the value, which makes it a lot easier to do conjoin, because you don't have to make the amount standard.

I makes it ambiguous, what's changed and what's not. It's really an interesting incremental privacy improvement. That somewhat helps the [inaudible 00:42:52], but definitely helps hide values. I thought, this would be interesting and try to explore with people who are closer to the implementation, or working on improvements, what it would take to integrate it in Bitcoin. It became apparent that they were dealing with complexity and security first, and it'd be difficult to get something as large as that into Bitcoin in a fast timeframe. That calls me to is instead of giving up to change topics, to try and find a way to make the coin more modular, Linux kernel has modules where you can write kernel modules that extend the core functionality, like many systems have layers of modules where you can do extensions.

I figured then that it would be very useful for Bitcoins to have a way to do modular extensions. That's where the sidechain concept came from, and indirectly Blockstream, because I wanted to build that and it's quite a large undertaking. I needed to recruit some very technical people, and all kinds of skillsets. People to build wallets, software and hardware, do applied crypto, do user interface, do the whole thing. That's where Blockstream.


[00:44:00] ANNOUNCER: Yo. What is going on, plebs? We’re going to take a break from our programming to tell you about the resurrection of our print magazine, starting with the El Salvador issue. Starting this fall, Bitcoin Magazine will be available on newsstands nationwide, and that retail stores, such as Barnes & Noble.

Don’t want to get off your couch though? No problem. You can also go to store.bitcoinmagazine.com. Skip the line and get each issue shipped directly to your front door with our annual subscription. I’m talking four issues a year that contain exclusive interviews and profiles with leading Bitcoiners, actionable insights on the state of the market, breaking news and cultural trends, along with powerful photos and artwork from the best artists in the world.

Subscribe today and get 21% off using code PODCAST at checkout. That’s P-O-D-C-A-S-T. PODCAST at checkout.


[00:44:54] AG: Yeah, just one more question for me. I would love to hear from Aaron on this. Your quest continues. Obviously, Blockstream is contributing to a sidechain that has CT on it. You've got Lightning that you're building and you're contributing to. Obviously, it seems like from a corporate perspective, you personally want to see Bitcoin more private, which is great.

How would you compare what's happening now with the, we'll call it the digital currency war, versus the crypto war of the early '90s, just in terms of feel, cultural feel? Is there some de ja vu? How would you compare yourself mentally, back then to now? Obviously, because of the money aspect, the fight is so much bigger, it touches so many more people. Would love to hear you compare that to eras.

[00:45:37] AB: Yeah. There’s definitely some transferable learnings. As part of PGP, and even Hashcash, I ended up talking with journalists who write for, like Wired Magazine, or different kinds of technical magazines, which there was some online, some in paper form. In discussing a topic with some establishment viewpoints that maybe pervade even mainstream journalism, you got to be careful what you say, or you get misquoted. You learn to say exactly what you want to be quoted on and nothing else, and not fall for the traps. Couldn't it be used for this bad acts, or technology is neutral, actually improves individual safety thing. You've got to think about how to communicate about things when the world at large is a little bit hostile or skeptical.

[00:46:26] AG: Meaning back then, they said, like the Clinton administration and the media were saying, “Oh, privacy tech and PGP will be used by criminals and pedophiles and terrorists and that thing.” Now, you're seeing the same thing again with Bitcoin, right?

[00:46:36] AB: Yeah. It's very reminiscent. People even called it the four horsemen of the apocalypse, which is the terrorists and so on.

[00:46:44] AVW: Money HODLers.

[00:46:46] AB: Yeah, it's just standard reframe of a catalog of hypothetical bad uses. Therefore, any new technology must be bad. Internet must be bad. Encryption must be bad. Having privacy online, you can have privacy in person, but they want to find you, having it online. They just use these argumentation, fallacy traps. Yeah, it was useful to learn how to do that, how to talk with journalists and not get tripped up.

[00:47:10] AVW: I think, one of the interesting lessons from that era is maybe also, that the crypto wars, the Cypherpunks were fighting the crypto wars, but it was not just the Cypherpunks. It was really a multi-faceted type of type of war, whatever you want to call it, where the Cypherpunks – Tim May described the Cypherpunks as the radical arm of that, like the Black Panthers arm off of the crypto wars. It was not just the Cypherpunks. It was also human rights groups. At some point, there was also just a Silicon Valley, like Netscape had their encryption broken. That was actually after a contest that was organized by Hal Finney. Netscape had their encryption broken, their export secure encryption. Then, Silicon valley made the arguments, Netscape made the argument that it was hurting their business. Now, you had all these different factions, the more radical Cypherpunks and then the human rights groups, and then the commercial enterprises. It's because they were all fighting for the same cost that they ultimately won, I think.

[00:48:04] AB: Yeah. It's interesting in that, and, for example, when we started Blockstream, the regulations were far less clear. It felt like a non-trivial risk that a major government could try to just blanket ban it. It seems like Bitcoin is somehow and navigated through that grown organically over time. At that time, no banks wanted to talk about Bitcoin or blockchain. That changed within a few years. Every bank had a blockchain R&D group. That probably added some establishment acceptance of the innovation, like it's a new Internet technology marble, and it arises from Bitcoin.

Today, of course, there are many financial institutions that have come around and it's Bitcoin, not blockchain. They have just had the first Bitcoin ETF in the US just a few days ago. It's been around. I think, the risk of regulatory fallout significantly impacting Bitcoin is receding. Suddenly, in the 2013 era, that was a phallus clear. It was just undefined, right?

[00:49:09] AG: P, you're with us now. Do you want to chime in?

[00:49:11] PR: Yeah. Thanks for having me. Yeah. Funny, you guys are talking about this. I'm actually curious to pick Adam's brain a little bit. Yeah, I was thinking about this today. I remember that Blockstream was doing a lot of work back in the day with firms like PWC and banks and financial institutions. You guys were doing some work with private blockchain. I guess, I'm just wondering, what insights you have there. Did we learn anything from that blockchain, not Bitcoin, period? Then, I guess, how have those conversations changed? Could you maybe speak a little bit about that? Because I feel like, it's changed significantly, but maybe we don't hear about that.

[00:49:41] AB: Yeah. Actually, we decided to not – There were banks that would be interested to engage technology companies to help with technology for pilot projects. We just could foresee that that probably wasn't going to go anywhere, and it would consume your focus and resources, so we ended up not doing any of those. The other thing with the private blockchains is I think, much of the value of non-Bitcoin applications of the blockchain as a public audit. If a blockchain is private, it's not really clear to me that it's delivering much value to the end users.

Therefore, it's not much different to the organizations either, it's just a different database and it's probably gets lost. We tried to make the argument that you could have confidentiality in a blockchain that was public and not needed to be private. You can use the internet analogy that originally people were talking about intranets, right? VPN, I rolled off a private little enclave of the internet with company internal information in it, and they were scared to connect to the internet proper. Eventually, they gave up on that and just realized, “Well, you can use the internet. If you need to encrypt something, you can encrypt it. If you need to access the office c computers, you can use a VPN.”

We would draw the analogy that because of confidential transactions, like which as a Bitcoin sidechain could be – it's like a VPN, right? Or, you had the confidentiality, so you don't need it to be a private blockchain, so you have all the encryption and access controls to get the confidentiality you're after, without losing the audit capability.

I think, the other thing is that you need blockchains to interoperate and for people to be able to transact with each other and build smart contracts out of the companies and individual developers, building blocks and contracts and financial instruments. That's going to be pretty difficult. Each organization is running their own private blockchain. They won't connect. Open networks tend to win.

The other thing you said, Peter, is the turnaround, so it became Bitcoin, not blockchain that apart from those other uses, like security tokens, I think, is where that's been heading lately, which is pretty interesting. The thing that turned it around is just the size of the markets. The crypto exchange market has grown by orders of magnitude, to the point that the volume on them is bigger than some national stock exchanges. That, and the wider investor demands basically, pushed financial institutions to offer Bitcoin financial products, like Bitcoin futures and Bitcoin ETFs and exposure to investors of Bitcoin in custody, or close trust and things like that. I think, that is what brought them around. There was a financial opportunity. They were losing out by – losing out on by not participating.

[00:52:23] PR: I guess, the other part of that question was really, have they really changed their mind about it? They know that they're offering trading products, but it seemed during that era, they were trying to compete against it with directly. Have they really stopped doing that? Or is it something else has happened?

[00:52:34] AB: I think, the general security token model doesn't have a competitive token. It's just a open network, back-office contracting method. If somebody is today on, existing financial infrastructure, they can issue a financial product and there's going to be a back-office, like some databases and servers that are going to evaluate options and exercise them if needed, or execute different things autonomously. That becomes possible to use on an open network, so that's one thing.

I think, yeah, certainly some of them are skeptical and say so, but are offering it because their customers denied it. If they don't provide it, their customers go to another financial provider to get exposure to it. You see some financial institutions talking about it in those terms, but they're also been, over time, some quite well-known macro investors who have taken large direct Bitcoin positions themselves and have spoken positively about it. It seems to be converting people over time.

Of course, the financial situation since COVID has probably taken us back to the Bitcoin Genesis “moral hazards,” and runaway quantitative easing, QE infinity, all that stuff, which causes people to think a lot more about inflation and an inflation hedge. I think, that has helped people see Bitcoin as an alternative to gold and probably, some probably away from gold into Bitcoin as a more modern replacement.

[00:54:03] AG: P, can we get you to talk about, given your extensive reporting on the Satoshi’s early days, or rather the only days that we know of, this tension between what Adam was just discussing, the fact that it was created during the great financial crisis and it relates to a desire to “fix central banking” in a way, versus the privacy component of the Cypherpunk spirit. What's your take on that?

[00:54:25] PR: Yeah, sure. I can riff off that. Yeah, I think one of the interesting things, my takeaway from looking at that time is I think, Satoshi definitely thought that Bitcoin was anonymous, that he had achieved anonymous payments. If you look at the early, his early writings and then the early bitcoin.org website, where he lists some primary value propositions. I think, while he does see it as an alternative to central banking, then, I think, there's at least a couple old website clips, where he just said straight up, “Yeah, this is anonymous payments are possible.” Obviously, we over time is that, that got walked back a bit.

Yeah, I'm still interested and I guess, speaking of that early period that seems like it's still part of the dream of Bitcoin, of trying to achieve a robust financial system. The way that Satoshi envisioned it is something that would compete against that level. I think, Satoshi’s tough though, too, because he's not super expressive. We don't have a ton of insight into his thinking. He's like, he’s very deliberate, to the extent that we can catch some of these little glimpses of things. I'd be curious to get Adam's thoughts on just Satoshi’s attitude towards privacy.

Because I don't even know to the extent that his perception on his own creation changes. We don't really have that insight. It's tough when you're looking at the old logs for Satoshi, because you can get glimpses of things, because you can see that he took action. He wrote words saying, like he thought big was private. Obviously, that's not in the white paper. Maybe that occurred to him later or, maybe he maybe that was something else. Maybe there was multiple people working on it, who just disagreed.

You can only really draw so many inferences. I guess, my takeaway on the privacy and the original part is, obviously not really there in the white paper, but seems to be there in the initial discussions when he starts circulating it. Then later on, there's a scrubbing and a moving away from that, where that language just changes. There's no declaration, or email list from Satoshi where he says, “Hey, these things aren't private anymore.” It just seems like that's a gradual realization. I don't know if Adam has any more insight from his reading of those logs. My takeaway as it seems to be more of a private realization that didn't happen. Yeah, certainly something that I wish we had more about.

[00:56:17] AB: You're right that didn't seem – In 2013, I went through and read the backlog on a Bitcoin talk forum. There really wasn't much in the way of technical motivation, like explaining the design considerations, or design alternatives. It’s just, here's the source code and here's the paper and here's how it works. Not what it was trying to solve, or alternatives discarded, or sparse information. It's similar about the use case motivations, but I think, probably the Genesis quote is pretty political in nature. It's like about a reform of monetary base, almost. Which was, actually, I would say was something that – some people had thought about, but not everybody. Other people were thinking about more about in previous lecture, we're thinking more about just the privacy angle. Not that it would be a reform for separate money from state, just that you'd be able to use fiat money anonymously and electronic form, or something like that.

By combining those two things, I think Bitcoin benefits a great deal, because at the time that it was released, and now there's a lot of concern about inflation and management of fiat currencies. The fact that it has a floating value create an adoption incentive. I think, people get exposed to Bitcoin for a lot of different reasons. One of them is as an investment. Then, they learn more about it, they philosophically become attracted to it. Or more philosophical reasons over time. I've got to assume that, accelerate the adoption a lot compared to something that was effectively like a stablecoin, which was a concept with the other systems.

[00:57:53] AVW: Yeah. Or worse than a stablecoin. Like RPOW, for example. RPOW works. It did offer the privacy benefits that Hal Finney and the other privacy advocates and Cypherpunks were looking for. However, it had this big problem that it didn't hold value very well. If it doesn't hold value, what then? People are, they're not very excited to accept it. If people are not very excited to accept it, then no one's accepting it, then you can spend it anywhere. Now you have private money, but you can't spend it anywhere. That's one of the things that Bitcoin very cleverly did.

On the one hand, of course you have the money reformers and the gold box, that really like this limited supply. On the other hand, the privacy should also like this limited supply, because now, at least works. At least, there's an incentive for people to accept it. Even if that's not their primary concern, at least, this economic incentive makes that it's being adopted. Now, you can actually use this money, which is fairly private at least, and hopefully, more private in the future.

[00:58:49] AB: Yeah. I think, the privacy is incrementally improving over time as well. Each major release of Bitcoin usually has some incremental privacy improvement in the networking, or the taproot proposal just now activated, has some anti fingerprinting, basically. The different types of transactions look the same, whether they're Lightning channel, or a single signature, or a multi-signature. In most cases, they look indistinguishable. That helps, because one of the ways that somebody would analyze a blockchain is to try and categorize types of transactions and cluster them, and then analyze within that, so they could identify, oh, that's a Lightning channel, that's a green wallet, but it's only sig type, which is distinct and stuff like that.

It can potentially solve that, many of those things once adopted widely.

[00:59:33] AG: Adam, we've got a couple of questions that people reached out to me. They want to maybe hear your take on — you spent a lot of your personal time and energy and obviously, your colleagues at Blockstream on during this block size war on trying to make sure to keep the blockchain in a state where the average person could run it at home. Why did you all spend so much time and energy on this? Can you give us some reflections on that period in Bitcoin history?

[00:59:57] AB: Yeah. Actually, the Blockstream as a company try to not have a official position. The views of individual people who worked on protocols, implementations varied a bit. There were a couple of people that thought big blocks would be good, or somewhere in between would be good. Other people thought too largely bad. I think, some people's views changed over the years as well. They thought large blocks would be okay, and then they came to realize that would actually be a problem.

I think, there's a couple of things. One generic argument is that if you look at Bitcoin's differentiator, what makes it unique and different from other systems is that it is permissionless and auditable. If it becomes too big and heavy, so that it can only be run by a business on million dollars of hosting per year or something, and nobody can verify it, then it's going to be subject to corporate interpretations. You've got to stay away from that extreme, or it will fail in a centralization sense. That was the concern, too.

The key differentiator from Bitcoin – I think, people have different views about what Bitcoin is. It seems to me and evidently to the majority of the market, given what happened after the forks, Bitcoin rapidly became the dominant financial outcome of it, is that the differentiator is that it's permissionless, and that arises from the decentralization, basically. If you try to scale it in a crude way, that will inevitably get eroded. That was one factor. Another factor is that networking is a – it sounds simple, but in practice, it's a area of computer science that is a specialized area and most network theory and most networks in practice, the Internet, GSM networks, 3G, 4G networks, they have some common patterns, which is that you don't broadcast everything, because broadcast doesn't scale very well.

They have to switch networking and not broadcast networking. It's pretty obvious to anybody with any networking experience that what you want to do is use the Bitcoin base layer as the censorship resistant, very survivable and robust, secure core. Then, you want to build switch networks on top. Obviously, Lightning is a switch network. It's much easier to scale switch networks, because not everybody has to deal with traffic. That's another thing.

The final thing was I think that Bitcoin has no governance by design. I think, I would describe governance as groups of humans and committees, or organizations that are going to decide, rules of management of some institution, or something. People use the word governance. I think, it just doesn't apply to Bitcoin. Without attributing [inaudible 01:02:43], I'm sure everybody at the time, both sides of the folk drama was just trying to improve Bitcoin and make it available to more people. The people that want a big block seemed to go about it in a sense of while they were going to make a run at it and set up a governance group of some companies and miners, and then they were going to tell the world how they were going to change Bitcoin.

That, I think more than I think, was unethical to what Bitcoin's about. You can't have a centralized governance process for a decentralized, permissionless system. It doesn't work. I think, that's what caused a lot of the backlash, that it wasn't – Bitcoin changes themselves are always opt in incremental improvements. Don't deprive anybody of previous functionality. There's no governance rate. There's no rule change of anything in variant, like number of clients, the supply, censorship, backwards compatibility. All that stuff's invariant. Having a centralized governance puts that invariant at risk. I think, that was part of it.

For some people, they would have been happy with doubling the block size. They didn't really mind. They weren't going to accept that being forced, or pushed by a centralized governance process. It was almost more about the way that it was proposed than what was proposed.

[01:03:58] AG: Thank you, Adam. CK, we've got questions coming in. I feel like, we could start taking some folks up here as well, if you want. Talking about some of the idiosyncratic, or interesting features of Bitcoin that were seemed weird maybe, when you first looked at, Adam, but maybe now seems more powerful.

One person's asking about halving, and it being every four years instead of a continuous decrease. Maybe that halving some very interesting butterfly effects later. Now, it's clear that the halving will probably be some global holiday thing in the future. Really, it does interesting things with the currency markets. Do you want to weigh in on this particular feature and then maybe comment on some of the other weird features of Bitcoin that you think maybe have become a big deal?

[01:04:38] CK: Hey, really quick. Sorry to interrupt. Before you answer that question, Adam, if anyone wants to come up and ask a educated question, I will be screening folks to come up. Yeah, when you come up on stage, we're going to have you ask the question and I'm going to take you off stage. Feel free to request and I'll screen people to come up. Yeah, go for that question.

[01:04:57] AB: You could certainly say that Bitcoin could have been designed – the technical specifics could have been different. One with a few, it wouldn’t make much difference. You have 21 million coins versus 42. Okay. We’ve been trading half Bitcoins and the rate of supply, inflation will be the same. That seems a arbitrary number.

The halving is interesting, because you could envisage it being a smooth curve. Now that we have it, it seems to create a heartbeat economic cycle almost, which is maybe beneficial, because it's going to be some cycles anyway, and it punctuates it or something, and kicks off new investment cycles, or people to plan around. Yeah, so that's interesting.

I think, there are some – just looking at the numbers, it seemed to me that there is some plan. There are some close to power of two, or close to power of 10 numbers, coincidentally. The 144 blocks a day. 2016, almost a pair of two blocks every two weeks. The number of blocks in the having. Some odd numbering systems that work out relatively elegantly. The halving cycle is some interest in multiple of that. Yet, almost coincides with a four-year cycle, but not quite. I guess, he had to tweak numbers to try and find pleasing sizes and periods that line up with weeks and years, even though they don't appear to be quite that. Now they're close.

Another piece of reverse engineered, and I don't know if it's true or not, but the claim about 21 million was that as one of the developers mentioned this to me at some point, that that an earlier version of Bitcoin had only two digits of precision below a Bitcoin. Only down to bitsense. Then, 21 million becomes 2.1-billion-bitsense, and that is coincidentally very close to the maximum sized integer you can fit in a signed 32-bit number that's common on CPU architectures. That’s plausible. Then, the further the visibility came later reportedly, because Hal Finney said, that it wasn't enough to visibility for the world.

Hal Finney was, I think, within a few days of 2009, was estimating the addressable market of store of value in the world around, let’s say 200 trillion dollars or something, and the necessarily the visibility of Bitcoin because of it, I guess.

[01:07:31] CK: Hal is a legend. So ahead of his time.

[01:07:33] AB: Yeah. That guy really gets around. He was in the remailers. He’s in RPOW. Actually, he had an input to Hashcash, too, the first version of Hashcash. I had a double collision and he made the observation that you could simplify it to one hash, by making the collision with zeros instead. There was somebody else that made the same observation by citing them in the paper when I read it later.


[01:08:01] ANNOUNCER: My fellow plebs, the Bitcoin Conference is back. Bitcoin 2022, April 6th through the 9th is the ultimate pilgrimage for the Bitcoin ecosystem. The Bitcoin Conference is the biggest event in all of Bitcoin and cryptocurrencies. We’re leveling up and making this bigger and better than ever. I’m talking straight to the moon with a four-day long festival in the heart of Miami at the Miami Beach Convention Center.

This has something for everyone. Whether you’re a high-powered Bitcoin entrepreneur, a core developer, or a Bitcoin newbie, Bitcoin 2022 is the ultimate place for you to be with your people and celebrate and learn about the Bitcoin culture.

Make sure to go to b.tc/conference to lock in your official tickets, and use promo code Satoshi for 10% off. Want more off? Pay in Bitcoin and you’ll receive a $100 off general admission and a $1,000 off whale pass. Those are stackable, so go to b.tc/conference and attend the best conference in Bitcoin history.

[01:09:06] ANNOUNCER: Yo, my fellow Bitcoin lovers. I’ve got something specifically curated for you. The Deep Dive is Bitcoin Magazine’s premium markets intelligence newsletter. This isn’t some paid group shilling by and sell signals. No. This is a premium Bitcoin analysis led by Dylan LeClair and his team of analysts.

They break down in easy divestible way what is happening on-chain, in the derivatives markets and in the greater macro backdrop context for Bitcoin. These loosely returns volatility into a joke. Hit up members.bitcoinmagazine.com and use promo code podcast for 30% off The Deep Dive. That’s members.bitcoinmagazine.com, promo code podcast for 30% off. Divorce your pay group and learn why Bitcoin is the strongest asset by Dylan LeClair and his team.


[01:09:57] CK: Paulo, why don’t you get us started? Please, address the question the panel. Then after that, make it succinct, because I will be letting you down after that.

[01:10:05] PAULO: All right. Thank you, guys very much. Hey Dr. Back, I would like to ask you, what do you consider that is the most promising technology besides Lightning and Liquid?

[01:10:17] AB: I think, actually, at least to an interesting observation. It seems to me that it's actually remarkably hard to improve Bitcoin. I say that in a sense that it seems to surprise a lot of people. I'll come back to your topic at the end of this comment. It seems to surprise a lot of people. You get a new technology and people would think, it's like the first car. Obviously, you can radically improve it, [inaudible 01:10:40]. They assume that it would be the case with Bitcoin's design.

If you're into distributed systems and applied cryptography and networking and stuff, and you take a shot at it, and I spent three or four months trying to figure out if there's any way to improve anything about it in 2013, and pretty much concluded that while there's almost nothing you can do, this design exists in a really narrow pocket of design space, where it works, but almost every variant you could think of to improve one aspect of it makes other aspects worse. It makes it more complicated, or it makes it more expensive. It's really hard to optimize.

I think, the only really promising new technology that could change something fairly dramatically is the signatures of execution technology, which is newer than Bitcoin. Takes us back in a few years now. People will know that under snarks, stocks, bulletproofs. Basically, the idea that you can make a signature that can be verified by other people that proves to everybody that a given program was run on a data and returned true, or something like that.

You can verify zero-knowledge proof and the data doesn't even have to be disclosed as well. It has some quite interesting possibilities for privacy and scalability. The technology is rapidly evolving. They are CPU heavy, sometimes expensive to verify, or involve experimental crypto. I think, the bulletproof security assumptions are very good, like dependable, similar to Bitcoin. You can rely on. That one is not as scalable. It's more CPU intensive to make proofs and to verify the proofs and they're not fixed size. They're long-scaled. It's still very impressive technology. If that crosses over, so that the reliable security assumption signatures of execution gets to a very scalable and efficiently verifiable stage, which it might do in the following years, that could be a very interesting and useful golden block. And, potentially solve some scaling problems. Will move privacy forward.

[01:12:42] AG: Great. All right. Should we take the next one?

[01:12:45] CK: Yeah, let's go, I think, the Roman HODLer.

[01:12:48] RH: Hi. Thank you. Thank you for inviting me in. I would like to ask Adam regarding the fee environment that we're in, considering that we are in all-time highs. Prices and fees are still really low, or in empty blocks, considering that we will have to transition to a fee record model within the next 10 to 15 years, where do you see the demand coming? Will we just either the increases in number of people, or will we have to somehow find another way to get a sustained high-fee environments to support the network? Thanks.

[01:13:25] AB: Yeah. I presume, actually, historically, I believe it's generally accepted that the reason fees get high has less to do with users and more to do with traders, because they're price insensitive, because they’re doing a lot of transactions and they’re time sensitive. They want to clear the transaction, so that they can do the trade. They might lose money. Some of those activities have moved to key management systems, so that funds can move between exchanges without going on the main chain increasingly. That's taken some of those out.

Then on the other end, retail transactions are increasing. You're using Lightning. Lightning adoption has grown rapidly. There’s literally millions of people in El Salvador using Lightning. That takes a lot of traffic for retail and micropayments off the main chain. In terms of the security budget for Bitcoin into the far future, I think that personally, we have a long time. There is a minimum fee rate. One Satoshi per [inaudible 01:14:22] is at the network relay level.

As price increases, that provides a floor minimum fee on the network. Just the price increases, making Bitcoin more expensive at base level. I think, with the halving cycle, Bitcoin’s price has grown a lot faster, by a lot more than two times every four years. Let's put it that way. It’s probably some decades away. As you say, it's eventually at the top of the S-curve, when everybody that wants to use Bitcoin is using it, what happened, and there's less new coins being mined, what happens to the security budgets? I think, you could say that potentially, the security budget is a pain too much at the moment, possibly.

There are other things you can do to make the network immutable. Miners that don't go backwards, like enforced by the ASICs and the hardware. I think, the other thing is that if you look at other money systems in the world, the infrastructure of the banking world, it's far less secure and reliable than Bitcoin security model. It's basically the weakest link in the chain and there are maybe 10,000 financial institutions, any one of which could have a database hacked and create a trillion dollars and it will take a while until anybody would discover it. I think, one answer is that money is a construct that humans need socially.

There's an enormous economic incentive to find a solution. That could include even that payment processes and exchanges and power users, each do a little bit of mining enough to be decentralized as a cost of doing business. Even if there was breakeven economics on it, because society has a family for something, then it will find a way to do it. You can see that actually, in the way the Internet works. As a user of Internet in a home environment, you don't see it because you just pay your Internet bill. Out on the Internet, there's pairing arrangements where traffic has to route through different individual companies, infrastructure, and they work out agreements to translate each of those data, so let's say for tile or something.

There are ways for things to work if people need them to work. The permissionless global electronic cash is an extremely valuable things. I think, people will have an incentive to find ways to make it work, basically.

[01:16:34] CK: I know for a fact that my opinion here is much less valuable than Adam Back's, but I think the block reward is very underrated. My name right now, 37 Sats. That's the block reward in a hundred years. I think, that's still going to be carrying its weight in terms of incentivizing the network. Get more bullish, is what I would say. Let's go over to BK. What's your question?

[01:16:54] BK: Hey, thank you for having me on. Thank you Professor Back for explaining a lot of this. My question to you is, can you speak about the importance of running your own full node as a Bitcoin holder, as well as what it means to the network at large?

[01:17:08] AB: Yeah. I think, it's important that it be possible for power users to run four nodes. People will use the phrase, “Not your keys, not your coins.” That's obviously true, because if you're using a custody solution, you really have an IMU, you don't actually have the coins and the custodian could fail, or freeze, or seize your funds, throw out somebody. I think, in a similar direction that running your own nodes, actually provides you with a lot more protection from a security perspective. It's a bit like having an anti-counterfeiting device. If you go into some stores, they put high denomination notes through a machine that tries to detect counterfeits.

Having a node is a bit like that. It ensures that, I think, during the folk drummer, where there were different hard forks running in parallel, it got choppy. However, if you run your own full node and you had your keys, there wasn't actually anything to worry about, because the miners couldn't change the rules, because your node would silently and automatically reject anything that doesn't follow the network rules.

Think about it. I think, a phrase people use is that Bitcoin has a decentralized, impenetrable shield of verification or validation. The four nodes, form part of that. I think, it's also true that a node doesn't really do that much, unless the operator of it relies on it. If you verify transactions you receive using it, then it is contributing value to the network, because if somebody sends you a coin and your node says, it's invalid, you're going to not accept it. That's going to cause the person that sent it to you to realize they've been fooled, or that they're on a different network.

That flows back through the network and means that, even if some reasonable percentage of people and services and exchanges and wallets are relying on nodes that effectively, the whole network very rapidly rejects anything that's not following the protocol rules.

[01:19:14] CK: All right. Pavo, you want to take a question?

[01:19:17] PAVO: Yeah. Yeah, thanks for this session. Learning a lot. I’m based in Africa. I noticed that from one of the [inaudible 01:19:25], it seems that Nigeria are really – about 30% of Nigerians are into crypto. Most of Nigerians who work through peer-to-peer platforms, because it’s [inaudible 01:19:39]. Crypto in general is actually, and also [inaudible 01:19:44], extended like finance, and the other on this. Is it possible to see the Nigerian government see a centralized exchange like Binance, to [inaudible 01:20:02] in Nigeria, country by country distinguish this event, yes? What kind of division would it have to form [inaudible 01:20:09]?

[01:20:12] AB: I'll repeat the question, because it was a little hard to hear, but I think I got it. Basically, the person asking the question is saying that in Nigeria, Bitcoin is banned and yet, people are using it anyway and trading on foreign exchanges. To what extent could governments in a given country effectively ban Bitcoin?

I think, Nigeria is interesting example, because the ban seems to be ineffective, or I don't know if it's the case in Nigeria, but certainly in some countries and cultures, when you ban things, they get more popular. Yeah, I think it's actually quite hard to ban things, because we can use them internationally. The Internet is quite porous. There are VPNs. There's Tor. It's hard to practically stop people transacting with Bitcoin, as long as there's an Internet connection and people can install apps and things. I think, it's a very difficult to stop.

It's build on that Blockstream stream, we deployed this Bitcoin satellite network to broadcast Bitcoin transactions and blocks and the Lightning cost of data and actually, the full history so that you can even sync a node with a satellite network. Just basically, to provide some additional redundancy and make it easier and lower cost to directly participate in the Bitcoin network by running a node, without consuming a lot of bandwidth, because the bulk bandwidth to sync a node can get expensive.

That also makes it harder to censor, because you can then participate with Bitcoin on much lower bandwidth, which could be sending a transaction. Transactions very small. You could send them an SMS message. I think that, in a way, the footprint of Bitcoin being small, that it doesn't consume an enormous amount of resources and bandwidth means that it's harder to sensor into text. Being able to receive the bulk data not fully anonymously and read-only over satellite means that it’s especially impossible to detect if you are even running a full node. Then if you send a transaction, it's very small and much easier to hide in the noise.

[01:22:06] CK: All right. We have about 15 minutes left, I think. Then, I'm going to start wrapping it up a little bit. I think, we can only take three or four more questions. I want to pass it to Tomer. I see you present a question and I'm going to start letting some people off stage, unfortunately. I apologize for folks who didn't get to ask their question. Tomer go for it.

[01:22:26] TS: Adam, it's such an honor to get to ask you a question. One of the things I find so amazing is just your enormously calm demeanor as you've lived through the prehistory of Bitcoin, and then through the history of it as well. For so many of us who have only discovered, not the existence of this technology since Bitcoin, and we get blown away by these numbers that cryptographers deal with. The hash rate right now is a 140 million trillion hashes every second. It's such an unimaginable number, and it can consume so much energy and it skips along, without even being challenged, because that number that is 256 bits is so big that you can be doing quintillions of calculations a second and not even putting any pressure on it.

Part of my question is so many of us are just blown away when we hear these numbers and our jaws black and we can't even fathoming them, let alone people inventing things with them as you have. Part of the question that I have is just, are you blown away frequently by the inventions as you tumbled down the rabbit hole and you just – you're putting on a very calm face first? Or is it just that as you've come through this, you've always had the calm demeanor? Or as you've watched it grow, that just lets you see this without having your mind blown all the time? It's a bit of a personal question, but does your mind get blown all the time?

[01:23:46] AB: I think, actually it may not be intuitive to everybody, but I think, everybody is learning about Bitcoin now, including the people writing the lowest level bits of consensus coders, or so on, because it's such a complicated – In some way, it's superficially simple and you can understand it at different levels as you get more involved in it.

The combination of the economics of it and how it resists on want to change. I think, lots of people learn things about that at the time and about the system in general. I think, everybody is learning as we go. I think, it may be a factor about society that society learning about things actually takes decades. We'll often look at historic things and think that that looks simple, or that seems obvious, or that doesn't work anymore. Actually, the conventions, or the companies organize with shares, or how society manages business and things like that are actually incrementally improved over hundreds of years and actually quite complex, elegant systems.

I think, Bitcoin has had some of that going on that we're still really getting to grips with what it is and what it can do and how it can operate on its own as a organism, or a system with assistance of its own. Yeah. In terms of getting excited about things, I'm more of a mindset to not get mad, but get even. I just want to see things succeed, so I just keep optimizing and trying to solve problems. I think it's easy, and you saw this on the Cypherpunks list, to get mad, it's so wrong what the government's doing. This is a policy abuse. They're depriving people of rights. The other approach is to say, “Okay, I agree with all of that, but you don't actually achieve anything by getting mad about it. What you want to do is build a system to change the balance of power and succeed that way.” What matters is the result and focusing on the price. Something like that.

[01:25:49] CK: All right, let's go as quickly as possible –

[01:25:50] TS: Thank you. The attitude that I have for you, and I know so many other people do is imaginable. Sorry.

[01:25:56] CK: Sorry about that Tomer. We're trying to go quick. Big love for Adam Back. Thank you so much for the time to, Adam. Yassin, why don't you go? Let's try to keep it brief. Then we're going to go Vivek, and then close it out with Log, and then want to give it back to Alex, he will maybe direct some closing words.

[01:26:13] Y: Hey, Dr. Back. This might be a silly question, but would it be possible for Blockstream to create a multi-signature hardware wallet that requires no third-party custodial? The reason why I ask is because in the US right now, there's this IRS bill that they're trying to pass, where they want to audit anyone and everyone with more than $600 in their bank accounts. My concern with the third-party custodials is that perhaps, the government can to their Bitcoin balances?

[01:26:42] AB: Yeah. Actually, coincidentally and probably it's not very well documented, the green wallet works on both Bitcoin and liquid. On liquid, as there's confidential transactions, which hides the values. It's actually the case, which is mind-blowing if you start to think about it. The green two-factor authentication server, which is providing security in a way, it doesn't actually know how much you're transferring, or even what type of asset is. You can get a third-party security service that doesn't have visibility into how much you're transacting, what asset you're transacting, and yet, can assist you in doing two-factor authentication security.

If you lose your two-factor authentication device, or after a time period, the small Bitcoin smart contract attached to the coin says that after 90 days, you can bypass that. If you lose the two-factor, you just wait for the contract time lock to expire, and then you can just spend it without it. As long as you haven't lost your two-factor and you're continuing to authenticate, that means you can get some very interesting hybrids of privacy, security and self-custody, basically. Smart contracts are very flexible, interesting things. I think, there are probably many more such interesting things that can be built to come, the key management and ease of use and assisting people to avoid losing their funds.

You have your own keys, but if you lose them, that's a big problem. What I'm saying is, I think, there remain interesting ways that the safety of doing, avoiding key loss can be achieved to improve on it.

[01:28:25] CK: Vivek, why don't you jump in?

[01:28:28] V: Sure. Yeah. I have a good segue, essentially. In bull runs, we increasingly hear the false statement that Bitcoin doesn't have smart contracts. I wanted to ask Adam, is there anything that excites him about a script, whether it's op codes, or other primitives? What's most promising, or what interests you?

[01:28:46] AB: Yeah. I think, obviously, Bitcoin had a smart contracting system from the beginning. It's just one thing, it’s focused on being secure securable, and scalable. Because Bitcoin has added incremental improvements over time, the CSP site where it's some programmable lock times, and now taproot, and Schnorr signatures. There are more things that people are exploring to add.

Another a more next generation smart contracting plan that may work its way into Bitcoin long-term is a smart contracting system called Simplicity. It's actually conceived of by Russell O'Connor. I think, it was in 2012 and ILC discussions. Some people may have heard of Most. Actually, the full story for Most is a language designed around that from scratch, which is called Simplicity. At one point, we're able to recruit Russell O'Connor to actually build that. He's been working on that quite a few years now. We're expecting to have that in liquid early next year. Now, you can downloads developer releases of Bitcoin branches and liquid with Simplicity integrated. It's a very interesting language, because it makes the Bitcoin scripting model self-extensible, so you can approximately add new op codes.

If simplicity was in Bitcoin today, you would be able to implement Schnorr signatures as a small extension without needing a soft fork, for example. The other point about Simplicity is that it's based on a low-level mathematical formal logic assembly language level of the base. Everything about the extensions and scripts you use is mathematically defined and can be fed to a brief assistant to make formal proofs about the correctness of a program. Actually, the simplicity interpreter is able to – you can make proofs about Simplicity interpreter itself.

One very interesting proof is that the simplicity interpreter will correctly interpret all simplistic programs, which is a very strong guarantee, but you can prove many things about it. The maximum runtime of a script, the maximum amount of memory scripts can use, or the only categorize and assure yourself that the only scenarios where money can be spent from the script is never a small list of intended outcomes and prove that is correct also.

I think, that is pretty interesting for the future. Another interesting crossover as we mentioned briefly, bulletproofs, which are a secure way to do the signature of execution with some very conservative security assumptions. Those are based on zero-knowledge proofs and circuits. It turns out to be possible to compile Simplicity assembly code into a bulletproof. Those two things fit quite well together, because with Simplicity, you have some security and semantics tools to have confidence that your program is going to do what you think it’s going to do. Then by compiling it into a bulletproof, you can get privacy, and a zero-knowledge proof that the program executed on some undisclosed there, so you can get privacy on top of it.

A usual problem with snarks and bulletproofs and things like that is you first have to design by hand a circuit that does what you want, and that's complicated and you could make a mistake with it. The fact that you could compile it is interesting, too, and an area for future development. I think, those security first approaches will be interesting to see, come to play. I think, Bitcoin, it takes some time between the technology being developed and the thorough security review and quality assurance and peer review, until things make their way into Bitcoin.

The Schnorr signature was first discussed in 2013 ILC discussions as a potentially interesting for Bitcoin. Over time, that became more concrete, and some developer started working on the details and implementing it in a library and cycle. Now, here we are today with Schnorr signatures in Bitcoin. I'm not saying that something like Simplicity is going to come that soon, but it is a path that could potentially achieve the ossification objective of largely freezing the base layer of programmability, so that you could do more general things on top of a secure base without having to have further soft forks, I guess.

[01:33:25] CK: Very thorough answer. Thank you very much. Alex, we're pretty much hitting end of time. How do you want to conclude this? Do you want a last word, or –

[01:33:32] AG: Sure. I just wanted to thank you, Adam, so much for your time. It's been really illuminating. We'll just end with a reflection on the one piece that you were when you were initially designing Hashcash, this idea of the faster computers could always create more monetary supply. This fixed through the difficulty algorithm in a way. One last reflection from you before we break. What was it like watching half the network, hash rate collapse, because there was, or just government essentially, almost attacked Bitcoin? Then, watching the network be so resilient that it could just soldier on and now, getting back close to all-time hash rates. What is your general summation of this difficulty algorithm and how important is it to Bitcoin?

[01:34:13] AB: Yeah. I think, it's one of the innovations that enables Bitcoin in a way. Because without it, the economics don't look like they would converge. It would lose integrity of the economic base or something. Yeah, the exodus of hash rate from China, we've seen a few situations where people get worried about dramatic changes. Some people thought the halving would create a death spiral, or too many transactions will clog up blocks, or blocks got slower, into a sudden drop in hash rate.

In practice, the network is extremely robust. I think, the media doesn't help because they will amplify what ifs without fully understanding the economics and technical mechanisms that all dynamically cope with things. It seems that Bitcoin is very robust. Of course, it's also meta-robust in the anti-fragility sense that if the real issues to arise, that there's a financial incentive for all of the very technically capable and a genius people working on it to solve, fix the problem, basically. Whether that is to do with the governance drama that was resolved by humans and the market, or a technical risk that materializes. I think, the combination of human ingenuity and the market and robust, elegant and simple base layer makes it an incredibly robust system.

[01:35:40] AG: Great. Thank you. CK, thanks for hosting. Thank you, Aaron. Thank you, P. Just massive, thanks to Adam, to Dr. Back, not just for his time today, but for all of his contributions to privacy and to freedom and to Bitcoin. Thank you.

[01:35:53] AB: Thank you.

[01:35:54] P. Yeah, this was an amazing conversation. I can pay you all no higher compliment than I said absolutely nothing. Thank you all.

[01:36:01] CK: Awesome. Awesome. Yeah, I think we're going to close this one out. Alex, thank you so much for your time. Thank you for writing for Bitcoin Magazine and writing the quest for digital cash. For everyone who listened to this entire conversation, I know many of you did, make sure to go click into the pin tweet up top. That'll take you to Alex's mega thread and a link to his full article, where you can dive into this history and the story of discovering digital cash and all the dynamics that are a part of that story.

I know that Mr. Pete Rizzo has a lot of fantastic work about the early days of Cypherpunks and Satoshi, and Aaron is the OG Bitcoin historian. Look up both of their works as well on Bitcoin Magazine. Yeah. Thank you to everyone who listened this entire time. I got to show the Bitcoin Conference, Bitcoin 2022, use a promo code – was it? Promo code –

[01:36:52] P: HFSP.

[01:36:54] CK: Yeah, HFSP. Have fun staying poor. Get your ticket before prices – I believe, Adam is going to be speaking there, so don't miss him there.

[01:37:01] P: He definitely is.

[01:37:02] CK: Yes. The print Bitcoin Magazine as well. Check that out. Promo code BR, to get your print magazine for the El Salvador edition of the Bitcoin Magazine. Alex has an article in there. Aaron has an amazing article in there. Rizzo has added to it. It's a piece of history that you got to get.

Yeah, with that, I will close it out. Thanks again to everyone and see you in Miami. Peace.

[01:37:26] P: Adios.

[01:37:27] AG: Thank you.