forked from LongForWisdom/rp-bounty
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
53 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,53 @@ | ||
| --- | ||
| title: Non-Custodial Staking As A Service | ||
| code: BA082402 | ||
| status: Draft | ||
| repeatable: No | ||
| summary: Create a non-custodial staking as a service option similar to AllNodes. | ||
| reward: | ||
| unit: USD | ||
| max: 80,000 | ||
| min: 80,000 | ||
| skillsets: | ||
| - development | ||
| - protocol-knowledge | ||
| - liquid-staking | ||
| date: 2024-01-28 | ||
| author: Valdorff | ||
| contacts: | ||
| - ShfRyn | ||
| - Valdorff | ||
| tags: | ||
| - frontend | ||
| discussion-url: https://dao.rocketpool.net/t/round-8-gmc-community-discussion-of-submitted-applications/2557/19?u=shfryn | ||
| application-url: https://dao.rocketpool.net/t/round-8-gmc-call-for-bounty-applications-deadline-is-january-14/2558/6?u=shfryn | ||
| --- | ||
|
|
||
| ## Description | ||
| Create a non-custodial staking as a service option similar to AllNodes. In a worst-case scenario, the RP validators could act as part of a cabal or self-slash to grief. Limiting that set is useful. Note also that allnodes has quite a lot of stake, eg from Lido. | ||
|
|
||
| It need not be identical. For example, it could require running something very lightweight on a home computer, which could be run on a primary machine (as opposed to dedicated hardware). | ||
|
|
||
| ## Requires | ||
| - The GMC must approve each milestone. | ||
| - Must be non-custodial (can have validator key shared, but not node wallet or withdrawal wallet) | ||
| - Graffiti must label the users of the service | ||
| - Milestone 0 must be completed within six months of this bounty's publish date. Milestone 2 must be completed within six months of milestone 0 | ||
| - Product must be compatible with macOS, Windows, and Linux | ||
| - Milestones will be accomplished either by the same entity or, in the event that the successful claimant of milestone 0 explicitly grants consent, by another party to complete milestones 2 and 3 | ||
|
|
||
| ## Optionals | ||
|
|
||
| ## Further Notes | ||
| This bounty must be divided into milestones. | ||
|
|
||
| Milestone 0: A fully written project specification outlining the design and implementation scope and including a business model for the financial viability and sustainability of the validating service without the bounty subsidiary | ||
| Milestone 1: A functioning product with 10 users and 100 minipools | ||
| Milestone 2: 5% the size of allnodes (within RP) – measured by block proposals across a week | ||
|
|
||
| Bounties for milestones are awarded according to the following scheme: | ||
| Milestone 0: First to write a detailed project specification receives $5,000 | ||
| Milestone 1: $20,000 | ||
| Milestone 2: $60,000 | ||
|
|
||
| ## Resources |