WEBVTT

1
00:00:00.120 --> 00:00:02.919
<v Speaker 1>Remember that feeling back in late two thousand and eight,

2
00:00:03.279 --> 00:00:05.639
<v Speaker 1>that sort of global anxiety, the loss of faith in

3
00:00:05.679 --> 00:00:09.560
<v Speaker 1>the financial markets. The sheer scale of that crisis born

4
00:00:09.599 --> 00:00:14.000
<v Speaker 1>from all that irresponsible lending regulatory failures, It really felt

5
00:00:14.039 --> 00:00:16.600
<v Speaker 1>like the whole system might collapse. It definitely made a

6
00:00:16.640 --> 00:00:19.399
<v Speaker 1>lot of us ask who, or maybe what can we

7
00:00:19.559 --> 00:00:22.640
<v Speaker 1>actually trust anymore? Well, this deep dive is all about

8
00:00:22.640 --> 00:00:27.239
<v Speaker 1>a technology that kind of grew directly out of that uncertainty, blockchain.

9
00:00:27.640 --> 00:00:31.440
<v Speaker 1>We're drawing our insights today from blockchain enabled applications. Understand

10
00:00:31.440 --> 00:00:34.359
<v Speaker 1>the blockchain ecosystem. It's a really fascinating source, digs right

11
00:00:34.399 --> 00:00:38.039
<v Speaker 1>into the foundations and the massive implications of this tech.

12
00:00:38.359 --> 00:00:40.479
<v Speaker 1>Our mission really is to cut through the hype, pull

13
00:00:40.520 --> 00:00:42.679
<v Speaker 1>out the key ideas, and show you how blockchain went

14
00:00:42.719 --> 00:00:46.119
<v Speaker 1>from this radical concept to something foundational for so many

15
00:00:46.159 --> 00:00:49.920
<v Speaker 1>new applications. Get ready for some aha moments. So let's

16
00:00:49.960 --> 00:00:52.799
<v Speaker 1>really unpack this. That two thousand and eight crisis. It

17
00:00:52.799 --> 00:00:54.320
<v Speaker 1>wasn't just about money, was it. It felt like a

18
00:00:54.320 --> 00:00:56.439
<v Speaker 1>fundamental crisis of trust. Can you walk us through the

19
00:00:56.439 --> 00:01:00.560
<v Speaker 1>core problems, especially around how well how transactions and relatedationships

20
00:01:00.880 --> 00:01:01.560
<v Speaker 1>just seemed.

21
00:01:01.320 --> 00:01:04.280
<v Speaker 2>To crumble absolutely you've nailed it. The crisis really threw

22
00:01:05.560 --> 00:01:08.879
<v Speaker 2>two critical flaws into sharp relief. First, like you said,

23
00:01:08.879 --> 00:01:12.439
<v Speaker 2>this widespread disappearance of trust. The system was just so opaque,

24
00:01:12.439 --> 00:01:16.040
<v Speaker 2>full of these incredibly complex financial instruments nobody fully understood.

25
00:01:16.599 --> 00:01:20.359
<v Speaker 2>And second, the massive issue of counter party risk, you know,

26
00:01:20.400 --> 00:01:22.640
<v Speaker 2>the basic fear that the other side of your dealer

27
00:01:22.719 --> 00:01:25.799
<v Speaker 2>just wouldn't hold up their end, right. We saw that

28
00:01:25.879 --> 00:01:30.239
<v Speaker 2>so clearly with those high risk mortgages. They got bundled, repackaged,

29
00:01:30.319 --> 00:01:34.959
<v Speaker 2>sliced and diced, and then sold as supposedly low risk

30
00:01:35.040 --> 00:01:38.040
<v Speaker 2>things like CDOs collateralized debt obligations.

31
00:01:38.079 --> 00:01:40.040
<v Speaker 1>It's turned out to be a huge mistake.

32
00:01:39.719 --> 00:01:42.560
<v Speaker 2>A catastrophic one, because it turned out property values in

33
00:01:42.599 --> 00:01:45.319
<v Speaker 2>different cities weren't independent at all, they were correlated. So

34
00:01:45.319 --> 00:01:46.519
<v Speaker 2>when one domino.

35
00:01:46.159 --> 00:01:47.959
<v Speaker 1>Fell, they all started cumbling exactly.

36
00:01:48.120 --> 00:01:52.519
<v Speaker 2>Those CDOs became worthless almost overnight. Whole investment packages just vaporized.

37
00:01:52.719 --> 00:01:54.840
<v Speaker 1>So it wasn't just a few bad apples. It sounds

38
00:01:54.840 --> 00:01:58.079
<v Speaker 1>like the whole system, the structure of how value moved

39
00:01:58.359 --> 00:02:02.120
<v Speaker 1>was fundamentally broken. And the source we're looking at brings

40
00:02:02.200 --> 00:02:04.879
<v Speaker 1>up this term double spending, which most people link to

41
00:02:05.000 --> 00:02:07.879
<v Speaker 1>digital cash How did something like that play out in

42
00:02:07.879 --> 00:02:10.639
<v Speaker 1>two thousand and eight before bitcoin even existed.

43
00:02:10.879 --> 00:02:13.479
<v Speaker 2>That's a really important point. It wasn't digital currency back then, No,

44
00:02:13.719 --> 00:02:18.080
<v Speaker 2>it was something maybe more insidious. Financial institutions were essentially

45
00:02:18.120 --> 00:02:21.120
<v Speaker 2>you could say, double pledging assets. They took those shaky

46
00:02:21.159 --> 00:02:24.439
<v Speaker 2>subprime mortgages, bundled them up and then sliced them into

