Alluvial

• Name: Alluvial
• URL: https://alluvial.finance/
• Category: staking infrastructure / liquid-staking integration API / institutional staking operations platform
• Tags: ethereum-ecosystem
• Summary: Alluvial is institutional staking middleware, not a staking primitive. The useful cut is the company/protocol split: Liquid Collective is the protocol, while Alluvial sells the API, onboarding, reporting, and workflow layer around it. SMS broadens that into a more general Ethereum staking operations console, but the leverage is still in workflow defaults and integration control, not in new validator mechanics.
• What it does:
  • Provides enterprise APIs that let platforms integrate Liquid Collective liquid staking, including onboarding, reporting, accounting, and related operational support
  • Maps institutional account structures into technical resources such as organizations, depositors, and wallets, with explicit guidance for custodial vs. non-custodial and segregated vs. omnibus setups
  • Publishes technical guides for ETH staking and LsETH redemptions that combine smart-contract interactions with offchain API calls
  • Offers Alluvial SMS, a staking management system for institutions that want automated workflows, multi-operator coordination, multi-custodian setups, auto-compounding, and configurable staking strategies
  • Positions itself as the software-development and integration layer around Liquid Collective rather than as the protocol itself
• Key claims:
  • The docs explicitly say Liquid Collective is the protocol while Alluvial is the software development company supporting that protocol’s development and ecosystem growth, which is the main categorization clue
  • The architecture docs are concrete about the real integration model, including how a platform’s internal account structure maps to Alluvial API resources and where signing responsibility lives in custodial and non-custodial flows
  • The staking and redemption guides show that Alluvial is not just selling a brochure layer; it exposes contract-call flows, redemption-status APIs, timing projections, and queue mechanics around LsETH
  • The enterprise APIs page says institutions can add Liquid Collective support within weeks and access onboarding, reporting, and accounting through Alluvial’s API layer, reinforcing the company’s role as integration middleware
  • The SMS product broadens the picture from liquid-staking integration into a more general institutional staking-control-plane story through multi-operator orchestration and configurable staking workflows
• Whitepaper: No canonical Alluvial whitepaper or litepaper surfaced in this pass. The strongest current source of truth is the official documentation plus the company product pages, with Liquid Collective docs needed to understand the protocol layer Alluvial supports; see ../whitepapers/alluvial-primary-sources-2026-04-27.md.
• Sources:
  • https://alluvial.finance/
  • https://alluvial.finance/enterprise-apis/
  • https://alluvial.finance/sms/
  • https://docs.alluvial.finance/
  • https://docs.alluvial.finance/readme.md
  • https://docs.alluvial.finance/readme.md?ask=What%20does%20Alluvial%20actually%20provide%20to%20institutional%20customers%2C%20what%20is%20the%20relationship%20to%20Liquid%20Collective%2C%20and%20which%20primary%20technical%20docs%20best%20explain%20its%20architecture%2C%20staking%2C%20and%20redemption%20flows%3F
  • https://docs.alluvial.finance/guides/supplemental_guides/architecture.md
  • https://docs.alluvial.finance/guides/supplemental_guides/staking.md
  • https://docs.alluvial.finance/guides/supplemental_guides/redemptions.md

Internal linkages

• Keep this note on the clearest adjacent reads: liquid-collective, stakewise, and figment.

Control surface

• The leverage is in onboarding, account mapping, approval flow, reporting, custody integration patterns, redemption handling, and which validator or liquidity paths SMS makes easy by default.

• Liquid Collective supplies the staking rail. Alluvial sells the workflow wrapper around it.

• Last reviewed: 2026-06-05 UTC