...
The following guide is written with instructions to be executed as a sudo-user. You will be a target for hackers, and your DOGE will be at risk. You are strongly encouraged 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 entirely up to you.
...
Before you begin:
The following example is based on the following specs:
Ubuntu 20.04 LTS x86_64 environment
2 GB of memory (RAM)
10 GB hard drive space PLUS the blockchain size (this example = 70 GB)
The DOGE blockchain grows by about 10GB per year, so you should provide enough space to accommodate that eventual growth.
Find the current blockchain size here: https://bitinfocharts.com/dogecoin/
...
Download and install the software:
Start at the terminal prompt.
Download the latest gzipped tarball from DOGECoin Github Site:
...
| Code Block |
|---|
wget https://github.com/dogecoin/dogecoin/releases/download/v1.14.3/dogecoin-1.14.3-x86_64-linux-gnu.tar.gz |
...
Unzip the tarball:
| Code Block |
|---|
tar xzf dogecoin-1.14.3-x86_64-linux-gnu.tar.gz |
...
the tarball will be decompressed into the current directory (here: home directory)
...
Create an RPC token:
The RPC token is designed to eliminate the need for hard-coded passwords in configuration and script files. You will receive a password here ONCE.
| Tip |
|---|
This password is required for CAS - it's your “RPC Password” noted in Step 6. |
Download rpcauth.py on GitHub:
| Code Block |
|---|
sudo wget https://raw.githubusercontent.com/bitcoin/bitcoin/master/share/rpcauth/rpcauth.py -O /usr/local/bin/rpcauth.py |
Modify the file permissions to allow the python script to execute:
| Code Block |
|---|
sudo chmod +x /usr/local/bin/rpcauth.py |
Then finally run the RPC token generator that you just installed and enabled:
| Code Block |
|---|
rpcauth.py GBRocks |
...
| Tip |
|---|
The password required in the parameter string is: |
...
Configure dogecoind for use with CAS:
Create the configuration file:
| Code Block |
|---|
mkdir .dogecoin touch .dogecoin/dogecoin.conf |
...
Add the required ingredients:
| Code Block |
|---|
nano .dogecoin/dogecoin.conf |
...
More information regarding the configuration settings can be found here: https://github.com/dogecoin/dogecoin/blob/master/contrib/debian/examples/dogecoin.conf
Press Ctrl+X (then Y) to exit & save the file (DO allow it to save, do NOT change the filename).
...
Optional: install the bootstrap blockchain
Started normally, the daemon will download and confirm the entire DOGE blockchain. This can be a VERY slow process, but it ensures the integrity of the blockchain. If you’re handicapped by impatience, you can download the “bootstrap” blockchain and skip much of the waiting.
...
When the bootstrap has been completely imported (may take an hour or longer), the daemon will rename the file to:
bootstrap.dat.oldand you may safely delete it.
...
Start the daemon
| Code Block |
|---|
dogecoin-1.14.3/bin/dogecoind |
...
| Tip |
|---|
To test if the blockchain is completely downloaded & up-to-date, use:
Compare the number returned with the number of “Blocks Count” from https://bitinfocharts.com/dogecoin/ When the 2 numbers are the same, the node is “synchronized” and functional.
|
...
Setup a secure tunnel for encrypted communication:
The GB Wallet Tunnel is recommended:
General Bytes has incorporated an open-source ssh client into CAS.
...
NOTE: to create a secure SSH tunnel between your CAS server and your node, use:
ssh -f -N -i /path/to/your/key -l <LOGIN_ID> -L 22555:127.0.0.1:22555 <NODE_IP>
This method is unusable with the GB Cloud, and provided for informational purposes only for those Operators with a Standalone CAS.
...
Prepare the parameters for the CAS Crypto Setting:
...
The protocol is currently always http.
...
(no “accountname” is specified in this example).
...
Save it!
...
Test it:
Re-enter the Crypto setting and run the Hot Wallet Buy test.
...