Podcast Transcript

Bitcoin Staking Without Bridges: How Slashing Works

David Tse Stanford professor and Babylon co-founder (at recording)

How can Bitcoin secure another blockchain while staying on Bitcoin? In this interview, published on September 22, 2023, Stanford professor and Babylon co-founder David Tse explains why staking can avoid a bridge, why a timelock alone is not enough, and how cryptography can turn validator misconduct into a Bitcoin spending condition. He discusses slashable fractions, consensus compatibility and the distinction from lending. Launch plans, market figures and security claims reflect the recording period.

  • Published 22 Sep 2023
  • Runtime 30:36
  • Operator
  • Recorded in English
Bitcoin Staking Without Bridges: How Slashing Works: podcast episode with David Tse, Stanford professor and Babylon co-founder (at recording)
// The short version
  • At 05:01, Tse describes the security-bootstrap problem of a new proof-of-stake chain with a low-value native token. He proposes adding external Bitcoin collateral. This is an economic-security argument, not a claim that market capitalization alone determines consensus safety.
  • At 07:36, Tse explains that the staking use case can leave Bitcoin on its own chain. The consumer chain receives security rather than a freely transferable wrapped asset. At the consensus layer, the idea does not depend on EVM compatibility. The Babylon Bitcoin staking litepaper describes the remote-staking approach.
  • At 10:00, a confirmed Bitcoin timelock transaction establishes that funds are locked; it does not itself enforce good validator behavior. At 13:48, Tse describes making misconduct unlock a slashing spend. The later Bitcoin Staking research paper formalizes remote slashing and secure unbonding assumptions.
  • At 16:23, Tse illustrates two transaction outputs, one protected from slashing and another slashable. His 90/10 split is an example, not a universal Babylon setting. The tradeoff is between the holder’s loss exposure and the consumer chain’s economic protection.
  • At 26:56, Tse distinguishes slashing from lending exposure and argues that good behavior makes slashing more controllable. This is his assessment in the interview published in 2023. Delegation, implementation failure, lockups and asset-price changes still matter; bridge-free staking is not risk-free yield.

Opening highlights and David Tse’s research background

Watch this part · 0:00

Kevin 0:00 Today with David, who’s a Stanford professor and co-founder of Babylon. Bitcoin possibly enhancing the security or consensus mechanism of proof-of-stake blockchains.

David 0:14 In my earlier life, I used to do research in wireless infrastructure. Five years ago, I read Nakamoto’s white paper. Doing research in consensus protocol, blockchain consensus protocol, so that’s our specialty. The more capital, the more secure the blockchain is. Your native token is usually a low market cap.

David 0:32 One of the reasons why most of the Bitcoin sits idle is because bridging is considered a very high risk. So the simple thing that you can do on Bitcoin is you can put it in a so-called time lock deposit. It’s called a spending condition. In making this idle asset useful for the rest of the crypto economy.

David 0:51 But another important function, which is essentially triggering the interest of Bitcoin holders. That a few months ago there was a new development in the Bitcoin ecosystem called Ordinals.

1:04 Wavect, the Web3 software company that understands what you want.

Kevin 1:13 Hi everyone, welcome at Wavect. Today with David, who’s a Stanford professor and co-founder of Babylon, a blockchain using Bitcoin’s proof-of-work consensus mechanism. And today we’ll talk about a super exciting topic, and that’s Bitcoin possibly enhancing the security or consensus mechanism of proof-of-stake blockchains.

Kevin 1:39 And David wrote, I think, at least two papers about this kind of topic. And so I’m super excited to have you here. Thanks for taking the time. And starting out, I want to give you the opportunity to introduce yourself, to let us know what you’re currently working on and whatever you think is worthwhile sharing.

David 1:59 Yeah, so hey, thanks, Kevin, for having me on the program. Uh, let me just say a few words about myself. So I’ve been primarily a researcher, so I started my career as a professor at UC Berkeley. And then eight years ago, I moved to Stanford. In my earlier life, I used to do research in wireless infrastructure, focusing on making the cell phones that we have right now work.

David 2:26 It didn’t work 20 years ago, but now it’s working, so that’s great. Uh, uh, but now 20 years later, I decided to move on to do other things. And so five years ago, I read Nakamoto’s white paper on Bitcoin, and I find it a very fascinating topic from a research point of view. And so I start assembling a research group at Stanford.

