Liquid Collective

Liquid Collective is a liquid staking protocol aimed at businesses that offer staking to their customers: exchanges, custodians, brokers and wallet providers. A depositor stakes ETH or SOL through the protocol and receives LsETH or LsSOL, a token that represents the staked asset plus rewards and can be held, transferred or used in DeFi.

Its documentation describes it as built and governed by a collective of Web3 teams including The Liquid Foundation. The website terms, dated 21 November 2022, name The Liquid Foundation as the operator of liquidcollective.io and give a contact address care of Leeward Management Limited in Camana Bay, Grand Cayman; they choose New York law. Alluvial is listed as a service provider and supplies the APIs that platforms use to onboard users, alongside Exiger, Rated and Hypernative. Liquid Collective does not publish founders' names in the pages we reviewed.

Its supported-platforms list includes Coinbase, Kraken, Anchorage Digital, BitGo, Fireblocks, Copper, Bitcoin Suisse, Galaxy and FalconX, grouped into platforms that mint, custody or give access to LsETH. Recent announcements on its site include FalconX joining in October 2025 and a Galaxy partnership in December 2025.

LsETH follows the cToken model: the number of tokens a holder has stays the same, and the conversion rate, the amount of ETH each LsETH represents, rises as rewards accrue. Every 24 hours oracles report the staked balance and the River contract updates the rate. Consensus rewards and execution-layer fees, including MEV, are restaked automatically. If validators are penalised or slashed badly enough, the rate can fall.

Deposits first sit in a deposit buffer and are committed to the consensus layer based on oracle reports, with an average delay of about 24 hours according to the FAQ. Stake is spread across the approved node operators in round-robin order. Withdrawal keys point to the protocol contract; node operators keep their validator signing keys.

Rewards and penalties are socialised: every LsETH holder shares in the performance of all of the protocol's validators, so one operator's MEV windfall or penalty is spread across everyone. On Solana, LsSOL works on the same principle and has launched on Orca, according to the Liquid Collective site.

The protocol service fee is 10% of network rewards, collected by minting new LsETH. That LsETH is split among node operators, platforms, wallet and custody providers, service providers, the Slashing Coverage Treasury and the Liquid Collective DAO. The docs do not publish how the 10% is divided among those parties.

The same documentation page also says, in its reward-distribution section, that LsETH holders receive 85% of network rewards, which does not match a 10% fee. Liquid Collective does not explain the remaining 5%. A user comparing net yields should treat 90% as the figure implied by the stated fee and ask the platform for its own terms, since a platform can add its own charge on top. For how its fee and liquidity compare with other liquid staking tokens, see how Liquid Collective compares with other liquid staking protocols.

Minting and redeeming LsETH are permissioned. A wallet must be on the protocol's Allowlist, and platforms add addresses only after their own KYC or KYB, AML and sanctions checks. In practice an individual stakes through a platform account rather than through a public dapp. Transfers of LsETH are open, so anyone can buy, hold or use it in DeFi without being allowlisted, but they cannot redeem it for ETH directly.

The website terms exclude residents and entities in Iran, Cuba, North Korea, Syria, Myanmar and the Crimea, Donetsk and Luhansk regions, and anyone on sanctions lists. The protocol also has an access-denial mechanism that can block an address from sending, receiving, minting or redeeming LsETH. Its stated policy is to use it only for security threats or legal requirements, and the docs say there is no way to force a transfer or change a balance.

Liquid Collective's contracts have been reviewed by several firms. Its audit page lists Halborn (July 2022), six Spearbit reviews between September 2022 and October 2023, including the code that enabled redemptions, a Quantstamp audit of off-chain components (May 2024), and Certora formal verification with manual audits in November 2024 and March 2026. Every feature deployed to mainnet has been reviewed by at least one of these teams, it says. A vulnerability disclosure policy is published on GitHub.

Control is less decentralised than the word DAO suggests. The FAQ says a multisig wallet with ecosystem participants governs the protocol and will move to more on-chain execution over time, and that a governance token is planned. The docs we reviewed do not give the multisig's threshold or signers, or any upgrade timelock.

The slashing coverage program is the distinctive part. It has three layers: bespoke Nexus Mutual cover that scales with assets on the platform, a Slashing Coverage Treasury funded continuously with a share of rewards, and node operator commitments that cover deductibles up to a cap for faults in their own infrastructure. The size of the treasury and the caps are not published in the pages we read. We found no hack, depeg or loss event involving Liquid Collective in its own disclosures or in DefiLlama's hacks database as of October 2026.

Staking happens through a platform. A user completes the platform's onboarding checks, the platform submits the wallet to the Allowlist through Alluvial's API, and the user can then deposit ETH and receive LsETH. Any amount can be staked.

Redemptions were enabled in June 2023 after Ethereum's Shapella upgrade. A redemption request joins a first-in, first-out queue. It is filled from the redemption buffer, from ETH moved over from the deposit buffer, or from validator exits; when a validator has to exit, Ethereum's exit and withdrawal queues set the pace, which the docs say can take minutes to days. Holders who are not allowlisted exit by selling LsETH on a secondary market.

Liquid Collective does not run a retail help desk; support for staking accounts comes from the platform the user signed up with. The protocol publishes news and documentation on its website, keeps code and audits on GitHub, and posts on X as @liquid_col and in a Telegram channel. Requests to block an address must be made in writing under its access policy.