Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trust assumptions #11

Merged
merged 3 commits into from
Jan 17, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,3 +40,29 @@ rewards in 2:

Finally, the owner of `manager` can call `getEth` specifying an address to
receive the Ether accumulated in the contract.

## Trust Model

Chorus One operates the Ethereum validators with this smart contract. They provide a
smart contract that should be used as the validator's fee recipient.
Users are required to place a significant amount of trust in Chorus One. This
trust encompasses:

1. **Validator Operation**: Users trust that Chorus One will operate its
enriquefynn marked this conversation as resolved.
Show resolved Hide resolved
validators effectively and in compliance with the network's protocols.
Slashing penalties are imposed on validators for actions deemed harmful to the
network, like double signing or downtime. Users trust that Chorus One
will avoid behaviors that could trigger these penalties, as slashing can lead to
a partial loss of the staked assets.

2. **Management of Validator Fees**: Validator fees are a portion of the rewards
earned by validators for their service to the network. Users trust that
Chorus One will maintain transparency and fairness in setting and distributing
these fees and not alter the recipient of these fees without clear communication
and rationale.

3. **Exit Validators on User's behalf**: Users might request to exit their validators,
in this case, they trust that Chorus One will exit the validators according to user requests.

Users should perform due diligence and continually monitor the validator's
performance and reputation.