Merge branch 'casper-network:dev' into 1259_aws_nodes

.github/workflows/main.yml

@@ -6,7 +6,8 @@ env:
 
 on:
   push:
-    branches: "*"
+    branches:
+      - dev
   pull_request:
     types: [ opened, reopened, synchronize ]
 

config/sidebar.config.js

@@ -110,6 +110,7 @@ module.exports = {
                 "developers/writing-onchain-code/contract-vs-session",
                 "developers/writing-onchain-code/writing-session-code",
                 "developers/writing-onchain-code/testing-session-code",
+                "developers/writing-onchain-code/contract-hash-vs-package-hash",
                 "developers/writing-onchain-code/best-practices",
             ],
         },
@@ -225,6 +226,7 @@ module.exports = {
                 "operators/setup/basic-node-configuration",
                 "operators/setup/node-endpoints",
                 "operators/setup/install-node",
+                "operators/setup/fast-sync",
                 "operators/setup/open-files",
                 "operators/setup/upgrade",
                 "operators/setup/joining",
@@ -297,6 +299,7 @@ module.exports = {
     resources: [
         "resources/index",
         "resources/build-on-casper",
+        "resources/moving-to-casper",
         "resources/casper-open-source-software",
         "resources/quick-start",
         //"resources/sample-projects", // NEW CONTENT WILL BE HERE

source/docs/casper/concepts/design/casper-design.md

@@ -259,7 +259,7 @@ The Casper *mint* is a system contract that manages the balance of *motes* withi
 
 The `AccessRights` of the URefs permissions model determines what actions can be performed when using a `URef` associated with a purse.
 
-As all URef`s are unforgeable, the only way to interact with a purse is for a `URef` with appropriate `AccessRights` to be validly given to the current context.
+As all `URef`s are unforgeable, the only way to interact with a purse is for a `URef` with appropriate `AccessRights` to be validly given to the current context.
 
 The basic global state options map onto more standard monetary operations according to the table below:
 

source/docs/casper/concepts/hash-types.md

@@ -34,7 +34,7 @@ For the sake of user convenience and compatibility, we expect the delivery of ha
 
 ## Hash and Key Explanations {#hash-and-key-explanations}
 
-`PublicKey` is a 32 byte asymmetric public key, preceded by a one-byte prefix that tells whether the key is `ed25519` or `secp256k1`.
+`PublicKey` is a 32 byte asymmetric public key, preceded by a one-byte prefix that tells whether the key is `ed25519` or `secp256k1`. There is a third type of `PublicKey` that refers to the system and it is a single `00`.
 
 `AccountHash` is a 32 byte hash of the `PublicKey` serving to identify user accounts.
 

source/docs/casper/concepts/serialization-standard.md

@@ -745,6 +745,7 @@ A `Map` serializes as a list of key-value tuples. There must be a well-defined o
 
 `PublicKey` serializes as a single byte tag representing the algorithm followed by 32 bytes of the `PublicKey` itself:
 
+-   If the `PublicKey` is a `System` key, the single tag byte is `0`. With this variant, the single byte of `0` is the entire key.
 -   If the `PublicKey` is an `Ed25519` key, the single tag byte is `1` followed by the individual bytes of the serialized key.
 -   If the `PublicKey` is a `Secp256k1` key, the single tag byte is a `2` followed by the individual bytes of the serialized key.
 

source/docs/casper/developers/cli/calling-contracts.md

@@ -68,7 +68,7 @@ The payment amount varies based on each deploy and network [chainspec](../../con
 The following sample response contains a `deploy_hash`, needed to verify the changes in global state, as described [here](./installing-contracts.md#querying-global-state).
 
 <details>
-<summary><b>Sample response</b></summary>
+<summary>Sample response</summary>
 
 ```rust
 {

source/docs/casper/developers/cli/installing-contracts.md

@@ -123,7 +123,7 @@ casper-client query-global-state \
 Here is how your account state would look. Notice that the sample response contains several named keys, including "counter", "counter_package_name", and "version". You can use these values to query the contract state further, as shown in the next example.
 
 <details>
-<summary><b>Sample account state</b></summary>
+<summary>Sample account state</summary>
 
 ```bash
 {
@@ -197,7 +197,7 @@ casper-client query-global-state \
 Here is how the sample contract would look and would contain details such as the `contract_package_hash`, the contract `entry_points`, and the `named_keys` for the contract.
 
 <details>
-<summary><b>Sample contract state</b></summary>
+<summary>Sample contract state</summary>
 
 ```bash
 {
@@ -257,7 +257,7 @@ casper-client query-global-state \
 ```
 
 <details>
-<summary><b>Sample stored value</b></summary>
+<summary>Sample stored value</summary>
 
 ```bash
 {
@@ -308,7 +308,7 @@ casper-client query-global-state \
 Here is how the contract package details would look. The response would contain the `contract_hash`, which you would need to [call a contract by hash](./calling-contracts.md#calling-contracts-by-hash) in the next section. You would also see the `access_key` for the `ContractPackage` and the current `contract_version`.
 
 <details>
-<summary><b>Sample contract package state</b></summary>
+<summary>Sample contract package state</summary>
 
 ```bash
 {

source/docs/casper/developers/cli/querying-global-state.md

@@ -60,7 +60,7 @@ casper-client query-global-state \
 Here is how your account state would look. Notice that the sample response contains several named keys, including "counter", "counter_package_name", and "version". You can use these values to query the contract state further, as shown in the next example.
 
 <details>
-<summary><b>Sample account state</b></summary>
+<summary>Sample account state</summary>
 
 ```bash
 {
@@ -134,7 +134,7 @@ casper-client query-global-state \
 Here is how the sample contract would look and would contain details such as the `contract_package_hash`, the contract `entry_points`, and the `named_keys` for the contract.
 
 <details>
-<summary><b>Sample contract state</b></summary>
+<summary>Sample contract state</summary>
 
 ```bash
 {
@@ -194,7 +194,7 @@ casper-client query-global-state \
 ```
 
 <details>
-<summary><b>Sample stored value</b></summary>
+<summary>Sample stored value</summary>
 
 ```bash
 {
@@ -245,7 +245,7 @@ casper-client query-global-state \
 Here is how the contract package details would look. The response would contain the `contract_hash`, which you would need to [call a contract by hash](./calling-contracts.md#calling-contracts-by-hash) in the next section. You would also see the `access_key` for the `ContractPackage` and the current `contract_version`.
 
 <details>
-<summary><b>Sample contract package state</b></summary>
+<summary>Sample contract package state</summary>
 
 ```bash
 {