47
00:02:24.439 --> 00:02:28.759
<v Speaker 2>different CDO packages and basically sold claims on the same underlying,

48
00:02:28.960 --> 00:02:33.199
<v Speaker 2>very risky assets multiple times over. It created this illusion

49
00:02:33.240 --> 00:02:37.120
<v Speaker 2>of value, this massive web of commitments based on assets

50
00:02:37.120 --> 00:02:38.159
<v Speaker 2>that just weren't solid.

51
00:02:38.560 --> 00:02:40.319
<v Speaker 1>So when the housing market crashed.

52
00:02:40.199 --> 00:02:44.400
<v Speaker 2>The real value just evaporated, and this systemic double spending

53
00:02:44.560 --> 00:02:48.080
<v Speaker 2>of trust, of commitment became brutally clear. It triggered that

54
00:02:48.159 --> 00:02:49.599
<v Speaker 2>dominant effect of failures.

55
00:02:49.800 --> 00:02:53.599
<v Speaker 1>Wow, okay, and then out of that chaos something completely

56
00:02:53.680 --> 00:02:57.199
<v Speaker 1>different started. November two thousand and eight, this anonymous person

57
00:02:57.240 --> 00:03:02.319
<v Speaker 1>or group, Satoshi Nakamoto, posts away paper Bitcoin a peer

58
00:03:02.319 --> 00:03:06.719
<v Speaker 1>to peer electronic cash system. How did that paper propose

59
00:03:06.840 --> 00:03:11.199
<v Speaker 1>to tackle these huge, ingrained problems of trust and central control?

60
00:03:11.479 --> 00:03:13.879
<v Speaker 2>Well, the Bitcoin Way paper it really reads like a

61
00:03:13.960 --> 00:03:17.639
<v Speaker 2>direct response to that crash in many ways. It was brilliant.

62
00:03:17.680 --> 00:03:20.800
<v Speaker 2>It laid out this completely new protocol, a way to

63
00:03:20.840 --> 00:03:24.400
<v Speaker 2>move away from needing a single central trusted authority like

64
00:03:24.439 --> 00:03:27.960
<v Speaker 2>a bank or a payment processor, to okay transaction.

65
00:03:27.639 --> 00:03:29.439
<v Speaker 1>Right bypassing the middleman exactly.

66
00:03:29.560 --> 00:03:33.599
<v Speaker 2>Instead, it proposed this massively distributed network, lots of participants,

67
00:03:33.719 --> 00:03:36.120
<v Speaker 2>nodes who could agree that a transaction is valid based

68
00:03:36.199 --> 00:03:38.960
<v Speaker 2>on well, an algorithm, not just someone's word. It was

69
00:03:39.000 --> 00:03:42.360
<v Speaker 2>a fundamental shift, offering really a new kind of security, privacy,

70
00:03:42.400 --> 00:03:45.240
<v Speaker 2>and verifiable trust for the online world.

71
00:03:45.080 --> 00:03:47.520
<v Speaker 1>And Setoci is often credited with solving this thing called

72
00:03:47.520 --> 00:03:51.080
<v Speaker 1>the Byzantine general's problem. Sounds very historical, almost like a riddle,

73
00:03:51.560 --> 00:03:54.039
<v Speaker 1>What is that problem? And how do bitcoin actually, you know,

74
00:03:54.280 --> 00:03:55.520
<v Speaker 1>solve it in a practical way.

75
00:03:55.759 --> 00:03:58.280
<v Speaker 2>Yeah, it sounds academic, but it's a really useful metaphor.

76
00:03:58.360 --> 00:04:01.439
<v Speaker 2>Imagine a bunch of generals surrounding a city. They all

77
00:04:01.479 --> 00:04:04.719
<v Speaker 2>need to agree attack or retreat at the same time. Okay,

78
00:04:04.800 --> 00:04:07.759
<v Speaker 2>but the catches, some of them might be traders sending

79
00:04:07.840 --> 00:04:11.360
<v Speaker 2>fake messages. There's no central commander they all trust, so

80
00:04:11.400 --> 00:04:13.800
<v Speaker 2>how do they reach a unified decision they know everyone

81
00:04:13.840 --> 00:04:19.040
<v Speaker 2>will follow. Tricky, very so in bitcoin. Satoshi's big innovation

82
00:04:19.240 --> 00:04:21.519
<v Speaker 2>was creating this peer to peer network, but with a

83
00:04:21.560 --> 00:04:24.879
<v Speaker 2>shared public ledger. Think of it like a giant open

84
00:04:24.959 --> 00:04:28.759
<v Speaker 2>record book. This ledger records everything, and the network uses

85
00:04:28.800 --> 00:04:31.519
<v Speaker 2>a process to reach a majority agreement on what's true.

86
00:04:32.240 --> 00:04:35.879
<v Speaker 2>False information like a trader's message gets exposed because it

87
00:04:35.879 --> 00:04:39.120
<v Speaker 2>doesn't match what the majority sees. It basically builds consensus

88
00:04:39.120 --> 00:04:42.079
<v Speaker 2>from the ground up, removing that need to trust one single,

89
00:04:42.199 --> 00:04:43.959
<v Speaker 2>potentially flawed central point.

90
00:04:44.240 --> 00:04:47.079
<v Speaker 1>So that shared ledger. Yeah, that's the blockchain, right. Can

91
00:04:47.079 --> 00:04:49.360
<v Speaker 1>you break down what a blockchain actually is for us?

92
00:04:49.439 --> 00:04:50.480
<v Speaker 1>Just in simple terms?

93
00:04:50.720 --> 00:04:54.480
<v Speaker 2>Precisely? That's the blockchain. At its heart, it's a digital

