Welcome to the LRT episode, covering the entire playing field of liquid restaking projects and what makes each one unique and special.
On the show we have representatives from Ion, Ether.fi, Puffer, Kelp, Swell and Renzo making this your one stop to go from zero to expert on the restaking landscape.
------ 🏹 USE PODCAST24 FOR 10% OFF https://bankless.cc/Citizen2024 ------ BANKLESS SPONSOR TOOLS:
🐙KRAKEN | MOST-TRUSTED CRYPTO EXCHANGE https://k.xyz/bankless-pod-q2
🔗CELO | CEL2 COMING SOON https://bankless.cc/Celo
🗣️TOKU | CRYPTO EMPLOYMENT SOLUTION https://bankless.cc/toku
🛞MANTLE | MODULAR LAYER 2 NETWORK https://bankless.cc/Mantle
💸 CRYPTO TAX CALCULATOR | USE CODE BANK30 https://bankless.cc/CTC
⚖️ARBITRUM | SCALING ETHEREUM https://bankless.cc/Arbitrum
------ TIMESTAMPS
00:00:00 Intro 00:02:45 Ion Protocol 00:17:06 Before You Listen 00:26:45 Ether.fi 00:37:46 Puffer 00:54:02 Kelp 01:10:26 Swell 01:21:40 Renzo
------ RESOURCES
Ion: https://ionprotocol.io/ Chunda: https://twitter.com/ChundaMcCain
Ether.fi: https://twitter.com/ether_fi Mike: https://twitter.com/MikeSilagadze
Puffer: https://twitter.com/puffer_finance
Kelp: https://twitter.com/KelpDAO Amit: https://twitter.com/GAmitej
Swell: https://twitter.com/swellnetworkio Daniel: https://twitter.com/daniel_swell_
Renzo: https://twitter.com/RenzoProtocol
------ Not financial or tax advice. See our investment disclosures here: https://www.bankless.com/disclosures
No summary for this episode yet.
Bankless Nation, welcome to the LRT episode. Today, we have a different kind of podcast than what you would normally expect out of the Bankless podcast feed. Today, we are talking with six different teams at different times, not all at once, all in the LRT space. Five different LRT teams, and then Chunda McCain from Ion Protocol, who can give us a little bit more of a meta perspective as to how to view the entire LRT landscape. I'm making this episode because there are so many questions that we have about the restaking and LRT ecosystem. It is developing at a mile a minute and the number of questions that we have are growing faster than the answers that I think we have for them.
And so I'm hoping to help answer some of those questions that we have in the LRT space. What are the risks of LRTs? What are the different strategies of LRTs? What are the different directions that different LRTs are going in? I've always thought that the LRT game is won by maximizing exposure and minimizing risk and each one of the LRT teams that you're going to hear from in the episode has different strategies of getting that done and different priorities, different orders of operations. In this episode, you're gonna hear from Etherfy, Puffer, Kelp, Swell, and Renzo in that order, all about their different LRT strategies, what they are doing and what their roadmap is.
Some of them have explicitly teased their token generation event, but all of them will have a token, I bet. I'm guessing there's a prediction in the year 2024, probably in the first half. But diving headfirst into the LRTs might be kind of a lot. So first, we're going to talk to Chunda from Ion Protocol. And Ion Protocol is an aggregator of LRTs. Kind of like, it's kind of like a compound. So LRT and LSTs go in one side, and then vanilla ether goes out on the other side. Where all of the different LRTs are producing different flavors of ETH, Ion uses a compound-style market maker application to re-aggregate and re-homogenize all of the ETH that comes out of Eigenlayer so we can more efficiently use capital in DeFi.
And because of this position that Ion Protocol has in the space, they have to be extra cautious and extra informed about all the different choices that LRTs are making. So that is why Chunda comes first in this interview. He is going to provide a framework for understanding how to evaluate LRTs at a meta level. And then we will go into the individual LRT projects. Every single interview is 15 minutes or less. I think the Chunda interview is maybe 18 minutes, but this is meant to really give you broad exposure to the entire LRT landscape and kind of download you very quickly about all the different players here so that we can all be informed about what's coming inside of the EigenLayer ecosystem.
So let's start with our interview with Chunda from Ion Protocol first, and then we will get into the LRTs after that. We got Chunda McCain of Ion Protocol. Chunda, welcome to the show. Thank you for having me, Devin. It's a pleasure to be here. I want to peek into your brain about how you think about the LRT ecosystem. Before we do that, I think we need to explain to listeners what Ion Protocol is and what vantage point it provides for viewing all of the different LRTs. Because you're kind of at the meta level, you're at the bird's eye view, satellite level view of the whole LRT landscape. Maybe you could explain a little bit about Ion Protocol and what it does and how it informs your thinking about the LRT space.
Yeah, 100%. So I guess I'm gonna give a little bit of context about myself and kind of how the idea of ION kind of came about, because I think I'll provide a good kind of foundational starting point to kind of understand a little bit more on how we're approaching the problems of addressing LRT risk, and specifically, how do we want to approach financial underwriting of LRT risk. So a little bit about myself, been in the crypto space, I'd say I first learned about it back in 2015, but really got into in the birth of DeFi 1718 era, and just started writing white papers on like peer to peer lending market design, and then starting doing research on AI based credit risk analysis frameworks, not for DeFi, but actually for in the more traffic context, thinking about how we can actually build systems for people who don't have access to like FICO scores or extensive credit history, and trying to get build an approach from more like heuristic data to say like okay how can we assure that these un and underbanked people in america gain access to the traditional financials that other people have and so you know thinking about those types of things in crypto uh kind of emerging like defy emerging onto the scene at around the same time really set the stage for me to like it just immediately clicked and so for me um i spent you know kind of the next i guess until now seven years um kind of getting engaged in the space working from you know being a software engineer like a smart contract engineer at like a neo bank building out crypto infrastructure there uh so working at defy startups to even spending a little bit of time adventure um and it was actually my time adventure i was working on the blockchain capital team back when we were looking at the eigen layer deal i think this was late 2022 um that i first i got my first glance into what eigen layer was as a concept And it just, I mean, it was one of those, like, I'd say it's probably like the second most important light bulb moment of my time in crypto, because the idea of extending the core concept of crypto economic security of Ether as an asset, which is basically the whole proposition why we all use ETH as kind of the current status quo settlement layer in the crypto ecosystem, extending that kind of power that Ethereum had to other networks and other services just immediately made sense.
And I realized there was kind of a big problem that existed within this context in DeFi in particular, which is that we don't really have primitives that internalize all this infrastructure risk that exists in restaking platforms. This idea that instead of underwriting traditional financial leverage or these terms that we're more familiar with in DeFi, I think you guys kind of mentioned this recently, there is no inherent leverage in restaking. The risk that you're taking on effectively is like, there's a bit of game theoretical risk about like node operator activity. There's a bit of infrastructure-based risk about like ABS setups and consensus network setups.
And then you also have a bit of risk around like the balancing the principal agent problem and like decentralization from node operator to network perspective, right? And so for us, we were like, all right, in order to tackle this problem, we need to first ask the questions of like, what is needed in the restaking space? And then like, all right, how do we build this infrastructure? So in terms of what was needed, where Ion effectively is a lending platform meant to underwrite all of these different types of risks to allow people to financialize their restaking positions as well as staking positions without having to kind of depend on the traditional means of financial underwriting that exists with like, you know, counterparty AMM liquidity and really deep like DEX liquidity and also all these like price oracles and kind of taking a step away from that infrastructure and thinking about, all right, what are the specific things about that?
this market that are important for us to address. That was a super useful explanation. I think one of the very interesting things about Eigenlayer and liquid restaking tokens is that at first glance, everyone sees Eigenlayer and they see the concept of you take your ETH, you stake it, and then you stake it again, and then again, and then again. And then everyone is like, oh, but that's like, we're like stacking risk on risk on risk, which is true. And so like then people's like heckles start to like rise up a little bit about just like, okay, what are the risks of eigenlayer? It's a very natural response.
And then like you layer on LRTs on top of that and LRTs are all playing the same game of like managing that risk. And then there's your game, which is managing the net aggregate of all the LRT risks. And so it's this simultaneous like yield seeking, risk seeking, inherent nature about Eigenlayer matched with like, OK, but like let's contain all of the risks, too, because ultimately at the end of the day, Eigenlayer, like you said, is going to reach out to far beyond the horizons of crypto, leveraging crypto economic security, providing new products to like TradFi, to the SaaS model, to like San Francisco, Silicon Valley.
And so it actually measuring and containing risk is really, really important. So like it's this kind of like two-faced nature of like restaking, which is like more risk, more yield, more upside, but we're going to manage it all. And that's kind of how like that's why I think this space is so interesting. And your perspective is not just like a user. We have a lot of users listening to this episode who are trying to get their just get educated about their risks of LRTs. You are coming from a protocol perspective because you are building a protocol. And so you have to think about it a little bit differently.
Can you illustrate some of the inputs that go into the risk assessment? Like what are the different things that Ion Protocol assesses when it does its underwriting of the LRTs? Like what are the inputs that are actually being evaluated? Yeah, that's a really good question. I think a good thing to remind everyone as well is this concept that LRTs, at first, before they're ever LRTs, they're LSTs. a lot of anyone that supports native staking, you're building an LST protocol first, and then you're building an LRT on top of that, right? So our first approach is to actually tackle that and say like, all right, we need to evaluate all of these different providers.
I call them providers because effectively they act in a very similar kind of function. And we need to assess, All right. Specifically, how do you look as a provider first? Because that's your core. That's the core dependency that exists right now, especially without IconLayer being live. We need to answer a question and make sure that everyone in from a provider infrastructure standpoint is being safe. So for for those things we look at, we take into account node operator setups. The idea of kind of two things. One, it's like a technical implementation standpoint. point um are you requiring bonds who has access to the node operator keys uh is it the user is it um the underlying node operator that's all the control who decides what node operators get included is it permissioned permissionless how exactly are you choosing these node operators who are these node operators are they Docs are they undocked all these questions that you would traditionally ask a liquid staking provider context um we're also asking for these lrts So that's the system-wide kind of perspective.
You also have technical implementation details that are important as well. How much are you using DVT? Are you using DVT at all? Do you plan on integrating TEs to abstract away key ownership? What's your client diversity looking like, right? All of these kind of more infrastructure-based questions are also things that we're looking at internally when it comes to assessing these various different providers on the staking level. Now, after the staking level, then the approach is, okay, you kind of have to balance two things when it comes to AVS delegation, which creates this actually interesting thing, which I think we wrote a bit of a paper on it with some folks.
I'm sure we can link that later, but what we call it is the efficient frontier of restaking risk, where even if you're delegating capital to what we seem as the most safe AVSs, you still end up centralizing your risk vectors. And so there's actually this interesting balance that you have to take where you want to decentralize your delegation, your internal delegation to multiple AVSs, thereby technically earning more yield, but also finding that balance where you don't over allocate to AVSs that take on additional risk. And so this idea of like creating silos of where you're allocating and delegating risk and diversifying that risk across multiple different ABS delegations is something that we're considering a lot.
And the one big thing right now, and this goes a little bit more on kind of like infrastructure based underwriting, is this idea of like, how common is this type of consensus model? Proof of stake and BFT-based consensus protocols have existed for a long time. We understand their risks really well. And as we've seen throughout the history of Ethereum, we can mitigate those risks pretty decently well so far. But one of the big concerns is when we start innovating on novel consensus models, even DA-based consensus models have some interesting things that make things like anti-slashers unviable for DA, which is an interesting kind of constraint there.
then we kind of start ending up walking into uncharted territory where we're not exactly sure what black swan events look like in these situations, what can cause them, and even what does the status quo of that network look like. And so for us, I think we're going to be heavily indexing. And I think users should also think about heavily indexing on what kind of consensus models and what kind of underlying infrastructure people building that we're already used to underwriting. And we're already used to kind of assessing within the context of the theorem and the consensus protocols that exist today.
One of the roles that Ion Protocol will do is it'll have an algorithm, I'm assuming, to actually like judge parameters, just to make it super clear. ion protocol, like compound, but LRTs go in one side and just normal ETH goes out the other. Or LSTs. Or LSTs on, yes, right. Yeah. Any sort of ETH derivative on one side, and that's bait with a protocol underneath, and then vanilla ETH on the outside. Which means that you need to have an algorithm to produce parameters, risk parameters about the collateral assets this will of course ingest some of the inputs that i asked you about earlier but like also how do you even design the algorithm because where do you get the data to even make waiting decisions right like we've never done this before you're doing it first how the hell are you doing it what do you know like how do you actually like build this thing yeah that's a very good question and it actually goes to the thing like the two things that concern me the most with eigen layer like holistically right the two things that concern me the most about eigen layer it has nothing to has nothing actually to do with eigen layer the product but instead on how we are able to observe the product those two things are opacity on data basically the limitations on being able to see access and view data uh in real time when it comes to all of these networks and And then two is like the ability to then ingest and analyze that data.
I feel like that is kind of a sector of restaking where we haven't really seen too many announcements of people building infrastructure, like scalable infrastructure around that. And that infrastructure is going to be crucial to informing users on how to actually participate in this ecosystem. And that's hopefully one of the things that we want to be one of the pioneers in is we built out right now, we built out a ZKML-based framework that ingests Ethereum consensus data. We use a variety of different data sources, some kind of centralized data provider APIs, some utilizing, building our in-house solution that draws like beacon chain data directly.
Eventually, we're going to be incorporating inputs via ZK state proofs to further decentralize and make our inputs more trustless. And we built this ZKML framework or zero-notice machine learning framework that allows us to analyze what we see as like common potential risk vectors in Ethereum's network in order to be able to kind of not necessarily mitigate, but have a better understanding of what kind of volatility could exist on a fixed time basis for slashing on Ethereum. The extension of that is now that we've built out the system for Ethereum, and like I mentioned before, most consensus protocols are going to fit within this kind of like BFT-based consensus model.
We plan on extending this kind of framework and, of course, testing it before we really allow robust capital efficiency for a lot of these ABSs. but testing this framework with other networks as well and benchmarking it based off the initial results we get from Ethereum to be able to see whether we can actually kind of scale these robust data frameworks across AVSs. And ideally, hopefully, we can eventually open source these frameworks and allow other people to build their own kind of unique frameworks to assess these different networks as well. So, Chunta, during the middle of this interview that we're doing right now, I have decided to instead of having this interview be at the very end, I'm going to put it at the very beginning because I think it provides a framework for listeners to have as they enter these five different LRT projects.
You've actually listened to every single one of these. We gave you the material ahead of time so you could review. What do you think listeners should know or what framework should they understand? What do they need to think about as they are listening to these different LRT projects talk about their own strategy? What would you want to have known going into this the first time around? Yeah, so there's a couple of things that I think is really important for every user to kind of ask themselves. These are the few questions that we always want people to ask themselves. I mean, I actually split them up into two verbals.
It's really easy for you to create this kind of like internal checklist to go and say, okay, I'm going to check off each one of these boxes and see which LRT or restaking solution or what have you has each one of these things. So the first one we've been chatting a little bit before about is operators, and specifically operator setups and operator risk. The operators are the lifeblood of Eigenlayer. They're the lifeblood of staking. They're the ones who are running the hardware instances or AWS instances, depending on the person. that make all of these networks run, right? And so within the operator framework, you should be asking yourself, who are these operators?
How are they selected? How much control do they have over the capital? Do you, as the user who holds the asset, are you permissionlessly able to kind of retrieve your capital from these operators? Or do the operators control those keys? Well, which is it, right? Asking about operator decentralization, How many operators exist? Is there a network of them, right? And then finally, asking yourself, is there a roadmap to permissionlessness with operator inclusion? Is that on the roadmap? Is that something that's going to be a plan for the long run? So that's kind of the operator framework. The other framework I like to ask is just about kind of access control for you as a user.
Do you have access to withdrawals, right? Do you have access to your underlying capital at any time, right? Or is it the node operator that has access to that? How are you actually able to retrieve the underlying rewards here? Is that something that you're always able to retrieve when you withdraw? Things like this, you should always be asking yourself when you're kind of depositing to these frameworks. And also, what is actually happening underneath the hood when I deposit? it understanding is it actually getting staked into an lst is it getting staked um into their own validators where is that capital actually going questions you should be asking yourself um and then finally uh uh actually i have four of these um but finally the last one for the lrts which i think is um uh i call it like the the future the future proofing vertical is the questions of like okay what are they looking towards in the future of like future proofing the system uh dvt usage is dvt a large priority for them i think dvt and the idea of even taking a single node operator and then splitting up the access control between multiple entities and a single node operator makes the difficulty of slashing that much higher right the same thing with te usage humans and human input is for ethereum at least is most of the reason why slashing events ever happen if you remove humans from the equation your risk of slashing goes immensely down, right?
So by removing human's alley question by using things like TEs, you're able to kind of mitigate slashing risk as well. Those are kind of the two main things, but I'm sure other people will be building really interesting and innovative ways to kind of future-proof staking and restaking the launch. The final thing I would ask is also, you know, the more practical thing. What can you do with this asset, right? Is it just going to be restaked? Can you use IndieFi? Are they prioritizing implementations in L2's bridges? Can you reduce your costs? Things like that. Those are also things that are important just from a user experience standpoint.
And although in crypto, we tend to have a, you know, bad rap for good UX, I think, you know, it's something we should be asking ourselves and prioritizing as well. Although, of course, you know, I put this as one vertical, I think we should also weight this idea of like safety and security a lot more than just kind of these UX improvements. Trinta, I'm so glad that I brought you into this conversation. I think that was immensely helpful for the listeners as they are about to hear all five of these interviews. Just maybe one last message for the listeners is like we're starting to color in a picture here.
The interviews that you are about to hear are going to help you further color in that picture, but there's just so much more research to be done. I only really was able to touch on the surface level of each one of these LRT projects. So like each one kind of represents some homework to be done. Chunda here just gave you the frameworks to do your homework with and by. So thank you, Chunda, for that. Chunda, you talked about some resources. We will put those links in the show notes. But overall, if people just want to learn more about Ion Protocol and learn more about the way that you think about risks in LRTs, where should they go?
Yeah, 100%. If you want to check us out at Ion Protocol, we post a lot of content about this kind of stuff, as well as the things we're thinking about internally when it comes to building out the protocol. So just check us out on Twitter at Ion Protocol, one word. You can take a look at our recent work with Shoal Research and the guys at Abuse Who Finance. This framework that I've been talking about, we put that on and added even more kind of a larger checklist that you can kind of run through and ask yourself questions of, OK, what is important about, you know, me using all these different LRT solutions.
And then also we had a little bit of a sprinkle in there about what is important about these solutions that we claim to underwrite these allergies. We put a couple a couple of different examples in there for you guys to interact with and learn a little bit more about. And then if you're interested in kind of hearing my thoughts about the like the little random things about Ethereum or infrastructure and you know, how they make implications on staking and restaking, feel free to follow me just to actually be on Twitter. you can check everything out there. Beautiful. Chunda, we'll get all those links and your Twitter into the show notes.
Thank you so much for all this knowledge. Yeah. Appreciate the invite, man. Thank you. All right. Thanks so much, Chunda. Now let's go ahead and get into all of the different LRTs. But first, I'm going to talk about some of these fantastic sponsors that make this show possible, especially Kraken, our preferred crypto exchange in 2024. If you do not have an account with Kraken, consider clicking the links in the show notes, getting started with Kraken today. If you want a crypto trading experience backed by world-class security and award-winning support teams, then head over to Kraken, one of the longest standing and most secure crypto platforms in the world.
Kraken is on a journey to build a more accessible, inclusive, and fair financial system, making it simple and secure for everyone, everywhere to trade crypto. Kraken's intuitive trading tools are designed to grow with you, empowering you to make your first or your hundredth trade in just a few clicks. And there's an award-winning client support team available 24-7 to help you along the way, along with a whole range of educational guides, articles, and videos. With products and features like Kraken Pro and Kraken NFT Marketplace and a seamless app to bring it all together, it's really the perfect place to get your complete crypto experience.
So check out the simple, secure, and powerful way for everyone to trade crypto, whether you're a complete beginner or a seasoned pro. Go to kraken.com slash bankless to see what crypto can be. Not investment advice. Crypto trading involves risk of loss. It's everyone's favorite season in crypto, tax season. And crypto tax is always an absolute headache, especially for all you degens out there. But it doesn't have to be a nightmare. That's where Crypto Tax Calculator comes in. The software built for degens by degens. As Coinbase's official global tax partner, Crypto Tax Calculator focuses on making complex transactions into easy ones, supporting over 300,000 currencies across Ethereum, Arbitrum, Optimism, as well as 1,000 other integrations as well.
It's as simple as connecting your wallet, pulling in all your transactions, and following the automated suggestions to quickly and accurately calculate your tax obligations. Plus, for all the airdrop farmers out there, Crypto Tax Calculator has your back as they are consistently adding support for new and upcoming Layer 1s, Layer 2s, and all the airdrops that you're currently farming. 2024 is the year when the degens do their crypto taxes with speed and confidence. Make taxes this year easy and affordable with Crypto Tax Calculator. Sign up at CryptoTaxCalculator.io and get a 30% discount with code BANK30.
Click the link in the show notes for more information. Are you launching a token? Is it already live? How are you managing the legal and tax obligations for providing token grants to your team? It's no secret that token management gets complicated. Between learning all the legal language and tax obligations in every country that your team is in, token grant management can feel like an obstacle course. But it doesn't have to. That's where Toku steps in. Toku provides practical tools to handle token grants, allowing for effective oversight of token distributions and payroll tax compliance for employees, contractors, advisors, and investors.
They also handle tax withholdings through their real-time tax calculations that can be done by Toku or integrated into any payroll EOR providers in any jurisdiction. Toku is a trusted provider of Protocol Labs, DYDX Foundation, Mina Protocol, and many more. Get started for free and make token compensation simple at toku.com slash bankless. Bankless Nation, I'm here with Mike Siligadze from EtherFi. Mike, welcome to the show. Hey, great to be here. I'm Mike Siligadze. I'm the founder and CEO of EtherFi. Previously, I've built some pretty large businesses that were valued in the hundreds of millions of dollars and I'm excited to help revolutionize the restaking universe.
Okay, so Mike, talk to us about how you came to the conclusion to work in the LRT space to build EtherFi. What was the inspiration? Where did it come from? And how did you end up building EtherFi? EtherFi actually started as a fund, an ETH staking fund. And we realized that there actually wasn't a product on the market that we were comfortable using ourselves. And so we really built Etherpride to solve our own problem, to solve the issue of ETH custody and risk management, and to build something that was natively integrated with restaking from the ground up. How did the team come together? Who are your co-founders?
What does the company look like? The core team consists of myself, Rock, Joseph and Rupert. I founded the team and the CEO, Rupert, is our head of engineering. Joseph is our COO and Rock is our head of revenue. Okay. And then eventually EtherFi went from fund to LRT. Can you talk about that like aha moment or eureka moment? Just talk to us about that decision. Yeah. So believe it or not, we planned to build EtherFi as an LRT from day one. When we were raising our seed round, we were talking about restaking at the core of the protocol because we saw that as a natural extension of proof of stake on Ethereum.
Was it always meant to be an LRT that would also allow users to deposit or as an LRT for just increasing the yields of the funds, Ether? Or has the North Star always been the same? That's a great question. So no, initially we started as a fund and within a few months, we pivoted to building a product because my previous life, I built a product company and I wanted to do that again in Ethereum rather than running a fund. Okay, let's talk about EtherFi as a product. There are so many LRT teams out there. That's why we're doing this episode. What about EtherFi is unique? What makes it stand out?
So there's two things that make EtherFi interesting. The first is that it's the only staking protocol that allows stakers to hold on to their keys. With every other liquid staking protocol, the node operator controls your keys and effectively has sort of a stranglehold on your custody of your ETH. The second thing is we were the very first protocol that was natively restaked from the ground up. And so that's why we were able to get to market first and become the largest liquid staking protocol. And the other thing I'll say is, believe it or not, it actually is not that crowded a space because although there are probably 50 different LRTs right now, nearly all of them are just wrappers of some LST or another.
And there's only a handful of actual natively restaked liquid tokens, and that includes us, includes Swell, includes Renzo, which are really awesome teams that we think are building cool things in the space. Let's unpack those one by one. Let's start with that first one, The one where node operators retain their own keys. Can you just unpack that a little bit? Kind of explain like on five what that means. Yeah, so there's a big challenge with most liquid staking protocols in that when you deposit your ETH into really any liquid staking protocol, a node operator generates the keys and spins up a validator.
You need that validator key that node operator generates in order to be able to get your ETH back. So when you go to Lido or any other protocol that has withdrawals, which is actually not that many, and try to get your ETH back, you submit a withdrawal request. What it does in the background is it effectively just voluntarily requests that a node operator return the ETH by exiting a validator. And now that introduces a lot of counterparty risk, in particular with protocols that have centralized node operators. It basically makes them a target. It makes it very easy to have a situation where you are not able to get your ETH back.
With EtherFi, stakers act as bondholders and generate the keys, and there's an economic incentive mechanism to make sure you get your ETH back. So when you go to EtherFi and request a withdrawal, if your withdrawal is not honored, somebody's ETH gets slashed. And so that basically, it makes it very likely that you're gonna get your ETH back. This sounds like an innovation on the LST layer, which the LRT layer is built on top of, But first, it sounds like a little bit like this is improving even just the raw, normal Ethereum staking stack for delegated staking. Yeah. So I don't think that there should be two categories.
I think it's a dumb idea to have LRTs and LSTs. All liquid staking protocols are going to be LRTs within a year. It's going to be something that's foundational to staking on Ethereum. So, yes, we call ourselves an LST because we think all LSTs eventually are going to have restaking baked in. beautiful okay uh so this I'm guessing this implies that individuals can become node operators with ether correct yeah that's exactly right so currently it is not a fully permissionless system we've got about 100 solo stakers who are operating nodes for ether5 within about two months it's going to be a fully permissionless system so anybody will be able to show up with a two bond and dvt managed keys uh be able to spin up a validator run it and generate an income beautiful okay leveraging dvt uh what are the the collateral requirements is there collateral in the system yeah so there's two a two eve bond requirement for anybody that runs a validator in order to have one shard of the the validator cluster one unique thing about ether5 is you guys are incubating an avs is that correct and can you tell me more we are yeah we're really excited about this uh so we are uh the plan is to build on top of our liquid staking uh protocol and add components to it to make it differentiated that hopefully generate higher returns for users one of the ways that we're doing that is by actually building an in-house uh avs uh specifically and i haven't this is a mouthful right here um it's called dat bridge and it is a decentralized rpc service similar to like a pocket network but built on uh restaking on eigen layer we're super excited about that.
We're actually going to be publicly talking about it, aside from here, I guess, for the first time in the next probably two or three weeks. And then we'll be launching a beta a couple months after that. Okay, so how does a decentralized RPC leverage Ethereum security to improve its product? So every Ethereum node in the world has an RPC endpoint. That's just how the protocol works. An RPC endpoint is basically just a way to talk to the Ethereum node and get data out of it or submit transactions to the blockchain so this is something that's already part of the network etherfi has now thousands and thousands probably ten thousand different uh nodes that run on etherfi and each one of those has an rpc endpoint and so the decentralized rpc service just leverages these existing rpc endpoints puts a bunch of load balancers in front of them and allows users to make use of this mostly idle infrastructure that's kind of sitting their uh you know validating blocks uh periodically okay so etherfi uh was built to be an lrt from the ground up from day one uh you guys had your own own capital that i think you guys have uh put into the etherfi system because you guys were a fund prior to that uh you have this unique uh uh node operators retain their own keys set up which uh allows for more permission stakers have their own keys which allows for just more permissionlessness and uh staker sovereignty in the system um yeah and you guys have your own avs that you guys are incubating internally uh what else would you add to this like report card so i would say i you know it's always uh hard to make a subjective claim but i would say we're super ethereum aligned i mean the reason that uh we're doing this is because we're really we really are passionate about ethereum and crypto and what it stands for you know the founding team myself certainly we've we've made enough money that we don't need to be you know working for a living day-to-day uh we're doing this because we actually believe that it's going to help the network and because we believe in the mission of crypto of self-sovereignty and giving people more control over their uh their wealth so they can't be taken away from them and so we're super ethereum aligned you know we we're giving one percent to the protocol guild which is the the team that builds the ethereum uh protocol one percent of our token uh supply uh we've got the you know sasso on our uh advisory board we've got a member of the james smith member of the ethereum foundation of uh on our advisory board um uh you know we're we treat this stuff seriously at the start of our white paper you know outlines our principles uh and what we believe in and at the core of it is that we'll do the right thing for the network i think that matters i think you know it's easy to think about short terms and token pumps and all that nonsense but i genuinely we plan to be doing this for another 10 20 years um and so we're we're trying to make the right decisions for the long term so etherfi is coming in at approaching 700 million dollars ether deposited into your guys's um contracts uh that placing it as number one in the lrt race to what to what do you credit the reason why etherfi is currently the number one in attracted capital well i think some of the things that we talked about so one we were the first that naturally you know sort of confers an advantage uh uh you know aside from building a good product that was just good uh good timing um uh i think uh i'd like to believe that our ethereum alignment and messaging and the the brand that we've put out there has made a difference that people you know believe that they can trust us uh and uh we hope to live up to that uh you know expectation so yeah all those things we've also done a really good job of uh integrations So we're plugged into, I think, more DeFi protocols than anybody else.
We're starting to deploy on Layer 2s and a bunch of other areas that make the token ultimately more useful for users. Is there something in EtherFi's future roadmap item that is exciting that users might be interested in? So the thing that I'm most excited about in the coming months of EtherFi, the first is that we are going to be announcing our Series A fundraising. Maybe by the time this episode airs, we have already announced it. So we're working with some pretty awesome investors that we're really excited about. And then the second thing is that we are, in fact, going to be doing our token launch.
We think our users are going to be super happy with that. We're doing some pretty interesting and unique things with the launch. And we hope that it ultimately ends up helping the ecosystem. Mike, if you have piqued the curiosity of any listeners of this episode and they want to learn more about EtherFi, where should they go? Just go to ether.fi, ether.fi, and then you could, you know, hang out, you can stake your ETH, you can check out our Discord, whatever you want. Awesome. Thanks, Mike. Thanks for the station. I'm super excited to introduce you to Amir from Puffer. Amir, welcome to the show.
Thank you, David. Thank you so much for having me. Amir, tell us a little bit about yourself and how you came to be at Puffer, and then we'll get into how Puffer came to be an LRT. But first, the first two questions. Absolutely. Well, I'm the CEO at Puffer Labs, where we're building the entire Puffer ecosystem. And how did Puffer come to be? Where did Puffer come from? Well, that's a very great question. We actually started to think about Puffer way before on a foundational level. We started to look into bringing scalable compute to Ethereum through the use of TEs. Of course, we met Justin Drake in our journey.
and we realized that the blockchain is not decentralized enough and it's not ready for the confidential compute and AI that we're focusing to bring on-chain. There, he proposed to use the same technologies that we were familiar with, trusted execution environments, to actually build anti-slashers. This was back in the day where actually all the talks were about Lido and RocketPool. And we started to focus on building the most scalable and decentralized LSD. And from this idea, we came to an important conclusion that building anti-slashers, reducing risks, is not going to be enough. Reducing the bond is not going to be enough.
And we need to actually grow the rewards pile for the validators to be able to make it more viable to host your own node, or even maybe run your node at home. That's where we were introduced to Shuram to enable restaking. So both validators and stakers can now generate more rewards. This opened the window for us to actually do specialized AVSs through the use of only TEEs enabled to our validators as well. That's where Puffer came from. It's basically on its base layer, it's an evolution to liquid staking on Ethereum. And the upgrades that we made to it actually enables many interesting features enabled on liquid restaking as well.
Okay, cool. TEE, Trusted Execution Environment. Sadly, every single time we talk, Amir, we're going to have to define what that is because most people don't know what that is. What is a TEE and then what does it do for Puffer? Basically, you can think of a TEE as a secure portion of the hardware that runs computation. It's encrypted through cryptography. What does it do in Puffer? The easiest way to explain this, which Justin Drake is very good at explaining this, is You can think of it as a hardware wallet for your validator, where your keys are generated in there. They're protected in there.
And in Puffer, we not only protect the validator keys inside of a TEE, but also we protect the database of previously signed material. So it's a separate stack running aside with a consensus client and an execution client that checks every signature that the validator operator is going to produce. that signature is going to produce a slashable message, basically this anti-slasher rejects it. That's where it becomes an anti-slasher and that's how T is working properly. Okay, so I've defined the LRT game as a competition to maximize exposure to AVSs and therefore yield while also minimizing risks.
There are a variety of different reasons, categories of slashing events that could happen to an LRT, to an operator. And then what you're saying is that there is this trick, this hardware trick with using TEEs, Intel SGX, people might be more familiar with, that actually protects against a certain class of slashing events. Can you kind of like delineate between the types of slashing events that TEE, leveraging TEE protects against and what class of slashing events it does not? Well, we are actually releasing articles like one at a time. We're actually, our docs is very up to date. We recently uploaded the docs.
We did a deep dive of how restaking and staking works on Puffer. Just please go to docs.puffer.fi. The Twitter is a good source. Our mediums are a good source as well with our latest views. But we are going to release more on these like more future roadmap and future steps. If an operator would like to break the trust boundaries of this TE, basically break into it, grab their key out, which we will be back to the status quo of running an Ethereum node, they can cause like a self-slashing event, which is of course malicious. But really, this anti-slasher prevents all slashing on Ethereum L1. Preventing all slashing is like, that's a really big statement.
Is it really that big? Is it really that like rock solid? It is because really it is so hard. The concept of slashing is so easy defined on Ethereum proof of stake. It is so hard to produce a slashing event. And therefore, like preventing it from the hardware side is also not that hard. But it's been mostly, if you've seen the past slashing events, either it was from a malicious actor who wanted to extract more MEV by causing a reorg, or it's been just a mistake by big node operators where what they usually do is they do this thing called load balancing. They spin up nodes spontaneously at the same time and they do a double signing on a block and therefore it causes slashing for them.
This really mitigates these all existing risks from mistakes. Really, it's something to protect against all the mistakes. There is like a mystery and demystification here. If someone turns off their hardware, and don't commit to attestation or proposing blocks, they do not get slashed. They're just going to miss rewards and have a very small penalty. And I think this is very important. Okay, so we talked about TEE as like the competitive advantage with the fundamentals of Puffer, if you will, like what sets it apart from others. But what about the actual like strategy of Puffer? What is like the near-term roadmap, the plan for action?
Like what does the near-term look like for Puffer? What's the plan here? Absolutely. I think we have beyond just anti-slashers. Our strategy is focus on research, focus on native restaking, and focus on ethos alignment. I can now unwrap each of these. Focusing on research, Puffer has been the decentralizing runway for Ethereum. Why do we say this? A lot of the research and products that we introduced to Puffer actually come from the wishlist of all the EIPs that are yet to be passed, but out of protocol. For example, there is EIP-7002. This is going to enforce a smart contract ejection of validators on Ethereum from execution layer.
This is good because especially in liquid staking platforms, if a trustless, basically untrusted node operator drops below a certain value, we can just eject it from the execution layer. This is not going to be implemented maybe in the next two years. This is a key factor to have to creating a permissionless decentralized protocol. We got around that by introducing our guardians. So aside from anti-slashers that makes it more secure to run a node, we introduced guardians so the stakers actually don't lose money if the validators just turn off their hardwares and walk away. And we find out that actually implementing these are translating really well to restaking.
If we have a more protected base layer of liquid staking through anti-slashers, it means the ETH that is protecting these AVSs also is more protected. A big challenge in native restaking today is if there is an AVS-level slashing happens on an Agen layer, there is no slashing can happen unless we can eject the validator first. Their ETH goes to the withdrawal address, and the withdrawal address that points to the Agen part gets slashed. Without it, we can't really have native restaking live. That's where Puffer can enable native restaking go live through this implementation of the research that we did on the base layer.
We say we focus on native restaking. Why do we say that? Because it has many advantages compared to just like LST restaking. One of them being that the node operators also can take advantage of the rewards. If any other protocol just turns on LST restaking, The base node operators on those platforms get nothing. They don't get exposed to the rewards from the restaking. That's where we say we increase the rewards by, and users can make more. Therefore, it's easier for me to run a validator at home and make more rewards. Imagine Puffer is this platform. You run an ETH validator with one ETH only, and you also get restaking rewards, which is not enabled on any other platform.
So that's on native restaking. Also, a quick advantage is the advantages of restaking that can be brought to Ethereum mainnet itself, including Mebboost+, including base rollups that I know Justin talked about in the previous episode as well, and many other features that are not enabled without restaking on the Ethereum mainnet itself. We save your ethos aligned. we need to actually keep Ethereum decentralized as much as possible. And that has been our strategy. That's why we're self-gapping our liquid stake into 22% total each stake. And also all these researches we're doing is aiming to keep decentralization one way to Ethereum main.
Amir, you alluded to it a little bit, but I want to go into it a little bit more. Again, going back to like the whole idea, LRTs are trying to maximize exposure while minimize risks. one way you could another present that is being sufficiently defensive as in making sure nothing gets slashed while also being sufficiently offensive which is making sure you go get yield so you go get the the rewards being paid out by the AVS networks this is kind of why we're all doing this is really what everyone's excited about how does Puffer and leveraging TEE can TEE T enable like relationships with AVSs that some sort of LRT without TE could not access?
Like how can this become like a service for AVSs? Absolutely. The first and the foremost easiest way that TE enables is just the anti-slash. Key management is a very important concept. And like we really like to see like AgendLayer as transferring all the existing infrastructure and Ethereum to restake it. And it's very simple to use TE on top of middlewares like bridges, oracles, and everything else to actually make sure that the activity that is supposed to be done is getting done in those key management scenarios. For example, even if we want to create an L2 based on basically an AVS, TE comes into play to play the similar role that it plays on the consensus layer.
just prevent slashable offenses from being signed by the sequencers. So these are the very basically unique things that Puffer can provide. But also the kind of like the craziest thing is Puffer nodes can become one AVS as an anti-slasher to all the other AVSs. Basically, we can provide anti-slashing as a service as an AVS across the map. And as you know, there is a lot of research going around confidential compute and also verifiable computation. There is FHE, there is MPC, there is ZK. One of the more practical forms of confidential compute is TEs. If you want to bring AI, confidential AI, something that I think WorldCoin focused on a little bit, this actually can be enabled with a big network of TEs on Puffer, which sets it apart from all the others.
Interesting. Okay, so let's go into the specific state of Puffer, the specific implementation. Y'all have collected a bunch of Lido staked ETH. There's a plan to swap that into Puff ETH. Can you talk about, and that's where we currently are in the Puffer roadmap. Talk about that event. What's the roadmap for that? And then what's the following roadmap after that? Absolutely. To actually help reduce the dominance of one LST player, we actually tried to just focus on SDE at this part of this campaign. Users actually get PuffEth in return where they can use it on DeFi platforms. It's liquid. This campaign showed even if EigenLayer is on Mainnet, people are ready for restating.
So yes, once we are going on Mainnet, we're going to redeem all these SDE from Lido. This actually today translates to almost three and a half percent of existing SDEs, which is going to significantly actually help for the decentralization of the protocol. On top of that, once we go on mainnet to PuffEth holders, there is no differences. They keep their PuffEth. Only the rewards that is generated for them is now from Puffer permissionless decentralized validators. We are aiming to go on mainnet completely fully permissionless. Today we are on testnet with our permissionless nodes. We are opening the testnet to public very soon actually.
I think this is going to be another very big milestone where people can see, oh wow, I can spin up a one ETH validator. I think this is for the kind of like first time with no extra overhead. They just have the same stack that they have at home with just the addition of like the anti-slasher which runs separate from that part of stack. They can spin up one ETH note. Moving forward, we're sprinting to mainnet. We're going to have mainnet on that layer also. We're going to natively restate the ETH on existing Eigenlayer Eigenpods. In parallel, we're going to work with existing AVSS and we're going to implement our own AVSS as well.
Another exciting part that I spoke about was this all existing infrastructure turning into eigen layer restaking. And that's where Puffer is capitalizing on it. Puffer is going to deploy its own L2 on its platform as an AVS. Now imagine this L2 is going to generate fees. Since the security provided to this L2 is from the PuffEth holders, PuffEth holders are going to take advantage of the fees that L2 is capturing. Of course, we implemented validator tickets. That's a one hour conversation of what they are, but they're essentially, this L2 is going to be a market, create this marketplace for these validator tickets.
But an L2 cannot just be standalone by itself. An L2 needs an Oracle. An L2 needs a bridge. All of these infrastructures today, there are many companies that run these as AVSs. They can be deployed on top of Puffer and we can create this infrastructure superdap where they all feed back to the PuffEth holder as extra revenue and also the node operators. That's on our roadmap and it's actually coming probably the second half of this year. Okay. So a layer two from Puffer leveraging TEE and being infrastructure for AVS is a massive rabbit hole that sadly we don't have enough time to go into. if people want to learn more about that and just learn more about Puffer, where can they go?
Well, we are actually releasing articles like one at a time. We're actually, our docs is very up to date. We recently uploaded the docs. We did a deep dive of how restaking and staking works on Puffer. Just please go to docs.puffer.fi. The Twitter is a good source. Our mediums are a good source as well with our latest views, but we are going to release more on these like more future roadmap and future steps. Beautiful. Amir, thank you so much. Thank you, David. Bankless Nation, I am here with Amit Gajila from KelpDAO. Amit, welcome to the show. Thanks. Thanks, David, for having me here. Talk to us a little bit about your background.
Where did you come from and how did you start KelpDAO? Yeah, I'm originally from Bangalore, India. I used to work at a consulting strategy consulting firm here and then had a strategy and transformation at India's largest food tech player. Been in crypto since 2020. Started Stata Labs, one of the largest liquid staking platform with 450 million in TVL. And early 2023, we also started this new protocol called KelpDAO, which is a liquid restaking platform. Beautiful. Okay, so Stater into KelpDAO. Talk about just like the creation of Stater and like the lessons and experiences that you learned there.
And then we'll carry that into how you are applying those lessons at Kelp. Pretty amazing experiences at Stater. So we were one of the early protocols on Terra 1.0. We had about $1.5 billion in TVL that completely had gone to zero right after the USD collapse. multiple learnings. First and foremost learning as a founder is diversify treasury and risks as much as possible, which kind of led us to expand to multi-chains. And today we are present across six different chains with majority being on Ethereum and Polygon. Back then we already diversified treasury, but we learned the lessons of treasury management in the hard way by losing some money in the USD collapse.
The third thing is team and people are the most important things. People who believe in your vision as well as your leadership will stick. So the most important lesson from the entire experience is hire people that are passionate as well as believe in the vision of the protocol. Okay, so Stater and ETHX is your staked ETH token. Talk about just like the growth of Stator? Because eventually this, like I said, will kind of like fold into KelpDAO. Talk about just like the experiences of growing Stator and just like learning to build an LST. Numerous experiences there. We have learned it the hard way and understood what are the major competitive modes for an LST and obviously drawing those lessons to KelpDAO as well.
The biggest competitive modes for LST are creating these access or distribution points that is taking staking or taking LSTs to places where people are already using, like for example, some of the largest hardware wallets like Metamask, largest hardware wallets like Ledger, wallets like Metamask, etc., where Stata solutions are already embedded natively. That's where we see a majority of growth for our LSTs. The second and the most important things are creating real utility for these LSTs. For example, we have deep integrations with Aave, Compound and several other DeFi protocols of the world where people find real use cases as opposed to Ponzi schemes where people go collateralize their LSTs while earning those staking yields, they can also borrow stable coins or they can borrow other assets that help them get to other yield opportunities.
So these two have been the most important and crucial learning aspects or competitive modes that we built with our LSTs on Polygon, now building those on Ethereum, and obviously carry those forward to KelpDAO as well. Right. Okay. So there is a relationship between Stator and Kelp. In Stator, the LST, of course, has EthX. And one of the big experiences that all LRT teams are going to have to fight against is like integrations for their LRT tokens into DeFi. And this is something that you've sharpened your teeth with, with Ether, with EthX and Stator, just like getting EthX into like Ledger and MetaMask.
So you can stake your Eth with Stator via like Ledger Live or MetaMask. And then also like getting EthX into Compound, right? Just normal DeFi applications for LRT tokens. Eventually we will all need these things. What you're saying is Stator's done this game before. And so you're going to just take the same playbook that you've developed at Stator, you're going to apply it at KelpDAO. That's probably, I'm assuming, where this goes. Is that right? That is one of the strengths that we borrow from our experience with Stator. But obviously, LRTs, given this is a new entire restaking and eigenlayer being new technology, there are multiple risks associated with it.
Obviously, we can't apply the same playbook as these, but the learnings are similar. Talk about the relationship between Stater and KelpDAO. How did that whole thing work out? How what is the relationship there? The relationship is very simple. Just the founders are common and Stater is one of the seed investors in KelpDAO. Apart from that, everything else is different. And one tactical relation is Stater's EthX is accepted as one of the deposit assets on KelpDAO. Okay, so founders are common, experiences are common. Is there like an ongoing relationship or are these two things going to come together or diverge?
They're going to be completely different. KelpDAO, as you probably know, accepts three different LSTs today, LIDOS, STETH, Fraxis SFRxETH, as well as TADAS ETHX. So Kelp will be a completely neutral entity that serves its own interests and has its own tokenomics and pnl so as much as possible they will continue to be two separate entities okay all right so let's get into more kelpdell specific subjects uh what what would you say are the strengths of kelpdell how does it stand out from the many different lrt teams out there uh what's your guys's like strategy yeah it's a very interesting question and useful question in in the current context of the competitive environment.
So some of the, like based on our experience so far, the biggest focus areas or strategies that we will employ with KelpDAO is one, creating access for restaking. What I mean by that is like, we need to take restaking to where users already are. That is when we can potentially scale this to like 10, 20, maybe $30 billion, right? We have seen what happened with staking with Lido and some of the largest validators of the world. So creating access for users is going to be top priority for us. And that is where we can attract capital in the right way and also the right set of capital that is more stickier than some of the mercenary capital out there.
So that's one most important strategy. The second critical strategy for us is going to be having majority of the DeFi integrations, which is where we are really bridging the nexus between restaking and DeFi. Today, both of them compete with each other for the same amount of Ethereum or capital. So the PMF for us, for KelpDAO, is going to be when there is real utility created for KelpDAO's RSE, among some of the largest DeFi platforms so that people can actually borrow using RSE or people could participate in PURPS using RSE, collateralize it for some other use case. So that is where we believe we have solved a real user problem.
So those are the two most important competitive modes in the long run. And also that is where we'll spend disproportionate time and efforts. Okay, so the strategy here is that if you want to restake with KelpDAO, one of the main benefits is that you will also be able to take your KelpDAO ETH and then take that capital and put it back into DeFi and do the thing you were already doing with your ETH and DeFi just now with the kelp doubt eth is that kind of the idea yep yep of course cool and what is the kelp doubt eth token it's called rs eth restaked eth okay so in terms of like a brand perspective like just having restaked eth i actually think is like pretty valuable like lido has st staked eth like easy and so you guys have rs eth uh maybe you guys just like got there first maybe the the playing field was open but just i do think there's like some benefit just having like we are restaked ETH.
We have RSE. Yeah, that was very easy to come up with in hindsight. Okay, beautiful. Talk about a little bit under the hood of KelpDAO. Who is doing the validating nodes? Who is actually running the hardware or doing the actual ETH layer one validation? Is there native restaking? Talk about the KelpDAO system under the hood. Absolutely. So just Just zooming out about the KelpDAO's product today. So far, we have been primarily accepting LSTs as deposit assets on KelpDAO. So there is no validators yet that are live on EigenLayer that take LSTs and validate. But soon, which is probably in two to three days, we are also launching native restaking on KelpDAO.
Okay, so that means it's out by the time this episode is released. So this is now a live product. Yeah, absolutely. So we will have native restaking live and we're talking to some of the top validators and going to onboard them. Okay. Are you able to share who you're talking to? It's still confidential. Okay. What about just like anyone entering into Calped out with their validator? Are you going to be able to open this up or what's the strategy around there? That's a very interesting question. for context, Stator allows any type of node operator to actually participate in validating nodes with just four ETH worth of capital.
That is the permissionless way of operating validators. So we do have the opportunity to allow permissionless validators to take part in Kelp Cloud. But the constraint that we face today is we do not know the slashing and penalty restrictions that some of these AVSs are going to impose. So coming up with a collateral that is required or sufficient enough to cover for the slashing risks is an unknown today. So while we'll have that use case in the future, but at this stage, it's a little premature to allow anybody because that means we're putting users' capital at risk. Like we said, by the time this episode goes out, KelpDAO will have announced native restaking.
What is on the near-term roadmap that is worth highlighting? Yeah, so there are a few most important aspects that we're working on. In the same theme of creating access for users, we are taking restaking natively live on some of the L2s, working with a couple of partners there who can offer native restaking for KelpDAO on L2s directly so users don't have to bridge their assets back to mainnet and restake. this is first of its kind and I think it is going to save a lot of gas fees and effort for users. So L2 expansion is the most important thing that we're focusing on apart from creating DeFi opportunities.
We already have over 15 million dollars in LP pools across four DEXs soon getting to 40 million and then that opens up a lot of lending market integrations and CDP protocol integrations that users can access. Those are the two things. And then apart from that, obviously, under the same theme of access, working with Ledger and several other wallet partners to have restaking right where users are using their platforms. Okay, so just taking the same relationship that you built at Stater, instead of, hey, stake with Stater via Ledger, you are saying, hey, restake with Kelp via Ledger. is a partnership that is underway.
Yep, yep, absolutely. And the third most important thing that we are focusing on is actually creating some interesting products and use cases for AVSS because those, so the AVSS are going to be a very important and critical part of the EigenLayer ecosystem. So we've been running some experiments and problem solving with a few AVSS on some of their requirements. Like some AVSS want triple staking. they want to stake their governance token user as a security and their partner's governance token user as a security along with idler's security so all of these interesting use cases are coming up during our conversations and learnings with the avss so focusing on that and soon we'll probably see some interesting products coming out of that stream as well beautiful ama if people are piqued about kelp dao and they want to learn more where should they go So they should just simply log into kelpdow.
xyz. You can find all information about KelpDow smart contracts, our security, which is the most important thing, along with option to stake or restake your assets. Beautiful. Where did the name Kelp come from? Kelp is this algae that powers this entire underwater ecosystem. And we believe restaking is going to be such ecosystem, which is rich and supports a lot of dApps and applications. So hence the name Kel. We want the RSE token to kind of nurture the entire ecosystem. Beautiful. Love it. Amit, thank you so much. Mantle, formerly known as BitDAO, is the first DAO-led Web3 ecosystem, all built on top of Mantle's first core product, the Mantle Network, a brand new high performance Ethereum Layer built using the OP stack, but uses Eigenlayer's data availability solution instead of the expensive Ethereum Layer 1.
Not only does this reduce Mantle Network's gas fees by 80%, but it also reduces gas fee volatility, providing a more stable foundation for Mantle's applications. The Mantle treasury is one of the biggest DAO-owned treasuries, which is seeding an ecosystem of projects from all around the Web3 space for Mantle. Mantle already has sub-communities from around Web3 onboarded, like Game7 for Web3 gaming, and Bybit for TVL and liquidity and onramps. So if you want to build on the Mantle network, Mantle is offering a grants program that provides milestone-based funding to promising projects that help expand, secure, and decentralize Mantle.
If you want to get started working with the first DAO-led Layer 2 ecosystem, check out Mantle at Mantle.xyz and follow them on Twitter at 0xMantle. Celo is the mobile-first, EVM-compatible, carbon-negative blockchain built for the real world. Driving real-world use cases like mobile payments and mobile DeFi, and with Opera MiniPay as one of the fastest growing Web3 wallets, Celo is seeing a meteoric rise with over 300 million transactions and 1.5 million monthly active addresses. And now Celo is looking to come home to Ethereum as a layer two. Optimism, Polygon, Matterlabs, and Arbitrum have all thrown their hats in the ring for the Celo layer two to build upon their stacks.
Why the competition? The Celo layer two will bring huge advantages like a decentralized sequencer, off-chain data availability secured by Ethereum validators, and one block finality. What does that all mean for you? With Celo Layer 2, gas fees will stay low and you can even pay for gas natively using ERC-20 tokens, sending crypto to phone numbers across wallets using Social Connect. But Celo is a community-governed protocol. This means that Celo needs you to weigh in and make your voice heard. Join the conversation in the Celo forums, follow Celo on Twitter, and visit Celo.org to shape the future of Ethereum.
Arbitrum is the leading Ethereum scaling solution that is home to hundreds of decentralized applications. Arbitrum's technology allows you to interact with Ethereum at scale with low fees and faster transactions. Arbitrum has the leading DeFi ecosystem, strong infrastructure options, flourishing NFTs, and is quickly becoming the Web3 gaming hub. Explore the ecosystem at portal.arbitrum.io. Are you looking to permissionlessly launch your own Arbitrum Orbit chain? Arbitrum Orbit allows anyone to utilize Arbitrum's secure scaling technology to build your own Orbit chain, giving you access to interoperable, customizable permissions with dedicated throughput.
Whether you're a developer, an enterprise, or a user, Arbitrum Orbit lets you take your project to new heights. All of these technologies leverage the security and decentralization of Ethereum. Experience Web3 development the way it was always meant to be. Secure, fast, cheap, and friction-free. Visit arbitrum.io and get your journey started in one of the largest Ethereum communities. Bankless Station, we are here with Daniel from Swell. Daniel, welcome to the show. Great to be here. Thanks for the opportunity, David. Daniel, I think Swell might be the earliest, the oldest of all of these projects.
You came onto the world of staking first before liquid restaking. Talk about the beginnings of Swell, the inspiration to build Swell, and then we'll get into the pivot into LRTs. Yeah, absolutely. Yeah, so just a quick background on myself. My name is Daniel. I'm the founder of Swell. Originally, my background has been a mix of like finance, technology, and innovation, and then really went down the crypto rabbit hole a little after the sort of Ethereum ICO. Went into sort of a reading of Austrian economics trying to understand central banking and one thing led to another and then into Bitcoin and then into DeFi.
In terms of the original inspiration for Swell, I saw an opportunity in late 2021, early 2022 to do something in what I thought would be one of the most powerful crypto economic derivatives, was the lst um i thought it would be the thing that would really take d5 to the next level to have a yield bearing instrument backed by you know a theory of sort of consensus mechanism um and then yeah put together a seed round and then um was often away uh from there and then we launched uh our lst uh in early 2023 and then um basically saw some good traction there um got up up to about 100 million in TVL and then saw the writing on the wall when reading the Eigenlayer white paper and seeing that, look, what the LSTs did for DeFi, the LRTs are going to do in a much bigger way.
If the venture model is sort of like you have this yield bearing instrument powering DeFi as a base layer asset, well, the LRT is sort of like a double plus yield bearing instrument powered by this new sort of ecosystem of upcoming AVS as an Eigenlayer. And then it made sense as well then to really triple down on that. Yeah, and the timing, I think, was pretty interesting for you guys because you guys, like you said, you guys were going to build an LST, but then you were pretty fortuitous in the way and when EigenLayer was born, if you will, for then you'd be able to take that advantage, all of the deposits into the LST version of Swell and turn that into the LRT version of Swell.
Talk about that transition, because I think that is what Swell is currently going through. Talk about the transition from LST to LRT and the logistics behind all that. Yeah, absolutely. I'd say, generally speaking, we're still early-ish in the evolution of LRTs generally. I think that LRT design will continue to shake out as IAEA moves through its various stages in this roadmap, with Stage 2, Stage 3, or M2M3, respectively. and so far as like Swell is concerned one of the biggest integrations from the LST perspective was always to get the LST accepted as restaking collateral on Eigenlayer so that was a big unlock for us when Eigenlayer did decide to expand its universe of LST collaterals to be accepted and then throughout that entire time we were building a very strong community that was passionate not only about liquid staking but also this new phenomena of liquid restaking and so when EigenLayer did open those caps initially, we saw a massive influx of people basically looking to get exposure to restaking.
And we're in the middle of this incentive campaign with our voyage, and it made a lot of sense for people to effectively farm both Swell Pearls and EigenLayer points too. And then we recently launched about two weeks ago, our own native LRT called R-Suite. R-Suite is effectively a mechanism for people to get uncapped exposure to eigenlayer points in a way that has the underlying validators natively restate. So this is the current sort of state of affairs at the moment with Swell. We're currently undergoing the development of R-Suite v2. And what R-Suite v2 will enable is not only the acceptance of native ETH at the underlying, but also LSTs such as Suite.
And that will sort of be a really important step to us, eventually hoping to unify some meaningful percentage of restake liquidity on eigen layer for utilization in d5 with maximum composability and optionality for restakers beautiful and that's been swell will become like one unified system and be able to uh inject all of its liquidity from its lst into its lrt uh so like bringing the advantage of being early into the uh into the world of native restaking right exactly right beautiful um okay what is what would you say is the competitive advantage uh of swell what does swell bring into the world of lrts that is like what's your guys's strategy yeah absolutely i think the i think just generally in terms of it from an advantage perspective i think the fact that we spent a lot of time thinking about ethereum staking like on the beacon chain side at first principles level for such a long time is a competitive advantage and also like our understanding of d5 which is in some ways one third of the total like lrt um sort of spectrum if you think about in terms of the beacon chain d5 and then everything on eigen layer so we have the beacon chain and d5 ready to go and i think everyone's sort of starting at a similar point in time um as regards i can layer trying to figure out okay how does this thing actually work where where are the risks where are the like how does the rewards work and where's the opportunities and how does one best position themselves to win the market um so i'd say like that's firstly the advantage and i think um from like a legacy standpoint or from an origin standpoint Moving forward though, I think in terms of our approach, there's been really three key things that we really focused in on as regards our design for an LRT protocol.
The first thing is really advocating for an ecosystem first approach. So Swells effectively created a liquid restaking council that comprises some of the best operators and most promising AVSs on EigenLayer. So we have folks like AltLayer there, Witness Chain, Imstones, P2, and a whole host of others as well. And having them be part and parcel of the co-building process means that the LRT that we will build out and continue to iterate on will be purpose-built for those ecosystem actors within EigenLayer. Because it's all about trying to match up across the opt-in mechanism between restakers, operators, and AVSs.
The second thing as well, in addition to the ecosystem approach, is also having a real focus on risk. and so part of that we've been working together with like the Argonne Labs team directly and also with various risk experts including Chaos and Gauntlet as regards things like ADS selection, pricing, underwriting and these sorts of things so that we're going in with eyes wide open as regards sort of risk return and these sorts of things. And the final thing for us is really just about trying to drive as much value to the underlying LRT as possible and so being early to these sorts of collaborations and then driving you know the rewards um and passing them through um to our restakers and also exploring ways in which we might be able to vertically integrate some of this stuff so looking at okay not only what like what's an lrt ultimately it's a liquidification of restake liquidity but then what else can you do on top of that could you create things like a sort of a proof of restake um l2 restake roll up and then pass through the revenues to the lrt like these sorts of things that we're sort of constantly ideated on which is like really a part of like this well core contributor dna is to think about these sorts of things beautiful that was that was a lot wow um one of the things that you touched on is about just making sure managing risk while also integrating with the avs's right and kind of the idea that i've had about lrts it's all about maximizing exposure to yields while minimizing risk right like how much extra uh yield can you get while making sure that you never ever get slashed um do you have any like sort of strategy or or plan around this yeah yeah i think that like generally speaking the the strategy is really about um trying to quantify and qualify um what operators to work with and also what avs's as well that those operators will be opting into and then understanding um not only how those interact but also like the underlying assets of the restaking pool itself um and so a lot of that is just going to be like constant dialogue with the operators and the avs's as well and then being able to feed into these models and then applying governance and interventions when necessary, particularly in the nascent stages of the technology, much in the similar way that EigenLay has approached it with their committees, with their multi-sigs, with their step through in terms of sort of opening up gradually through a guided launch, liquidity, getting battle tested, audits, and these sorts of things.
So yeah, it's definitely a multifaceted approach as regards risk. What are you guys working on right now? Like what is on the near-term roadmap for Swell? And then just overall, what would you say in the Swell community are people excited about? Yeah, definitely. I think the key new term things that we're working on is our TGE. So we're getting busily ready for that. The other thing is governance and like DAO operations, which will become part of the token being live. We've got a flow of DeFi integrations as well that we want to have for our LRT, including supporting that with various oracles and whatnot.
and also some cross-chain plans too uh in terms of what the community's uh most excited about i'd say it's it's it's a token um so yeah yeah so i want to make that as successful as possible um and yeah just um keep keep growing the protocol and keep providing as best as we can the um a really seamless and easy to use researching experience since uh as well you guys have been around for a while because like again you guys did the lst before even like restaking was even a thing uh so you guys have grown a community uh which i think is one of the uh kind of unique things as well you guys have actually had the time to collect a bunch of people who are now uh what do you call them swellian swellers uh swellers yeah uh and so like talk about the growth of the the swell community what's the vibe of swell culture yeah i think the the vibe of swell culture is um yeah i think a lot of people wanted the restaking like early and we told them look we We can't get it on the first one.
We didn't we didn't make it to the first whitelist, but we'll be there for the second one. So I think the community is really invested in restaking. I think they're really invested in DeFi. I think we have quite a crypto native and DeFi savvy user base. We've got circa you know, 100,000 stakers or unique depositors at the moment. If even if you were to sort of like take out some of the like potential like gaming or sibling, I think it's still a very strong community. um so um yeah i think people are really excited about restocking to be honest beautiful if people want to go and open up like the the technical documents or just read a higher level uh landscape about swell where should they go yeah they just go to our website uh swell network.
io and then just jump into the docs section and then and if you have any questions feel free to jump to the discord the team's always happy to answer any questions and take on any feedback uh what about uh you daniel where can they follow you um yeah you could just follow me on Twitter. My handle is Daniel underscore Swell underscore. Beautiful. And we'll get all those links in the show notes. Daniel, thank you so much. Thank you so much, David. I appreciate your time. Bankless Nation, I'm here with Lucas Kaczynski of Renzo. Lucas, welcome to the show. David, thanks for having us. Excited to talk about Renzo and what we're up to.
Hell yeah. Let's talk a little bit about you first. Who are you? How did you come to be at Renzo? What's your quick crypto background? So I've been in the space full time since 2018. I first joined the Tezos Foundation and was what a company called Tokensoft, and then a founding contributor to a project named Moonwell, which is a lending protocol. Earlier over the summer of 2022, a group of us got together and started just brainstorming about how Eigenlayer is going to play out, some of the challenges. and what we realized was that there was a need for two things. A product that could align incentives very well, both on users that are trying to stake and AVS is trying to get those stakers and a team that had experience on managing risk and has been around in the space for a long time.
So we pulled together a small team. This is June, July of last summer and started building Renzo in August. Beautiful. And how did the team come together? How did this team form? Who are the other founders and team members? Yeah, so the contributing founders to Renzo, we all know each other. So there's three of us, James and Krothik. I was a portfolio company for Krothik when he was at a fund named Woodstock. And James previously co-founded Tokensoft. So when I worked at Tokensoft for two years, I reported directly to him. So what you essentially have is three founding contributors that have a technical background, heavy research quant background, and a growth operations background across the crypto space for the last six, seven years.
So. Beautiful. Let's go into a little bit of that realization that you had about just the aligning of the incentives between the users, the liquidity and the AVSs. I really like that as an entrance point. Let's just keep going down that conversation. Shed a little bit more light about just like the problem that you identified and wanted to help tackle. Yes. So when you look at EigenLayer and you take a step back, there's a lot of noise right now around points and everything else. But at its core, EigenLayer has AVSs, as you guys have done a really good job explaining what they are. And there are services that other projects are going to be using, mostly roll-ups.
And there's this really nice cycle that Renzo is able to help complete. And what I mean by that is AVSs have clients, and those clients are roll-ups. those roll-ups are going to use AVSs and they need security. And that security has to come from somewhere. And there's a lot of complications, not complications, but complexity built into EigenLayer because it's a marketplace. It's a free marketplace. To attract those users and make it very simple for them to have an on and off ramp into EigenLayer is really important for an ecosystem to thrive. You need both parts of the supply and demand of the marketplace to come together.
So there's this issue right now where EigenLayer is attracting roll-ups to use them. But roll-ups, so we're talking like Arbitrum, Optimism, Bates, the same services that are being used and adding value, it's actually sucking liquidity out of those ecosystems. So Renzo is positioned in a way where we're actually aligned incentives with those roll-ups, L2s and L1s, and the AVSs so that the value could also remain on those networks. And the reason we're able to do that is how we designed Renzo from the very beginning. So this past week we introduced our next feature which we launched with just native restaking.
Renzo is the first protocol that is actually able to take native restaking and LSTs and use them as collateral to have one LRT. And the reason that's really important is where we're seeing other players having to do things like vampire attack other networks to be able to bring that funnel in. Renzo is directly aligned with those ecosystems. So one of the partnerships that that we announced was BNB. So in a few weeks here, BNB users are actually going to be able to come to Renzo on BNB chain, deposit BEath and get EZEath back on that chain. So it completes this loop. Same thing with Arbitrum. We announced a partnership with Arbitrum and Connex.
Using Connex as the bridge layer, users on Arbitrum are going to be able to deposit ETH, native ETH, get easy ETH back, and the TVL stays on that chain. And that same TVL is secure in the same services that EigenLayer is essentially offering to rollups. Okay. I really like this. So we have capital on these rollups, mainly ETH, usually ETH, stem stables too, but ignoring the stables. And what you're saying is that if you, you can either put your ETH in EigenLayer or you can put it on the layer too. And so right now, this thing, there's a tension here because any capital that goes into Eigenlayer is pulling away from liquidity in DeFi.
And so Renzo is trying to actually complete this circuit. And so when you put it into specifically the Renzo LRT, then actually that capital gets immediately returned back to the ecosystem in the layer two. Is this, are you natively minting EZETH? EZETH is Renzo's liquid restaked token. So this is your guys' particular one. Is EZETH natively minted on each of these Layer 2s? Or how does that actually flow back to the Layer 2? Yeah, so you're spot on. We're trying to close this loop because what's happening right now, that TVL has to get bridge back to mainnet, and the rollups are losing their TVL.
Their users want access to Eigenlayer, so we are going to provide that. EZETH will be natively minted on each of these L2s. And the nice thing is it's not just native ETH, but also if that L2 has their own LST, you're able to actually deposit both into Renzo and get one LRT token back. So the fungibility and the user experience is much better because you're not fragmenting liquidity. So that's like a Mantle ETH, for example. Is that kind of what you're alluding to? Exactly. So if you look at Mantle, METH could get deposited into Renzo on Mantle. You get EZETH back on Mantle. But if they also have native ETH, you could also put that into Renzo and you still get EZETH back.
And the reason that's really important, it seems like this slight differentiation, but the fungibility of a token is so important because for a user to have a good experience when we say good experience to actually be able to use d5 properly you need to have deep liquidity on dex's the more tokens that you have lrts kind of representing it you're fragmenting it and the user experience becomes really bad and then essentially you start compounding what the integrations could be whether it's a lending protocol an aggregator a per platform the deeper the liquidity the the better um experience that users have being able to use that uh asset okay so the strategy here from renzo is you guys are just using layered twos as like your top of capital funnel into the renzo liquid restaking protocol um is that uh is are there any other tricks up your guys sleeve or is that the main differentiator or like what else would you like to bring onto the table here yeah so uh we're starting off with mainnet so today you could go balancer uni v3 curve pool there's a pendle pool and there's a couple other integrations in the pipeline and then we're branching out to create the funnel um a bigger funnel for users to be able to actually access uh eigen layer and we're the only ones that have those inside incentives perfectly aligned.
The other piece that is super important, and we're going to start hearing about this a lot more as EigenLayer DA and EigenLayer Mainnet comes a little bit closer. All the frenzy right now is on points and these DeFi integrations, but where our team is actually focused. So there's 11 people now contributing to Renzo. We're doing all these things, but at the same time, we're spending a ton of time aligning on the risk management and how AVSs are going to be captured. And what we mean by that is it's a huge coordination effort between operators and AVSs to safely and efficiently be able to get capital and then return those rewards that are getting generated by AVSs back to the users.
And that sounds very simple, but there's quite a bit of complexity that's built in there. And not everybody's going to be able to capture those rewards. So, for example, we see points right now on LRTs to be able to attract users and capital. We think that's going to actually get shifted down towards AVSs because you're going to have new AVSs that launch that can't pay stakers in ETH, right? They don't have anybody using them, but they're trying to attract capital and solve for their cold start problem. So what are they going to do? They're going to incentivize an either point or their native token.
So thinking about these things and making sure that you have a protocol that not only accepts native ETH, but is also able to collect ERC-20 tokens as rewards and efficiently return those to the users. That's where you start getting this risk return optimal strategy that we're building within Renzo. Beautiful, beautiful. Okay, Lucas, what is near term on the roadmap that you want to highlight? What is getting users excited about Renzo? Yeah, the biggest thing is essentially what we're talking about right now. So in a couple of weeks here, you're going to see Renzo launch on Arbitrum and on BNB chain.
And in the coming weeks, you're going to see a half dozen other L2 announcements come out, whether it's BASE, whether it's Metis, whether it's Scroll. There's a lot of conversations going on with Linnea and bringing all these people to and all these ecosystems really to EigenLayer, right? So Renzo is becoming this settlement layer. And in order to be able to do that, we also have to take into take into consideration how risk is managed on the protocol. One last question before we tie this off here. What about becoming a validator in the Renzo system? Is this a closed? Is it open? What is the future of that look like?
Yeah. So the way Renzo is going to market, it's following a similar playbook that you saw Lido do a few years ago where there's a smaller set of operators, but they're extremely high quality. So right now, Figma and P2P are the two validators that are staking and will be restaking the assets deposited on Renzo. And over time, you'll see us decentralize that operator set. The reason that's really important is you want a high quality operator from a security standpoint securing these AVSs because every single AVS is different. And the operator has different requirements to be able to secure them.
And the coordination effort to secure something very new is extremely high. So you'll see maybe three to five operators in the early days. And then over time, we'll decentralize as things become more easier and less risky. Sure. Beautiful. Lucas, if people are piqued about Renzo, where should listeners go to find out more? Yeah. Just go to renzoprotocol.com. You could restate directly from mainnet. It's literally one click, super easy. We try to make it easy with EasyEth. Beautiful. Awesome. All those links will be available in the show notes. Lucas, thank you so much for joining me. Thanks, Dave, for having us.