David 2:46 We have now seven students and postdocs, postdoctoral researchers at Stanford University doing research in consensus protocol, blockchain consensus protocol. So that’s our specialty. And over the years we’ve collaborated with industry groups as well. For example, we collaborated with Ethereum Foundation on improving the proof-of-stake Ethereum protocol before the Merge.

David 3:09 And so about a year and a half ago, we came with this idea of, hey, actually there’s a lot of advantages combining Bitcoin security with a proof-of-stake blockchain. So that’s where the project Babylon come from. It’s a startup we started about a year and a half ago.

Kevin 3:27 Awesome, sounds exciting. Well, I obviously did some research on your project, right? And from my understanding, you will launch your mainnet next year or in the early next year, [unclear].

Why use a non-native asset for proof-of-stake security?

Watch this part · 3:28

David 3:40 Yeah, we’re shooting for launching, uh, around the, uh, next halving.

Kevin 3:45 Okay, next Bitcoin halving. Exciting. Great timing. Well, um, based on that, right, um, the main issue, just to summarize for the less technical people here, and please, David, correct me if I’m wrong from your point of view. Well, most proof-of-stake blockchains, if they launch, uh, usually have the issue to meet that, let’s say, necessary threshold of staked native assets to actually provide a good, let’s say, or a decent security based on its consensus mechanism.

Kevin 4:22 And your papers, especially the last or the newest one, which I think has been released this month, right, it focuses on actually making non-native assets like Bitcoin, for example, part of this consensus mechanism, right? How, or let’s say, let’s go from the personal standpoint first. How did you came up with this?

Kevin 4:48 Because that’s quite out of the box. Like, what triggered that thought that you thought this is something that’s feasible, doable and actually makes sense?

David 5:00 Yeah, so just to start a little background, so proof of stake protocol, as you mentioned, is secured by capital. The more capital, the more secure the blockchain is. So the, uh, traditionally proof of stake protocol has always been focused on launching a native token and then use that native token to secure the blockchain.

David 5:25 Now, however, there are some issues here, especially when you start a new blockchain. Your native token is usually a low market cap, so low market cap means low security. And so to improve the security, you have to offer a very high inflation, typically, of the currency in order to attract people to invest in your blockchain and increase the market cap, increase the amount of value staked.

David 5:49 And so this is causing a lot of problems for many new blockchains because new blockchains wants to focus on developing the application. They don’t wanna spend all this inflation on security, which is a means, but not really the ends of a blockchain. And so our idea is that, if instead of in addition to your native token, you can pull in a much, much larger and in some sense more stable asset like Bitcoin to stake on, to validate and secure your blockchain.

David 6:19 That would be a double win situation because from the point of view of the blockchain, the proof of stake blockchain, now it has a much more stable capital to land on and potentially cheaper because it’s such a large supply. And two is from a point of view of the Bitcoin holders. Right now, most Bitcoin holders are earning almost zero yield on their Bitcoin.

David 6:42 They’re just holding it. Now it is an opportunity for them to earn some upside by investing in a proof-of-stake blockchain and earning upside on the reward from that blockchain. So we think it’s a double win situation.

Kevin 6:54 Uh, well, I have to be honest, the first thing that I thought when reading your, or skimming your paper, was like, how is that supposed to work in a way that you don’t, as, that you are not subject to the same security issues that bridges face, for example, or any cross-chain protocols, especially since Bitcoin is non-EVM compatible and a lot of proof-of-stake blockchains, for example, are EVM chains, EVM networks.

How can Bitcoin staking avoid a bridge?

Watch this part · 6:56

Kevin 7:29 So we’d love to know what you approach, maybe on a superficial or also in-depth level.

David 7:37 Sure, yeah. Let me try to deconstruct your question into multiple aspects. So first, uh, you’re correct. One of the reasons why most of the Bitcoin sits idle is because bridging is considered a very high risk operation for Bitcoin holders, and they don’t want to bridge the Bitcoin from the Bitcoin chain.

David 7:57 And that’s why, since most of the DeFi activities are happening on elsewhere, not on the Bitcoin chain, there’s very little way for Bitcoin holders to earn yield. So, uh, so our design is really, we, we basically figure out that to achieve this particular use case of staking, there is no need actually to bridge the Bitcoin.

David 8:21 So you can think of bridging the Bitcoin allows you to do anything you want on the other chain, but you’re subject to bridging risk. What we’re saying here is that if you focus on a very specific use case, but a very important use case of providing security to the proof of stake chain, then the technology that we develop says that actually bridging is not needed.