94
00:04:54.519 --> 00:04:56.199
<v Speaker 2>recording ledger, simple as that.

95
00:04:56.319 --> 00:04:56.600
<v Speaker 1>Really.

96
00:04:57.199 --> 00:05:02.319
<v Speaker 2>It gives everyone involved a secure, synchronized and transparent record

97
00:05:02.360 --> 00:05:06.279
<v Speaker 2>of transactions start to finish, Similar transactions that happen around

98
00:05:06.279 --> 00:05:08.720
<v Speaker 2>the same time get grouped together into a block. Okay,

99
00:05:08.879 --> 00:05:11.600
<v Speaker 2>That block gets sealed with the timestamp saying when it

100
00:05:11.639 --> 00:05:16.959
<v Speaker 2>was created and a unique cryptographic fingerprint it's hash, and crucially,

101
00:05:17.240 --> 00:05:19.759
<v Speaker 2>that hash links it directly to the block that came

102
00:05:19.800 --> 00:05:23.399
<v Speaker 2>before it, creating a jaine exactly, an irreversible, tamper evident

103
00:05:23.519 --> 00:05:26.319
<v Speaker 2>string of blocks. That's why it's so secure. Change one

104
00:05:26.319 --> 00:05:28.720
<v Speaker 2>thing in an old block and the fingerprint changes, breaking

105
00:05:28.720 --> 00:05:31.639
<v Speaker 2>the chain, everyone sees it, and because every member of

106
00:05:31.639 --> 00:05:33.800
<v Speaker 2>the network has an up to date copy, there is

107
00:05:33.839 --> 00:05:36.600
<v Speaker 2>this distributed consensus on what the true history is.

108
00:05:36.720 --> 00:05:39.000
<v Speaker 1>Okay, this is where, for me, at least, it gets

109
00:05:39.040 --> 00:05:41.720
<v Speaker 1>really interesting. How does this network with no one in

110
00:05:41.839 --> 00:05:45.959
<v Speaker 1>charge actually create the blocks and verify them? The source

111
00:05:45.959 --> 00:05:48.279
<v Speaker 1>talks about proof of work POW and this idea of mining.

112
00:05:48.319 --> 00:05:49.199
<v Speaker 1>What's going on there?

113
00:05:49.560 --> 00:05:51.680
<v Speaker 2>Right? Proof of work is the engine driving it. It's

114
00:05:51.759 --> 00:05:55.199
<v Speaker 2>quite clever. It actually came from an earlier idea called hashcash,

115
00:05:55.240 --> 00:05:57.759
<v Speaker 2>which was designed to fight email spam Believe it or not,

116
00:05:57.920 --> 00:06:02.399
<v Speaker 2>AH in bitcoin, it's this intent competitive computation. So these

117
00:06:02.399 --> 00:06:07.079
<v Speaker 2>participants called miners, gather up recent transactions, bundle them into

118
00:06:07.120 --> 00:06:10.000
<v Speaker 2>a potential new block, and then they all race to

119
00:06:10.079 --> 00:06:13.560
<v Speaker 2>solve a really hard cryptographic puzzle related to that block.

120
00:06:14.000 --> 00:06:17.759
<v Speaker 2>They're essentially trying to find a specific number, a specific

121
00:06:17.839 --> 00:06:21.199
<v Speaker 2>hash output using a function called sha two five six,

122
00:06:21.519 --> 00:06:23.959
<v Speaker 2>like a lottery sort of, but one where you have

123
00:06:23.959 --> 00:06:25.839
<v Speaker 2>to do a lot of computational work to even buy

124
00:06:25.839 --> 00:06:28.920
<v Speaker 2>a ticket. The first miner to find that correct hash

125
00:06:29.040 --> 00:06:31.639
<v Speaker 2>proves they did the work. The proof of work. That

126
00:06:31.680 --> 00:06:34.560
<v Speaker 2>act of finding the hash validates the transactions in their block,

127
00:06:35.000 --> 00:06:38.000
<v Speaker 2>and as a reward for their effort for securing a network,

128
00:06:38.079 --> 00:06:41.319
<v Speaker 2>they get newly created bitcoins. The mining rule, Yeah, precisely.

129
00:06:41.920 --> 00:06:45.959
<v Speaker 2>It's not just about solving puzzles. It's a powerful economic incentive.

130
00:06:46.560 --> 00:06:51.120
<v Speaker 2>Miners invest real money in hardware and electricity. They're motivated

131
00:06:51.160 --> 00:06:53.439
<v Speaker 2>to play by the rules to get that reward and

132
00:06:53.519 --> 00:06:58.199
<v Speaker 2>protect their investment. This makes attacking the network incredibly expensive

133
00:06:58.480 --> 00:07:01.240
<v Speaker 2>because you'd need more computing pass then basically half the

134
00:07:01.360 --> 00:07:05.360
<v Speaker 2>entire network combined. So trust isn't given. It's earned through

135
00:07:05.399 --> 00:07:07.920
<v Speaker 2>this verifiable, costly work, and the.

136
00:07:07.839 --> 00:07:11.000
<v Speaker 1>Whole process takes about ten minutes roughly.

137
00:07:11.079 --> 00:07:14.360
<v Speaker 2>Yes, the difficulty of the puzzle adjusts automatically to keep

138
00:07:14.360 --> 00:07:16.519
<v Speaker 2>it around that ten minute mark no matter how much

139
00:07:16.519 --> 00:07:19.120
<v Speaker 2>computing power joins the network. Then the race starts all

140
00:07:19.120 --> 00:07:20.319
<v Speaker 2>over again for the next block.

