Figment’s average SRR throughout Q2 was 5.6%. When Figment Validators were selected to propose blocks, they outperformed the median EL rewards by ~3%. View the Ethereum Validator Insights Q2 2023 Report here.

There are two different types of ETH rewards. 

Consensus layer (CL) rewards consist of new issuance from attestations, block proposals, and sync committee participation. Including evidence of slashable events in a block is also a source of CL rewards. Even though on a per block basis the rewards for proposing are much higher, over the long term, the vast majority of CL rewards come from attestations.

Execution layer (EL) rewards are received by validators only when they are proposing blocks, which is a random and infrequent event. EL rewards include MEV rewards and tips (i.e., priority fees).

The CL rewards account for the majority of the rewards in the second quarter of 2023 at ~68% compared to ~32% for EL rewards. Check out our Ethereum Validator Insights Q2 2023 Report here.

You can view, in detail, your staking rewards on the Figment Staking App or via Figment’s Rewards API. Learn more about post-Merge rewards.

Unstaking on Ethereum requires permanently exiting your validator from the active set. The total amount of time it takes to unstake on Ethereum varies and is a function of the number of currently active validators and how many are requesting to exit. After requesting to exit, a validator first enters the exit queue (of which 8 validators are currently dequeued per epoch) and is still subject to rewards and penalties while in this queue. Once the validator has left the exit queue, the validator no longer earns rewards and waits an additional 256 epochs (27.3 hours) until it becomes eligible for the withdrawal sweep. Ethereum processes 16 withdrawals per block in order of validator index. Currently,  this process can take several days. Take a look at our unstaking time estimator in the Figment App and learn more about the process in depth here.

Figment provides rewards reporting via the Figment Staking App, CSV files and the Rewards API.

Post Shanghai & Capella upgrades, partial withdrawals allow stakers to access a portion of their CL rewards, i.e., any amount above 32 ETH, while continuing to stake. Execution layer rewards are liquid almost immediately as they are received by validators while Consensus layer rewards are made liquid periodically (currently every ~4 days per validator) by Ethereum. View the detailed composition of your rewards on the Figment Saking App.

When staking ETH with Figment, all rewards are sent automatically to your validator’s withdrawal address.

Figment mitigates ETH staking risks such as slashing by applying its “safety over liveness” approach, which prioritizes security. Figment takes a four layer approach to slashing risk mitigation in our Ethereum infrastructure. 

1. Automated, deterministic key distribution across validator clients upon generation to ensure only one validator key is deployed to one validator client.
2. Local anti-slashing database per VC that records every block and attestation signed by validators. The validator client uses this information to avoid attesting or proposing two different attestations or blocks for the same slot.
3. The Remote Signer acts as a universal slashing database across all validator clients to detect multiple signatures for the same block height to prevent a double-signing event.
4. Private keys stored separately from signing infrastructure in zero-trust secured vault.

To learn more, read “What does Safety Over Liveness Really Mean?” in the Figment Insider Q3 Report.

A maximum of 250 validators (or 8000 ETH) can be staked in a single transaction with Figment by using our audited and battled tested batch smart contract.

Transactions for depositing to validators incur gas and transaction fees, so it is recommended to keep some extra ETH liquid in the wallet from which you wish to stake when depositing. Figment’s commission for staking ETH is tailored to each customer based on their staking volume.

Figment supports both the Lighthouse and Teku Ethereum clients. Multiple client implementations can make the network stronger by reducing its dependency on a single codebase. Figment supports multiple clients to avoid client concentration and reduce the impact of a client-specific problem leading to potential penalties.

Figment supports multiple MEV relays: Flashbots and Blocknative. Multi-relay support helps maximize the rewards derived from MEV-Boost.