This script installs the latest stable version of Tor, Bitcoin Core, Uncomplicated Firewall (UFW), Debian updates, enables automatic updates for Debian for good security practices, installs a random number generator, and optionally a QR encoder and an image displayer.
For more information on Bitcoin-Standup:
- The Main Bitcoin-Standup Repo contains general information on the project.
- Why Run a Full Node? details why you would want to run a full node in the first place.
- Security for Bitcoin-Standup offers notes on ensuring the security of your Bitcoin-Standup node.
The Bitcoin-Standup-Scripts are updated every year or two for the newest versions of Bitcoin and Debian, and so remain a work-in-progress. We're also working toward improving the modularity of various plug-ins that could be installed.
- Added Cypherpunkpay Installation, courtesy of @nochiel and sponsorship from HRF.
- Updated scripts to Bitcoin Core 22.0
There are two linux based StandUp scripts; StandUp.sh and LinodeStandUp.sh.
LinodeStandUp.shis built as a StackScript for the Linode platform and can be used as is. It's been tested on Debian 12 (Bookworm), with previous versions tested on Debian 9 (Stretch), Debian 10 (Buster) and Debian 11 (Bullseye).StandUp.shcan be used on a Debian VPS and has been tested on Debian 12 (Bookworm), with previous versions tested on Debian 9 (Stretch), Debian 11 (Bullseye) and Ubuntu 18.04.
You will use different installation methods depending on which script you use (or if you want to run the installation entirely by hand)
In order to run this script you need to be logged in as root, and enter in the commands listed below.
The $ represents a terminal command prompt; do not actually type in a $.
-
Give the root user a password:
$ sudo passwd -
Switch to the root user:
$ su - root -
Create the file for the script:
$ nano standup.sh- Nano is a text editor that works in a terminal, you need to paste the entire contents of the Standup script into your terminal after running the above command. Then you can type:
control x(this starts to exit nano)
y(this confirms you want to save the file)return(just press enter to confirm you want to save and exit)
- Nano is a text editor that works in a terminal, you need to paste the entire contents of the Standup script into your terminal after running the above command. Then you can type:
-
Make sure the script is executable:
$ chmod +x standup.sh -
Run the script with the optional arguments like :
$ ./standup.sh "<insert Tor V3 pubkey>" "<insert node type>" "<insert ssh key>" "<insert ssh allowed IP's>" "<insert password for standup user>"- It is highly recommended to add a
Tor V3 pubkeyfor cookie authentication, so that even if your QR code is compromised an attacker would not be able to access your node. - The
node typeis "Mainnet", "Pruned Mainnet", "Testnet", "Pruned Testnet", or "Private Regtest", default is "Pruned Testnet". - If you supply a
SSH_KEYin the arguments, you will be able to easily access your node via SSH using your rsa pubkey. - If you add
SYS_SSH_IP, you host willl only accept SSH connections from those IPs. - The
passwordis used for a user calledstandup.
- It is highly recommended to add a
The LinodeStandup.sh script is intended for use at Linode.com. You can find more precise information on using it from our Learning Bitcoin from the Command Line course. The following is a summary.
First, copy the LinodeStandup.sh script to your Linode:
- Copy the complete LinodeStandup.sh script.
- Go to the Stackscripts page on your Linode account; choose Create New Stackscript
- Paste
LinodeStandup.shinto the "Script" area. Make sure you got it all, from the "#!/bin/bash" to the "exit 1"! - Choose "Debian 12" (Bookworm) for the "Target Images".
- Click "Save".
Second, create a node based on the script:
- On the Stackscripts page, click on the "..." to the right of your new script and choose "Deploy New Linode".
- Fill in a hostname and the password for the "standup" user.
- Choose an Installation Type in your options. This is likely "Mainnet" or "Pruned Mainnet" if you are setting up a node for usage and "Pruned Testnet" if you're just playing around.
- Fill in any other advanced options.
- Choose a region for where the Linode will be located.
- Choose a Linnode plan. Our general experience is that a Linode 8GB is needed to store the whole blockchain if you choose unpruned "Mainnet", while for testnet and the pruned options (and regtest) you'll instead be dependent on memory, where a Linode 4GB will definitely be sufficient, and a Linode 2GB has worked or not on various versions of Bitcoin Core. (If it fails, you'll get out-of-memory errors.) For deployment you may wish to use "Dedicated CPU", but for everything else a "Shared CPU" should be sufficient.
- Enter a root password.
- Click "Create".
Finally, if you prefer, you can install all of the packages for Bitcoin-Standup by hand. The Learning Bitcoin from the Command Line course has instructions on how to do so, but those methodologies will only install a full node, not include tor and not linking with the Quick Connect API. As such, this methodology is not recommended, but is simply included to provide you with the widest breadth of options.
Because this by-hand methodology does not embody the full Bitcoin-Standup protocol, the following notes on what to do next do not apply.
By default the scripts set up a pruned testnet node and a Tor V3 hidden service controlling your rpcport and enable the firewall to only allow incoming connections for SSH. Tor and Bitcoin Core are set up as systemd services so that they start automatically after crashes or reboots.
-
You should check the Bitcoin-Standup logs to ensure that the installation went correctly:
$ cat /standup.err$ cat /standup.log -
You can now scan a QR code from Bitcoin-Standup to link to a remote app such as FullyNoded 2. There are two ways to do so.
- A
btcstandup://uri appears in plain text in the/standup.log. You can convert that to a QR Code. - Alternatively, you can directly access
/qrcode.png, which you can open and scan. One way to do so is tosudo apt-get install fimthenfim -a qrcode.pngto display the QR in a terminal (as root).
- A
-
After reviewing your logs and accessing your QR code, you should remove the
/btcstandup.uri,/qrcode.png,/standup.log, and/standup.errfiles.
rm -R -f standup.log
rm -R -f standup.err
rm -R -f btcstandup.uri
rm -R -f qrcode.png
Version 0.8.0 of the Bitcoin Standup Scripts added support for Cypherpunkpay installation. Cypherpunkpay may be installed by inputting four variables:
- USECYPHERPUNKPAY ; set to YES
- CPPLITE ; for a lighter installation, usually set to YES
- XPUB ; the xpub for the wallet where you will receive your funds
- CPPCAUSE ; the title for your Cyperpunkpay donations
If you use the Linode Stackscript, you will be able to set these variables on the Stackscript deployment page; if you use the .sh scripts, you must find these lines in the script, uncomment them, and edit them as appropriate (particularly the XPUB and CPPCAUSE variables).
After running the script, you can verify that Cypherpunkpay is running with systemctl status cypherpunkpay:
# systemctl status cypherpunkpay
â—Ź cypherpunkpay.service - CypherpunkPay
Loaded: loaded (/lib/systemd/system/cypherpunkpay.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2021-10-07 00:49:18 UTC; 1min 28s ago
Main PID: 9136 (cypherpunkpay)
Tasks: 37 (limit: 4680)
Memory: 63.6M
CPU: 1.404s
CGroup: /system.slice/cypherpunkpay.service
└─9136 /opt/venvs/cypherpunkpay/bin/python /usr/bin/cypherpunkpay
Once Cypherpunkpay is running, you will need to integrate it into your website.
Bitcoin-Standup is a project of Blockchain Commons. We are proudly a "not-for-profit" social benefit corporation committed to open source & open development. Our work is funded entirely by donations and collaborative partnerships with people like you. Every contribution will be spent on building open tools, technologies, and techniques that sustain and advance blockchain and internet security infrastructure and promote an open web.
To financially support further development of Bitcoin-Standup and other projects, please consider becoming a Patron of Blockchain Commons through ongoing monthly patronage as a GitHub Sponsor. You can also support Blockchain Commons with bitcoins at our BTCPay Server.
We encourage public contributions through issues and pull requests! Please review CONTRIBUTING.md for details on our development process. All contributions to this repository require a GPG signed Contributor License Agreement.
The best place to talk about Blockchain Commons and its projects is in our GitHub Discussions areas.
Gordian User Community. For users of the Gordian reference apps, including Gordian Coordinator, Gordian Seed Tool, Gordian Server, Gordian Wallet, and SpotBit as well as our whole series of CLI apps. This is a place to talk about bug reports and feature requests as well as to explore how our reference apps embody the Gordian Principles.
Blockchain Commons Discussions. For developers, interns, and patrons of Blockchain Commons, please use the discussions area of the Community repo to talk about general Blockchain Commons issues, the intern program, or topics other than those covered by the Gordian Developer Community or the Gordian User Community.
As an open-source, open-development community, Blockchain Commons does not have the resources to provide direct support of our projects. Please consider the discussions area as a locale where you might get answers to questions. Alternatively, please use this repository's issues feature. Unfortunately, we can not make any promises on response time.
If your company requires support to use our projects, please feel free to contact us directly about options. We may be able to offer you a contract for support from one of our contributors, or we might be able to point you to another entity who can offer the contractual support that you need.
The following people directly contributed to this repository. You can add your name here by getting involved. The first step is learning how to contribute from our CONTRIBUTING.md documentation.
| Name | Role | Github | GPG Fingerprint | |
|---|---|---|---|---|
| Christopher Allen | Principal Architect | @ChristopherA | <[email protected]> | FDFE 14A5 4ECB 30FC 5D22 74EF F8D3 6C91 3574 05ED |
| Peter Denton | Project Lead | @Fonta1n3 | <[email protected]> | 3B37 97FA 0AE8 4BE5 B440 6591 8564 01D7 121C 32FC |
We want to keep all of our software safe for everyone. If you have discovered a security vulnerability, we appreciate your help in disclosing it to us in a responsible manner. We are unfortunately not able to offer bug bounties at this time.
We do ask that you offer us good faith and use best efforts not to leak information or harm any user, their data, or our developer community. Please give us a reasonable amount of time to fix the issue before you publish it. Do not defraud our users or us in the process of discovery. We promise not to bring legal action against researchers who point out a problem provided they do their best to follow the these guidelines.
Please report suspected security vulnerabilities in private via email to [email protected] (do not use this email for support). Please do NOT create publicly viewable issues for suspected security vulnerabilities.
The following keys may be used to communicate sensitive information to developers:
| Name | Fingerprint |
|---|---|
| Christopher Allen | FDFE 14A5 4ECB 30FC 5D22 74EF F8D3 6C91 3574 05ED |
You can import a key by running the following command with that individual’s fingerprint: gpg --recv-keys "<fingerprint>" Ensure that you put quotes around fingerprints that contain spaces.