141
00:07:20.680 --> 00:07:23.319
<v Speaker 1>Okay, that makes sense for securing the network itself. But

142
00:07:23.439 --> 00:07:25.360
<v Speaker 1>let's bring it down to the user level. If I

143
00:07:25.399 --> 00:07:28.279
<v Speaker 1>want to actually use bitcoin, send some check my balance,

144
00:07:28.319 --> 00:07:30.480
<v Speaker 1>and how does that work day to day? What are

145
00:07:30.480 --> 00:07:32.439
<v Speaker 1>these transactions and wallets really doing.

146
00:07:33.040 --> 00:07:35.160
<v Speaker 2>It works a bit differently than a traditional bank account.

147
00:07:35.240 --> 00:07:41.000
<v Speaker 2>It revolves around something called unspent transaction outputs or utxos X. Yeah,

148
00:07:41.199 --> 00:07:43.680
<v Speaker 2>think of it like this. When someone sends you bitcoin,

149
00:07:44.040 --> 00:07:47.160
<v Speaker 2>you don't just see a number go up in an account. Instead,

150
00:07:47.199 --> 00:07:51.399
<v Speaker 2>you receive these specific, discrete chunks of bitcoin, the utxos

151
00:07:51.800 --> 00:07:55.279
<v Speaker 2>linked to your bitcoin address, like digital coins or notes

152
00:07:55.319 --> 00:07:55.920
<v Speaker 2>in your wallet.

153
00:07:55.959 --> 00:07:58.759
<v Speaker 1>Okay, like carrying specific bills rather than just having a

154
00:07:58.800 --> 00:08:00.000
<v Speaker 1>balance number exactly.

155
00:08:00.519 --> 00:08:03.560
<v Speaker 2>So, to send bitcoin, you use your private key, which

156
00:08:03.639 --> 00:08:06.160
<v Speaker 2>is your secret Think of it like your signature. To

157
00:08:06.360 --> 00:08:10.160
<v Speaker 2>unlock specific utxos that you own, you essentially create a

158
00:08:10.160 --> 00:08:13.920
<v Speaker 2>new transaction saying send these utxos to this other address.

159
00:08:14.319 --> 00:08:17.160
<v Speaker 2>That transaction it gets broadcasts, the miners pick it up,

160
00:08:17.800 --> 00:08:21.040
<v Speaker 2>verify your signature using your public key, and include it in.

161
00:08:21.000 --> 00:08:23.079
<v Speaker 1>A block And my wallet what's that doing.

162
00:08:23.160 --> 00:08:26.240
<v Speaker 2>Your wallet software isn't actually holding the bitcoin itself. The

163
00:08:26.240 --> 00:08:29.360
<v Speaker 2>bitcoin exists only on the blockchain ledger. Your wallet holds

164
00:08:29.360 --> 00:08:32.240
<v Speaker 2>your private key securely, and it scans the blockchain to

165
00:08:32.240 --> 00:08:35.639
<v Speaker 2>find all the utxos associated with your addresses. Then it

166
00:08:35.759 --> 00:08:37.799
<v Speaker 2>just adds them up to show you your total balance.

167
00:08:37.879 --> 00:08:39.799
<v Speaker 1>Got it. So the wallet is more like a keychain

168
00:08:39.799 --> 00:08:40.600
<v Speaker 1>and a calculator.

169
00:08:40.720 --> 00:08:42.679
<v Speaker 2>That's a great way to put it. And wallets can

170
00:08:42.720 --> 00:08:45.360
<v Speaker 2>be software on your computer, apps on your phone, or

171
00:08:45.399 --> 00:08:49.919
<v Speaker 2>even physical cold storage devices like special USB drives, or

172
00:08:50.159 --> 00:08:52.159
<v Speaker 2>just a piece of paper with QR codes for your

173
00:08:52.200 --> 00:08:54.759
<v Speaker 2>keys and address is printed on it. It's all about

174
00:08:54.799 --> 00:08:55.960
<v Speaker 2>controlling those keys.

175
00:08:56.039 --> 00:08:59.559
<v Speaker 1>That control is powerful, definitely. But you mentioned the blockchain ledger.

176
00:09:00.120 --> 00:09:02.879
<v Speaker 1>It must get huge over time, right, with every single

177
00:09:02.919 --> 00:09:06.559
<v Speaker 1>transaction recorded. How does something like a mobile phone wallet

178
00:09:06.919 --> 00:09:11.159
<v Speaker 1>check a transaction quickly without needing to download gigabytes and

179
00:09:11.159 --> 00:09:14.120
<v Speaker 1>gigabytes of history. That seems like a massive barrier.

180
00:09:14.320 --> 00:09:17.480
<v Speaker 2>Yeah, that's a critical challenge for usability. And the solution

181
00:09:17.600 --> 00:09:20.879
<v Speaker 2>is pretty elegant. The source mentions Merkle trees and something

182
00:09:20.919 --> 00:09:22.919
<v Speaker 2>called simple payment verification or.

183
00:09:22.879 --> 00:09:24.399
<v Speaker 1>SPV Herkle trees.

184
00:09:24.559 --> 00:09:27.720
<v Speaker 2>Right, it's a clever bit of cryptography. Basically, you take

185
00:09:27.759 --> 00:09:30.639
<v Speaker 2>all the individual transaction hashes in a block, pair them up,

186
00:09:30.720 --> 00:09:33.799
<v Speaker 2>hash the pairs, pair those hashes and so on until

187
00:09:33.840 --> 00:09:37.399
<v Speaker 2>you get a single hash for the entire set of transactions.

188
00:09:37.879 --> 00:09:40.080
<v Speaker 2>That single hash is the Merkle.

