Launch a Full Node on Binance Smart Chain with Erigon Client
Description	A tutorial demonstrating the process of deploying a full node on Binance Smart Chain using the Erigon client.
Assignee	C. J. (Unlicensed)
Document Status	DRAFT

The following instructions will demonstrate the process of deploying a full node on Binance Smart Chain using the Erigon client.

DRAFT → Link to Chris' demo w/ timestamps

Top-Level Guide

The following demonstration will exhibit the step-by-step processes of:

Logging into the system
1. Username & password login by default
2. Secure user credentials with a Public SSH Key.
  1. Option A → Run ssh-keygen command:
    ssh-keygen -t rsa
  3. Option B → ls -al .ssh
  4. fdafdasd
    ssh-keygen -t rsa
Get Erigon
Run Erigon + Setup as a service so it will run again after rebooting
Change the hostname of the server
Make an exception for SSH, then turn on the firewall.
Open Erigon port 30303 through the firewall to allow incoming connections to the node (allows for a trustless, distributed system).
Setup DNS so it can be accessed with a domain name.

Launching an Erigon Node on Binance Smart Chain
Tutorial Demo for MacOS Systems

Specification	Minimum Requirement	Used for Demo
Hardware	Linux / Mac / Windows system running the latest OS version	MacBook Pro running MacOS Monterey 12.2
SSD / NVMe Storage	≥ 2 TB	7.68 TB
RAM	≥ 16 GB	256 GB
Server OS	Linux OS (64-bit)	Ubuntu Server 20.04.3
Network Settings	SSH enabled TDP / UDP traffic enabled

Linux, Mac, or Windows computer running the latest operating system (OS) version.
(For Demo: MacBook Pro + MacOS Monterey 12.2)
Terminal Emulator / SSH Client
- Mac: Terminal || Windows: PuTTy || Linux: OpenSSH
Login credentials for the server being accessed.

To access the server remotely, the user must enable Secure Shell (SSH) on their home system.

Open Terminal.
Run the systemsetup command to Enable SSH:
```
sudo systemsetup -setremotelogin on
```
When prompted for a password, enter the system admin password to confirm enabling.
```
Password: [?]
```

Following the session - and anytime the server is not being accessed - it is best practice to disable SSH on the home system for ensured security.

Disable SSH by running this Terminal command/s:

sudo systemsetup -setremotelogin off
Password: {Admin Password}

To access the server with SSH, run the following Terminal command/s (replacing details inside the brackets with your provided credentials):
```
ssh your_username@{server.ip}
Password: {Server Password}
```

2.1 Viewing and Verifying the Server’s Components

Run the List Block command to view drives and partitions installed on the server.

lsblk

$ sudo apt-get update
$ sudo apt dist-upgrade -y
$ sudo apt autoremove -y
$ sudo apt install git
$ sudo apt install npm