Skip to content

Commit

Permalink
Trust assumptions
Browse files Browse the repository at this point in the history
  • Loading branch information
enriquefynn committed Jan 4, 2024
1 parent db14be7 commit dc62a2e
Showing 1 changed file with 22 additions and 0 deletions.
22 changes: 22 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,3 +40,25 @@ 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 provides a fee recipient.
Users are required to place a significant amount of trust in Chorus One. This
trust encompasses several key areas:

1. **Validator Operation**: Users must trust that Chorus One will operate its
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 need to 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 must 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.

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

0 comments on commit dc62a2e

Please sign in to comment.