189
00:09:39.840 --> 00:09:42.559
<v Speaker 1>Root, okay, like a summary hash for the whole.

190
00:09:42.360 --> 00:09:46.039
<v Speaker 2>Block's contents exactly, And that Merkle root is stored in

191
00:09:46.080 --> 00:09:49.159
<v Speaker 2>the blockheader, which is much much smaller than the full

192
00:09:49.200 --> 00:09:52.679
<v Speaker 2>block with all its transactions. So SPV clients, like your

193
00:09:52.679 --> 00:09:55.720
<v Speaker 2>mobile wallet, they don't download the whole blockchain, they just

194
00:09:55.799 --> 00:09:59.600
<v Speaker 2>download the blockheaders lightweight. Then, if you want to check

195
00:09:59.600 --> 00:10:02.320
<v Speaker 2>if you're pacific transaction is in a certain block, the

196
00:10:02.440 --> 00:10:05.039
<v Speaker 2>wallet asks a full node for a small bit of

197
00:10:05.159 --> 00:10:08.879
<v Speaker 2>proof the Merkle path that connects your transaction hash up

198
00:10:08.919 --> 00:10:11.200
<v Speaker 2>to the Merkle route in the header it already has.

199
00:10:11.840 --> 00:10:14.399
<v Speaker 2>It only needs a few hashes to verify instead of

200
00:10:14.440 --> 00:10:18.279
<v Speaker 2>scanning potentially millions of transactions. It's incredibly efficient.

201
00:10:18.480 --> 00:10:21.600
<v Speaker 1>That makes sense. It allows for practical use on everyday devices.

202
00:10:21.639 --> 00:10:24.639
<v Speaker 2>Absolutely, it's key to making bitcoin usable. There's even that

203
00:10:24.679 --> 00:10:28.480
<v Speaker 2>interesting example of Julian Assange. I think he supposedly used

204
00:10:28.480 --> 00:10:32.440
<v Speaker 2>a recent block hash, probably verified via SPV, as a

205
00:10:32.480 --> 00:10:35.360
<v Speaker 2>sort of proof of life when there were rumors.

206
00:10:35.000 --> 00:10:37.919
<v Speaker 1>Right I remember that, using the blockchain's public timestamp as

207
00:10:37.919 --> 00:10:39.000
<v Speaker 1>a verifiable signal.

208
00:10:39.200 --> 00:10:42.480
<v Speaker 2>Yeah, a pretty creative use case for this kind of verification.

209
00:10:42.919 --> 00:10:46.879
<v Speaker 1>Okay, so Bitcoin really set the stage secure trustless value

210
00:10:46.879 --> 00:10:51.480
<v Speaker 1>transfer proven. But then Etherium arrived and seemed to well

211
00:10:51.519 --> 00:10:54.519
<v Speaker 1>blow the doors open, moving way beyond just digital money.

212
00:10:55.200 --> 00:10:58.279
<v Speaker 1>Bitcoin showed we could do digital scarcity transfer of value

213
00:10:58.320 --> 00:11:02.600
<v Speaker 1>peer to peer asked, what if the blockchain could run code?

214
00:11:03.360 --> 00:11:05.639
<v Speaker 1>What was the big idea there? The paradigm shift.

215
00:11:05.960 --> 00:11:08.039
<v Speaker 2>You're right, it was a major leap. If you think

216
00:11:08.039 --> 00:11:11.559
<v Speaker 2>of Bitcoin primarily as this brilliant transfer program, like a

217
00:11:11.600 --> 00:11:16.360
<v Speaker 2>decentralized calculator and ledger for value, Ethereum aimed to generalize that.

218
00:11:16.840 --> 00:11:20.039
<v Speaker 2>It created a true computational platform built on a blockchain.

219
00:11:20.440 --> 00:11:23.559
<v Speaker 2>The core idea was building a native programming language, Solidity

220
00:11:23.879 --> 00:11:27.360
<v Speaker 2>and the Ethereum Virtual Machine, the EVM. This let developers

221
00:11:27.360 --> 00:11:31.399
<v Speaker 2>write and deploy actual programs, business logic, rules, applications directly

222
00:11:31.440 --> 00:11:32.960
<v Speaker 2>onto the blockchain itself.

223
00:11:32.720 --> 00:11:35.279
<v Speaker 1>So transactions weren't just about sending value anymore.

224
00:11:35.440 --> 00:11:38.960
<v Speaker 2>Exactly in Ethereum, a transaction can be a function call.

225
00:11:39.320 --> 00:11:43.480
<v Speaker 2>It can trigger code execution on the blockchain, verifiable code execution.

226
00:11:44.159 --> 00:11:47.120
<v Speaker 2>This transformed the blockchain from just a ledger into something

227
00:11:47.159 --> 00:11:51.159
<v Speaker 2>more like a global decentralized computer. Anyone could run code

228
00:11:51.200 --> 00:11:53.879
<v Speaker 2>on it and everyone could trust the outcome because the

229
00:11:53.919 --> 00:11:57.000
<v Speaker 2>EVM ensures deterministic execution, and.

230
00:11:57.000 --> 00:12:02.000
<v Speaker 1>This enabled smart contracts and decentralized applications DAPs. Can you

231
00:12:02.039 --> 00:12:04.480
<v Speaker 1>explain those? What could they do that? Bitcoin could?

232
00:12:04.759 --> 00:12:08.039
<v Speaker 2>Sure? Smart contracts are basically just pieces of code deployed

233
00:12:08.039 --> 00:12:11.080
<v Speaker 2>to the Ethereum blockchain. They live at a specific address,

