Ethereum Network
Meta Pool on Ethereum (spETH)
Section titled “Meta Pool on Ethereum (spETH)”Meta Pool provides liquid staking on Ethereum. Stake ETH and receive spETH, a yield-bearing LST that accrues staking rewards while remaining usable in DeFi.
- Stake / unstake: metapool.app
- Product docs: spETH — benefits, liquidity pool for fast unstake, true price (ERC-4626), delayed unstake
- Historical alternate UI: Liquid Staking in BOS (NEAR Social widget; prefer metapool.app)
Meta Pool ETH staking uses distributed validators (including SSV Network integration, as noted elsewhere in these docs). You do not need to run your own 32 ETH validator to hold spETH.
Appendix: Ethereum client background
Section titled “Appendix: Ethereum client background”The Ethereum Network is composed of two layers, Execution Layer and Consensus Layer, both working together with their own clients.
To run a full Ethereum validator yourself (not required for Meta Pool liquid staking), you need a validator connected to a full node running both Consensus and Execution clients.
Execution Client
The execution client (also known as the Execution Engine, EL client or formerly the Eth1 client) listens to new transactions broadcasted in the network, executes them in EVM, and holds the latest state and database of all current Ethereum data.
| Client | Language | Operating systems | Networks | Sync strategies | State pruning |
|---|---|---|---|---|---|
| Geth | Go | Linux, Windows, macOS | Mainnet, Sepolia | Snap, Full | Archive, Pruned |
| Nethermind | C#, .NET | Linux, Windows, macOS | Mainnet, Sepolia, and more | Snap (without serving), Fast, Full | Archive, Pruned |
| Besu | Java | Linux, Windows, macOS | Mainnet, Sepolia, and more | Snap, Fast, Full | Archive, Pruned |
| Erigon | Go | Linux, Windows, macOS | Mainnet, Sepolia, and more | Full | Archive, Pruned |
Consensus Client
The consensus client (also known as the Beacon Node, CL client or formerly the Eth2 client) implements the proof-of-stake consensus algorithm, which enables the network to achieve agreement based on validated data from the execution client.
| Client | Language | Operating systems | Networks |
|---|---|---|---|
| Lighthouse | Rust | Linux, Windows, macOS | Beacon Chain, Sepolia, and more |
| Lodestar | TypeScript | Linux, Windows, macOS | Beacon Chain, Sepolia, and more |
| Nimbus | Nim | Linux, Windows, macOS | Beacon Chain, Sepolia, and more |
| Prysm | Go | Linux, Windows, macOS | Beacon Chain, Gnosis, Sepolia, and more |
| Teku | Java | Linux, Windows, macOS | Beacon Chain, Gnosis, Sepolia, and more |
A consensus client serves as a Beacon Node for validators to connect. Each consensus client has its own validator software described in detail in its respective documentation.