When people hear of staking, there are often two modes of thought:
While these two views are closely intertwined, there have been fewer discussions about how to think about (2) when one considers the world of restaking and liquid restaking — this post aims to bridge this gap.
Staking allows token holders to earn interest on their capital by contributing to the security of a blockchain. In exchange for locking their capital and performing their duties (including validating blocks, proposing blocks, or generating proofs), stakers are compensated with new tokens. In this way, staking is a perpetual duration bond. The staker lends their economic value to the protocol in exchange for interest and the ability to regain their principal upon stopping their participation. In addition to locking up their capital, stakers are also responsible for honoring the protocol; they forfeit their principal if they commit an attributable slashing violation [0]. Stakers may run validators but commonly delegate to a third-party node operator. This delegation also fits nicely into the bond analogy. The delegated staker lends their tokens to a node operator, who pays the interest and keeps the additional profit.
Restaking extends this paradigm to allow token owners to use their capital to provide economic security to multiple protocols. In the parlance of Eigenlayer 8, each of these protocols is termed an Actively Validated Service (abbr. AVS). By doing so, capital earns additional rewards exceeding the underlying staking yield while also being subject to additional slashing conditions. As with regular staking, capital owners may choose to run their services, but delegation is the likely outcome for most tokens in the system; the delegated restaker lends their tokens to a node operator, who participates in protocols to earn further rewards paid as interest. Restaking offers a clean generalization to staking but adds complexity and layering to the protocol mechanisms. Additionally, restaking may grow to present a risk to the underlying core protocol by subsuming a significant portion of the stake. Vitalik voiced this concern early, penning “Don’t overload Ethereum’s consensus.” 19
Liquid staking tokens (LSTs) represent an extension to delegated staking by issuing tokens to represent the staker share of the capital in the pool. These tokens represent a fraction of the capital and node-operator generated fees, allowing usage of the assets within DeFi by providing delegators liquidity (at a cost). Liquid staking tokens first became popularized as a way to realize liquidity or take leverage on locked beacon chain positions that were not withdrawable before the Merge.
In much the same way, liquid restaking tokens 8 (LRTs) are garnering significant attention. While LSTs represent a basket of L1 stake positions, a basket of restaked positions underwrites LRTs. LRTs, analogous to the growth of LSTs before the Merge, present a way to provide liquidity and/or leverage to users who are restaking within Eigenlayer before the launch of AVSs such as EigenDA. While this distinction seems innocuous, it contains many subtleties that make LRTs a meaningfully differentiated asset class. We outline a brief timeline of events over the past four years to contextualize the extreme growth of LRTs in the past two months.
The figure below provides a recent timeline of milestones within traditional, staking, and restaking markets. These events illustrate similarities in asset adoption, highlighting temporally correlated risks between these markets.
diagram-202402262486×906 435 KB
We present an asset-backed case study to help illustrate the relationships between these instruments, dividing them into two tables and incorporating the concepts above alongside the traditional finance counterparts.
For each of the six assets, we walk one-by-one through five attributes:
The following sections follow the above numbering, with each attribute defined at the beginning of each section.
We note the similarities and differences between traditional financial instruments (sovereign bonds and bond funds). One can view a sovereign bond as non-fungible because a sovereign sells each bond to an entity (an individual, a corporation, or another sovereign). If the buyer ‘holds to maturity’ (e.g., akin to Silicon Valley Bank, discussed in Section 4), their position is only salable in a peer-to-peer transaction. In the staking context, this is equivalent to an L1 staker selling their private keys to another individual – the same ‘level’ of non-fungibility as a bond. We note that there also exist explicit sovereign bonds that do not allow for resale whatsoever (US savings bonds that are explicitly non-transferrable).
Individuals owning money market funds 2 and capital in savings accounts constitute a significant portion of sovereign bonds. One can think of this as analogous to delegating funds to a fund operator or commercial bank in exchange for interest payments less a fee (much like the role of node operators for an LST). These funds tend to hold many bond positions of different maturities, á la a LST with many different L1 positions held through a set of node operators. As we discuss below, the rules for creating or redeeming shares in such funds can vary (see here 3 for example). We consider any such fund a bond fund, as it shares features with LST positions [1].
Editorial note — The following is a Gedanken or thought experiment and a (hopefully) valuable framework for understanding the different properties of LRTs in the context of assets that the reader is more familiar with. This list is not exhaustive, nor is each analogy perfect; we merely found it helpful as a lens to reason about the ever-more complex staking landscape. We note that, for instance, different LRTs have different withdrawal or redemption conditions and/or AVS allocation strategies, which can meaningfully change the risk inherent to holding these assets.
We begin our journey with the Liquidity & Leverage category, the simplest when comparing these assets. We clump these two concepts together because they dovetail nicely; more liquid assets are more straightforward to borrow against and thus create better leverage opportunities. To be more precise, we define these terms explicitly (these are just the definitions as we use them – we do not aim to be authoritative):
Liquidity: The liquidity of an asset is a measure of the transaction cost (in percentage terms) that it takes to divest X units in exchange for a numéraire. The more liquid an asset, the lower the transaction cost to divest a range of sizes of X.
Leverage: Leverage refers to the ability to borrow against an asset to reinvest. Whether through direct lending (such as collateralized on-chain lending) or synthetic forms (such as perpetual futures), a levered user increases the risk of loss of their initial investment if they violate the default conditions of the loan (e.g., due to a loss in value of collateral or margin). On the other hand, the user increases their payoff with leverage if the asset price appreciates substantially.
upload_0dcdfa035aceb6fb7393a85f9072900a2102×784 43.5 KB
Table 1 assets
Table 2 assets
Key points:
The second attribute we consider is yield.
Yield: Interest earned on an investment.
For the non-fungible assets (Table 1), we analyze both the source, the generator of the interest, and the denomination, the unit-of-account of the interest. For the fungible assets (Table 2), we also examine the aggregation, how the yields of many individual instruments are combined.
upload_9401f6c48943e6d125ab2ed847429f942294×902 204 KB
Table 1 assets
Table 2 assets
Key points:
The third attribute we consider is duration.
Duration: The amount of time an investment lasts. We also define it as how long it takes to withdraw the underlying principal without selling the asset on the open market.
upload_cbbc8afb2ee8eb6536713c02b89623d72224×956 228 KB
Table 1 assets
Table 2 assets
Note that “native restaked ETH” (where the restaker also controls the L1 staking position) and “liquid restaked ETH” (where the restaker uses an LST) may have different rate limits from the restaking protocol itself too. In the case of EigenLayer, all unstaking incurs a 7-day escrow period 3 in addition to the AVS and Ethereum rate limits. For liquid restaked ETH, the withdrawal may be from the restaking position alone and not from the L1 protocol. Long story short, durations for these instruments are critically detail-dependent.
Key points:
The fourth attribute we consider is default conditions.
Default: The event when the principal investment is not returned to the lender upon request. TradeFi and DeFi have different default procedures, so we informally use the term to refer to a situation where the instrument liabilities exceed the underlying assets.
upload_23d4b8bc066435357be0d5c431d0db262424×972 248 KB
Table 1 assets
Table 2 assets
Key points:
The fifth and final attribute we consider is portfolio construction.
Portfolio construction: The selection process for the assets that underpin a basketized product.
Note that the non-fungible (Table 1) assets do not require portfolio construction; this attribute only applies to the construction of the fungible basket assets (Table 2).
upload_9f9b65ccef864f0ea65974807cdb03812548×894 204 KB
Table 1 assets
Table 2 assets
Key points:
Combining each row we iterated above, let’s construct our complete asset + attribute table!
upload_4ec421de37c3268c40543a9b9b2fc83d1754×1494 440 KB
While the tabular text maximally captures the essence of this article, it is helpful to distill some of the themes. To that end, we present two additional diagrams encapsulating the ~attributable essence~ of each section. The first diagram draws the link between the non-fungible and fungible assets.
upload_197d86e7088bbd762e73f31fcc71c90b1766×1458 376 KB
Moving left to right, we highlight the five aforementioned attributes (e.g., “going from L1 staking positions to LSTs liquifies and enables leverage on the asset”). Each number maps to the corresponding section above.
In addition to comparing the two tables, we also consider the following progressions within the non-fungible and fungible classes:
The figure below captures the theme of each attribute when using this “top-down” view.
upload_4615bcbcc26dc01a370489ea8f4f2a821702×1426 358 KB
Again, each number maps to the corresponding section above. The (5) box only applies to the right “fungible” set of assets, and thus is connected only to the right side.
Phew … that was … a lot. Thanks for sticking with us. The exasperated reader may wonder, “So what?”; this reaction is justified :D. Reiterating the two-fold goals of this article:
“That’s it…? It took you 4500 words to say that?”. Well dear reader, yes, “that’s it, that’s all.” 38
Footnotes:
[0] This is slightly different than a bond where the counterparty is the source of a default, which closer resembles the delegated staking setting
[1] We note that the centralized nature of bond funds means that the creation-redemption, trade execution, and custody semantics are different from those of LSTs and likely impact the precise financial performance of these assets differently than LSTs. In this note, we ignore these differences for the sake of simplicity.
When people hear of staking, there are often two modes of thought:
While these two views are closely intertwined, there have been fewer discussions about how to think about (2) when one considers the world of restaking and liquid restaking — this post aims to bridge this gap.
Staking allows token holders to earn interest on their capital by contributing to the security of a blockchain. In exchange for locking their capital and performing their duties (including validating blocks, proposing blocks, or generating proofs), stakers are compensated with new tokens. In this way, staking is a perpetual duration bond. The staker lends their economic value to the protocol in exchange for interest and the ability to regain their principal upon stopping their participation. In addition to locking up their capital, stakers are also responsible for honoring the protocol; they forfeit their principal if they commit an attributable slashing violation [0]. Stakers may run validators but commonly delegate to a third-party node operator. This delegation also fits nicely into the bond analogy. The delegated staker lends their tokens to a node operator, who pays the interest and keeps the additional profit.
Restaking extends this paradigm to allow token owners to use their capital to provide economic security to multiple protocols. In the parlance of Eigenlayer 8, each of these protocols is termed an Actively Validated Service (abbr. AVS). By doing so, capital earns additional rewards exceeding the underlying staking yield while also being subject to additional slashing conditions. As with regular staking, capital owners may choose to run their services, but delegation is the likely outcome for most tokens in the system; the delegated restaker lends their tokens to a node operator, who participates in protocols to earn further rewards paid as interest. Restaking offers a clean generalization to staking but adds complexity and layering to the protocol mechanisms. Additionally, restaking may grow to present a risk to the underlying core protocol by subsuming a significant portion of the stake. Vitalik voiced this concern early, penning “Don’t overload Ethereum’s consensus.” 19
Liquid staking tokens (LSTs) represent an extension to delegated staking by issuing tokens to represent the staker share of the capital in the pool. These tokens represent a fraction of the capital and node-operator generated fees, allowing usage of the assets within DeFi by providing delegators liquidity (at a cost). Liquid staking tokens first became popularized as a way to realize liquidity or take leverage on locked beacon chain positions that were not withdrawable before the Merge.
In much the same way, liquid restaking tokens 8 (LRTs) are garnering significant attention. While LSTs represent a basket of L1 stake positions, a basket of restaked positions underwrites LRTs. LRTs, analogous to the growth of LSTs before the Merge, present a way to provide liquidity and/or leverage to users who are restaking within Eigenlayer before the launch of AVSs such as EigenDA. While this distinction seems innocuous, it contains many subtleties that make LRTs a meaningfully differentiated asset class. We outline a brief timeline of events over the past four years to contextualize the extreme growth of LRTs in the past two months.
The figure below provides a recent timeline of milestones within traditional, staking, and restaking markets. These events illustrate similarities in asset adoption, highlighting temporally correlated risks between these markets.
diagram-202402262486×906 435 KB
We present an asset-backed case study to help illustrate the relationships between these instruments, dividing them into two tables and incorporating the concepts above alongside the traditional finance counterparts.
For each of the six assets, we walk one-by-one through five attributes:
The following sections follow the above numbering, with each attribute defined at the beginning of each section.
We note the similarities and differences between traditional financial instruments (sovereign bonds and bond funds). One can view a sovereign bond as non-fungible because a sovereign sells each bond to an entity (an individual, a corporation, or another sovereign). If the buyer ‘holds to maturity’ (e.g., akin to Silicon Valley Bank, discussed in Section 4), their position is only salable in a peer-to-peer transaction. In the staking context, this is equivalent to an L1 staker selling their private keys to another individual – the same ‘level’ of non-fungibility as a bond. We note that there also exist explicit sovereign bonds that do not allow for resale whatsoever (US savings bonds that are explicitly non-transferrable).
Individuals owning money market funds 2 and capital in savings accounts constitute a significant portion of sovereign bonds. One can think of this as analogous to delegating funds to a fund operator or commercial bank in exchange for interest payments less a fee (much like the role of node operators for an LST). These funds tend to hold many bond positions of different maturities, á la a LST with many different L1 positions held through a set of node operators. As we discuss below, the rules for creating or redeeming shares in such funds can vary (see here 3 for example). We consider any such fund a bond fund, as it shares features with LST positions [1].
Editorial note — The following is a Gedanken or thought experiment and a (hopefully) valuable framework for understanding the different properties of LRTs in the context of assets that the reader is more familiar with. This list is not exhaustive, nor is each analogy perfect; we merely found it helpful as a lens to reason about the ever-more complex staking landscape. We note that, for instance, different LRTs have different withdrawal or redemption conditions and/or AVS allocation strategies, which can meaningfully change the risk inherent to holding these assets.
We begin our journey with the Liquidity & Leverage category, the simplest when comparing these assets. We clump these two concepts together because they dovetail nicely; more liquid assets are more straightforward to borrow against and thus create better leverage opportunities. To be more precise, we define these terms explicitly (these are just the definitions as we use them – we do not aim to be authoritative):
Liquidity: The liquidity of an asset is a measure of the transaction cost (in percentage terms) that it takes to divest X units in exchange for a numéraire. The more liquid an asset, the lower the transaction cost to divest a range of sizes of X.
Leverage: Leverage refers to the ability to borrow against an asset to reinvest. Whether through direct lending (such as collateralized on-chain lending) or synthetic forms (such as perpetual futures), a levered user increases the risk of loss of their initial investment if they violate the default conditions of the loan (e.g., due to a loss in value of collateral or margin). On the other hand, the user increases their payoff with leverage if the asset price appreciates substantially.
upload_0dcdfa035aceb6fb7393a85f9072900a2102×784 43.5 KB
Table 1 assets
Table 2 assets
Key points:
The second attribute we consider is yield.
Yield: Interest earned on an investment.
For the non-fungible assets (Table 1), we analyze both the source, the generator of the interest, and the denomination, the unit-of-account of the interest. For the fungible assets (Table 2), we also examine the aggregation, how the yields of many individual instruments are combined.
upload_9401f6c48943e6d125ab2ed847429f942294×902 204 KB
Table 1 assets
Table 2 assets
Key points:
The third attribute we consider is duration.
Duration: The amount of time an investment lasts. We also define it as how long it takes to withdraw the underlying principal without selling the asset on the open market.
upload_cbbc8afb2ee8eb6536713c02b89623d72224×956 228 KB
Table 1 assets
Table 2 assets
Note that “native restaked ETH” (where the restaker also controls the L1 staking position) and “liquid restaked ETH” (where the restaker uses an LST) may have different rate limits from the restaking protocol itself too. In the case of EigenLayer, all unstaking incurs a 7-day escrow period 3 in addition to the AVS and Ethereum rate limits. For liquid restaked ETH, the withdrawal may be from the restaking position alone and not from the L1 protocol. Long story short, durations for these instruments are critically detail-dependent.
Key points:
The fourth attribute we consider is default conditions.
Default: The event when the principal investment is not returned to the lender upon request. TradeFi and DeFi have different default procedures, so we informally use the term to refer to a situation where the instrument liabilities exceed the underlying assets.
upload_23d4b8bc066435357be0d5c431d0db262424×972 248 KB
Table 1 assets
Table 2 assets
Key points:
The fifth and final attribute we consider is portfolio construction.
Portfolio construction: The selection process for the assets that underpin a basketized product.
Note that the non-fungible (Table 1) assets do not require portfolio construction; this attribute only applies to the construction of the fungible basket assets (Table 2).
upload_9f9b65ccef864f0ea65974807cdb03812548×894 204 KB
Table 1 assets
Table 2 assets
Key points:
Combining each row we iterated above, let’s construct our complete asset + attribute table!
upload_4ec421de37c3268c40543a9b9b2fc83d1754×1494 440 KB
While the tabular text maximally captures the essence of this article, it is helpful to distill some of the themes. To that end, we present two additional diagrams encapsulating the ~attributable essence~ of each section. The first diagram draws the link between the non-fungible and fungible assets.
upload_197d86e7088bbd762e73f31fcc71c90b1766×1458 376 KB
Moving left to right, we highlight the five aforementioned attributes (e.g., “going from L1 staking positions to LSTs liquifies and enables leverage on the asset”). Each number maps to the corresponding section above.
In addition to comparing the two tables, we also consider the following progressions within the non-fungible and fungible classes:
The figure below captures the theme of each attribute when using this “top-down” view.
upload_4615bcbcc26dc01a370489ea8f4f2a821702×1426 358 KB
Again, each number maps to the corresponding section above. The (5) box only applies to the right “fungible” set of assets, and thus is connected only to the right side.
Phew … that was … a lot. Thanks for sticking with us. The exasperated reader may wonder, “So what?”; this reaction is justified :D. Reiterating the two-fold goals of this article:
“That’s it…? It took you 4500 words to say that?”. Well dear reader, yes, “that’s it, that’s all.” 38
Footnotes:
[0] This is slightly different than a bond where the counterparty is the source of a default, which closer resembles the delegated staking setting
[1] We note that the centralized nature of bond funds means that the creation-redemption, trade execution, and custody semantics are different from those of LSTs and likely impact the precise financial performance of these assets differently than LSTs. In this note, we ignore these differences for the sake of simplicity.