234
00:12:11.279 --> 00:12:14.840
<v Speaker 2>just like a user account. They automatically execute predefined functions

235
00:12:14.840 --> 00:12:17.240
<v Speaker 2>when certain conditions are met or when they receive a

236
00:12:17.240 --> 00:12:22.159
<v Speaker 2>transaction triggering them, no intermediaries needed. They run exactly as programmed.

237
00:12:21.720 --> 00:12:24.159
<v Speaker 1>Like a digital vending machine for more complex tasks.

238
00:12:24.360 --> 00:12:27.879
<v Speaker 2>That's a good analogy. Yeah, they're deterministic, meaning every node

239
00:12:27.960 --> 00:12:30.360
<v Speaker 2>running the code gets the exact same result, which is

240
00:12:30.440 --> 00:12:35.919
<v Speaker 2>crucial for maintaining consensus across the network and DAPs. Decentralized applications, well,

241
00:12:36.120 --> 00:12:38.519
<v Speaker 2>they use these smart contracts as their back end logic.

242
00:12:38.840 --> 00:12:41.320
<v Speaker 2>Instead of running on a central server owned by one company,

243
00:12:41.399 --> 00:12:44.960
<v Speaker 2>their core functions run on the decentralized Ethereum network. The

244
00:12:45.000 --> 00:12:47.240
<v Speaker 2>front end with the user sees, can still be a

245
00:12:47.240 --> 00:12:50.080
<v Speaker 2>normal website or app, but the back end is trustless

246
00:12:50.120 --> 00:12:51.600
<v Speaker 2>and distributed.

247
00:12:51.279 --> 00:12:53.000
<v Speaker 1>Which opens up possibilities for.

248
00:12:53.159 --> 00:12:58.720
<v Speaker 2>Huge possibilities decentralized finance or defied lending, borrowing exchanges without banks,

249
00:12:59.000 --> 00:13:02.519
<v Speaker 2>online gaming with true ownership of in game items, digital

250
00:13:02.559 --> 00:13:06.679
<v Speaker 2>identity systems, you control, supply chain tracking, voting systems, so

251
00:13:06.799 --> 00:13:09.360
<v Speaker 2>much more. Ethereum even had this vision of a world

252
00:13:09.360 --> 00:13:12.960
<v Speaker 2>computer with integrated components like Whisper for secure p top

253
00:13:13.080 --> 00:13:16.879
<v Speaker 2>messaging and Swarm for decentralized file storage, really laying the

254
00:13:16.879 --> 00:13:19.399
<v Speaker 2>groundwork for what people now call Web three point zero.

255
00:13:19.480 --> 00:13:24.519
<v Speaker 1>It all sounds incredibly ambitious, almost utopian, democratizing finance computation,

256
00:13:25.399 --> 00:13:28.679
<v Speaker 1>but as always, new tech brings new risks. Our Source

257
00:13:28.679 --> 00:13:31.240
<v Speaker 1>spends a whole chapter on something called the DAO hacked.

258
00:13:32.320 --> 00:13:35.120
<v Speaker 1>That sounds pretty bad. What was the DAO, what happened

259
00:13:35.159 --> 00:13:37.279
<v Speaker 1>and crucially what did the ecosystem learn?

260
00:13:37.519 --> 00:13:40.799
<v Speaker 2>Ah, the DAO, Yes, that was a huge moment and yeah,

261
00:13:40.879 --> 00:13:45.559
<v Speaker 2>pretty painful. The DAO stood for Decentralized Autonomous Organization. It

262
00:13:45.600 --> 00:13:49.720
<v Speaker 2>was this incredibly ambitious early project on ethereum. The vision

263
00:13:49.840 --> 00:13:53.440
<v Speaker 2>was a decentralized venture capital fund. People bought DOAO tokens

264
00:13:53.440 --> 00:13:55.840
<v Speaker 2>and tokenholders would vote on which projects to invest. A

265
00:13:55.919 --> 00:13:59.480
<v Speaker 2>theorym in all run by code, no managers, no central office,

266
00:13:59.720 --> 00:14:03.000
<v Speaker 2>true automated organization. That was the dream. But there was

267
00:14:03.039 --> 00:14:06.399
<v Speaker 2>a flaw, a bug in the dao's smart contract code,

268
00:14:06.799 --> 00:14:09.960
<v Speaker 2>specifically something called a re entrancy bug entry. Just think

269
00:14:09.960 --> 00:14:12.279
<v Speaker 2>of it like this. The code that handled withdrawals had

270
00:14:12.279 --> 00:14:15.039
<v Speaker 2>a flaw. It sent the ether before updating the user's

271
00:14:15.080 --> 00:14:18.360
<v Speaker 2>internal balance exactly, so an attacker figured out they could

272
00:14:18.399 --> 00:14:21.440
<v Speaker 2>make the withdrawal function call itself again recursively before the

273
00:14:21.480 --> 00:14:24.120
<v Speaker 2>balance was updated. They could just keep withdrawing the same

274
00:14:24.159 --> 00:14:27.519
<v Speaker 2>funds over and over until the doo's coffers were drained.

275
00:14:27.720 --> 00:14:29.960
<v Speaker 1>Wow. So it wasn't a hack of Atheroreum itself, but

276
00:14:30.000 --> 00:14:32.200
<v Speaker 1>the application built on top precisely.

277
00:14:32.440 --> 00:14:36.080
<v Speaker 2>The attacker exploited a vulnerability in the dato's code. It

278
00:14:36.159 --> 00:14:39.120
<v Speaker 2>led to this massive drain millions of dollars worth of ether.

279
00:14:39.240 --> 00:14:42.759
<v Speaker 2>At the time, it was catastrophic for confidence, and it

