ObolNetwork / ObolNetwork/obol-splits

Split the principal into multiple parties when they contribute to funding a validator

Open
#136 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

contracts
Dominant language
Solidity
Stars
17
Forks
24
PR merge metrics
No merged PRs in 30d

Description

🎯 Problem to be solved

When multiple parties contribute to funding a validator, it's not currently possible to split the principal into multiple parties. We should mimic the behaviour we have now for rewardAddress on principalAddress, ensuring safety and minimizing the risk of losing funds.

image.png

🛠️ Proposed solution

  • Investigate how to allow splitting the principal between different parties when funding a validator, considering the safety concerns and potential risks involved.
  • Determine the feasibility of implementing such a feature within the existing Splits contract architecture while maintaining high security and reliability.
  • Design and document the proposed solution, including contract modifications and user flows, with a focus on ensuring that the process is foolproof and minimizes the risk of losing funds.

This proposed solution aims to provide more flexibility and options for validators funded by multiple parties, allowing them to distribute the principal according to their specific needs and agreements.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by tracing the existing rewardAddress splitting behavior and the principalAddress handling in the Splits contract architecture; document a safe design, contract changes, and user flows that address the stated fund-loss risks.

Written by the indexing model from the issue text.

Assessment

Tech stack
solidity
Domain
blockchain, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.