Staking Documentation
  • Getting Started
  • 🏰Keep Network
    • About the Keep Network
  • 🥇KEEP Tokens
    • About KEEP Tokens
    • How to get KEEP
  • 🚩Keep Staking
    • KEEP staking 101
    • Staking rewards
    • Staking risks
    • Staking minimums
    • Navigating the token dashboard
    • Staking yourself
    • Staking providers
    • Authorizing contracts
    • Bonding and adding ETH
  • 📊Manage Stake Rewards
    • About the Token Dashboard
    • Earnings vs. rewards vs. liquidity
    • Managing your stake
    • Claiming your rewards
    • Withdrawing KEEP tokens
  • 🙋‍♀️ Help
    • Access Ropsten testnet
    • FAQ
    • Resources
    • Terminology
Powered by GitBook
On this page
  • Random Beacon
  • Overview
  • Risks
  • TBTC / ECDSA
  • Overview
  • Risks
  • A note on "all stake"
Export as PDF
  1. Keep Staking

Staking risks

Slashing and liquidation are not punitive and are designed to prevent bad actors in the network.

Random Beacon

Overview

The random beacon is a service to generate strong randomness in a distributed setting via a distributed signature generation. Nodes are put into signing groups of 64 members, which then jointly generate a signing key used whenever a new entry (name used for the randomness in the contracts) is requested.

At the moment, this randomness is mostly used to randomly select operators for keeps.

Risks

A slash is a penalty for signing group misbehavior. It results in the removal of a portion of your delegated KEEP tokens (usually one minimum stake). If you’re using a staking provider, you shouldn’t need to worry about slashing.

Slashing vectors are kept minimal, and only seriously punitive in nature if malicious behavior is suspected. As long as a Random Beacon group (64 members) produces an entry, you won't be slashed if you had down time and were part of the group selected to produce an entry.

The risks of running a tBTC/ECDSA signer node are:

Event

Slashing (KEEP)

Refer to the minimum staking intervals chart at the bottom of the page to see what the minimum stake would be at a given creation date.

TBTC / ECDSA

Overview

The two services offered by operators are depositing and redemption of BTC. Depositing BTC into custody produces a DepositToken (TDT), which can be exchanged for TBTC. Redemption then requires a TDT and burning of TBTC.

Risks

In both cases described above, operators can misbehave or fail and thus violating protocol needs to be discouraged. Slashing only occurs in the case of malicious behavior. Here we try to outline these mechanisms for node operators, in order for them to better assess the risks of providing these services.

The risks of running a tBTC/ECDSA signer node are:

Event

Slashing

Lose collateral (ETH)

❌

collateral price peg breaking

❌

❌

A note on "all stake"

Please note that "all stake" in the above charts refers to the stake locked in during the creation of the keep. Each keep creation locks the minimum stake at the time, so slashing all stake here means slashing 100% of the minimum stake at keep creation date.

Learn more about staking minimums:

PreviousStaking rewardsNextStaking minimums

Last updated 4 years ago

more than 50% of beacon group members are offline for

✅ ()

(requires collusion of > 50% of group members)

✅ ()

failing to create signing groups ()

✅ (only paid by user)

✅ (goes to and )

✅ ()

✅ (goes to and )

✅ ()

✅ (split between and )

failing to honor a redemption request (signature, ; spv proof, )

✅ ( and bond is auctioned off, auction remains are )

✅ ()

✅ (redeemer gets )

For more reading on risks for operators, please refer to the Keep community created doc authored by Discord user @ssh.

🚩
Staking minimums
You can read it here.
6 * 64 blocks (~90 minutes with 14s block time)
100% of min stake
fraudulent signature is generated
100% of min stake
3 hours grace period
setup fee
auction winner
left-over split between group and reporter
group producing fraudulent signatures during funding
all stake
auction winner
left-over split between group and reporter
group producing fraudulent signatures
all stake
submitter
auction winner
2 hour grace period
6 hour grace period
redeemer gets tBTC
split between fraud reporter and signer group
group producing fraudulent signature during redemption
all stake
full bond