280
00:14:42.840 --> 00:14:46.879
<v Speaker 2>led to a huge, very controversial decision a hard fork

281
00:14:46.960 --> 00:14:50.679
<v Speaker 2>of the entire ethereum blockchain, basically rolling back the chain

282
00:14:50.759 --> 00:14:53.399
<v Speaker 2>to before the hack to return the stolen.

283
00:14:53.039 --> 00:14:55.679
<v Speaker 1>Funds, which wasn't universally popular, right, not at all.

284
00:14:55.799 --> 00:14:58.080
<v Speaker 2>A portion of the community believed the code was law,

285
00:14:58.159 --> 00:15:01.279
<v Speaker 2>even flawed code, and that reverse seeing the chain violated

286
00:15:01.320 --> 00:15:05.799
<v Speaker 2>the principle of immutability. They stuck with the original, unforked chain,

287
00:15:05.840 --> 00:15:09.720
<v Speaker 2>which became Etherium Classic or etc. The main chain with

288
00:15:09.759 --> 00:15:13.600
<v Speaker 2>the rollback continued as Ethereum eth So a.

289
00:15:13.519 --> 00:15:17.080
<v Speaker 1>Major vulnerability exposed a split in the community. But was

290
00:15:17.080 --> 00:15:20.120
<v Speaker 1>it ultimately a failure or just a really hard lesson

291
00:15:20.200 --> 00:15:21.000
<v Speaker 1>learned very early?

292
00:15:21.039 --> 00:15:23.720
<v Speaker 2>On? Looking back, it was definitely a harsh lesson, but

293
00:15:23.799 --> 00:15:26.639
<v Speaker 2>a crucial one. It wasn't a failure of the core

294
00:15:26.759 --> 00:15:31.200
<v Speaker 2>blockchain concept or Ethereum's EVM. It was purely a bug

295
00:15:31.240 --> 00:15:35.360
<v Speaker 2>in the application layer smart contract. It brutally highlighted how

296
00:15:35.399 --> 00:15:38.879
<v Speaker 2>young the technology was, especially the tools and best practices

297
00:15:38.879 --> 00:15:43.639
<v Speaker 2>for writing secure smart contracts, formal verification, thorough auditing. These

298
00:15:43.720 --> 00:15:45.600
<v Speaker 2>became top priorities overnight, so.

299
00:15:45.559 --> 00:15:48.080
<v Speaker 1>It forced the ecosystem to mature fast.

300
00:15:48.240 --> 00:15:51.320
<v Speaker 2>Absolutely, it was a trial by fire, painful, yes, but

301
00:15:51.480 --> 00:15:54.080
<v Speaker 2>it paved the way for much more robust development standards,

302
00:15:54.120 --> 00:15:57.039
<v Speaker 2>security tools, and a deeper understanding at the risks involved.

303
00:15:57.399 --> 00:16:01.279
<v Speaker 2>And paradoxically, it probably accelerated the movie towards more enterprise

304
00:16:01.320 --> 00:16:03.720
<v Speaker 2>focused applications where security is paramount.

305
00:16:04.039 --> 00:16:06.120
<v Speaker 1>And how have those lessons been applied since then? How

306
00:16:06.120 --> 00:16:09.720
<v Speaker 1>are we seeing more robust, trustworthy applications being built now?

307
00:16:09.919 --> 00:16:12.519
<v Speaker 1>Maybe in areas like healthcare where trust and privacy are

308
00:16:12.519 --> 00:16:13.720
<v Speaker 1>absolutely non negotiable.

309
00:16:13.919 --> 00:16:16.879
<v Speaker 2>Yeah, that's where things get really interesting now seeing the practical,

310
00:16:16.960 --> 00:16:21.200
<v Speaker 2>mature applications emerge you have consortia like the Enterprise Ethereum

311
00:16:21.240 --> 00:16:25.799
<v Speaker 2>Alliance EEA and projects like hyper letter Fabric, which IBM

312
00:16:25.960 --> 00:16:30.519
<v Speaker 2>championed initially. These are often focused on permission blockchains, not

313
00:16:30.600 --> 00:16:34.840
<v Speaker 2>fully public like Bitcoin or Ethereum, but networks where participants

314
00:16:34.919 --> 00:16:36.799
<v Speaker 2>need authorization to join.

315
00:16:36.679 --> 00:16:38.519
<v Speaker 1>More suited for businesses exactly.

316
00:16:38.600 --> 00:16:42.120
<v Speaker 2>Fabric, for instance, allows for private transactions too. Data that

317
00:16:42.200 --> 00:16:44.399
<v Speaker 2>only needs to be seen by specific parties on the

318
00:16:44.399 --> 00:16:47.919
<v Speaker 2>network goes directly between them, not broadcast to everyone. That's

319
00:16:48.000 --> 00:16:52.360
<v Speaker 2>critical for business confidentiality and regulations like GDPR or IPA.

320
00:16:52.720 --> 00:16:54.799
<v Speaker 1>Makes sense for healthcare data definitely.

321
00:16:55.039 --> 00:16:59.000
<v Speaker 2>We're seeing real pilots and applications now, things like verifiable

322
00:16:59.120 --> 00:17:02.720
<v Speaker 2>data audit. Deep Mind Health was exploring this, or look

323
00:17:02.759 --> 00:17:06.960
<v Speaker 2>at pharmaceutical supply chains tracking drugs from manufacture to pharmacy,

324
00:17:07.279 --> 00:17:10.720
<v Speaker 2>creating that immutable record of custody. Pilots like the Bruin

