S15 E59: David Burkett on MWEB & Privacy
Search this conversation
0:47Vlad CosteaHello there and welcome to the Bitcoin Takeover podcast. I'm Vlad. I'm here at the Proof of Work Summit in Frankfurt, organized by the ETC people and the Litecoin Foundation people. And I'm sitting next to the creator of MWEB, which is the Mimblewimble Extension Block. His name is David Burkett, and he used to be a Grin developer who came to Litecoin, built this very beautiful construction which provides scalability and also some privacy. And it's very cool that we get to talk to the architect himself, because this was an idea by Andrew Poelstra, which dates back to 2015 or 2016. But it was just an idea. It was never coded. And this is the man who made it happen. So it's good to have him. David.
1:32David BurkettThanks for having me. It was actually even before Poelstra. It was like an anonymous drop, and then he refined it. So yeah, it was, it was just like an anonymous onion share link.
1:44Vlad CosteaYou mean Tom Elvis Jedusor?
1:46David BurkettYeah, yeah, yeah.
1:47Vlad CosteaNo, but he was the one to make Mimblewimble, but Andrew Poelstra...
1:51David BurkettOh, he refined...
1:52Vlad Costea...also proposed the extension block side for Bitcoin.
1:55David BurkettOh, that's true. That's true. Yeah. Okay.
1:58Vlad CosteaYeah. And I did interview him this year, and I told him about MWEB, and he said it's very cool that the Litecoin people were able to pull this off, but I don't think it's relevant for Bitcoin anymore in the post-Taproot era, because we can do Tapscript, whatever. And I was a bit disappointed, but...
2:17David BurkettYeah, you know, fads, they come and go for Bitcoiners. It was the greatest thing, and then they had moved on.
2:25Vlad CosteaWhy do you think this is a fad?
2:27David BurkettWell, I mean, I think they saw it... They have fads, is what I'm saying. It's like they get interested in some idea, the communities in general, and then they find a different way to do it, and it's just whatever. At some point, you actually have to implement something. You can't just continue to look for the next greatest privacy. Although I hope that in 10 years from now we have really, really cool privacy tech, and then maybe we'll be regretting our choice of MWEB, or maybe find a way to scale it out and find some new, better thing. But in the meantime, people need privacy now. So everything can't be this, like, just academic exercise. We at some point have to adopt something. And Litecoin, while Bitcoin was, you know, debating everything, we went ahead and did it. And I'm glad we did.
3:16Vlad CosteaI remember in 2018 when Charlie Lee posted this tweet in which he said that he's working on ways to make Litecoin fungible. His first idea was to implement the confidential transactions that were created by Adam Back and Greg Maxwell, working at Blockstream. And I guess he searched for something which was more avant-garde and more scalable than CT. He came across Mimblewimble, but his first idea was to work with the guys from Beam. So I'm not sure exactly what happened along the way, but then he said, you know, I found this very smart Grin++ developer, which is Grin written in C++, and you're the guy who basically worked for a couple of years to make it happen.
4:01David BurkettYeah, so the Beam guys, I like them. They're smart people. They were very busy with their other things. They had so much they were trying to ship. And, you know, though they kind of somewhat worked with Charlie for a little there, it was just, they didn't really have, like, resources to dedicate to it. And then, like, I, you know, I was looking for other opportunities at the time, so it was an obvious... you know, with my background, it was obvious choice was: hey, let's see, you know, let's see some real usage out of this. Because I had done a lot with Mimblewimble, but then we just had these small ecosystems that weren't really mature at all. They're brand new, hard to use, whatever. I wanted to see what it was like in a large, well, you know, mature ecosystem, basically.
4:55Vlad CosteaYeah. Let's break it down a bit for people who may not be aware what this is about. So what is Mimblewimble, and what is Grin?
5:03David BurkettOkay, so Grin was the first implementation of Mimblewimble. Mimblewimble is a kind of clever way... it's like a combination of confidential transactions, which just means hidden amounts with fancy proofs, along with sort of like a CoinJoin mechanism, which means like you take multiple transactions, they have like their inputs, that are coins you're spending, and outputs, which are like coins you're creating. And you always create like equal or less coins when you send. You just kind of destroy the old ones, create new ones, and you do so in a transaction.
5:44The CoinJoin kind of combines all the transactions, all the inputs from all of them, and then the outputs from all of them, into one big transaction to help eliminate the privacy leak that comes from transaction graphs. And so by combining those two ideas and some clever proofs based off Pedersen commitments, and just some really, really simple math, actually, as far as elliptic curve crypto goes, it's just basic math to just prove that no new coins were created and that value was transferred appropriately from one party to another in a verifiable way.
6:26And it was just a really clever idea that was just, you know, developed by some anonymous person somewhere. And so Grin, seeing how... it's like a very beautiful proof, like seeing how cool it was, decided to go and implement it. And they were very... like early Bitcoin days. There were a lot of pseudonyms working on it. There were a lot of really smart people that, you know, well known in the Bitcoin community, were also contributing. It was just a really cool, like, cypherpunk-type-style development. And so it was really cool to see all of that come together, and over almost three years, then Grin was born. But it struggled to get adoption for various reasons. And so it was, yeah... Litecoin was next.
7:23Vlad CosteaHold up a minute! Did someone just pay you in stablecoins? Swap that CBDC wannabe for free market, scarce, and provably yours, BTC with SideShift.ai. Do you want to swap your BTC for something else? Use SideShift, the direct-to-wallet exchange. It's fast, it has lots of liquidity for your needs, and the fees are lower than you might expect. SideShift is also available via integrations with Trezor Suite and BTCPay Server. Check out SideShift.ai today. And yes, you can also use SideShift to dump every other coin and token to make more BTC. Keep stacking, man. SideShift.ai.
8:18I remember when Grin was launched, it was very popular. It was basically the most cypherpunk project since Monero, maybe. Yeah. And something that was purely driven by... something that was purely driven by users. And then there was this report that you can run your node and not prune the previous transactions from blocks, and you can basically surveil what's happening. And therefore some people gave up on it and said that it has pretty poor privacy primitives.
8:53David BurkettSo the history gets a little blurred there. We actually... adoption was not really occurring at that point. We were already losing. We had lost a lot of the big names that were early supporters of it, that were well known in the Bitcoin world. It was already struggling. And then the report that came out was sort of like stating the obvious. It's like, you know, if only one person is transacting a minute, it's like saying, "I can tell only one person is transacting a minute." It's like, we didn't have enough usage to have any, like, of the serious privacy benefits.
9:29But it was well written, and it ended up being like a, you know, looking like a big hit piece and whatever. So the ones who were already, like, struggling to stay interested with Grin, a lot of them had dropped off at that time. But I don't think that's really what, you know, like, the nail in the coffin there. It was just like, things were already going down. You know, we were already losing a lot of users at that point.
9:58Vlad CosteaI did interview a Grin developer, and I'm searching for... his name is Marek Narozniak.
10:05David BurkettOh, yeah, yeah.
10:06Vlad CosteaHe very much looks up to you. I spoke with him. He's a physicist. He also talked about quantum computing and how that can pose a threat in the future. He's a big fan of yours, I guess. Sometimes you take one month to reply to his emails, but he's always happy when he gets a reply.
10:28David BurkettShout-out to Marek. Yeah, thanks. Yeah, glad to hear it. I enjoy working with him. He's a very smart guy too, so.
10:36Vlad CosteaSo why do you think Mimblewimble is still relevant today?
10:40David BurkettIt's... it's still a very... the way it provides practical privacy in a very scalable manner without introducing any kind of complex new primitives. There's no, like, crazy SNARKs or anything like that. It's very, very simple to audit, simple to understand for anyone with any kind of crypto background. It's easier to really ensure that it's safe. We don't have, like, you know... Zcash is really fancy stuff, right?
11:10And I know it can do a lot of things that, you know, Mimblewimble can't, but like, when 12 people in the world know how it works, and, you know, that's a lot of faith to put into a small group of people. And we are getting some ZK proofs these days that are a little easier to understand, and there's at least more of a knowledge background amongst the academic crypto community. But still, there's nothing so simple as what, you know, Mimblewimble was. It's based entirely off the same crypto primitives that we use for every other thing in Bitcoin and Litecoin. So it was not like a drastic security adjustment, to make any kind of new, you know, risks there.
12:05Vlad CosteaBut as far as I know, and I think I used Beam last week, and it does have addresses, but Mimblewimble in its purest form, it has no addresses.
12:15David BurkettSo yeah, the addresses... so Mimblewimble can have addresses in its purest form. Like, Grin has addresses, but those addresses aren't to, like, send on chain. They're more to, like, encrypt some... it's like to deal with the communication, basically. One of the biggest hurdles with pure Mimblewimble is that you can't just send to someone offline. You have to actually communicate with the person you're sending to. There's a back-and-forth protocol. And that led to a lot of issues with adoption for Grin, and less so for Beam, because they took a different approach. But yeah, there's got to be some kind of form of communication.
12:56So what a lot of the Mimblewimble implementations will do is have, like, an address that maybe is where they can meet to make the... to form the conversation. Like, a Grin address is one of two things. It's a Tor address, so they first try to communicate via Tor through an onion address. And when that fails, then they can go encrypt some kind of packet that can be then manually transferred to the other person, to then sign it and give it back. But yeah, on chain, there's no kind of, like, address or anything like that. But also with MWEB, you know, we have addresses which are stealth addresses...
13:41Vlad CosteaBecause I guess it was hard to code this extension block implementation on Litecoin, because it has a different system. You don't just have these temporary addresses that, for example, in Beam, if I don't get online to receive my transaction within 24 hours or something, the transaction gets cancelled. But in the case of Litecoin MWEB, you have this MWEB address, which is permanent, and you can post it somewhere, and people can send you money even years later.
14:16David BurkettYep. Yeah, it's based off the stealth address technologies used in Monero and some other coins. It's like a couple of public keys, or, like, elliptic curve points, that, like, the sender basically generates new one-time-use addresses when they send to you. So it allows you to generate a near-infinite number of, you know, private one-time-use addresses. There's no address reuse or anything. And so yeah, adapting Mimblewimble to support that was one of the biggest challenges, and it's something, when we started out with the project, we weren't sure we were going to even be able to do.
14:58I had serious concerns early on about how Litecoin would work with, like, the existing ecosystem expecting instantaneous sends, you know, or at least instantaneous, like, mempool broadcast. I was worried that we would have some kind of issues, not being able to, like, handle the communication involved there. But luckily we were able to come up with a way to have stealth addresses, to have, you know, one-sided sends. You just create a transaction like normal and just send it to an address. And there were a lot of security concerns there. We worked with some academics on it. We worked with some auditors. But we were able to fortunately find a very good solution, I think.
15:49Vlad CosteaSo, are you a Bitcoin maximalist? Do you want everything to get built on Bitcoin? Then read more about drivechains from LayerTwo Labs, an initiative to create a two-way pegged sidechain for every use case. Everything from Zcash privacy to Ethereum smart contracts will be available on a dedicated chain that pays fees to the Bitcoin miners and uses BTC for every transaction. But you don't have to imagine what this would look like. Go to layer2labs.com/download and check out the software. It currently runs on the Bitcoin Signet, but with your help, this grand vision of doing everything on Bitcoin will come true. layer2labs.com/download.
16:48It's very impressive how it works, because for the average user there is no distinction. They don't have to think that they're activating something else. At least in the Core client, which I used. I'm not sure what it's going to look like on mobile, but I'm pretty sure that it's going to be the exact same user experience.
17:07David BurkettYeah, I don't know exactly what they're doing for transaction creation on mobile. They have a lot of flexibility how they handle it, but I know that I personally, like on Core, focused a lot on making sure that, first off, it works seamlessly. They, you know, they had the easy... like, you don't have to know exactly what's happening under the scenes. For those who do care, you can. But then also choosing private defaults, because, like, if you just send whichever, whatever, like, you can lose the privacy benefits of MWEB. So there was a lot of emphasis on, like, let's make sure that we can do this, that maximizes privacy while still being super simple to send and receive. And I think what we have right now works pretty well.
17:56Vlad CosteaYeah. You have, I think, four or five types of privacy. So I'm going to spell them out so that we can count them. You have sender privacy. You have receiver privacy. You have amounts privacy. You also have network-level privacy. So four of them.
18:10David BurkettYeah, so network-level privacy is not some... so that's, that's like when you broadcast the transaction, is that what you mean? Yeah. So I mean, Bitcoin and Litecoin already have, Tor, the option to run via Tor and everything else. We don't, with MWEB, do anything particularly new there. You can still run with Tor, and then that gives you the network-level privacy. If you don't run with Tor...
18:41Vlad CosteaVPN on your mobile.
18:42David BurkettOr VPN, or yeah, there's various options. But even if you don't, we still, you know, follow the same standards, the same practices as normal transactions, where we try not to just be spamming the network, broadcasting all the time, you know, making it obvious where the source is. We try to limit that, to gain as much privacy as we can.
19:07Vlad CosteaYep. In the Bitcoin white paper, chapter 10, you have this mention that they have... so Satoshi envisioned this idea that you have receiver privacy, which means that if you generate a different receiving address for every transaction, you're going to have pretty good privacy until, and this is actually mentioned in the white paper, you use multiple inputs and you consolidate them together, and that can give people analyzing the blockchain some idea about who might be behind.
19:37David BurkettYeah, and Mimblewimble doesn't perfectly solve that. So you still, you know, like, even if you have the good receiver privacy, you always send to a new address, which stealth addresses guarantee, that you are always sending to a new address. Yet we still have to spend coins together. And there's been a lot of research on coin selection algorithms, which we take advantage of too, to try to, you know, maximize privacy in that aspect. But you can still run into similar issues, which is where it's very useful to have the CoinJoin that comes from Mimblewimble.
20:13And we're working on CoinSwap, which will allow you to, like, when you receive something, then you can kind of submit it to a pool to, like, kind of join with hundreds, maybe thousands of other coins, get a fresh coin back, and that gives you a much larger anonymity set for those coins. Then the person who sent it to you can't just watch that coin to see which ones you spend it with. That's no longer an option. So yeah, right now it's not perfect. There's still ways we can leak it, but we are working closer, we are getting much closer to Satoshi's vision for what good privacy would be.
20:56Vlad CosteaYeah. But would you say that there is sender privacy?
20:59David BurkettYeah, so sender privacy just... I mean, that's kind of what the input linking is, would be the sender. If carefully choosing its inputs, has sender privacy, or if carefully following practices, like mixing and whatever. But yeah, I don't usually think of it in sender/receiver privacy that way. But if you were to, then sender privacy would rely strictly on the sender making smart choices, which in the wallet we always try to do the best we can for you. But if you're an advanced user and you understand UTXO management, you'll get even better privacy if you do it yourself.
21:43Vlad CosteaYep. I actually have a curiosity. I did not try this. Let's say that in my wallet I have two inputs. One of them is MWEB, and the other one is clear chain, or main chain. Can I batch them together to send out one transaction?
21:56David BurkettYou can, and it will do that automatically, and you don't have to think about what it does. It's a little complicated. It was really hard to make this work. But what it ends up doing is it will, like, let's say you're sending to... you want to send to clear, you know, main chain Litecoin, it will actually peg in those coins to the MWEB, then build an MWEB transaction with those two inputs that pegs out.
22:22Vlad CosteaThat's very smart, because you're not de-anonymizing the setup.
22:25David BurkettYeah, yeah, yeah, because you want to not make the privacy worse. So yeah, we actually peg in, and it worked well with the protocol, how it was set up. You peg in, and all in one transaction, it's a peg-in and then the MWEB transaction pegs out. But you don't even see the link from peg-in to peg-out, necessarily... No, actually, you do. Yeah. But you don't know, like, the inputs involved, or what the sizes were, or anything like that.
22:54Vlad CosteaYep. Hey Anon, have you heard of STARKs? Scalable Transparent Argument of Knowledge. It's a protocol that uses zero-knowledge proofs to make transactions more scalable and private. Currently, this tech exists only on Ethereum, but if Bitcoin activates OP_CAT, we're going to get STARKs too. Learn more about STARKs by listening to Season 15, Episode 36 of the Bitcoin Takeover Podcast with Eli Ben-Sasson. Also consider supporting OP_CAT. Meow. What about amounts privacy? Does MWEB hide the amounts being sent from one party to the other?
23:43David BurkettYes, it's very good at that. It's not perfect at that, because of the peg-in, peg-out mechanism. If you were purely using Mimblewimble, or the MWEB side, and you were not pegging in or pegging out, you'll have perfect amounts privacy. But there are rare cases, if you just, like, send into the MWEB and send right back out, that you can leak your amounts, or maybe have a range of them. Like, if you know only, if you know 100 litecoins is pegged in this amount, but you're only referring to that many inputs, the inputs that were pegged in your transaction, then you'll know that it's 100 or less litecoin. So there's ways that you can lose some of the amount privacy. But if you're using good practices and you're keeping your coins on the MWEB side, you'll end up with perfect amount privacy.
24:37Vlad CosteaNo, and I think it was Charlie who mentioned that it could be a good idea to CoinJoin into MWEB and then CoinJoin out of MWEB, and this would give the participants much greater privacy.
24:49David BurkettYeah, so... so when you do peg into MWEB, you do kind of CoinJoin, in a way, to do it, but... I think, yeah, it gets a little complicated about whether, like, it's giving you privacy advantage or not. But definitely the biggest thing to improve your privacy there is, like I said, keeping as much of your transacting on the MWEB side as possible. The weak link there is the peg-in, peg-out mechanism. We've got to work with the existing chain, which only deals in transparent amounts, and it doesn't have the kind of automatic CoinJoin mechanism. So the key to improving your privacy is always going to be: limit main chain use, try to keep your activity on the MWEB. But there are other things, maybe pegging in and out, where you may be able to improve.
25:50Vlad CosteaYeah. I was thinking about Wasabi Wallet's feature, that now they're adding something to pay directly from the CoinJoin. So it becomes very difficult to figure out which one of the outputs actually belongs to the sender.
26:03David BurkettYeah, yeah. And part of maybe our CoinSwap service, we could do something like that too. Like, the CoinSwap is the automatic, you know, "I have a dirty UTXO, I want you to give me a clean one that's mixed with lots of other users." Perhaps we could even build into that something, some kind of a send-to-other at the same time, which would be... similar.
26:27Vlad CosteaVery cool. Now, there's a lot of interesting research into this. Would you describe right now Litecoin to be the most liquid and most listed of all the privacy coins? Or would you say it's a privacy coin at this point?
26:40David BurkettI mean, if you came to my talk, you would know that, like, I'm very hesitant to label anything "privacy," because though it has privacy features, you're not fully private, nor are you in any coin you use. You're better off in Monero. You know, if you're using Monero for privacy, it's better off at default privacy. But there are ways you can screw that up too. There are ways that things can go bad. So like, I think that Litecoin has good privacy against many attacks, the ones that are very practical, everyday people have to worry about. Litecoin's very good at that.
27:24But that doesn't mean, you know, it's private, you can just, you know, do whatever. You still have to be... it's best to understand what its capabilities are and what its limitations are, if you want to really preserve your privacy. Yeah. But as far as the coins that have serious privacy features, yeah, Litecoin is probably the most liquid, aside from, like, Ethereum had Tornado and things like that, and, you know, it's very fuzzy whether you consider all that part of Ethereum or some other application on it. But as far as, like, core part of the protocol privacy features, Litecoin would be the most liquid of the coins, yeah.
28:12Vlad CosteaWhat is the best way to store your Bitcoin? Do you need a multisig setup? Should you buy hardware wallets? And if yes, what kind? How many backups do you need? And how should you spread them around? These are all difficult questions which deserve an individual answer for every user. Thankfully, Hodling.ch is here to help you. So if you're part of a company that wants to add BTC to its balance sheet but needs to figure out a multisig scheme, or you are a whale who needs to discover the safest long-term holding strategy, you can talk with Polto and Darko, the Swiss co-founders of Hodling. Their service makes you 100% sovereign and puts you in control. Not your keys, not your Bitcoin. Check out Hodling.ch today.
29:08Do you envision a future where you're going to have swaps between MWEB Litecoin and Monero or something?
29:17David BurkettAbsolutely. There's already efforts to do that. I don't know that we've ever had a successful swap yet, but I know that there's other... like, the Monero guys have gotten pretty good at swaps, because Monero is a little weird to swap with, but they've gotten pretty good at it. And MWEB is not as hard to swap with. It's a lot more traditional, so we know it's possible to swap that. And I do foresee that in the future. I don't know who's going to implement it. There were thoughts of maybe Cake Wallet, but I don't think Justin works with them anymore, so I don't know if they have the same kind of technical resources they used to. But I do expect at some point there will be at least one wallet that has swaps into Monero and possibly other private... and Zcash. Zcash too, yeah.
30:09Vlad CosteaThat would be very cool, because they can tap into the liquidity of Litecoin and still use the privacy benefits of their own coin.
30:18David BurkettRight, right.
30:19Vlad CosteaYeah. And as fun as it would be to have just one currency, Bitcoin as the only one that does everything, it seems very unlikely at this point.
30:29David BurkettYeah, there's a lot of technical challenges with that, and, you know, the solutions a lot of people really, you know, threw their weight behind, they're not panning out, of course. So, yeah, as far as I can tell, it's always going to be a multi-coin future. I'm hoping that people don't have to think heavily about which coin they're using or which one they're storing in. In the future that I'm hoping for, you store your coins in whatever you're comfortable in, and when you purchase, I hope we have very good, very efficient swap systems built right into the wallets we use, so you don't even have to think about it. You know, it converts it to whatever value in a decentralized and maybe not instantaneous, but relatively quick way. All seamless. That's the goal.
31:22Vlad CosteaYeah. I got to tell you at this point, and you have to know, because I'm going to place the ad at one point during our interview: LayerTwo Labs is sponsoring this. And I know that they're also trying to bring their sidechains, their drivechains, to Litecoin. And I know that you're not a big fan of that, because you don't think that general-purpose stuff should be built without a clear goal in mind. I was going to ask you, like, could you please phrase your argument?
31:49David BurkettYeah, I hate to get into the drivechains too much, because there's passionate people who want to see drivechains on there. And then, like, if I go against that, I'm going to be seen as the anti-drivechain guy. But I'm not the anti-drivechain guy. I have some concerns with the design of it. It's a little bit messy. It's one of the hackier protocols I've seen. I'm not afraid of hacky, but, like, I'm kind of surprised by, like, some... many of the weird things that are in the design for drivechains. But I could get over those, and we could find solutions there.
32:29But my concern is that, like, everybody just wants drivechains because they want drivechains. But I've seen no one saying, "Wow, this will help me do X, Y, Z. Like, I have this business idea I want to do," or whatever. It's all just "we should have drivechains," often because Bitcoin doesn't have that, and we would, you know... And, to me, you want the clear vision. Like with MWEB, the clear goal was privacy, right? Or fungibility. Improved privacy, maybe not perfect privacy, but improved privacy. There was a very clear, direct benefit to adding that feature. So that's why we worked on it.
33:10I think it's kind of wrong to find a technology and just go push it for the sake of the technology. Imagine if Charlie stuck with confidential transactions because he really wants confidential transactions. No, we wanted privacy. But he started with confidential transactions, found that, well, Mimblewimble would be even better, and moved to that. So if whatever use cases do arise in the future where people do have a need for something like drivechains, at that time then it seems to make sense to talk: is drivechain the best solution?
33:46But just going from the... finding a solution without a problem just seems like the wrong way to approach it. It seems strange to me to just, like, push drivechains without a real use case in mind. And that's why I've been hesitant to really, like, get involved with the drivechain discussion. Because I'm not anti-drivechains. I don't see anything, like, any huge red flags in there that would make me think, no, this doesn't belong in the protocol. It's just, I'm not a fan of adding things that we don't have a direct need for.
34:24Vlad CosteaI think the worst-case scenario is that they get activated and that nobody uses them.
34:30David BurkettYeah, there's, I mean, there's always risks involved with consensus. Like, even though it's been pretty well studied what can go wrong with drivechains, you never really know until it's actually on a network with actual value behind it, what kind of weird attacks could be thought of, or even just implementation issues. Like, presumably I would be implementing it, or... with someone else, and, you know, I don't have 100% faith in everything I do, so I could screw up the implementation and cause an issue.
35:01And it's just such a large, valuable network that to touch the consensus code without a clear reason, without a clear benefit from it, is an unnecessary risk. So, like, I know the claim is like the worst that could happen is, you know, we have a feature that's not used. But really the worst that could happen is we could kill our chain. Very unlikely, but there's always a risk when you're messing with consensus code. And you had the same risk with MWEB, even bigger, because it was a much larger change. But, yeah, it's just, to me, I'm personally not interested in any consensus change without a reason, without a solid reason.
35:44Vlad CosteaWell, the cypherpunk in me would love to have basically swaps from MWEB into a Zcash sidechain or something like this. Because it'll be the same currency, but with different privacy benefits.
35:55David BurkettAnd we were just talking... but is drivechain the best way to do that? Because I was just talking with another team about including Groth-like proofs and ZK proofs into an opcode, and then you could have a layer two that way, where you have, you know, you just have proofs that you have to verify on the chain. I don't know how it would work about actually moving coins back and forth. It's got different constraints than drivechains. But I think having people ready and really wanting to do these things, and a community who sees a real benefit in it, is the most important thing, not just one that wants to add the technology for the sake of experimenting. You can always experiment in lower-value coins. Not every experiment should happen on Litecoin.
36:58Vlad CosteaYeah. You have to go to a group photo. Before we end this, I got to ask: what do you think about rebranding MWEB as Virtual Private Money, which is VPM?
37:08David BurkettI mean, I'm not a marketing guy, but that's not... I don't care for the idea. It's a little confusing, a little odd. It's so similar to VPN. I don't know. But I'm not a marketing guy, so I'm going to just keep writing code and let the community adopt whatever terminology they see fits best.
37:29Vlad CosteaI just think it's weird that they're going to call it VPM, and then they send addresses that start with the prefix MWEB.
37:36David BurkettYeah, that could always be changed, but that causes another mess too. Yeah, I like MWEB. I've grown to like it over the years, so it seems odd to change it now without a good reason.
37:49Vlad CosteaThank you very much, David.
37:51David BurkettThank you.
37:52Vlad CosteaWhere can people follow your work? Very fast.
37:53David BurkettTwitter, @DavidBurkett38. I don't know, just... I, I used to post on LitecoinTalk quite a bit, but I'm very far behind on everything in life right now, so I don't do that quite as much as I did. That's probably the best thing, is just follow my Twitter. And that's it.
38:16Vlad CosteaAll right.
38:17David BurkettThanks for having me.
38:17Vlad CosteaThanks for joining.
38:18David BurkettThank you.
38:20Vlad CosteaSo I was going to mention something about privacy and the fact that you mentioned liquidity, and that you need to increase the liquidity to have a better anonymity...
38:29David BurkettYeah, it's not necessarily liquidity as much as the anonymity set. So liquidity has more to do with the ability to just buy and sell, but anonymity set is more like buying and selling, being, transacting all around you, in enough capacity that you can hide reasonably well. Because, you know, the most important part of any privacy system is the anonymity set. If you're just trying to hide by yourself, it doesn't help at all.
38:59Vlad CosteaYeah. I actually caught this.
39:01David BurkettOh, cool. Oh, cool. All right. I'll see you later.
39:04Vlad CosteaThank you. Hey you! Thank you for listening to the Bitcoin Takeover Podcast. This episode is sponsored by SideShift.ai, StarkWare, LayerTwo Labs, and Hodling.ch. Don't forget to subscribe!
39:04================================================================================ Production notes: CORRECTED. Base: the pipeline's NanoGPT Whisper-Large-V3 transcript with automatic speaker diarization, reconciled word by word against YouTube's automatic captions of the recording (read-only copies: zcash-documentary S15E59.en.vtt / S15E59.timed.txt; YT time = mp3 time + about 8 s) and the bitcoin-takeover-articles s15-e59-david-burkett.whisper(.novad).txt transcripts, with a full local faster-whisper (small.en) pass on the mp3 plus clip re-runs on doubtful stretches as a further opinion. Recorded in person at the Proof of Work Summit in Frankfurt. Re-transcribed the 5:03-7:21 Mimblewimble explanation, which the raw replaced with made-up inserts ('MWEB, a platform for investing in Bitcoin', 'The MweB Podcast is a production of the Center for Autonomous Management Services') and loops; removed other inserts ('♪ © BF-WATCH TV 2021' at 0:30, 'Like, comment, and post text' at 7:21, 'www.patreon.com/download' at 16:39, 'I'M NOT SURE IF I'M GOING TO BE ABLE TO TALK ABOUT THIS' at 27:22, 'DAVID BURKE:' labels at 37:4x) and restored dropped words (e.g. 'it will actually peg in those coins', 'people need privacy now', 'and MWEB is not as hard to swap with'). Speaker turns were rebuilt with local TitaNet speaker embeddings (voice centroids for Vlad and David), which moved several turn changes and short interjections the raw diarization had merged. Names and terms checked against the show notes and the web (Tom Elvis Jedusor, Andrew Poelstra, Marek Narozniak, Pedersen commitments, Grin++, @DavidBurkett38, LitecoinTalk). Sponsor reads (SideShift.ai, LayerTwo Labs, StarkWare, Hodling.ch) normalized to their standard wording. Remaining doubtful words are marked best guess.