David 8:44 Okay. So that’s number one part to your question. The second part about EVM or not EVM compatible, actually because our security is happening at the consensus level. Okay. So this is one level below the EVM, and so it doesn’t matter actually whether the chain is EVM or non-EVM. Our technology still works.

Kevin 9:12 And how does it actually work, right? Because I can imagine that you have, for example, uh, uh, a simple, probably not so simple, uh, Bitcoin, uh, smart contract, if you call it that way, right, where you basically stake your Bitcoins, and the destination chain, or not destination chain, but the proof of stake chain then somewhat maybe gets a validity proof or something like that.

What does a Bitcoin timelock prove?

Watch this part · 9:13

Kevin 9:39 I don’t know, it’s just an assumption on my end, that testifies, well, Bitcoins have been staked and you get your rewards on that proof of stake chain. That would be my first thought. Would you mind correcting me to your solution? That would be awesome.

David 9:59 Yeah, so I think what you say is at the high level quite correct. Okay, but let me elaborate a little bit more. Let me elaborate a little bit more. So when you put, first of all, there’s no smart contract on Bitcoin. There’s no smart contract on Bitcoin. In other words, you can’t write an arbitrarily complex contract.

David 10:16 Okay? However, however, there are something simple that you can do on Bitcoin. And essentially, our technology is to use what is simple on Bitcoin and still achieve our purpose. And that’s really the challenge of the technology. So the simple thing that you can do on Bitcoin is you can put it in a so-called time lock deposit, a time lock deposit.

David 10:39 There is a, uh, ability on the Bitcoin script that Nakamoto came up with that enables you to put it on a time lock, say, time lock it for six months. Okay? So you can do that. Now, once you put it on a time lock, what does that mean? That means you have entered a particular transaction on the Bitcoin chain.

David 10:58 The transaction says, okay, this one Bitcoin is now put in a time lock for six months. Okay. Now everybody in the world, including the proof of stake chain, can actually see this transaction on the Bitcoin chain. It’s confirmed on the Bitcoin chain. So this is the validity proof that you actually mentioned.

David 11:20 It is not any, it doesn’t require any fancy technology like ZK proof or that kind of thing. But it’s just a transaction entered into the Bitcoin chain, confirmed, and everybody can see. So at this point, the proof of stake chain knows that, oh, okay, this guy has locked up his one Bitcoin to secure my chain.

David 11:41 Okay. However, what is the key challenge, though, is that, uh, staking has a very, very important aspect to it, which is called slashing. It’s like, you know, you go to an Airbnb, right? You need to put down some deposit to guarantee that you won’t trash the Airbnb upon departure. So after you put the deposit and you behave properly and you leave, then you can get deposit back.

David 12:11 So that deposit is very important to ensure good behavior. And the similar thing here is that if you stake the one Bitcoin on a particular proof of stake chain, the proof of stake chain has to be sure that your behavior is guaranteed to be good, you won’t trash the chain. And the way to do that is the proof of stake chain needs to have an ability to be able to slash or take away this one Bitcoin or fraction of this one Bitcoin upon bad behavior, so that no bad behavior can be, can happen.

David 12:48 So that is actually the challenge of the whole problem, how to do slashing.

Kevin 12:53 And the communication between those networks basically happens through Cosmos' Inter-Blockchain Communication protocol, right? Because, uh...

Does remote slashing require IBC or a smart-contract VM?

Watch this part · 12:54

13:02 Oh, no. No.

David 13:04 Yeah, so, so yeah, so okay, so Cosmos is certainly one ecosystem that we have collaborated with a lot, but our technology actually works in general. The communication is actually, all it needs is to send transactions onto the Bitcoin chain. So we don’t need a very complicated communication protocol.

Kevin 13:28 But okay, I, the good thing is the funds will be slashed on Bitcoin and so on, obviously, right? Everything happens there. But yes, how does bit, the Bitcoin chain determine, know that, right?

David 13:46 Yeah, exactly, exactly, exactly. So the Bitcoin chain is not very smart. So the Bitcoin chain can’t look at the proof of stake chain and then try to figure out what’s happening over there. Okay. So instead, our design is the other way around, is that if something bad happened on the proof of stake chain, okay, we want to be able to enable anybody actually to go and send a transaction to the Bitcoin chain to slash the funds.

David 14:20 So, uh, your audience may have heard of a concept called fraud proof. For example, this rollup technology called Arbitrum. They use fraud proof, right? Fraud proof basically means that, hey, something bad happens. Misbehavior happens on the rollup. Then it is used to send back to the main chain, in this case, Ethereum, to tell Ethereum to, you know, slash the fund or revert the transaction, etc.

