REVIEW 1 cited by
SoK: Liquid Staking Tokens (LSTs) and Emerging Trends in Restaking
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
read the original abstract
Liquid staking and restaking represent recent innovations in Decentralized Finance (DeFi) that garnered user interest and capital. Liquid Staking Tokens (LSTs), tokenized representations of staked tokens on Proof-of-Stake (PoS) blockchains, are the leading staking method. LSTs offer users the ability to earn staking rewards while maintaining liquidity, enabling seamless integration into DeFi protocols and free tradeability. Restaking builds upon this concept by allowing staked tokens, LSTs or native Bitcoin tokens to secure additional protocols and PoS chains for supplementary rewards. Liquid Restaking Tokens (LRTs) unlock liquidity of restaked assets. This Systematization of Knowledge (SoK) establishes a comprehensive framework for the technical and economic models of liquid staking protocols. Using this framework, we systematically compare protocols mechanics, including node operator selection, staking reward distribution, and slashing. Our empirical analysis of token performance reveals that protocol design and market dynamics impact token market value. We further present the recent developments in restaking and discuss associated risks and security implications. Lastly, we review the emerging literature on liquid staking and restaking.
Forward citations
Cited by 1 Pith paper
-
Liquefaction: Privately Liquefying Blockchain Assets
Liquefaction demonstrates that private keys inside trusted execution environments can be encumbered with multi-user policies, enabling private, policy-controlled sharing of blockchain assets that breaks the single-own...
Discussion (0). Continue with ORCID to comment.