# Ethereum (staking and Replace by Nonce) The generic [Operator](/helpcenter2/for-operators/operators-overview.md) and [Administrator](/helpcenter2/overview.md) guides cover Ethereum. Two things are Ethereum-specific: **Pectra staking** and **Replace by Nonce (RBN)**. ## Pectra staking Ethereum staking on Webapp 2.0 uses the network's **Pectra** model, which lets a single validator hold a larger balance and compound its own rewards. You stake through one of Ledger Enterprise's supported staking **providers** (partners), shown by company name, for example Figment, Chorus One, Luganodes, Galaxy, Globalstake, P2P, Kiln, and Everstake. ### Before you can stake An Administrator enables a **Staking ruleset** on the Ethereum account (during [create or edit](/helpcenter2/creating-and-editing-accounts.md)), limited to multi-authorization and threshold rules. An **Operator must be part of that ruleset** to see the Staking tab and stake. See [Governance rules & whitelists](/helpcenter2/governance-rules-and-whitelists.md). ### Start staking From the account's Staking tab, choose to start staking. You enter the **total amount** to stake and pick a **provider**; a **validator-count selector** (1 to 20) then appears. The default count is the total divided down into roughly 2,048-ETH validators, and the amount is split evenly across them, with any remainder left in the account. All validators in one request go to the single provider you chose, and the whole batch is submitted as one Ethereum transaction. Two limits are enforced per validator: * a **minimum of 32 ETH** per validator, and * a **maximum of 2,048 ETH** per validator. If the provider can't supply the requested number of validators, you're asked to retry or reduce the count. ### Manage a position Each Pectra (0x02) staking position offers, in priority order: * **Withdraw**: partially withdraw, or use **Max** for a full exit. Pectra requires at least 32 ETH to remain in a position unless you're doing a full exit. * **Top-up**: add to the position (up to the 2,048-ETH cumulative cap). The position you started from is fixed as the target. * **Consolidate**: merge this position into another Pectra position (two at a time, up to the 2,048-ETH cap). The amount is the full position; you choose the target validator. ### Legacy positions and upgrading An older **legacy (0x01)** position isn't supported for ongoing management and shows an **Upgrade to Pectra** action. Upgrading converts the position's credentials (covering its full 32 ETH) to Pectra so it can compound and be managed. The validator provider doesn't change when you upgrade, and remains unknown, because that information isn't published on-chain. > **Note:** In the history, **Upgrade** and **Consolidate** operations are labelled as such with their own icon. Reviews on your device show the relevant details: for a batch stake, each validator and its amount; for a consolidate or upgrade, the source and target validators. ## Replace by Nonce (RBN) Ethereum's equivalent of [Bitcoin's Replace by Fee](/helpcenter2/network-specific-guidance/bitcoin-replace-by-fee.md) is **Replace by Nonce (RBN)**: when an Ethereum transaction is stuck unconfirmed, you can replace it to **speed it up or cancel it**. The flow and behaviour mirror RBF almost exactly. The difference is that, because Ethereum orders transactions by nonce, the review shows the **replaced nonce** of the transaction being superseded. As with RBF, the actions appear only while the transaction is still replaceable, the original request ends up **Cancelled** with its approvals intact and no resulting operation, and only the replacement appears in the operations history once confirmed. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.enterprise.ledger.com/helpcenter2/network-specific-guidance/ethereum-staking-and-replace-by-nonce.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.