David 14:49 So the design here is somewhat similar. We allow the proof of stake relayer, relayer, to see bad behavior and then send a fraud-proof-like thing back to the Bitcoin chain. However, there’s a huge difference between Bitcoin and Ethereum, is that Bitcoin has a smart contract that enables it to process the fraud proof and understand the fraud proof.

David 15:19 Bitcoin has no smart contract. And so Bitcoin doesn’t understand anything except for one thing. The only thing that Bitcoin knows how to do is to spend the Bitcoin. It’s called a spending condition. Okay, so basically we have to design our fraud proof system using cryptography in such a way that all Bitcoin needs to do is to take the message and say, oh, this is a spending message, and I will slash it based on this spending message.

Can only part of a Bitcoin stake be slashable?

Watch this part · 15:54

Kevin 15:54 Okay, okay. Uh, that basically answers my next question, because I just read that you’re actually revealing the private key, and I just thought, well, how is that supposed to work, right? You won’t just slash the full thing. But if you have like 10 Bitcoins staked, you won’t, hopefully, oh, slash 10 Bitcoins, uh, just because of one misbehavior.

Kevin 16:18 Um, so that explains that part, right? And yeah.

David 16:25 So, yeah, so about, about slashing a 10 Bitcoin, right? So this is, slashing a 10 Bitcoin would be the extreme point of the design. It would be a very, very strong security to the proof of stake chain, but it would be rather scary, potentially, for the Bitcoin holder. So in any design, you’re always trading off between the staker’s peace of mind and the proof of stake chain security.

David 16:56 So the way this can be done is actually quite simple, is that you can actually design your contract on a Bitcoin [unclear] in such a way that, for example, you spend, you put 90% of the money in a time lock, and 10% of money, only 10% of that can be slashed. So this is possible because you can actually specify two outputs on a Bitcoin transaction.

David 17:22 One output goes to 90%, always locked, and only can be withdrawn but cannot be slashed. 10% is also time locked but can be slashed. So that is completely possible.

Kevin 17:36 And are these parameters, like this ratio, something that these proof of stake chains can choose themselves, or the community?

David 17:44 Yeah, okay, correct. It’s pretty cool, because that particular contract is signed between the staker and the proof of stake chain that it wants to stake to validate. So different proof of stake chains may have different parameters. Some may prefer 10% slashing. Some may prefer 5% slashing. Some may prefer 50% slashing.

David 18:07 In the current-day chains, for example, Ethereum is pretty high, it’s around 50%. Cosmos chains that you just mentioned, it’s lower, it’s about 5%. So different chains have different parameters.

Kevin 18:18 Um, when I hear all this, um, well, research is usually very challenging, especially in the cryptography area, right? And what I’m wondering is, what was, in your opinion, the most challenging aspect coming up with that? Like, where did you have, have you been stuck at all?

Combining consensus research, cryptography and Bitcoin Script

Watch this part · 18:20

Kevin 18:46 Or what was the point where you were like, okay, that, that’s difficult?

David 18:51 Yeah, so the biggest challenge is really the following. Okay. Um, fraud. There are many types of frauds, right? Bitcoin is dumb, it cannot interpret anything. So now, to be able to convert sort of many types of fraud into something simple that Bitcoin can interpret, which is basically spending the transaction through this private key release mechanism, is the biggest challenge.

David 19:26 And to achieve this, we bring on sort of two sets of expertise to solve this problem. One is our expertise in consensus protocol design. Because in consensus protocol design, we understand what are the bad actions that a protocol participant, a validator, can achieve. And through this understanding, we’ve redesigned the consensus protocol in such a way that all the bad action can be converted into this simple event.

David 20:01 Second, we layer on top of that a special cryptographic scheme, which upon this simple bad event can force the release of the private key. So combining these two set of expertise, which is actually quite interesting, because, you know, in the world of researchers, actually, on blockchain, there are researchers who knows a lot about cryptography.

David 20:28 And there are researchers who knows a lot about consensus protocol. But typically, these two sets, they don’t overlap a whole lot. And so we kind of collaborate with different partners to try to get these two together. Plus, we also need some pretty deep understanding of the Bitcoin script to get this whole thing to work.

David 20:50 So I would say that, in some sense, if you think about our research, not to elevate ourselves, but just as an analogy, is that this kind of research is a bit of the same flavor as Nakamoto’s white paper. Because when he designed Bitcoin, actually he needs to combine many different expertise from many different areas to be able to solve this really hard problem.

