[Dev] Design non-custodial sharedDeposit for SharedStake v2

[chimera-defi]

1. Write an article for the design
2. High level technical design
3. Code it up
4. Deploy it
5. Integrate it with the front end

For Sharedstake v2. We want to launch a contract for non-custodial staking. Use Stakewise for inspiration with how they use a preset ETH1 withdrawal address.
Article should mention Sharedstake launched our first version before this was a feature, same as Cream, Lido, stafi, stakehound.

Based on user feedback

• use a price oracle, so the virtual price changes and increases over time, thus preventing dilution for early depositors, instead of having the same total rewards across the pool as was the case for v1. You may use the current veth2 oracle impl for inspo.
• pre-set eth1 withdrawal address should ideally be an escrow contract owned by the multisig so that the ETH can be directly routed to a withdrawal contract when the time comes. This makes it non-custodial to a large extent until more details for withdrawals are offered from the EF

Key parameters:

• 0.3-1% initial fee
• Total fee should be competitive, i.e. <=10% of profits, any initial deposit fee should be deducted from taker fee at withdrawal.

Bonus:

• Can we make this extensible to allow infra providers to spin up their own pools and use our UI and SC to solicit deposits for themselves?
• if we do the above, can we ensure it wont have the same bug Stakewise pointed out in lido and rpl?
• Can we make it extensible to allow integration with RPL?

Open for support but will most likely need to be spearheaded by me.

[chimera-defi]

Got started on this https://medium.com/@chimera_defi/shareddeposit-pool-v2-93af9633332a

[NateBrune]

1. It was comforting for to be able to deposit into the V1 contracts knowing that some of it would be used for fractional banking purposes
2. It would be interesting to use part of the administration fees to gain protocol controlled liquidity and be the first to do so.