OIP-9 Lock Project Reserve

Hey Octonauts,

Recently we've faced a lot of FUD, but we stayed strong as our project is built with transparency and good intentions in mind. Also for us, FUD is an inspiration to improve. One concern being mentioned is the possibility of a "rug pull" from the project reserve. We can understand that trusting anons is hard and calls for a third party solution. To prevent FUD in the future regarding "rug pulls" of the project reserve, we want to implement a solution to address concerns.

Project reserve: 247,818 OCTO Source: https://etherscan.io/address/0xd06777d9b02f677214073cc3c5338904cba7894a

1. Locking 200000 OCTO for 1 year and stream 25000 over 6 months back into the project reserve
2. Locking 150000 OCTO for 2 years and 90000 OCTO streamed over 1 year back into the project reserve
3. Locking 200000 OCTO for 2 years and 47818 OCTO streamed over 1 year back into the project reserve

You can also suggest different solutions via our telegram group and we will include them in another OIP round if required.

We found the potential solutions to create a locking period and streaming, provided they are in accordance with our UX/UI and code standard due diligence.

Locking: team.finance or https://docs.lock.finance Streaming: sablier.finance

Cost: Nil

Question: Which solution do you like ?

Best wishes from Dr Octavius.