David 21:14 So he combined this idea of proof of work. He combined this idea of cryptography, public key cryptography. He combined this idea of incentive from game theory, and he combined some ideas from control theory in terms of tuning the difficulty of the proof of work chain to solve all these problems. So I think our work is of that flavor.

David 21:36 And that’s pretty exciting.

Why Bitcoin rather than another chain’s asset?

Watch this part · 21:38

Kevin 21:39 Yeah. Um, well, you started with integrating Bitcoin liquidity, basically, right? I’m wondering, uh, well, I understand why from a consensus perspective, and I, I do a lot, I don’t [unclear] what’s going on today, right? But from a mindset perspective, it definitely makes sense. But why, or what’s your perspective on having these non-native assets from other, uh, non-native, other proof-of-stake blockchains?

Kevin 22:19 For example, if you launch your own new proof-of-stake network, you could use the liquidity from Ethereum, you could use the liquidity from Solana, which is definitely more difficult [unclear], and these kind of things, because they offer a more complex tool set, toolkit to actually achieve that mission in an easy way.

Kevin 22:44 Is that something that you plan to do? Are you, do you want to stick to Bitcoin as a source of liquidity in that sense?

David 22:53 Ah, okay, I got your question. Um, yeah, so this general idea that you mentioned of using a foreign asset, right, to secure a proof of stake chain is actually quite general. It doesn’t have to be Bitcoin. It could be another proof of stake chain even, right?

David 23:19 So, um, I agree with you. Now, to us, though, the most, uh, important reason why we are focused on Bitcoin as the source of security or the source of the asset is multiple folds. One is that proof, Bitcoin is by far, by far the largest asset in the world, crypto asset in the world, 600 billion.

David 23:49 It’s about two to three times as big as Ethereum and many, many times as big as Solana. So it’s just a huge source of capital. And what is more interesting is that although this is the largest crypto asset in the crypto ecosystem, it is also the most idle asset, is the most idle asset.

David 24:14 It’s mainly a store of value, and it’s not used to improve or facilitate the economy, the crypto economy. So we view our technology as one important step, one important step in utilizing this idle asset, in making this idle asset useful for the rest of the crypto economy.

David 24:40 Now, the very good use case here is because our staking protocol is a trustless staking protocol. So it has the highest possible security, and it could be a very good first step for the Bitcoin holders to venture out into the non-Bitcoin world because it is very secure.

David 25:07 Now, once you start venturing out and you start earning other coins yield, then a second step could be that, hey, you can now do, maybe do other things which may not be as secure, but now you’re more willing to do other things. So we view our protocol on the one hand as providing an important function of providing security, but another important function, which is essentially triggering the interest of Bitcoin holders in participating in the economy in a broader sense.

David 25:41 So maybe one can draw an analogy. Your audience is probably aware that a few months ago, there was a new development in the Bitcoin ecosystem called Ordinals. Ordinals is NFT, basically, for Bitcoin. And Ordinals, I think, is a very good example of this kind of work. That is, is a particular use case of Bitcoin that triggers people’s interest, renew interest in Bitcoin more broadly than just a store of value.

David 26:13 So we view our project as of similar flavor by focusing on security.

How does staking risk differ from lending risk?

Watch this part · 26:20

Kevin 26:20 Okay. Well, just thinking about that research [unclear], we see the same issue with almost every crypto protocol on the application layer as well. It doesn’t need to be the consensus layer. If we think about lending protocols, which you have compared in your blog article as well, for example, that’s a potential business or use case for that research too.

Kevin 26:47 Or what’s your take on that part? Or do you think it’s more applicable on the consensus layer only?

David 26:56 Yeah. So, uh, one reason why we’re focusing on the consensus layer is because staking has a very interesting distinction from lending, for example. So staking, the so-called risk you take is basically the slashing risk. And this slashing risk is a fully self-controllable risk in the sense that you go to an Airbnb, if you behave nicely, you don’t expect your deposit to be removed from you.

David 27:26 So this is fully under your control. On the other hand, if you do lending, for example, then you’re subjected to market conditions. You’re subject to market conditions. So I think slashing among all the crypto investment or crypto DeFi activities is kind of the lowest, most controllable risk. And so we felt that starting from this one would be a good thing for Bitcoin holders.

Web3 research surprises and the next guest’s question

Watch this part · 27:53

