Event: “Liquid Staking: The Next Big Wave” — a Panel in NYC Presented by Coinbase Cloud and Alluvial A panel discussion on Liquid Collective and liquid staking, with representatives from Coinbase Custody, Alluvial, Figment, Kiln, Kraken, and Coinbase Cloud. Presented by Coinbase Cloud and Alluvial at the Messari Mainnet conference in NYC. Watch the video →
Liquid staking is a rapidly growing alternative to locking up a user's tokens and contributing to the security of proof-of-stake blockchains. Whereas traditional methods of staking are subject to bonding and unbonding periods (ranging from days to weeks), liquid staking provides stakers with increased liquidity and capital efficiency. Token holders stake their token and receive a receipt token as evidence of their ownership of their staked token. The receipt token can be transferred, stored, traded, and utilized in DeFi or supported dapps.
Liquid Collective is the secure liquid staking standard: a protocol with multi-chain capabilities designed to meet the needs of institutions, built and run by a collective of leading web3 teams. The protocol is stewarded by an independent industry consortium, which includes The Liquid Foundation, Alluvial, Coinbase Cloud, Figment, Kiln, Rome Blockchain Labs, Kraken, Staked, and other web3 industry participants. Liquid Collective will be governed in a decentralized manner by a broad and dispersed community of industry participants.
Liquid Staked ETH (LsETH) is the receipt token programmatically generated when users stake ETH through the Liquid Collective protocol. Dive into LsETH, its use cases, the risks of liquid staking, the tax implications, and more. Read more about LsETH.
The Liquid Collective protocol uses a cToken model for the LsTokens. The cToken evidences ownership of a staked token plus any accrued staking rewards and less any slashing penalties and fees. The conversion rate between the receipt token and the corresponding tokens continues to reflect the staked tokens + staking rewards — penalties and fees. The aToken model continuously updates the supply of a representative token to track the underlying token 1:1. This model can also be referred to as a rebase token model.
Yes. Halborn has successfully completed one audit in August and a second audit will be completed in September. The Alluvial, Kiln, and Figment teams remediated the issues identified during the audit process and received final validation from Halborn. View results of the Halborn audit.