325
00:17:10.839 --> 00:17:13.599
<v Speaker 2>chain working with the FDA are showing this can potentially

326
00:17:13.640 --> 00:17:17.599
<v Speaker 2>save billions by reducing counterfeit drugs, spoilage and fraud.

327
00:17:17.759 --> 00:17:18.319
<v Speaker 1>It's huge.

328
00:17:18.440 --> 00:17:23.160
<v Speaker 2>It is and physician credentially verifying doctor's qualifications is another area.

329
00:17:23.480 --> 00:17:28.759
<v Speaker 2>It's currently a slow, expensive, paper based mess blockchain could

330
00:17:28.799 --> 00:17:33.079
<v Speaker 2>streamline that significantly, and the key enabler for privacy in

331
00:17:33.119 --> 00:17:36.039
<v Speaker 2>many of these, especially in healthcare, is the growing use

332
00:17:36.160 --> 00:17:39.039
<v Speaker 2>of zero knowledge proofs like zk snarks.

333
00:17:39.319 --> 00:17:41.920
<v Speaker 1>Zero knowledge proofs sounds like magic.

334
00:17:41.640 --> 00:17:44.200
<v Speaker 2>It almost feels like it. It's cryptography that lets you

335
00:17:44.279 --> 00:17:46.680
<v Speaker 2>prove you know something or that a statement is true

336
00:17:46.920 --> 00:17:49.480
<v Speaker 2>without revealing the underlying information itself.

337
00:17:49.519 --> 00:17:50.440
<v Speaker 1>How does that apply here?

338
00:17:50.640 --> 00:17:53.319
<v Speaker 2>Well, imagine proving a patient is eligible for a certain

339
00:17:53.359 --> 00:17:56.279
<v Speaker 2>treatment based on their medical history without ever revealing their

340
00:17:56.319 --> 00:17:59.640
<v Speaker 2>specific conditions or identity on the blockchain, or proving a

341
00:17:59.680 --> 00:18:04.960
<v Speaker 2>drug authenticity without exposing proprietary batch details. It's revolutionary for

342
00:18:05.000 --> 00:18:07.000
<v Speaker 2>balancing transparency and privacy.

343
00:18:07.240 --> 00:18:11.000
<v Speaker 1>What an incredible journey we've traced from the ashes of

344
00:18:11.000 --> 00:18:13.240
<v Speaker 1>the two thousand and eight financial crisis and that deep

345
00:18:13.240 --> 00:18:16.759
<v Speaker 1>need for trust, through the technical breakthroughs of bitcoin and ethereum,

346
00:18:17.119 --> 00:18:20.119
<v Speaker 1>that cautionary tale with the DAO a real wake up call,

347
00:18:20.680 --> 00:18:24.880
<v Speaker 1>and now into these really promising, secure, privacy preserving applications

348
00:18:24.880 --> 00:18:28.079
<v Speaker 1>that are starting to mature. It's clear blockchain is way

349
00:18:28.119 --> 00:18:29.799
<v Speaker 1>more than just a fancy database.

350
00:18:29.880 --> 00:18:33.160
<v Speaker 2>Absolutely, and one point our source really emphasizes is that

351
00:18:33.200 --> 00:18:37.519
<v Speaker 2>this isn't just about technology. It's described as a new discipline,

352
00:18:37.680 --> 00:18:40.440
<v Speaker 2>applied behavioral economics in real time.

353
00:18:40.279 --> 00:18:42.000
<v Speaker 1>Applied behavioral economic.

354
00:18:41.720 --> 00:18:45.799
<v Speaker 2>Yes, it's about using game theory, designing economic incentives like

355
00:18:45.839 --> 00:18:49.799
<v Speaker 2>the bitcoin mining reward to encourage cooperation and build trust

356
00:18:49.839 --> 00:18:53.160
<v Speaker 2>within the system itself. Programmatically, it's about empowering users, giving

357
00:18:53.200 --> 00:18:55.279
<v Speaker 2>them back control over their own data, their own value,

358
00:18:55.279 --> 00:18:58.559
<v Speaker 2>instead of relying solely on intermediaries whose incentives might not

359
00:18:58.559 --> 00:19:00.640
<v Speaker 2>always align with theirs power.

360
00:19:00.880 --> 00:19:04.519
<v Speaker 1>So what's the takeaway for everyone listening this shift from

361
00:19:04.640 --> 00:19:09.319
<v Speaker 1>central control to decentralized consensus. It's still happening, it's still evolving.

362
00:19:09.799 --> 00:19:12.119
<v Speaker 1>Maybe the question for you, the listener, is this, how

363
00:19:12.200 --> 00:19:18.039
<v Speaker 1>might this fundamental change, this democratization of trust, of verifiable value,

364
00:19:18.039 --> 00:19:21.680
<v Speaker 1>How might that reshape your industry, your daily life, even

365
00:19:21.960 --> 00:19:24.160
<v Speaker 1>just how you think about interacting online. It really is

366
00:19:24.200 --> 00:19:28.000
<v Speaker 1>about empowering people, building systems where value is maybe clearer

367
00:19:28.039 --> 00:19:31.079
<v Speaker 1>based on fundamentals, not just opaque relationships or these single

368
00:19:31.279 --> 00:19:34.079
<v Speaker 1>points of failure we saw breakdown so badly. We really

369
00:19:34.079 --> 00:19:36.640
<v Speaker 1>hope this deep dive into the blockchain ecosystem has given

370
00:19:36.680 --> 00:19:39.559
<v Speaker 1>you a solid shortcut to understanding the core ideas and

371
00:19:39.599 --> 00:19:41.839
<v Speaker 1>maybe spark some curiosity about what's coming next.