The following guide is written with instructions to be executed as a super user (“sudo”). You will be a target for hackers, and your ADA will be at risk. We strongly encourage you to implement any and all restrictions available to you to protect your server from unauthorized access. These enhancements however, are beyond the scope of this guide, and are entirely up to you to implement.
Hire a professional, unless you are willing to accept the entire burden of this project.
These instructions are tested & verified on version 1.30.1
Before you begin:
The following example is based on the following (officially recommended) specs:
Ubuntu 20.04 LTS x86_64 environment,
4 CPUs (2 cores minimum),
16 GB RAM (4 GB minimum memory),
10 GB hard drive space PLUS the blockchain size (currently ~23 GB).
The ADA blockchain grows over time, so you should provide enough free space to accommodate that eventual growth (40gb is currently sufficient).
The Cardano software is constantly being updated, in phased implementations called “eras”. As these new phases are rolled out, this article will become obsolete. Please notify Support if this article is stale.
As new Eras come live, the hardware demands will also increase. The recommendations provided above will only satisfy the current Era’s needs.
Start at the terminal prompt; login to your host (assumed: non-root sudo user).
the host used here (the node IP) is required below (assembling the CAS parameters).
Many hours (if not days) will pass as the blockchain synchronizes. Grab some coffee; go see a movie.
This delay is currently unavoidable.
Messages will begin scrolling by; this is normal. If anything is wrong, the node will stop itself.
Identify the synchronization state at anytime using this command:
cardano-cli query tip --mainnet
That should return something similar to this, indicating the node’s current “tip”:
Navigate to https://explorer.cardano.org/en and search for the epoch. That will reveal the date of the block currently being verified by your node, and give you some idea of your node’s progress. The progress slows as newer (busier) blocks are processed. If no progress occurs over the course of an hour, and the tip remains exactly the same - you may be stuck at an “Era boundary”. You’ll need to download the newest version of Cardano and restart the process. If you’re already using the latest version - then you should research the problem on a Cardano forum. Please notify GB Support of the issue, but please understand that we’ll be less helpful than the forum. We’re not Cardano, we didn’t write the software, and GB can’t fix their problems (and software under development always has problems).
Setup a secure tunnel for encrypted communication.
Your CAS server and this node must have a secure line. Your passphrase and other sensitive information will be passed back & forth. Encrypt (and protect) this communication by using a secure tunnel.
The GB Wallet Tunnel is recommended:
General Bytes has incorporated an open-source ssh client into CAS.
This method is unusable with the GB Cloud, and provided for those Operators with a Standalone CAS that wish to use “standard” stock OS tools.
Start the wallet HTTP server.
This is the piece that CAS actually “talks” to. The wallet server depends on a functional node, so all the previous work was done just to get to this point. Thank you for your patience.
At this point, you should have a secure connection from CAS to your node (as accomplished in the previous step). When you start the cardano-wallet using the parameters supplied below, port 8090 (default) will be exposed only to localhost (127.0.0.1).
The wallet will NOT work with CAS until the local blockchain has fully synchronized.