Updates docs for Core 0.3.0 release. (#238)

* joining the network

* key reshare

* registering

* signing

* jumpstart

* validators

* Update content/concepts/TDX.md

Co-authored-by: Johnny <[email protected]>

* reshare extra explanation

* Consolidates pages. Adds better lead text. Adds redirects.

---------

Co-authored-by: Jesse Abramowitz <[email protected]>
Co-authored-by: JesseAbram <[email protected]>

Author: johnnymatthews

content/concepts/TDX.md

@@ -0,0 +1,7 @@
+---
+title: "TDX"
+lead: ""
+draft: true
+---
+
+TODO

content/concepts/joining-the-network.md

@@ -0,0 +1,32 @@
+---
+title: "Key management"
+lead: "This page explains the process for periodically substituting signers, swapping keyshares, and other processes the network uses to manage keys."
+aliases:
+    - key-reshare
+---
+
+## Key reshare
+
+The idea here is that when validators join the network they may be selected to the signing comittee. A smaller randomly selected group of validators that is responsible for holding the parent network key. Every session, which consists of 2400 blocks (equivalent to 4 hours), the chain will notify the TSSs (Threshold Signature Servers) that a reshare is taking place. The chain will also reandomly select a validator to join the netowrk and remove the oldest signer from the comittee.
+
+The selected TSSs will connect to each other and execute the key reshare protocol on the parent network key, generating a new set of key shares. This protocol is similar to the distributed key generation protocol used during jump starting the network. Upon receiving a new key share, the recipients will hold the new key share in a secondary slot and rotate them to the current parent network key when everyone in the signing group has agreed that the rotation was succeful. All previous key shares will be incompatible with the refreshed key shares. However, the public validating key of the parent network key signing keypair never changes. This means all child keys will also remain the same.
+
+For information on chain randomness used see (here)[https://docs.substrate.io/build/randomness/]
+
+```mermaid
+sequenceDiagram
+    Entropy Chain->>+Validator TSS: Tells selected validator to do Reshare (with new signer to add and old to remove).
+    Validator TSS->>+Validator TSS: Does Reshare with other selected validators stores new share in holding slot.
+    Validator TSS->>+Entropy Chain: Tells chain everything was A-OK
+    Entropy Chain->>+Validator TSS: When everyone is done tells all signers to rotate their holding key to the new parent key.
+```
+
+### Negative pathways 
+
+- The above describes the happy pathway this part is for edge cases 
+
+#### A failure of reshare protocol 
+
+- There are multiple ways this process can fail, if that were to happen the offending party would be known as everyone in the new signing party needs to participate 
+- Since the process is two steps the current signing party would remain the offending party would be moved to slashing and the chain would initate a new reshare (not implemented yet)
+- All parties are unable to unbond until leaving the singing party so their funds would be at risk and able to be slashed

content/concepts/key-management.md

@@ -0,0 +1,64 @@
+---
+title: "Network setup"
+lead: "This page covers how the Entropy network functions from a conceptual standpoint. For techincal and actionable information on the various Entropy networks, check out the [Networks reference page](../reference/networks.md)."
+aliases:
+    - joining-the-network
+---
+
+## Joining the network 
+
+This section explains the process for validator nodes to join the network. The process works something like this:
+
+1. The new validator operates an Entropy chain node and a threshold server.
+1. This new validator registers with the chain.
+1. If the stake is enough and the node gets selected to be a validator, it will act as a relayer and be eligible to be added to the signer set.
+
+```mermaid
+sequenceDiagram
+    title Joining The Network
+    participant NV as New_Validator
+    participant C as Chain
+
+    NV->>NV: Spins up chain instance
+    NV->>NV: Starts threshold server
+    C->>NV: Places NV in validator set
+    CV->>NV: Validates validator's subgroup, then encrypts and sends keys
+```
+
+{{< callout type="info" >}}
+The network is not currently accepting public/user-ran validator nodes. We will [announce](https://github.com/entropyxyz/community/discussions/categories/announcements) when we plan to start allowing new nodes to join the network.
+{{< /callout >}}
+
+### Required information
+
+Each validator node requires the following information before it can join the network:
+
+- **Endpoint**: The IP address of its threshold server.
+- **X25519 Public Key**: Its public encryption key for encrypting messages to and from other validators.
+- **Threshold Server Signing Account**: The account for the threshold server to submit transactions to the Entropy chain.
+
+## Jumpstart
+
+The network needs a "jump start" to be in a usefull state. Pretty much this means we need to do a network wide DKG to create the network parent key. This is started through a blockchain call which informs the selected TSSs to do a dkg. These TSSs will create the network parent key and create the first signing comittee.
+
+Through reshares TSSs will get subbed in and out of the signing comittee. At registration user's are given a derivation off of the parent key and during signing we have a just in time key derivation to allow for singing for a given account. 
+
+```mermaid
+sequenceDiagram
+    participant Anyone
+    participant Chain
+    participant Validator Alice
+    participant Validator Bob
+    participant Validator Charlie
+    participant Validator David
+
+    Anyone ->> Chain: Calls jumpstart_network().
+    
+    Note over Chain: Selects validators for distributed-key-generation (DKG).
+    Chain ->> Validator Alice: do DKG message sent.
+    Chain ->> Validator Bob: do DKG message sent.
+    Note over Validator Alice, Validator Bob: Perform DKG.
+    Validator Alice ->> Chain: Confirms network is jumpstarted.
+    Validator Bob ->> Chain: Confirms network is jumpstarted.
+    Note over Chain: Network is jumpstarted, Alice and Bob are signers.
+```

content/concepts/network-setup.md

@@ -1,6 +1,6 @@
 ---
 title: "Registering"
-lead: "A user needs to register in order to be able to use the Entropy network to sign messages. This page covers that process."
+lead: "This section explains the technical steps involved in registering a user account on the Entropy network, including the selection of programs and configurations, and the generation of a verifying key."
 ---
 
 The SDK method for registering is [`Entropy.register`](https://github.com/entropyxyz/sdk/blob/main/README.md#register).
@@ -12,46 +12,11 @@ sequenceDiagram
     actor User
     participant Chain
 
-    participant Validator Alice
-    participant Validator Bob
-    participant Validator Charlie
-    participant Validator David
-
-    box Subgroup 1
-    participant Validator Alice
-    participant Validator Bob
-    end
-
-    box Subgroup 2
-    participant Validator Charlie
-    participant Validator David
-    end
-
-    User ->> Chain: Informs chain of registration.
-
-    Note over Chain: Selects validators for distributed-key-generation (DKG).
-    Chain ->> Validator Alice: Sends user information.
-    Chain ->> Validator Charlie: Sends user information.
-
-    Note over Validator Alice, Validator Bob: Perform DKG.
-    Note over Validator Charlie, Validator David: Perform DKG.
-    Validator Alice ->> Validator Bob: Sends key-share to rest of subgroup.
-    Validator Charlie ->> Validator David: Sends key-share to rest of subgroup.
-
-    Validator Alice ->> Chain: Confirms user is registered.
-    Validator Charlie ->> Chain: Confirms user is registered.
-    Note over Chain: User now in a registered state.
+    User ->> Chain: Informs chain of registration. And selects programs and configs associated with account
+    Chain ->> User: Selects user's derivation path and returns verifying key associated with that user
 ```
 
-1. The user registers with the Entropy chain by submitting a transaction from the 'signature request account' containing the 'Account Key', and initial 'ProgramsData'. 
+1. The user registers with the Entropy chain by submitting a transaction from any account containing the 'Account Key', and initial 'ProgramsData'. 
     * ```ProgramsData``` - Is multiple Programs Instances. Which contain the ```program_pointer``` (the hash of the program you want to use) and the ```program_config``` for that program. On the evaluation of a signature request a threshold server will run all the programs and pass through the program config for that program.
 
-1. The chain selects which nodes should perform a [distributed key generation (DKG)](https://docs.rs/synedrion/latest/synedrion/sessions/fn.make_key_gen_session.html) based on the current block number.
-1. As each block is finalized, an off-chain worker makes an HTTP POST request to each selected threshold server with the signature request accounts of all users who have registered, as well as details of the other validator nodes in the signing subgroup. Specifically, the `/user/new` ([src](https://github.com/entropyxyz/entropy-core/blob/master/crypto/server/src/user/api.rs) [API](https://docs.rs/entropy-tss/latest/entropy_tss/#usernew---post)) endpoint is called with a [`OcwMessageDkg`](https://docs.rs/entropy-shared/latest/entropy_shared/types/struct.OcwMessageDkg.html).
-1. All selected threshold servers:
-    1. Connect to each other over websocket and make a [noise handshake](https://noiseprotocol.org/noise.html) to establish an encrypted channel for protocol messages.
-    1. Perform a [DKG](https://docs.rs/synedrion/latest/synedrion/sessions/fn.make_key_gen_session.html) and store their [key-share](https://docs.rs/synedrion/latest/synedrion/struct.KeyShare.html) in their [encrypted key-value store](https://docs.rs/entropy-kvdb).
-    1. Send the generated share to other members of their signing subgroup by POSTing to `/user/receive_key` ([src](https://github.com/entropyxyz/entropy-core/blob/master/crates/threshold-signature-server/src/user/api.rs) [API](https://docs.rs/entropy-tss/latest/entropy_tss/#for-other-instances-of-the-threshold-server)).
-    1. They submit a transaction to the entropy chain to confirm the user has successfully registered.
-1. On receiving a key-share via `receive_key`, the threshold server will check with the chain that the sender is in the correct subgroup, and if so store the key-share in their key-value store.
-1. On receiving a confirmation transaction from all selected threshold server, the chain sets the user to a 'registered' state, making it possible to sign messages. 
+1. The chain selects a derivation path based on a running count and stores said user information in a mapping with the veryfying key for that user as the key in the mapping. The veryfying key will be the account that the edcsa signatures resolve to. 

content/concepts/proactive-refresh.md

@@ -1,8 +1,14 @@
 ---
-title: "Node encryption and authentication"
-lead: "When sending messages to threshold signature servers on the Entropy network, you must authenticate and encrypt the messages. This page covers that process."
+title: "Security"
+lead: "Entropy leverages cutting-edge cryptographic techniques and distributed systems principles to deliver a highly secure network. Learn more about our security architecture and protocols."
+aliases:
+    - node-encryption-and-authentication
 ---
 
+## Node encryption and authentication
+
+When sending messages to threshold signature servers on the Entropy network, you must authenticate and encrypt the messages. This section covers that process.
+
 The authentication process is simple: each node has a substrate account stored on the chain, referred to as a TSS account.
 
 Messages are signed using SR25519. This encryption requires using an X25519 public key which gets used in [Hybrid Public Key Encryption](https://www.rfc-editor.org/rfc/rfc9180.html), using the [`hpke-rs`](https://docs.rs/hpke-rs) crate.