GitBook: [master] 66 pages and 40 assets modified

Author: jpop32

.gitbook/assets/image (1).png

@@ -52,7 +52,7 @@ AVAX is the native token of Avalanche. It’s a hard-capped, scarce asset that i
 
 ## Avalanche Consensus Protocol
 
-![Consensus Comparison](.gitbook/assets/consensus-comparison.png)
+![Consensus Comparison](.gitbook/assets/image%20%2810%29.png)
 
 Protocols in the Avalanche family operate through repeated sub-sampled voting. When a [validator](http://support.avalabs.org/en/articles/4064704-what-is-a-blockchain-validator) is determining whether a [transaction](http://support.avalabs.org/en/articles/4587384-what-is-a-transaction) should be accepted or rejected, it asks a small, random subset of validators whether they think the transaction should be accepted or rejected. If the queried validator thinks the transaction is invalid, has already rejected the transaction, or prefers a conflicting transaction, it replies that it thinks the transaction should be rejected. Otherwise, it replies that it thinks the transaction should be accepted.
 

.gitbook/assets/consensus-comparison.png renamed to .gitbook/assets/image (10) (1).png

@@ -231,7 +231,7 @@ For assistance with this update, follow our [Developer FAQ](https://support.aval
 
 ## v1.0.4 AvalancheGo Release Notes  \([View on GitHub](https://github.com/ava-labs/avalanchego/releases/tag/v1.0.4)\)
 
-![AvalancheGo release notes v1.0.4.png](../../.gitbook/assets/AvalancheGo-release-notes-v1.0.4.png)
+![AvalancheGo release notes v1.0.4.png](../../.gitbook/assets/image%20%2817%29.png)
 
 {% hint style="danger" %}
 This update is optional but encouraged. The patch includes quality of life improvements and various performance enhancements. Note that this update requires the CLI parameters to be specified with -- rather than allowing for either - or --. For example, `-public-ip=127.0.0.1` is no longer allowed and must be specified as `--public-ip=127.0.0.1`. Otherwise, this update is backwards compatible.

.gitbook/assets/image (10).png

@@ -20,11 +20,11 @@ It is _highly_ recommended that you set up Multi-Factor Authentication on your A
 
 Once your account is set up, you should create a new EC2 instance. An EC2 is a virtual machine instance in AWS's cloud. Go to the [AWS Management Console](https://console.aws.amazon.com/) and enter the EC2 dashboard.
 
-![AWS Management Console.png](../../../.gitbook/assets/AWS-Management-Console.png)
+![AWS Management Console.png](../../../.gitbook/assets/image%20%2835%29.png)
 
 To log into the EC2 instance, you will need a key on your local machine that grants access to the instance. First, create that key so that it can be assigned to the EC2 instance later on. On the bar on the left side, under **Network & Security**, select **Key Pairs.**
 
-![Select "Key Pairs" under the "Network & Security" drop-down.](../../../.gitbook/assets/Network-and-Security.png)
+![Select "Key Pairs" under the "Network & Security" drop-down.](../../../.gitbook/assets/image%20%2838%29.png)
 
 Select **Create key pair** to launch the key pair creation wizard.
 

.gitbook/assets/image (11).png

@@ -2,7 +2,7 @@
 
 ## Introduction
 
-![Primary Network](../../../.gitbook/assets/primary-network.png)
+![Primary Network](../../../.gitbook/assets/image%20%2821%29.png)
 
 Avalanche's Primary Network is a subnet that has three chains: P-Chain, X-Chain, and C-Chain. The C-Chain is an instance of the Ethereum Virtual Machine powered by Avalanche’s Snowman consensus protocol. The [C-Chain RPC](../../avalanchego-apis/contract-chain-c-chain-api.md) can do anything a typical Ethereum client can by using the Ethereum-standard RPC calls. The immediate benefits of using the C-Chain rather than Ethereum are all of the benefits of using Avalanche. These properties that could considerably improve the performance of DApps and the user experience.
 
@@ -12,7 +12,7 @@ Today, we will deploy and test a smart contract on Avalanche using Remix and Met
 
 Log in to MetaMask -> Click the Network drop-down -> Select Custom RPC
 
-![metamask network dropdown](../../../.gitbook/assets/metamask-network-dropdown.png)
+![metamask network dropdown](../../../.gitbook/assets/image%20%2860%29.png)
 
 #### **Avalanche Mainnet Settings:**
 

.gitbook/assets/image (13).png

@@ -23,7 +23,7 @@ In this tutorial, you will:
 
 After you log in to your Metamask account, connect it to the Avalanche network. Click the Network drop-down -> Select **Custom RPC**:
 
-![metamask network dropdown](../../../.gitbook/assets/metamask-network-dropdown.png)
+![metamask network dropdown](../../../.gitbook/assets/image%20%2860%29.png)
 
 Enter the information for the network of your choice:
 

.gitbook/assets/image (14).png

@@ -8,7 +8,7 @@ Avalanche features 3 built-in blockchains: [**Exchange Chain \(X-Chain\)**](./#e
 
 Here are tutorials on [creating a subnet](../../build/tutorials/platform/create-a-subnet.md) and [adding validators](../../build/tutorials/nodes-and-staking/add-a-validator.md) to a subnet.
 
-![Primary network](../../.gitbook/assets/primary-network.png)
+![Primary network](../../.gitbook/assets/image%20%2821%29.png)
 
 ## Subnets