Kevin 27:53 Yeah, absolutely makes sense. I just was curious on my end, right? Um, okay, well, I have, or we have a tradition introduced since our last podcast, and that’s the previous guest always asks a question to the next guest without knowing who the next guest will be. So, and the question would be, what is the most interesting thing you found out that exists in Web3 that really surprised you?

David 28:25 Yeah. Um, so I’ve been working in the Web3 space for the past five years. So I think my answer, since the question does not know who he or she is, was asking, so I’ll answer this question from a researcher point of view, from a researcher point of view. So from a researcher point of view, I find the most fascinating about the Web3 space is that there’s a collection of really smart people working in this space from a research point of view.

David 28:57 And the people are very broad. And also they come from all directions. And they’re all just extremely brilliant. And I really enjoy working with these people. And they’re not only academics, but mainly also from industry, founders. For example, I collaborate with a lot of founders from the Cosmos ecosystems that you mentioned briefly, and they’re all just amazingly strong researchers as well as entrepreneurs.

David 29:24 So that is one thing I find it very impressive after spending a few years in the crypto space.

Kevin 29:33 Awesome. Well, in that case, do you have a question for the next guest as well?

David 29:40 Yes, my question for the next guest is, what do you think is the iPhone moment for Web3? When is it coming, and what form will it come in?

Kevin 29:54 That’s a brilliant question. Okay, awesome. Yeah, uh, in that sense, I would say thanks, David, for taking the time talking with me today. Is there anything left you want to share? I definitely will put all your links, um, into the video description and so on. And yeah, I hope you enjoyed the episode as much as I did.

Kevin 30:17 Same for the, uh, audience. And yeah, thank you for watching.

David 30:22 Yeah, it’s great to be here. So thanks for the very enjoyable conversation.

30:29 Wavect, the Web3 software company that understands what you want.

Transcribed from the original audio with Whisper large-v3 and AI-reconciled with the original automatic captions. Unclear speech is bracketed; speaker labels and translations are editorial aids. No complete human listening pass. The recording remains authoritative; statements reflect its date. This interview was published on September 22, 2023. Launch plans, market figures, illustrative slashing percentages and opinions about risk reflect the conversation’s context, not current protocol parameters or investment guidance. Bitcoin Script supports spending conditions; references to no smart contracts concern arbitrary Ethereum-style execution. In the fraud-proof comparison, Tse says Bitcoin has a smart contract that can process fraud proofs; the comparison appears to refer to Ethereum. The transcript preserves the spoken wording. Avoiding a bridge does not eliminate validator, implementation, lockup or market risk.

Questions this episode answers

In the design David Tse describes, yes. BTC is locked under spending conditions on Bitcoin while another proof-of-stake chain uses the stake for security. At 07:36 he distinguishes this narrow use case from bridging an asset for arbitrary activity on another chain. Bitcoin itself continues to use proof of work. No bridge does not mean no protocol or staking risk.
Tse describes designing consensus rules and cryptography so detectable misconduct reveals the signing material needed for a slashing transaction. Bitcoin checks the resulting spending conditions instead of interpreting the other chain’s entire execution history. This is a high-level explanation, not a claim that every fraud type can be punished without protocol-specific rules. The later remote-staking paper details the formal construction and assumptions.
No. A confirmed lock transaction shows funds are committed for a period, but the chain also needs enforceable consequences for relevant misconduct. At 10:00 Tse introduces the timelock; he then identifies slashing as the hard part. Withdrawal and unbonding rules must preserve the opportunity to penalize faults before collateral escapes.
Tse says the security mechanism operates at consensus level, below the EVM. He describes Cosmos as one ecosystem they have collaborated with, while explaining that the technology works in general: communication only requires sending transactions to Bitcoin, without a complicated communication protocol. This does not mean an arbitrary blockchain is already integrated or compatible without adaptation of its consensus and verification rules.
No. At 16:23 Tse gives an illustrative 90/10 split across two outputs, followed by other example ratios. Actual slashable fractions depend on the protocol and deployed parameters. The interview’s Ethereum and Cosmos percentage remarks are historical speaker examples, not a current parameter reference or a guarantee of maximum loss.
The interview distinguishes securing consensus from lending to borrowers, but does not establish a universal ranking of safety. Tse argues at 26:56 that slashing is more behavior-dependent than lending exposure. Delegated validator behavior, protocol implementation, withdrawal restrictions and market risk can still affect holders. The conversation is a historical technical interview, not a current yield offer or investment recommendation.

Want this kind of thinking applied to your product?

We build MVPs and act as fractional CTOs for founders who’d rather ship than talk.