Original Validator FAQ

1.Has the rETH product been audited?

Yes, the rETH has passed the security audit conducted by top blockchain security team PeckShield.

Please check the rETH security audit report.

2.What are rETH Original Validators(OVs)?

In rETH, Original Validators specifically refer to Ethereum 2.0 validators who have joined the StaFi rETH OV program and run nodes for the funds in rETH Staking Pool.

3.Why should I become an OV?

There are 4 main reasons why you should consider joining in rETH Original Validator Campaign:

1) No KYC and Permission Required

Any Eth2.0 validator, no matter whether you are a personal validator or an institutional validator, can join in to be an OV in rETH freely without any KYC or permission.

2) Higher APY

The OV's staking profits will be 23.50% higher than totally self-funding the 32 ETH, so that the APY of ETH staking for OVs will be around 13.59% in the current stage. Please check the OV APY calculation table for details.

3) Competent Liquidity

StaFi rETH designs a liquidity solution for OV's deposits and rewards. rETH OV can redeem 2 or 4 ETH per node.

4)Slash Insurance

Stafi will cooperate with Nexus Mutual, Tidal and other DeFi insurance protocols to provide slash insurance for OVs. Also, StaFi will establish an insurance fund pool to compensate the slash loss over 8 ETH per node.

4.How to onboard?

The following three requirements would apply to a rETH OV:

1) Run an ETH2.0 node.

2) Deposit 8ETH to the Address of the Staking Pool of rETH.

3) When 24 ETH are automatically allocated to the same address, OV should upload the deposit_data-*.json file generated by the validator client in rETH validator dashboard.

After completing the above three steps, you will officially become an OV in rETH. An OV can deposit more ETH in order to run multiple nodes simultaneously (8*N, where N refers to the number of validators planning to operate) .

rETH Original Validator Onboard Guide: Original Validator Guide

5.How to Onboard?

Onboard Guide: Original Validator Guide

6.Is there any requirement of self-bonding for OVs?

The validators who join the StaFi rETH Original Validator program will deposit 8ETH into the mini staking pool. Once slashing occurs, the staker loss will be deducted from the OVs' deposit, so as not to affect the stakers initial deposits.

Please note: The number is set to 8ETH in the early stage, and will be adjusted according to the situation in the later stage.

7.How to deal with the Salsh Problem in ETH2.0?

We will solve the slash problem through the following ways:

1) OV is required to deposit 8 ETH per node. When Slashing occurs, the staker loss will be deducted from the 8 ETH deposited by OV in priority.

2) StaFi will cooperate with Nexus Mutual, Tidal and other DeFi insurance protocols to provide slash insurance for OVs. Also, StaFi will establish an insurance fund pool to compensate the slash loss over 8 ETH per node.

In addition, according to our research on ETH2.0 slashing, the probability of slashing on all nodes is 0.05%, and the maximum slashing quota does not exceed 2ETH. For detailed research, please see: https://medium.com/stafi/stafi-reths-solution-to-the-slash-of-eth-ae44e3767fb0

8. Fund allocation rules in rETH product solution

rETH staking contract will automatically allocate funds to OVs in the waiting list according to the following rules:

1) Firstly, pick up all the waiting OVs who have deposited 8 ETH in the mini staking pool, and wait for allocated funds currently in the rETH solution.

2) Then, allocate the funds to the OVs who had deposited at the earliest time.

Currently, the commission rate charged by rETH OV is set at 10%. The parameter will be adjusted according to the relationship between the demand for OVs and the current supply of OVs.

When the supply of OVs in rETH is not enough, the commission rate will be increased to incentivize validators to join the rETH OV program.

When there are too many OVs in the waiting list, we will lower the commission ratio to encourage stakers to deposit ETH into the rETH staking contracts.