Skip to content

Commit

Permalink
Merge pull request #715 from multiversx/add-multikey-recommendation
Browse files Browse the repository at this point in the history
added recommendation for multikey
  • Loading branch information
bogdan-rosianu committed Oct 10, 2023
2 parents ce0f08e + 8ad2514 commit c4836a5
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions docs/validators/key-management/multikey-nodes.md
Original file line number Diff line number Diff line change
Expand Up @@ -80,6 +80,14 @@ will want to consider when deciding to switch the operation towards the multikey
operator when the number of managed keys is greater than the number of shards. So, for the time being, when we have
at least 5 keys that are either *eligible* or *waiting*, the switch to multikey mode becomes feasible.

:::caution
Although there are no hard limits in the source code to impose a maximum number of keys for a multikey group, the MultiversX team
strongly recommends the node operators to not use more than 50 keys per group. The reason behind this recommendation is that a single node
controlling enough keys could cause damage to the chain as, in extreme cases, it could propose consecutive bad blocks, disrupting the
possibility of blocks synchronization or blocks cross-notarization.
:::


[comment]: # (mx-context-auto)

## Usage
Expand Down

0 comments on commit c4836a5

Please sign in to comment.