Skip to content

Commit

Permalink
Add minimum Stake
Browse files Browse the repository at this point in the history
  • Loading branch information
jamesbayly committed Mar 8, 2024
1 parent 4e7989f commit dba4de1
Show file tree
Hide file tree
Showing 4 changed files with 4 additions and 9 deletions.
8 changes: 1 addition & 7 deletions docs/subquery_network/node_operators/introduction.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,4 @@
## Node Operators / Indexers

:::info SubQuey Kepler Network

The SubQuery Kepler network only has the concept of Data Indexers. RPC Providers will launch with the mainnet.

:::
## Node Operators

SubQuery has a commitment to expanding the SubQuery Network to decentralise both Data Indexers, as well as supercharging RPCs to address a much broader centralisation issue throughout Web3 infrastructure. The SubQuery network will see thousands of decentralised Indexers and RPC providers (together called Node Operators) simplify the data layer for a myriad of applications and use cases.

Expand Down
2 changes: 1 addition & 1 deletion docs/subquery_network/node_operators/rewards.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Check out [reward distribution](../introduction/reward-distribution.md) for more

## Staking

In order to register and become a Node Operator, a minimum amount of SQT is required to stake in the staking contract. If a Node Operator is caught misbehaving (such as by providing invalid, incomplete, or incorrect data), they are liable to have a portion of their staked SQT (on the particular reward pool) reallocated to the SubQuery Foundation Treasury, diminishing their staked SQT in the network and therefore reducing their potential rewards.
In order to register and become a Node Operator, a minimum amount of SQT (currently 200,000 SQT) is required to stake in the staking contract. If a Node Operator is caught misbehaving (such as by providing invalid, incomplete, or incorrect data), they are liable to have a portion of their staked SQT (on the particular reward pool) reallocated to the SubQuery Foundation Treasury, diminishing their staked SQT in the network and therefore reducing their potential rewards.

[Learn more about staking and allocating existing stake here](./stake.md).

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,7 @@ We highly recommend setting up SSL on your new server and [consulting our securi
Once your Indexing Service is all set and running successfully, you should open the Node Operator Admin App and follow the steps to register yourself (usually this is `http://localhost:8000/` depending on your installation). This includes:

- Connect your metamask
- Register and stake your minimum required stake
- Register and stake your minimum required stake (currently 200,000 SQT)
- Add metadata information for your network

## 4. Index or Sync a Project
Expand Down
1 change: 1 addition & 0 deletions docs/subquery_network/node_operators/stake.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,6 +63,7 @@ You can use the estimate of the Own Stake and Total Delegated for the next Era o

There are multiple reasons why Node Operators should consider staking more SQT or attracting more Delegation.

- All Node Operators must stake a minimum amount of SQT to become a Node Operator, at the moment this is 200,000 SQT
- There is a maximum allowed delegation amount based on the size of the Node Operator's self stake, this ensures the Node Operator has sufficient skin in the game. Increasing self stake can mean delegators are able to delegate more to you.
- More total stake means more SQT to allocate on different deployments the Node Operator runs and more Network Inflation Rewards to earn.
- It provides an advantage over other Node Operators when payment method is flex plan (PAYG) due to the way the [Cobb-Douglas function](../introduction/reward-distribution.md#cobb-douglas-production-function) works.
Expand Down

0 comments on commit dba4de1

Please sign in to comment.