ssh - Setup ubuntu server on Raspberry Pi 4 without ...

How to run Bitcoin Core 0.20.0 on Ubuntu Server 20.04 LTS using a Raspberry Pi 4 (or Virtual Machine)

I was helping someone on twitter with this so I figured I'd share the information here as well so that other people would have an easier time than I did.
I'm going to explain how to do this setup on a Raspberry Pi, but note that this should work on a VM as well. You can also set up and run the node headless this way, but I will be explaining how to set up the node using a monitor that you can then later disconnect and access remotely once everything is setup.
Hardware:
-Raspberry Pi 4 (2GB RAM minimum) preferably 4GB RAM -Raspberry Pi 4 Heatsinks -Raspberry Pi 4 case -Micro HDMI cable -USB-C power cable and wall adapter -Monitor -Keyboard and mouse -Ethernet cable (Optional) -16GB or larger microSD card -500GB or larger external hard drive (SSD or portable)
Node Requirements: -50 KBps upload internet speeds (Most people should have this) -Unlimited or high data cap internet download/upload service -6 hours or longer per day dedicated run time
Okay, once you have the hardware its time to get started!
The first thing you'll need to do is install the Raspberry Pi imager, this is how we're going to install Ubuntu onto our Raspberry Pi. After your download and install finishes, open the imager.
  1. Click the "choose OS" box and from the list select Ubuntu, then select Ubuntu Server 20.04 LTS (Raspberry Pi 2/3/4).
  2. Insert your microSD card to your computer directly or via a USB converter. Click "choose SD card" and select your inserted microSD card.
  3. Click "Write" and wait for the imager to finish flashing the OS onto your card
When it is done, remove the SD card and reinsert it to access the files installed. You can choose the overclock the Raspberry Pi by editing the config file. To connect to the Raspberry Pi remotely, you'll need to create an SSH file. If you're on windows this is pretty easy. In the File Explorer, highlight the address bar at the top, erase the text and type cmd, press enter and the Command Prompt will pop up. Type the following:
echo\ssh
This will create an SSH file in your SD directory so that you can remote access the Rasberry Pi later. Now you can go ahead and eject the SD card from your computer.
Now we can set up the Raspberry Pi
Go ahead and connect all your peripherals to your Raspberry Pi, insert the microSD, and connect it to power to turn it on. Give it a moment to boot up, then when prompted enter "ubuntu" for the password. It will make you change the password. Afterward, it will print a bunch of information to the screen, write down the IPv4 address, this is the IP address you'll use to remote access the Raspberry Pi. Now, at any time you can remote access your Raspberry Pi by entering a terminal on another PC in your network and typing:
ssh [email protected](your IP address)
The next step is to install a desktop. There are plenty to choose from so feel free to use a different one than what I use, you can also choose to ignore this and to just work from in the terminal from this point forward.
You need to update all the repositories so type: (Note you'll either have to be connected by ethernet or have edited the network-config file to setup your wifi in advance)
sudo apt-get update
Once it's done updating type the following to upgrade your system:
sudo apt-get upgrade
Now that you're up-to-date, you can install the desktop using the command:
sudo apt-get install ubuntu-gnome-desktop
This will take a while to download and install so just sit back and let it do its thing. Once it's done downloading, restart your Raspberry Pi and log in with the password you changed earlier. Your first boot may take a while so just be patient, don't freak out if you see a single purple square in the center of the screen while it's loading. You should now have the Ubuntu desktop ready to go and now it's on to installing Bitcoin Core!
Installing Bitcoin Core 0.20.0
Since we're running Ubuntu Server 20.04 LTS, it should come preinstalled with the Snap Store. This makes installing apps very easy and works similar to pip install in Python. Simply open your terminal and type:
sudo snap install bitcoin-core
This will install Bitcoin Core into your Snap folder and will add the application to your system. Unfortunately, there are still a few steps left before we can begin downloading the blockchain. By default, Bitcoin Core doesn't have the removable-media Plug connected to the Socket. You can view this by typing:
snap connections bitcoin-core
This means when you try installing everything onto your external hard drive, Bitcoin Core won't be able to identify it or write to it even when passed the directory path. To fix this first locate your Snap folder, make a copy of the bitcoin-core folder inside, and paste it into your external drive.
NOTE: You must make a copy, you can't just move the snap file to the external drive.
Now, you can connect the removable-media Plug to the Socket by typing:
sudo snap connect bitcoin-core:removable-media :removable-media
This gives you the read/write permissions necessary to access the /media path. Finally, you can now launch Bitcoin Core and select "use a custom directory path" when prompted. Highlight the current directory path and replace it with the path to your external hard drive, it should look something like this:
/media/(external drive)/bitcoin-core/common/.bitcoin
This is why we had to make a copy of the bitcoin-core folder to the external drive earlier, the Bitcoin Core application will create the new data directory through ".bitcoin". Hit "Okay" and the application will begin synchronizing with the network! Once the synchronization is finished your very own node will be up and running!
EDIT: (08/01/2020) Bitcoin Core 0.20.01 has been released, I will update the tutorial soon with how to run the latest release.
submitted by Noblefire_62 to Bitcoin [link] [comments]

New Qubes OS Room on Matrix!

New Qubes OS Room on matrix!
 
This is just to let potentially interested people know that there is now a new Qubes OS room on matrix which is part of the +cybersec:matrix.org community. The rules for this group are simple, have a (qubes-ish) question, ask a (qubes-ish) question or take it to #cybersec-offtopic. In general the main rule is don't be a D*ck (not duck in case you were wondering, ducks are fine).
 
Some reasons/examples of why Qubes might be of interest:
 
And many more reasons. The room welcomes all, if you are a noob come ask a question, if you are a guru (not even necessarily with Qubes but maybe distro or application specific) please come and help add to the knowledge base! One of the main goals here is to have flexible and civil support/discussions related to Qubes.
 
Hope to see you all there!
PS Apologies to the mods if you do not consider this appropriate, I reviewed the rules and think its ok? My reasons for cross posting is that I think Qubes has a very real use case for this subreddit so I thought it would be useful for users in these subreddits and hopefully helpful for Qubes users as well.
submitted by privacytooled to privacytoolsIO [link] [comments]

Running a Bitcoin node on a $11.99 SBC

Running a Bitcoin node on a $11.99 SBC
Just wanted to let you guys know that I'm successfully running a (pruned) Bitcoin node + TOR on a $11.99 single board computer (Rock Pi S).
The SBC contains a Rockchip RK3308 Quad A35 64bit processor, 512MB RAM, RJ45 Ethernet and USB2 port and I'm using a 64GB SDCard. It runs a version of Armbian (410MB free). There's a new version available that even gives you 480MB RAM, but I'm waiting for Bitcoin Core 0.19 before upgrading.
To speed things up I decided to run Bitcoin Core on a more powerful device to sync the whole blockchain to an external HDD. After that I made a copy and ran it in pruned mode to end up with the last 5GB of the blockchain. I copied the data to the SD card and ran it on the Rock Pi S. After verifying all blocks it runs very smoothly. Uptime at the moment is 15 days.
I guess you could run a full node as well if you put in a 512GB SDcard.
The Rock Pi S was sold out, but if anybody is interested, they started selling a new batch of Rock Pi S v1.2 from today.
Screenshot of resources being used
Bitcoin Core info
Around 1.5 GB is being transferred every day
---
Some links and a short How to for people that want to give it a try:
  1. This is the place where I bought the Rock Pi S.
  2. Here you find more information about Armbian on the Rock Pi S. Flash it to your SDCard. Follow these instructions.
  3. Disable ZRAM swap on Armbian. If you don't do this eventually Bitcoin Core will crash. nano /etc/default/armbian-zram-config ENABLED=false
  4. Enable SWAP on Armbian sudo fallocate -l 1G /swapfile sudo chmod 600 /swapfile sudo mkswap /swapfile sudo swapon /swapfile sudo swapon --show sudo cp /etc/fstab /etc/fstab.bak echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab
  5. Set up UFW Firewall sudo ufw default deny incoming sudo ufw default allow outgoing sudo ufw allow ssh # we want to allow ssh connections or else we won’t be able to login. sudo ufw allow 8333 # port 8333 is used for bitcoin nodes sudo ufw allow 9051 # port 9051 is used for tor sudo ufw logging on sudo ufw enable sudo ufw status
  6. Add user Satoshi so you don't run the Bitcoin Core as root sudo adduser satoshi --home /home/satoshi --disabled-login sudo passwd satoshi # change passwd sudo usermod -aG sudo satoshi # add user to sudo group
  7. Download (ARM64 version) and install Bitcoin Core Daemon
  8. Download and install TOR (optional). I followed two guides. This one and this one.
  9. Create a bitcoin.conf config file in the .bitcoin directory. Mine looks like this: daemon=1 prune=5000 dbcache=300 maxmempool=250 onlynet=onion proxy=127.0.0.1:9050 bind=127.0.0.1 #Add seed nodes seednode=wxvp2d4rspn7tqyu.onion seednode=bk5ejfe56xakvtkk.onion seednode=bpdlwholl7rnkrkw.onion seednode=hhiv5pnxenvbf4am.onion seednode=4iuf2zac6aq3ndrb.onion seednode=nkf5e6b7pl4jfd4a.onion seednode=xqzfakpeuvrobvpj.onion seednode=tsyvzsqwa2kkf6b2.onion #And/or add some nodes addnode=gyn2vguc35viks2b.onion addnode=kvd44sw7skb5folw.onion addnode=nkf5e6b7pl4jfd4a.onion addnode=yu7sezmixhmyljn4.onion addnode=3ffk7iumtx3cegbi.onion addnode=3nmbbakinewlgdln.onion addnode=4j77gihpokxu2kj4.onion addnode=5at7sq5nm76xijkd.onion addnode=77mx2jsxaoyesz2p.onion addnode=7g7j54btiaxhtsiy.onion ddnode=a6obdgzn67l7exu3.onion
  10. Start Bitcoin Daemon with the command bitcoind -listenonion
Please note that I'm not a professional. So if anything above is not 100% correct, let me know and I will change it, but this is my setup at the moment.
submitted by haste18 to Bitcoin [link] [comments]

How to get a public static ip for your local lightning node

My lightning node is a node that is running locally on my server hardware in my house down under, far from the New Jersey Digitalocean datacenter, which is what will come up if you look up the ip of the node. This is done via an OpenVPN tunnel from your local machine to a VPS. I am doing this by renting a VPS from Digitalocean for $20 a month (2 vCPUs, 2GB RAM) running Ubuntu 18.04. You can do this just as easily on a $5 a month VPS with 1 vCPU and 1GB RAM or even a $2.50 a month VPS from Vultr with 512MB RAM. I needed the extra power because I have many web services running there as well.
This setup allows me to have a highly available lightning node, not affected by my home IP address changing. If you are using a mobile connection or have a CGNAT, you wont be able to port forward for your lightning node. This setup allows you to do so. You can also use this to make a portable lightning node, which can get you a full lightning node wherever you have power and internet, without having to mess with network settings. If you don't want others to know your home IP, this is a good option for privacy.
  1. Setup a local lightning node, preferably on a linux machine. I followed the Raspibolt tu`ial (with some tweaks) on a 2 vCPU and 8GB RAM VM running Ubuntu 16.04.
  2. Get a VPS with a static IP address. Digitalocean and Vultr VPSs already are. This VPS wont need much power, so get the cheapest one you can.
  3. Secure the VPS. I used this tutorial. Essentially, setup a non root user, use ssh keys, and setup ufw. Also make sure to allow port 9735 through ufw for lightning. I also additionally made adjustments to the ssh config and installed fail2ban.
  4. Setup an OpenVPN server on the VPS. I used this tutorial.
  5. Install on OpenVPN client on the local linux machine and connect to the server. The tutorial from step 4 shows how to this. Keep this connected for step 6.
  6. SSH into the VPS and figure out the OpenVPN IP address of the client. It should be 10.8.0.x. To figure out the x, setup a simple python web server or something on the local machine on port 8000 or something and open the port on ufw in the local machine. Keep the OpenVPN connection, and use a new ssh session when accessing your local machine. Don't kill the OpenVPN connection, as it may complicate things when finding the ip.
    mkdir testweb
    cd testweb
    echo hello >> index.html
    sudo ufw allow 8000
    python -m SimpleHTTPServer 8000
  7. SSH back into the VPS. Run the curl command below, and try all the numbers between 2-10 for x. When you get hello as your output, then you found the right IP. I found mine at 6. You may have to try higher numbers, but this is unlikely. You can kill your python webserver on your local machine once you find it.
    curl 10.8.0.x:8000
  8. Once you have the IP, you want to make this static, so it doesn't change when you reconnect. This is done on the VPS side, so ssh back into the VPS. This tutorial worked for me. Just make sure to change values like the CommonName and and the IP to match yours (client1 and 10.8.0.x). If it doesn't work search "make openvpn ip static" and look around.
  9. SSH into your local machine, and make the OpenVPN connection persistent. You can kill the OpenVPN connection now. Doing this and this worked for me. If it doesn't work search "openvpn keepalive" or "openvpn auto connect linux" or "make openvpn connection persistent linux".
  10. Restart your local machine, and make sure it connects on boot. Do the python webserver test again, and make sure the same ip is shown on the VPS, and it is still accessible.
  11. SSH back into the VPS. Now, you have to port forward with iptables. you have to add the 2 lines below starting with -A PREROUTING in the same place in your /etc/ufw/before.rules file. Here is what mine looks like. Change the x to your OpenVPN IP. Do sudo ufw disable and sudo ufw enable to restart ufw to update your changes.
    *nat
    :POSTROUTING ACCEPT [0:0]
    -A PREROUTING -i eth0 -p tcp -m tcp --dport 9735 -j DNAT --to-destination 10.8.0.x:9735
    -A PREROUTING -i eth0 -p udp -m udp --dport 9735 -j DNAT --to-destination 10.8.0.x:9735
    -A POSTROUTING -s 10.8.0.0/8 -o eth0 -j MASQUERADE
    COMMIT
  12. SSH into your local machine. Change your lnd.conf to match with this setup, like changing the externalip. Here is what my config looks like, a slight tweak from the Raspibolt one:
    [Application Options]
    debuglevel=info
    maxpendingchannels=5
    alias=GCUBED [LND]
    color=#68F442
    listen=0.0.0.0:9735
    externalip=157.230.95.74:9735
    [Bitcoin]
    bitcoin.active=1
    bitcoin.mainnet=1
    bitcoin.node=bitcoind
    [autopilot]
    autopilot.active=1
    autopilot.maxchannels=5
    autopilot.allocation=0.6
  13. Do a sudo service lnd restart to restart lnd and apply the changes. Remember to do a lncli unlock after any restarts. Your lnd node should now have a public static ip. Look it up a few hours after you do this on 1ml, your ip should be the one of your VPS now.
I am monitoring this for free with uptimerobot. It will notify you if it has gone down. So far mine has been running for 3 days and hasn't gone down.
EDIT: Formatting
EDIT 2: The main reason I didn't use a ddns or a hidden service was mainly for high uptime, and low latency. I am planning on developing a lapp with this node and I didn't want to risk any downtime. Running lightning as a hidden service is a great idea as well, this tutorial shows how to achieve something similar with the clearnet.
EDIT 3: You can achieve a similar result from using TOR
submitted by ggelango to Bitcoin [link] [comments]

Audit coming soon - feels good

Hi guys,
We have an ISO 27001 audit next week and my boss asked me to be prepared to arrange access to all our systems whenever required by the auditors.
Now I like to think of myself as a proactive employee rather than a reactive one if you catch my drift....so I have been looking at ways to automate the process just because I can.
Lately I have been really working on my skill sets, and it's all about automation and adopting a devops/agile mindset these days, so I created user's stories to put myself in an auditor's shoes and the first thing that hit me was how much time they waste looking for credentials when trying to log to some of our systems while they could be doing other things more gratifying for them.
After a long period of trial and error, I was finally able to reproduce my production setup to the test environment. I have used a mix of Ansible/Python/Bash/DSC/fortran/cobol/perl/go/ubuntu to totally remove authentication prompts on all servers, routers, firewall so you can RDP or SSH easily into all our critical systems without having to spend an hour finding and typing a complicated password. I know the auditors like to wrap things up quickly because they like to take their time at our cafeteria since it has a great food selection.
I like to think it as a friendly open house visit, where auditors will be greeted with a drink and have all the freedom to look at very room so they can project themselves into our premises, I am thinking long term relationship.
I hope my boss will appreciate the effort and I cant wait to see the auditors face when I'll tell them they can even RDP from home next time without passwords if they want to watch the football game lol :)
Anyways if anyone is interested with my code I will put everything on Github, please change my public IPs with yours otherwise you will just connect to my servers
EDIT: WOAH looks like the post is blowing up and people are interested! If you feel like giving back, my bitcoin address is 1BvBMSEYstWetqTFn5Au4m4GFg7xJaNVN3
submitted by leaving_los_vegans to ShittySysadmin [link] [comments]

Vertnode - An automated solution for installing Vertcoin node(s) on Single Board Computers

Hello Vertcoin Community,
Eager to contribute to the Vertcoin Community I began creating step by step walkthrough guides on how to get a Vertcoin node up and running on a Raspberry Pi, Raspberry Pi Zero and Intel NUC. Along with information to get a Vertcoin node up and running was also optional steps to install p2pool-vtc.
I decided that while this step by step guide might be helpful to a few, a setup script may prove to be useful to a wider range of people. I have this script to a point where I think it may be productive to share with a bigger audience, for those who are brave and have this hardware sitting around or like to tinker with projects; I invite you to test this setup script if you are interested, if you run into errors any sort of verbose console output of the error proves to be extremely helpful in troubleshooting.
The script was designed to produce a “headless” server... meaning we will not be using a GUI to configure Vertcoin or check to see how things are running. In fact, once the server is set up, you will only interact with it using command line calls over SSH. The idea is to have this full node be simple, low-power, with optimized memory usage and something that “just runs” in your basement, closet, etc.
Why run a headless node on a Single Board Computer?
The idea is to have this full node be simple, low-power, with optimized memory usage and something that “just runs” in your basement, closet, etc.
Required: USB Flash Drive 6GB - 32GB
Please note that the script was designed for Single Board Computers first and looks for an accessible USB Flash Drive to use for storing the blockchain and swap file, as constant writing to a microSD can degrade the health of the microSD.
Supports

Hardware

All of the hardware listed above is hardware that I have personally tested / am testing on myself. The plan is to continue expanding my arsenal of single board computers and continue to add support for more hardware to ensure as much compatibility as possible.
Functionality
It is worth noting that LIT can be ran with multiple configurations, the ones displayed in the Post Installation Report reflect values that run LIT with the Vertcoin Mainnet. Please be aware that the Vertcoin Testnet chain has not been mined 100% of the time in the past, if you make transactions on the Vertcoin testnet that do not go through it is likely because the chain has stopped being mined.
BE CAREFUL WITH YOUR COINS, ONLY TEST WITH WHAT YOU ARE OKAY WITH LOSING IF YOU USE THE MAINNET.

Vertcoin Testnet Coins

https://tvtc.blkidx.org/faucet/
I've included some documentation on LIT I created which includes information I found to be useful: https://github.com/e-corp-sam-sepiol/vertnode/blob/mastedocs/lit.md
Please visit the mit-dci/lit github repository for the most up to date information on lit: https://github.com/mit-dci/lit

Vertnode | Automated Vertcoin Node Installation Script

https://github.com/e-corp-sam-sepiol/vertnode

Recommended: Use Etcher to install the chosen OS to your microSD card / USB flash drive.

If you intend on installing Ubuntu Server 16.04 to your Intel NUC please use Etcher to install the .iso to your USB flash drive.
https://etcher.io/
PLEASE NOTE THIS SCRIPT MAY GIVE AN ERROR. THIS IS THE NATURE OF TESTING. PLEASE REPORT YOUR ERRORS IF YOU WANT THEM TO BE FIXED/RESOLVED. THANK YOU FOR BETTERING THE DEVELOPMENT OF THIS SCRIPT.

Ubuntu Server 16.04 Setup Details

You can use different clients to ssh into your node. One option is using PuTTY or Git Bash on Windows which is included in the desktop version of Git. If you are using Linux you can simply open a new terminal window and ssh to the IP address of your node (hardware you intend installing the Vertcoin node on).
You will need to know the IP address of your node, this can be found on your router page.
ssh 192.168.1.5 -l pi For example, this command uses ssh to login to 192.168.1.5 using the -l login name of pi. The IP address of your node will likely be different for you, in this example I am logging into a Raspberry Pi which has a default login name of pi.
A brief list of commands that can be used to check on the Vertcoin node status:
vertcoin-cli getblockchaininfo | Grab information about your blockchain
vertcoin-cli getblockcount | Grab the current count of blocks on your node
vertcoin-cli getconnectioncount | Grab the current count of connections to your node. A number of connections larger than 8 means that you have incoming connections to your node. The default settings are to make 8 outgoing connections. If you want incoming connections please port forward your Raspberry Pi in your Router settings page.
vertcoin-cli getpeerinfo | Grab the information about the peers you have connected to / are connected to
vertcoin-cli getnettotals | Grab network data, how much downloaded/upload displayed in bytes
tail -f ~/.vertcoin/debug.log | Output the latest lines in the Vertcoin debug.log to see verbose information about the Vertcoin daemon (ctrl+c to stop)
Thank you to all who have helped me and inspired me thus far, @b17z, @jamesl22, @vertcoinmarketingteam, @canen, @flakfired, @etang600, @BDF, @tucker178, @Xer0
This work is dedicated to the users of Vertcoin, thank you for making this possible.
7/20/2018 Thank you @CommodoreAmiga for the incredibly generous tip <3
You can reach me @Sam Sepiol#3396 on the Vertcoin Discord, here on reddit or @ [email protected]
submitted by ecorp-sam-sepiol to vertcoin [link] [comments]

Lightning node setup - estimation (time needed)?

Hi, at work I may try to sell this idea to my boss, to setup a bitcoin lightning node. We have a good infrastructure and it would be quite cool to have a node running on one of our dedicated VMs.

My boss or the person who will approve/deny this idea may ask me of course how much will this cost, in time and money. I didn't do much research yet, but seen several tutorials how to setup a lightning node... thus I may include also the time to do more research...

Here various tutorials I've found so far:
- Detailed guide to installing LND and Bitcoind on Ubuntu 16.04 LTS for Mainnet (this seems very good for ubuntu users)
- Bitcoin Lightning Node on Ubuntu Linux
- The Lightning Network: How to install and (hopefully) make money
- Installing Lightning Network part 2: Here We Go Again
- Bitcoin Lightning Network: run your node at home for fun and (no) profit (explains how to install LND, which saves space as the blockchain doesn't need to be stored locally)

Other resources:
- Bitcoin Core Download (since I use ubuntu I may use the PPA)
- Lightning LND Releases (this still needs to be compiled)

Can you help me estimating this task? I tried to split it into sub-tasks:
- Install Ubuntu Linux on VM, setup SSH, firewalls, basic dependencies: 4h
- Follow tutorial to install bitcoin and lightning daemons: 8h
- Setup/automate backup: 4h
- Documentation (write down notes -if different than existing tutorials- to make things work & share the results): 4h
- Time spent researching, estimating, making an offelittle presentation of the project: 4h

Total estimation: 3 days
- The initial step to download and verify the blockchain (even if in prune mode it won't be stored, this is required) takes a few days

Is this realistic? Did I forget some parts? Should I estimate more time? (I personally tend to underestimate tasks)

Your feedback is welcome, thank you
submitted by firepol to Bitcoin [link] [comments]

Looking to see if a seedbox is a good fit

First let me lay out what I have and how I use it, and then I'll go thru the Q&A from the sticky.

I am currently using a private tracker (IPT) that I have no real issues with. I pay every 6 months, and use it daily. I mainly grab movies and TV shows. I also have a VPN that I am fairly happy with, although I haven't figured out the port-forwarding they offer.
I have 3 computers that tie all this together:
-A centos7 box that runs Medusa. I have a 4x2tb raid array for storage of the TV shows. There are ~10000 files and 5tb of used space on the array. Medusa grabs torrents from the tracker and sends them to:
-An ubuntu box that runs transmission. It connects to the array on the centos machine via NFS. This machine uses the VPN, it is not visible outside my home network. This machine also runs Couchpotato. After downloading torrents, I view them on:
-My win10 machine running Plex. It connects to the raid array on centos via CIFS mount. I have a 2x4tb storage on this machine that stores the movies. There are 1250 files using 2.7tb. This machine is a few months old and has tons of horsepower - [email protected], 32gb ram, 2x1tb 970 EVO m.2 drives. Plex runs with no issues.
Putting all this together was fun, but now I have 3 computers running all the time just so I can watch tv shows and movies I download. I've been hearing more and more about seedboxes, I was hoping I could use one to do the work of the 2 linux boxes as far as downloading and seeding torrents (at least to start), and I'm guessing I move the files to my local network after they've been downloaded, then I also can leave them up for seeding on the seedbox to maintain a good ratio. This is where I'm a bit fuzzy....should I leave well enough alone or spend a bit to streamline the whole thing?

Here's the Q&A:
What is the primary reason for getting a seedbox? DMCA? Ratio? Wife discovered Porn? Please expand.
See above, trying to simply my existing setup and maybe tighten security.

Location (yours and/or the vendors)? Most seedboxes are concentrated in Europe (France, Netherlands, Germany)
I'm in USA

Particular speed (100M, 1G, 10G, Ludicrous Speed, etc)? Slow, fast, fastest.
Not the biggest factor, but faster is always better. I get 300Mbps from my ISP.

Do you use public trackers extensively?
Almost never. In 4-5 years, I've gotten one notice from my ISP, it was a torrent I got from TPB.

How much experience do you have with seedboxes, linux, and alike? Need a lot of handholding?
Newb on seedboxes, pretty good on linux (for a machinist).

Is your location problematic? e.g. I'm at university. I'm one of three people on the island of Yap.
No.

Particular payment methods the vendor needs to accept: bitcoin, paypal, paysafecard, Turkish Lire?
Paypal preferred, no bitcoin.

Particular content: Games, TV shows, Anime; Movies; Remuxes; the oeuvre of Fatty Arbuckle?
TV and Movies

Using problemsome trackers like public ones or challenging trackers like RED and CHD?
No. Using IPT for last 3 years.

Any idea on how much bandwidth you need a month? 1TB; 3TB; 30TB?
We use 1-2tb /month

Are you a paranoiac, need special safety assurances?
Why, did someone say I was paranoid?

Other more unique requirements? You want to run a website too; Azureus is your favorite client, can't live without it; Or god forbid you really, really need Windows.
Medusa for sure, transmission or equivalent, rsync, ssh
submitted by rabid_lamb to seedboxes [link] [comments]

Looking for a dedicated server/seedbox or something close.

40 - 65 euros.
4TB+
Prefer dedicated but can do shared if it's a good deal.
Racing and Plex, want to race as much as I can but still be able to enjoy Plex and have it setup.
I want to seed as much as I can
Europe, doesn't matter where but locations beside Germany are a little more open to public trackers.
1G At least.
Quite rarely, only when IPT doesn't find what I need. (don't bully me I was never able to get into other trackers)
Been using seedboxes for many years and I have okayish linux experience, minimal/medium handholding. (although I usually just use a script like swizzin or the one to rule all)
Not at all, I have a 1G connection at home and my ISP is pretty open to torrenting and don't care. :)
PayPal, BTC, Credit Card is fine.
I mostly just watch the latest TV Shows and Movies and whatever autodl picks up to race and boost up ratio.
No I only use IPT and some public trackers sometimes. I just got accepted into AvistaZ but their rules are simple. :)
Anything above 20TB. I'd like to at least upload 20TB or more a month to give back to you awesome lads.
Not at all, country doesn't care, I don't care.
I'd like to run Nextcloud and a bunch of other apps like basically bytesized seedbox. I usually mess up a lot while setting up my server so I reinstall ubuntu pretty often until I get it right cause I'm not that good at it, so SHH would be nice.
I know about Andy and I've used him in the past to tune up my server and he's fantastic. I just don't think I can get what I would like at my price range and as far as I know he doesn't allow SSH but I wouldn't mind if he had a server at my price point. :(
submitted by MrTiesti to seedboxes [link] [comments]

Small form factor for home server and Bitcoin node

Before I start, let me emphasize on the fact that this request is something probably quite unusual for this sub and I apologize if it doesn't belong here. If that's the case, please let me know.

What will you be doing with this PC? Be as specific as possible, and include specific games or programs you will be using.
I'm looking for a small, quiet and affordable computer which will run 24/7 in my house. The aim is to make it a personal server and a Bitcoin node (not for mining, just a node).
A Bitcoin node should run on hardware with good endurance, stable internet connection, a large storage and that can run for a long period of time.

What is your maximum budget before rebates/shipping/taxes?
300€

When do you plan on building/buying the PC? Note: beyond a week or two from today means any build you receive will be out of date when you want to buy.
Anytime during this summer.

What, exactly, do you need included in the budget? (ToweOS/monitokeyboard/mouse/etc)
I'm not sure if it's the right place but here are my criteria:

Which country (and state/province) will you be purchasing the parts in? If you're in US, do you have access to a Microcenter location?
France

If reusing any parts (including monitor(s)/keyboard/mouse/etc), what parts will you be reusing? Brands and models are appreciated.
I will use this computer as as server so via SSH after the install. I already own some spare monitors and peripherals.

Will you be overclocking? If yes, are you interested in overclocking right away, or down the line? CPU and/or GPU?
No

Are there any specific features or items you want/need in the build? (ex: SSD, large amount of storage or a RAID setup, CUDA or OpenCL support, etc)
As said earlier, I need a large storage for the Bitcoin node. I'm thinking about a 2TB NAS HDD so it can last for a very long time. The NAS variant of HDD is probably the one which suits my needs the most as the disk will be very frequently accessed and will run 24/7.

Do you have any specific case preferences (Size like ITX/microATX/mid-towefull-tower, styles, colors, window or not, LED lighting, etc), or a particular color theme preference for the components?
Mini ATX if possible. I'd prefer a small form factor. The most important part of the case is its protectiveness, the rest is not important.

Do you need a copy of Windows included in the budget? If you do need one included, do you have a preference?
No, I will install a linux distro.

Extra info or particulars:

I found the Odroid H2 and Odroid HC2 which fit my needs perfectly but they are either sold out, unavailable or have insanely high customs fees. Also I checked Intel NUCs but I'm not sure it is what I need, especially for the price. A Raspberry Pi is not a good choice because of the storage capabilities (connected by USB 2.0) and limited RAM.
I considered building a machine myself but I'm not sure which components to use, and where to buy them. This is why I came here and this is something I'm still open to, if the price is not too high.
submitted by ImAFlyingPancake to buildapcforme [link] [comments]

Creating a Headless Staking Node on Ubuntu 18.04

Creating a Headless Staking Node on Ubuntu 18.04
##UPDATE## Step 8 - Option 2, has some bugs in the final build process. i haven't had time to work them out yet!

This guide will take you through building and running a headless x42 Full Node! The OS I am using here is Ubuntu 18.04, this guide picks up from a complete/fresh ubuntu install.
This is meant to setup a staking node and so this guide will run you through building, configuring and setting up staking. It will not cover sending transactions or anything else.
The things we are going to do:
  • Step 1 - Install .net core
  • Step 2 - Download The x42 Node Source & Compile It
  • Step 3 - Setting The x42 Node Up To Run On Boot
  • Step 4 - Setup A New Wallet
  • Step 5 - Configure The x42 Daemon
  • Step 6 - Get Address
  • Step 7 - Check Balance
  • Step 8 - Connect The UI Wallet To A Headless Node
  • Step 8 - [Option 1 - Use Installer] Connect The UI Wallet To A Headless Node
  • Step 8 - [Option 2 - Build/Compile UI Only] Connect The UI Wallet To A Headless Node # BROKEN#

Step 1 - Install .net Core

Here is the reference link:
https://dotnet.microsoft.com/download/linux-package-manageubuntu18-04/sdk-current
Register Microsoft Key’s & Install Their repos:
cd /tmp wget -q https://packages.microsoft.com/config/ubuntu/18.04/packages-microsoft-prod.deb sudo dpkg -i packages-microsoft-prod.deb sudo add-apt-repository universe sudo apt -y install apt-transport-https sudo apt update sudo apt -y install dotnet-sdk-2.2 
Microsoft collect telemetry data by default, if you are part of the “tin foil hat brigade” you can set the following environment variable to turn it off:
echo "DOTNET_CLI_TELEMETRY_OPTOUT=1" >> /etc/environment 
now you should be at a point where .net core is installed on your system… that wasn’t so hard was it! You can check by running the following command:
dotnet--list-sdks 
The output should look like this:
$ dotnet --list-sdks 2.2.103 [/usshare/dotnet/sdk] 

Step 2 - Download & Compile The x42 Node

This part assumes you have GIT installed, if not:
apt -y install git 
Now to pull down the source and compile it!
cd ~/ git clone https://github.com/x42protocol/X42-FullNode.git # “cd” into the source folder cd X42-FullNode/src/ 
Now .net core uses NuGet for package management, before we compile, we need to pull down all of the required packages.. its as simple as running (this will take a couple of minutes) inside of “X42-FullNode/src/”:
dotnet restore 
now we are ready to compile the source, execute (inside of “X42-FullNode/src/”):
dotnet build --configuration Release 
ignore the yellow warnings, this is just the rosyln compiler having a grumble.. if you get red ones then something went wrong! The “--configuration Release” will strip out all debug symbols and slim things down.. only a little, this optional parameter is not mandatory.
Once this is done everything is built/compiled, you can run the daemon directly from the repository, this can be done by going to:
cd ~/X42-FullNode/src/x42.x42D/bin/Release/netcoreapp2.1 dotnet x42.x42D.dll 
this will kick off the node, however if you exit SSH at this time it will kill the process! however I always recommend copying out the binaries to a separate folder. This can be done with the following:
mkdir ~/x42node mv ~/X42-FullNode/src/x42.x42D/bin/Release/netcoreapp2.1/*.* ~/x42node/ 
now we have everything we need to run the node outside the git repository! What we need to do now is run the node and have it create the default x42.conf file.. so
cd ~/x42node dotnet x42.x42D.dll 
feel free to hit “CTRL + C” to exit the application after a couple of seconds, by then the folders/files would have been created at the following path:
~/.x42node/x42/x42Main/ 

Step 3 - Setting The x42 Node Up To Run on Boot

Now we are going to create a service file so our x42 node automatically starts when the system is rebooted.
THINGS TO NOTE ABOUT BELOW.. CHANGE THE ##USER## to the username your currently using as these files are within your home directory!
We need to drop to root for this..
sudo -i cat < /etc/systemd/system/x42node.service [Unit] Description=x42 Node [Service] WorkingDirectory=/home/##USER##/x42node ExecStart=/usbin/dotnet /home/##USER##/x42node/x42.x42D.dll Restart=always # Restart service after 10 seconds if the dotnet service crashes: RestartSec=10 SyslogIdentifier=x42node User=##USER## Environment=ASPNETCORE_ENVIRONMENT=Development [Install] WantedBy=multi-user.target EOF 
To enable the service, run the following (as the root user):
systemctl enable x42node.service 
BOOM.. the node isn’t running yet.. but next time the system restarts it will automatically run!
now lets exit out of root!
exit 
We can now start the node up and begin downloading blocks, by running the following command:
sudo systemctl start x42node.service 
if you want to check its loaded and see some of the output, you can run:
sudo systemctl status x42node.service 
an example of the output:
$ sudo systemctl status x42node.service ● x42node.service - x42 Node Loaded: loaded (/etc/systemd/system/x42node.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2019-01-24 15:47:55 UTC; 14s ago Main PID: 5456 (dotnet) Tasks: 23 (limit: 1112) CGroup: /system.slice/x42node.service └─5456 /usbin/dotnet /home/darthnoodle/x42node/x42.x42D.dll Jan 24 15:48:09 x42staking x42node[5456]: Batch Size: 0 Mb (0 headers) Jan 24 15:48:09 x42staking x42node[5456]: Cache Size: 0/50 MB Jan 24 15:48:09 x42staking x42node[5456]: Jan 24 15:48:09 x42staking x42node[5456]: =======Mempool======= Jan 24 15:48:09 x42staking x42node[5456]: MempoolSize: 0 DynamicSize: 0 kb OrphanSize: 0 Jan 24 15:48:09 x42staking x42node[5456]: Jan 24 15:48:09 x42staking x42node[5456]: info: Stratis.Bitcoin.Connection.ConnectionManagerBehavior[0] Jan 24 15:48:09 x42staking x42node[5456]: Peer '[::ffff:86.184.76.255]:52342' connected (outbound), agent 'x42:1.2.13 (70012)', height 213920 Jan 24 15:48:09 x42staking x42node[5456]: info: Stratis.Bitcoin.Connection.ConnectionManagerBehavior[0] Jan 24 15:48:09 x42staking x42node[5456]: Peer '[::ffff:86.184.76.255]:52342' offline, reason: 'Receiving cancelled.'. All node screen output can be found in the /valog/syslog file. 

Step 4 - Setup a New Wallet

With the Node running, we now need to setup and/or restore a wallet!
Everything will be performed through the API’s, however by default these API’s are listening on localhost (127.0.0.1), if you are connecting in remotely then this would be a problem since you cant hit that IP. The solution, SSH TUNNEL!
Execute the following command on your local system:
ssh -L 42220:localhost:42220 @ 
This binds the local port (on your system) with 127.0.0.1:42220 on the remote system, once you have executed the command you can type the following address in your laptop/desktop’s web browser and be able to access the API’s:
http://127.0.0.1:42220/swaggeindex.html 
It should look something like this:
https://preview.redd.it/9lzeg3vob8d21.jpg?width=482&format=pjpg&auto=webp&s=b5d574998816056140d5d6de7b03c56772a892fe
To Create a new wallet, first we have to generate some mnemonic works (e.g. the seed), you can do that by going to the following API:
/api/Wallet/mnemonic 
Hit the “Try it out” button which then prompts you for 2 fields:
https://preview.redd.it/dvbdllfrb8d21.jpg?width=722&format=pjpg&auto=webp&s=766d14bafba6facbcd56d31c63c0012748e682e5
Enter “English” and I would recommend 24 words as this greatly increases the seed strength! Once that is done you hit execute and then scroll down to see the “Response Body”, this should contain the mnemonic which you are going to use to create the wallet! This looks something like below:
https://preview.redd.it/6p4q0rsub8d21.jpg?width=603&format=pjpg&auto=webp&s=44b9265626467a43ca670b134c4d28187f475c2e
THIS IS VERY IMPORTANT, BACKUP THIS MNEMONIC TO A SAFE SECURE LOCATION THAT IS ENCRYPTED!!!
So now we have our mnemonic, its time to generate the wallet, for this we need to use the API:
/api/Wallet/create
There are a number of parameters which are required in order to create a wallet:
WalletCreationRequest{ mnemonic string password* string passphrase* string name* string } 
It should be noted that the password and mnemonic are is the most important parts of this request where the “password” will encrypt the wallet and Is required to unlock it.
  • Hit the “Try it out” button
  • input the necessary data
  • Insert the mnemonic
  • Put a password & passphrase
  • “Name” is what your wallet will be called
It should look something like the following:
https://preview.redd.it/958ttfbxb8d21.jpg?width=603&format=pjpg&auto=webp&s=ce48336436ea4b469b5e87513da802de0bf444ee
Hit “Execute”, the “Loading” sign may spin for a few minutes while the wallet is created… once the wallet has been created the “Response Body” will return the mnemonic you have just used.. we now have a wallet!!
HOWEVER IT IS NOT LOADED INTO THE NODE JUST YET!
This is where we will now jump back out and to configure the node to automatically load the wallet and automatically start staking when it first loads.
AGAIN BACKUP YOUR MNEMONIC AND PASSWORD, MAKE SURE THEY ARE ENCRYPTED AND STORED SOMEWHERE SAFE!

Step 5 - Configure The x42 Daemon

Now we are going to modify the x42.conf file in order to automatically load our wallet and start staking 😊
First things first, lets stop our node by running the following command:
sudo systemctl stop x42node.service 
CD to the following folder and view its contents:
~/.x42node/x42/x42Main ls -lah 
within that folder there should be 2 files you are interested in:
-rw-r--r-- 1 darthnoodle darthnoodle 18K Jan 28 16:01 TestWallet.wallet.json -rw-rw-r-- 1 darthnoodle darthnoodle 3.1K Jan 24 15:25 x42.conf 
So TestWallet.wallet.json is our physical wallet that will be loaded, but for right now we want to modify the x42.conf file.. fire up your favourite text editor (if you use VI you’re a masochist)..
nano x42.conf 
The area we are interested in is the following:
####Miner Settings#### #Enable POW mining. #mine=0 #Enable POS. #stake=0 #The address to use for mining (empty string to select an address from the wallet). #mineaddress= #The wallet name to use when staking. #walletname= #Password to unlock the wallet. #walletpassword= #Maximum block size (in bytes) for the miner to generate. #blockmaxsize=1000000 #Maximum block weight (in weight units) for the miner to generate. #blockmaxweight=1000000 #Enable splitting coins when staking. #enablecoinstakesplitting=1 #Minimum size of the coins considered for staking, in satoshis. #minimumstakingcoinvalue=10000000 #Targeted minimum value of staking coins after splitting, in satoshis. #minimumsplitcoinvalue=10000000000 
Uncomment (remove the #) of the following lines and change their value:
stake=1 (changed to 1) walletname=TestWallet (changed to our Wallet Name) walletpassword=password123 (changed to the wallet password) 
save the file and exit back to the command prompt, now we shall restart the node with the following command:
sudo systemctl status x42node.service 
now the wallet is automatically loaded and ready for action!
YES I KNOW YOU HAVE PUT YOUR PASSWORD IN CLEARTEXT, THIS IS WHERE YOU SHOULD HARDEN YOUR BOX. IF THEY CAN GET TO THE POINT WHERE THEY CAN READ YOUR CONF FILE THEY CAN JUST GRAB YOUR WALLET AND BRUTEFORCE THE PASSWORD.
You can check its loaded by going back to the API and executing the following command:
/Dashboard 
Or execute the following command on the NODE:
curl -X GET "http://127.0.0.1:42220/Dashboard" -H "accept: application/json" 
both will produce the same output, if you scroll to the bottom you should see something like this:
======Wallets====== TestWallet/account 0, Confirmed balance: 0.00000000 Unconfirmed balance: 0.00000000 
This means the wallet is loaded and ready for action!!

Step 6 - Get Addresses

Next thing you are probably going to want is a receive address and to check the balance and TX history.. so lets start with getting an address!
Go to the following API:
/api/Wallet/unusedaddress 
Fill in the Wallet name which is “TestWallet” (in this example) and “account 0” (which is the first/default account):
https://preview.redd.it/ayri5jk0c8d21.jpg?width=602&format=pjpg&auto=webp&s=2d16bbb78da49c0125d24d0834c9454d702cb7a1
Hit execute and you should have an x42 address within the “Response Body”:

https://preview.redd.it/tmc495j3c8d21.jpg?width=349&format=pjpg&auto=webp&s=b00177f66a9e24c980d3c6d4e532a33cbf3fb0bc
BOOM… ok now we can receive funds! 😊

Step 7 - Check TX History

Go to the API and the following call:
/api/Wallet/history 
The 2 fields we are most concerned about are:
https://preview.redd.it/lw194af6c8d21.jpg?width=602&format=pjpg&auto=webp&s=27e264bc008879355ff5b9c50a0a5cb06f16e960
Input the name of the wallet and account you want to view the history of, then hit execute. The other fields can be black. This will return a list of TX’s that the wallet has received:
This should look like the following:
https://preview.redd.it/x1hgargac8d21.jpg?width=585&format=pjpg&auto=webp&s=4fd25f22772f4bcec523a6e82b321ae8146a2c75
There is an easier way of doing this, that doesn’t require you to be connected to your node.. especially if your only interested in viewing your staking rewards… THE EXPLORER!
Access the following URL:
https://explorer.x42.tech/address/ 
this will allow you to easily see all TX’s associated with this address, it should look something like below:
https://preview.redd.it/e480grscc8d21.jpg?width=601&format=pjpg&auto=webp&s=0f8a9ebc7944dfcc73f7df659bd839bb983ba90c
… and your done! By this point your node should be running, staking and you have an easy way to view transactions/rewards 😊


Step 8 - Connect The UI Wallet To A Headless Node

The UI utilises a combination of technologies, however the important part is the code attempts to access the x42 Node API on 127.0.0.1:42220.
So you have 2 options here:
  1. Download the Wallet Installers
  2. Compile The UI Yourselves
Pick the option that best suits you given the pros/cons below:
Option 1 - Pro's/Cons
Pro's
  • If you use the installer, its quick and easy.
Cons
  • This also installs an x42 node on your system which runs when the UI loads.
  • If you dont setup an SSH tunnel before running the wallet the local node will bind to the port and the tunnel wont work.. you will be connecting to the local wallet!!
Option 2 - Pro's/Cons
Pro's
  • You only run the UI, the x42 node is not installed
  • you dont have a superfluous node running, downloading blocks on your local system
Cons
  • Time Consuming
  • Have to download dependencies and manually compile the code

Pre-Requirement - Needed For Both Options!!
As previously mentioned, the UI attempts to access the API's on 127.0.0.1:42220, however our node isnt running on our local system. IN ORDER TO GET IT WORKING YOU NEED TO HAVE AN SSH TUNNEL, THIS TUNNEL NEEDS TO REMAIN ACTIVE WHENEVER YOU WANT TO ACCESS THE WALLET.
this can be done by executing the following command:
ssh -L 42220:localhost:42220 @ 


Step 8 - [Option 1 - Use Installer] Connect The UI Wallet To A Headless Node

Download and install the UI/Wallet & Node from:
https://github.com/x42protocol/X42-FullNode-UI/releases

DO NOT RUN THE WALLET YET!
Those of us who dont want to run a local node and just want the UI, execute the following commands (as an administrator):
cd C:\Program Files\x42 Core\resources\daemon\ ren x42.x42D.exe x42.x42D.exe.bak 
The above is with Windows, if your are in *NIX then locate the daemon and rename it (i will update how to do that/where to find it shortly)
Setup the SSH tunnel as outlined above, Execute the wallet and it will load, however you will see an exception:

https://preview.redd.it/9os5h8q7scd21.jpg?width=550&format=pjpg&auto=webp&s=ac45ed7bc987917142075c61fb486e7d71f820d1
dont worry, this is just the wallet trying to execute/start the x42 node which we dont want, if all works according to plan.. after you click "OK" you should now be presented with the wallet UI and have the option to select what wallet you would like to load:

https://preview.redd.it/hnyt0b4mscd21.jpg?width=958&format=pjpg&auto=webp&s=a47df710a804375d8363ffcd77d1ede2862b9b4d
... DONE!

Step 8 - [Option 2 - Build/Compile UI Only] Connect The UI Wallet To A Headless Node ###BROKEN

THIS IS STILL A WORK IN PROGRESS, THE ELECTRON BUILD DOESNT WANT TO COMPILE BECAUSE SOME CODE IS MANGLED SOMEWHERE!!

Ok, this is the fun bit! .. we need to install the following dependencies. these instructions are written for a Windows system but it should be easy enough to perform the same on a *NIX system.
Install Dependencies
In order to build the wallet UI, you need to install the following components:
  • git
  • NodeJS
  • Electron Builder
First thing you need to do is install git, so download and install the package:
https://gitforwindows.org/
Next you need to install NodeJS, download and install the package:
https://nodejs.org/en/download/
Next we need to install the node package manager:
npm install npx –verbose 
next we need to make sure we have Visual Studio build tools and Python (2.7) installed, this can be done by executing the following (AS AN ADMINISTRATOR!):
npm install -g --production windows-build-tools 
this will install the necessary tools to build C#/C++ code and python 2.7, this could take some time! When its done you should have something like the following;

https://preview.redd.it/5ekfy5g1kcd21.jpg?width=490&format=pjpg&auto=webp&s=f65196dee6f78f2ececec5ee8b5df1044d68f635

Build & Install - Windows
Create a temp folder to navigate to a folder where you want to download the GIT repository, execute the following command:
git clone https://github.com/x42protocol/X42-FullNode-UI.git 
This will clone the repository into the folder, it will only clone the wallet and not the Node source! now lets CD into the folder and build the UI:
cd X42-FullNode-UI\FullNode.UI npm install 
This will download and install all dependencies (can take a while), at the end you should see something like..

https://preview.redd.it/0zfbfxa8kcd21.jpg?width=601&format=pjpg&auto=webp&s=438d072a6ab2bc7a3d84a8dfe773968acc762bc7
Now the stock UI has a number of third-party libraries which contain some vulnerabilities, being a security conscious person, ive also run:
npm audit fix 
when this is done, we have fixed most of the package vulnerabilities 😊 We also get a complaint about the typescript library being too new for the version of angular in use, so run the following command to install the additional dependency:
npm install [email protected]">=2.4.2 <2.7.0" 
now its time to build the UI, execute the following:
npm run build:prod 
once complete you should see something like the following..

https://preview.redd.it/56vf9zfckcd21.jpg?width=601&format=pjpg&auto=webp&s=31b72daff9ab5001843cba529a7bd38c76fd099d
Next its time to compile the electron binary, it should be noted that the build/package process utilises AppVoyer which is not installed and if you attempt to build right now you will get the following error:
cannot expand pattern "${productName}-v${version}-setup-${os}-${env.arch}.${ext}": env arch is not defined. 
To fix this we need to modify the build file, this is a quick one liner that can do it:
powershell -Command "(gc electron-builder.json) -replace 'env.arch', 'arch' | Out-File electron-builder.json" 
Essentially the offending line for Windows is..
"artifactName": "${productName}-v${version}-setup-${os}-${env.arch}.${ext}" 
The build cannot resolve “env.arch”, so the above one liner replaces “env.arch” with “arch” which works 😊
execute the following command:
npx electron-builder build --windows --x64 
At present i get the following error, no matter what i do.. and ive ran out of time to go hunting about.. if anyone has any ideas on how to fix then please post in here or message me on discord:

https://preview.redd.it/t66rtuqdtcd21.jpg?width=918&format=pjpg&auto=webp&s=a3f1a5ff682586348909c67645ca7ae9454922ff


Happy staking!

If you found this post helpful, then buy me a beer and send a donation to XQXeqrNFad2Uu7k3E9Dx5t4524fBsnEeSw
submitted by D4rthNoodle to x42 [link] [comments]

How I stopped bitching and started my own bitcoinxt node

Hi sorry for the mean title, I'm developer and I really care about bitcoin and I want to do something to help, so I made this simple script to start your own bitcoinxt node. I tried to make it as simple as possible for anyone who has 5 minutes, regardless of your technical ability. It costs $25 a month (first month free) to vote with your code, so please help out if you care enough to complain. So here's instructions for how to setup a google cloud instance of bitcoinxt.

Get a google cloud account

Go to https://cloud.google.com/
Click on the "Try it free" button
Sign into google
Fill out your personal info
Click on the "My console" link in the top right corner of the cloud page, after signing in
Click on the 3 horizontal bars in the top left of the page, it should pull out a drawer. Go down to "Compute Engine" and click on it.

Create your instance! (Exact flow might be slightly different, use your head and look around!)

Create a project name, say no to the emails and click "Create"
Click on "VM Instances" on the left
Click the button "New instance" top center of the page
Name your instance something like "bitcoinxt-01"
Leave the Machine type as 1 vCPU 3.75 GB of memory
Pick Ubuntu 15.10 (Any ubuntu will do for this script)
Leave Boot disk type as "Standard persistent disk"
Set Boot disk size to 100GB and click create
Wait for the spinning wheel to turn into a green check

Setup the firewall!

Click on the green check, scroll down to where it says
Network default
Click on "default"
Click "Add firewall rule"
Set "bitcoin" as the name
Set "Source filter" to "Allow from any source (0.0.0.0/0)"
Set "Allowed protocols and ports" to "tcp:8333" and click "Create"

Install bitcoinxt!

Click the SSH button at the top left above the green check, this should open a new tab with a command line in it. You can type stuff here.
Copy this command into the command line
wget -O- https://gist.githubusercontent.com/snakecharmer1024/97bcc84f6336ee50e63d/raw/9d15cb62c4e53ba27f5f7e00c71404f437d2cf64/bitcoinxt-installer.sh | sudo bash
or if you want BitcoinUnlimited, another excellent choice
wget -O- https://gist.githubusercontent.com/snakecharmer1024/922e31196c98675b54b5/raw/02b5e8d2e7296fbb41c3fc28e5b39f192d9cb2c6/bitcoin-unlimited-installer.sh | sudo bash
and hit "Enter"
After it returns the command prompt, you've install bitcoinxt!

Check that your node is up

Close your ssh tab
Back on your google cloud tab, click the back button above the ssh button
To the right of the green check, you should see an ip address (something like 130.211.161.234). Copy it
Go to https://bitnodes.21.co/
Near the bottom of the page, it says, "Join the network", copy your ip address into the first text box, type 8333 into the second text box and click "Check Node"
If it's green, you're up! Otherwise something went wrong...
Ok thanks for reading, please ask for help if you can't get it to work.
submitted by ganesha1024 to btc [link] [comments]

How to Mine BiblePay on Linux

This guide is outdated, please refer to:
https://wiki.biblepay.org/POBH_Setup
https://wiki.biblepay.org/PODC_Setup
 
 
 
 
 
 
 
 
IMPORTANT - Evolution Upgrade:
Quick Start https://wiki.biblepay.org/Quick_Start
Evolution Upgrade Information https://wiki.biblepay.org/Evolution_Upgrade
Getting Started with Evolution https://wiki.biblepay.org/Getting_Started_with_Evolution
Generic Smart Contracts https://wiki.biblepay.org/Generic_Smart_Contracts
What is BiblePay Evolution? https://www.reddit.com/BiblePay/comments/bifvpk/biblepay_evolution_what_is_it/
Recommend 2GB RAM or can get stuck compiling (if 1GB RAM can use Swap File) Use Ubuntu 16.04
INFO
https://github.com/biblepay/biblepay-evolution/blob/masteBuildBiblePay.txt
INSTALL COMMANDS
apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils apt-get install libboost-system-dev libboost-filesystem-dev libboost-chrono-dev libboost-program-options-dev libboost-test-dev libboost-thread-dev apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler apt-get install git apt-get install curl build-essential libtool autotools-dev automake pkg-config python3 bsdmainutils cmake sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install libdb4.8-dev libdb4.8++-dev git clone http://github.com/biblepay/biblepay-evolution prefix=x86_64-pc-linux-gnu cd biblepay-evolution/depends make -j4 # Choose a good -j value, depending on the number of CPU cores available cd .. ./autogen.sh #Note: if echo `pwd` does not return your working directory, replace it with your working directory such as /biblepay-evolution/ ./configure --prefix `pwd`/depends/x86_64-pc-linux-gnu make # See more here: #https://github.com/biblepay/biblepay-evolution/blob/mastedoc/build-unix.md 

SWAP FILE
NOTE: if server is 1GB RAM, before running last command "sudo make", set up a swap file
free #check if swap is 0 dd if=/dev/zero of=/vaswap.img bs=1024k count=1000 mkswap /vaswap.img swapon /vaswap.img free #check if swap is 1024 sudo make 

RUN COMMAND LINE
cd src ./biblepayd -daemon 
OR
RUN GUI
Your GUI program will be located in: /biblepay-evolution/src/qt
./biblepay-qt 
You can also run it in the background (to free up your terminal) if you call it with:
./biblepay-qt & 
To start mining, instructions are the same as for Windows: Go to Tools -> Debug Console
Execute this command (to start mining with 8 threads)
setgenerate true 8 
From there you can use all other commands such as getmininginfo, getwalletinfo, etc. Execute help command to get the list of all available commands.
Note: GUI will be built automatically only if you meet the requirements for qt library, i.e. make sure you ran this line before compiling:
sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler 
BIBLEPAY is now Running!

SETUP CONFIG
Stop BiblePay and set up the config file to get starting nodes to sync with and enable mining:
./biblepay-cli stop cd ~/.biblepayevolution/ vi biblepay.conf addnode=node.biblepay.org gen=1 genproclimit=1 
Escape Key + : (Colon Key) + w + q + Enter (saves file and quits)

addnode --- adds a node to the list of nodes to connect to gen=1 --- turns on mining genproclimit --- sets number of threads to use when mining

Run BiblePay again and fully sync with network
cd ../biblepay-evolution/src ./biblepayd -daemon ./biblepay-cli getinfo 

USEFUL COMMANDS
./biblepay-cli help ./biblepay-cli getaccountaddress "" ./biblepay-cli getinfo ./biblepay-cli getmininginfo ./biblepay-cli setgenerate true 8 ./biblepay-cli sendtoaddress "insertAddressHere" 777 "" "" true ./biblepay-cli stop ./biblepayd -daemon top #CPU usage q to quit 

MINING THREADS: To change number of threads to use up for mining
a. Edit home/yourusername/.biblepayevolution/biblepay.conf file:
genproclimit=X 
and restart BiblePay -or- b. Menu >> Tools >> Debug Console >> Type command:
setgenerate true X 
(Replace X with number of threads Use top command to view CPU usage)

POOL
NOTE: To use the pool you must now use the external miner, not the wallet miner https://whitewalr.us/2019/biblepay-nomp-pool-mining.html
  1. Set up an account on pool website: https://pool.biblepay.org/
  2. Create Worker Username(s) - Workers tab >>> Add
  3. Enable pool and add Worker Username in ~/.biblepayevolution/biblepay.conf file, add these lines and save:
    pool=https://pool.biblepay.org workerid=insertWorkerUsernameHere
4. Restart BiblePay
./biblepay-cli stop ./biblepayd -daemon 
Setup Auto-Withdraw Navigate to Account >>> Account Settings >>> Verify your BBP Receiving Address >>> Click Authorize-Auto-Withdraws

UPDATE:

### Turn off/stop BiblePay
cd /home/yourname/biblepay-evolution/src ./biblepay-cli stop 

### Pull down latest Biblepay code and build it
cd /home/yourname/biblepay-evolution git pull origin master sudo make 

### Turn BiblePay back on and check version number
cd src ./biblepayd -daemon ./biblepay-cli getinfo ./biblepay-cli setgenerate true 8 

UPDATE IN ONE COMMAND:
./biblepay-evolution/src/biblepay-cli stop ; cd && cd biblepay-evolution/ && git pull origin master && sudo make && cd src && ./biblepayd -daemon && sleep 90 && ./biblepay-cli getmininginfo 
Note: the ";" says do this after, regardless of the outcome Note: && says do this after only if previous command finished with no errors

SPEED UP COMPILE:
To speed up the compile time, add -j4 or -j8 after make. This way it compiles using 4 or 8 threads instead of just 1.
./configure LDFLAGS="-L${BDB_PREFIX}/lib/" CPPFLAGS="-I${BDB_PREFIX}/include/" sudo make -j8 
Reference: http://www.linux-databook.info/?page_id=2319

RSYNC stop biblepay from your nodes compile on your fastest machine then rsync with your machines only src folder is required
rsync -avuz /root/biblepay-evolution/src/ [email protected]:/root/biblepay-evolution/src/ 
https://stackoverflow.com/questions/3299951/how-to-pass-password-for-rsync-ssh-command https://www.thegeekstuff.com/2008/11/3-steps-to-perform-ssh-login-without-password-using-ssh-keygen-ssh-copy-id/
people make cron jobs and rsync automatically

OUTDATED

Unofficial Bash Script
https://gist.github.com/anonymous/d1c1d35e3c8f67f5fb2e204479fa5c6b

Official Ubuntu Package
https://launchpad.net/~biblepay-official

Unofficial Ubuntu Package
https://www.reddit.com/BiblePay/comments/7rwqqs/unofficial_ubuntu_packages_available/

Unofficial Mine in One Line
https://www.reddit.com/BiblePay/comments/7ryuk1/mine_in_one_line/
NOTE: DONT RUN ON A COMPUTER WITH COINS -- THIS IS A CLEAN INSTALL SCRIPT

COMPILE WITHOUT GUI: https://bitcointalk.org/index.php?topic=2042657.msg21878317#msg21878317 https://bitcointalk.org/index.php?topic=2042657.msg21878389#msg21878389
ADVANCED:

DOCKER IMAGES (NOTE: I havent tested these, use at your own risk) https://hub.docker.com/gagaha/biblepay/ https://hub.docker.com/cryptozero/biblepay-opt/
submitted by togoshige to BiblePay [link] [comments]

DECENT MINING SETUP & RESSOURCES SHORTCUT

To all DECENTants,
I would like to encourage you to become a seeder or witness (actually not miner) on DECENT.

SHORT INTRODUCTION ABOUT ME

As a pioneer with Bitcoin I truly believed in the DCT project and it's proposal. The first day of the ICO release I sent all my BTC balance to the DECENT. Not knowing when and what they will deliver. To participate in this great adventure means a lot to me. Another project from my home country I strongly encourage you to get familiar with is Ethereum. I have been an early CPU miner: before Crypto Currency I used to compute for sience projects grid for Clean Water and Cancer Research. If I hadn't bought Rainforest with the Ripple they distributed to all contributors, I'd be a rich man today. :P

DECENT SUPPORT

https://decent.ladesk.com/

DECENT WIKI

https://wiki.decent.ch/doku.php?id=decent:howto#build_decent_from_source

DECENT GITHUB

https://github.com/DECENTfoundation/DECENT-Network

BLOCK EXPLORER

https://explorer.decent.ch/

DECENT DB

https://decent-db.com/

GRAPHENE CLI Wallet Cookbook

https://github.com/bitshares/bitshares-core/wiki/CLI-Wallet-Cookbook

RESSOURCES

https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-16-04
http://www.hamvocke.com/blog/a-quick-and-easy-guide-to-tmux/
https://digitizor.com/create-swap-file-ubuntu-linux/

I - SERVER SETUP

A dedicated server with Linux Ubuntu 16.04 LTS is most recommend for 24/7 operation. I suggest you close the root and create a new user with SSH Key, secure the system with a firewall.

1. Create a new user

adduser bob 

2. Elevate him

usermod -aG sudo bob 

3. Generate a new keyset

ssh-keygen 

4- Bind the new keys

ssh-copy-id [email protected]_server_ip 
Copy the keys to your local drive. You'll need them to connect.

5. Change the config file

sudo nano /etc/ssh/sshd_config 
Change Line PasswordAuthentication no

6. Finish with

sudo systemctl reload sshd 

7. Login with your ssh key, user and password

ssh [email protected]_server_ip 

II - PREREQUISITES

1. Grab your tools

sudo apt-get update sudo apt-get install build-essential autotools-dev automake autoconf libtool make cmake checkinstall realpath gcc g++ flex bison doxygen gettext git qt5-default libqt5svg5-dev libreadline-dev libcrypto++-dev libgmp-dev libdb-dev libdb++-dev libssl-dev libncurses5-dev libboost-all-dev libcurl4-openssl-dev python-dev libicu-dev libbz2-dev 

2. Download and build Boost 1.60.0

mkdir -p ~/dev/DECENTfoundation/DECENT-Network-third-party cd ~/dev/DECENTfoundation/DECENT-Network-third-party rm -rf boost_1_60_0* boost-1.60.0* wget https://sourceforge.net/projects/boost/files/boost/1.60.0/boost_1_60_0.tar.gz tar xvf boost_1_60_0.tar.gz mkdir boost-1.60.0_prefix cd boost_1_60_0 export BOOST_ROOT=$(realpath ../boost-1.60.0_prefix) ./bootstrap.sh --prefix=$BOOST_ROOT ./b2 install cd .. rm -rf boost_1_60_0 boost_1_60_0.tar.gz 

III - INSTALLATION

1. Clone the repo

mkdir -p ~/dev/DECENTfoundation cd ~/dev/DECENTfoundation #via ssh $ git clone [email protected]:DECENTfoundation/DECENT-Network.git #via url $ git clone https://github.com/DECENTfoundation/DECENT-Network.git cd DECENT-Network git submodule update --init --recursive 

2. Build and install Decent

mkdir -p ~/dev/DECENTfoundation/DECENT-Network-build cd ~/dev/DECENTfoundation/DECENT-Network-build cmake -G "Unix Makefiles" -D CMAKE_BUILD_TYPE=Debug ~/dev/DECENTfoundation/DECENT-Network cmake --build . --target all -- -j -l 3.0 cmake --build . --target install 

IV - USE DECENT

You don't want your server to shut down the process when you lose connection or quit.
I use tmux. Though nohup is sufficient for infrequent access. Use it when you fire up decentd after miner setup.
nohup ./decentd & disown 

1. RUN decentd - On first run decentd will create .decent in the home directory.

~/dev/DECENTfoundation/DECENT-Network-build/artifacts/prefix/bin/decentd 
Always close it via Ctrl+C to save the current state Ctrl+S Freeze Ctrl+Q Resume

2. Get HELP

cd ~/dev/DECENTfoundation/DECENT-Network-build/artifacts/prefix/bin/ ./decentd -h 

3. RUN cli_wallet

~/dev/DECENTfoundation/DECENT-Network-build/artifacts/prefix/bin/cli_wallet 
Close it with Ctrl+D

4. USE cli_wallet

set_password xy unlock xy 

5. IMPORT your account

import_key decentgo_username your_private_key 

6. CREATE 3 sets of keys for your new account

suggest_brain_key 
write them down, don't use the ones below. ;)

1. new owner key

{ "brain_priv_key1": "UNBUSH ROAR CHKALIK STRUE PLATTEN DEMOB COLETIT DECAYER SPERONE SPASMED ANATASE LAGGARD BESPETE AXOID SERAL CHEKI", "wif_priv_key1": "5J4brX9bydADigEtsXZhCZ1YLVXkq8frp4xcKAREQ3Gh3P2DE7e", "pub_key1": "DCT5VNJni7HypYi159qiwazZ1WZUt4p2v7NLQmFCJPDvjBpW2oG8a" } 

2. new active key

{ "brain_priv_key2": "FUSION BLART JAIL FESTAL LAXNESS ROSTEL TITI VANADYL PUG BATATA KAIK ROSETY STUCCO TETE BEMUDDY WUDGE", "wif_priv_key2": "5HvsjRsokHSeeUdRkM88JgLzYJ6vnc2e35CzyZNRnmh1fvm91Jz", "pub_key2": "DCT7G7KeUnMPVKXN2y8M7BnyosLRE3LtSnNp7kbxtYd9xHiBoX6wd" } 

3. new public signing key

{ "brain_priv_key3": "DECESS LABBA PLAN DEHUSK FISTY MOSSER SPURTER SCORIAE INDART UNDYE MASTER STEIGH SAFROLE FLURR THAPSIA JOB", "wif_priv_key3": "5JgMsecySgt2BQsmmEE9QnwAGuudC9fGeZJhreyPatcu2TVY9bs", "pub_key3": "DCT6D7TLeVJmPQWR73XHvEhTVHzTDoG6oTSUyvfGa58nuc5wL96UH" } 

7. CREATE your new account

register_account new_username pub_key1 pub_key2 decentgo_username true 

8. SEND some DCT to your new account

transfer decentgo_username target_username 3.00 DCT "memo" true 

9. IMPORT the new account

import_key new_username wif_priv_key2 

10. Close the Wallet and edit the config.ini inside /root/.decent/data/decentd/

private-key = ["pub_key2","wif_priv_key2"] 

11. Launch again and create your miner

create_miner username "proposal URL" true 

12. Change your signing key to 3rd keypair from suggest_brain_key

update_miner username "proposal URL" public_key3 true 

13. Edit the config.ini again inside /root/.decent/data/decentd/

enable-stale-production = true miner-id = "1.4.X" private-key = ["pub_key3","wif_priv_key3"] 

Your Server is now ready to run a DECENT witness.

Be aware that you should not close your daemon at any time.

V - USEFUL COMMANDS

get_brain_key_info dump_private_keys get_private_key public-key get_account texxi get_miner texxi list_my_accounts list_account_balances texxi set_desired_miner_count username 99 

Now get some support for your miner and join the community!

https://decent-project.slack.com/

You can vote for me and I will gladly return the favor. Please make sure your server runs stable and you're not missing any blocks. Good Luck!

vote_for_miner username texxi true true

All voters will receive early preview access to my first cryptocurrency trading tool to be released in 2018. But remember: Always trade for good and invest in green.

submitted by Texxer to Decentplatform [link] [comments]

Lore v2 QT on Raspberry Pi

Hello,
 
To follow up to mindphuk's excellent piece on building the headless client on Raspberry Pi (https://www.reddit.com/blackcoin/comments/6gkjrw/wip_blackpi_a_stake_device_based_on_raspberry/), I thought if anyone was interested I'd show you how to get the full QT version running on the Pi on the Jessie with Pixel desktop. This works and has been soak tested for several days now on a standard Raspberry Pi 3. I have since added some coins and it stakes a handful of times a day.
 
Running staking Lore clients paves the way for some of the future use cases of BLK utilising the Bitcoin 0.12 (and newer) core tech, including colored coins. So I'm going to leave this one going indefinitely to kickstart the number of Lore clients staking. It's certainly not mandatory but it will be good in the longer term to have a nice distribution of Lore staking clients.
 
The cross-compile which lets you create binaries for multiple platforms didn't work for the QT version on the Pi, so there is more to do than just running the binary unfortunately, as below. There are folks working on some much cleaner solutions than this for the Pi, with a custom front end, and where you won't have to do any mucking about. That is coming soon. In the meantime, if you enjoy a fiddle with such things, here's how to get this QT client working on your Pi.
 
These instructions assume you are starting from scratch with a completely blank OS.
 
Download Jessie with Pixel from: http://downloads.raspberrypi.org/raspbian/images/raspbian-2017-07-05/2017-07-05-raspbian-jessie.zip
 
Note they have since (August 2017) released a version called 'Stretch' which does not work with this guide. I'll see if I can come up with something new for that at some point and link to it here when I have. In the meantime the guide should work with the Jessie image above.
 
Unzip the file and extract the .img file to burn it onto Fresh SD card to boot from (to be safe, use 16GB or larger), using a tool like win32diskimager or Etcher.
 
Assuming you have keyboard/mouse and monitor plugged into your pi, boot it up and the Jessie Desktop will show.
 
Before we do anything else, you should increase the default swap size on the pi, as compiling certain libraries can exhaust the RAM and get stuck otherwise. To do this, launch a Terminal window and type:
 
sudo nano /etc/dphys-swapfile 
 
and Change the CONF_SWAPSIZE from 100 to:
 
CONF_SWAPSIZE=1024 
 
Exit nano with control + x to write out the file.
 
Then, run the following to restart the swapfile manager:
 
sudo /etc/init.d/dphys-swapfile stop sudo /etc/init.d/dphys-swapfile start 
 
Now, launch the browser and download the Lore 2.12 binaries for ARM here: https://mega.nz/#!k2InxZhb!iaLhUPreA7LZqZ-Az-0StRBUshSJ82XjldPsvhGBBH4 (Version with fee fix from 6 September 2017)
 
(If you prefer to compile it yourself instead, it is possible by following the instructions in the original article by Mindphuk just taking into account this is the newer version of the Lore client than when that was written (https://github.com/janko33bd/bitcoin/releases) and the versions of Boost and the Berkeley DB need to be the same as below.)
 
Double click the zip and extract the Lore binary files. Yes, at the moment they are all called 'bitcoin', not 'blackcoin' or 'Lore' - this is because the code derives from a recent bitcoin core implementation so this has not yet been updated. You can place these wherever you like.
 
In the Terminal window, change directory to where you put the binaries, e.g.:
 
cd Downloads/lore-raspberrypi-armv7-jessie-pixel chmod +x * 
 
That marks the binaries as executable.
 
Now, we need the Boost libraries installed for any of the Lore binaries to work. The project was done with Boost 1.62.0. Unfortunately the Jessie repository only goes up to 1.55, so we need to download and build 1.62 manually on the device.
wget https://sourceforge.net/projects/boost/files/boost/1.62.0/boost_1_62_0.tar.gz/download tar -xvzf download cd boost_1_62_0 sudo ./bootstrap.sh sudo ./b2 install 
 
(This will take almost 2 hours. Have a nice cup of tea and a sit down.)
 
When I came to run the binaries, I found they couldn't find Boost. Running this command fixes that:
sudo ldconfig 
 
Now we are going to install the packages which aren't already included in the default OS installation which the binaries need in order to run:
sudo apt-get install qrencode libprotobuf-dev libevent-pthreads-2.0-5 
 
Now we need to install the Berkeley Database version 6.2.23. This is the version Lore v2 uses. Bitcoin still uses 4.8 which is 10 years old! This doesn't take too long.
wget http://download.oracle.com/berkeley-db/db-6.2.23.tar.gz tar -xvzf db-6.2.23.tar.gz cd db-6.2.23/build_unix ../dist/configure --prefix=/usr --enable-compat185 --enable-dbm --disable-static --enable-cxx 
 
I find this next section of the Berkeley instructions worked better just switching to root, which can be fudged by running sudo su before the rest:
sudo su make make docdir=/usshare/doc/db-6.2.23 install chown -v -R root:root /usbin/db_* /usinclude/db{,_185,_cxx}.h /uslib/libdb*.{so,la} /usshare/doc/db-6.2.23 
 
Now we're going to go up a couple of directories to where the binaries were:
cd ../.. 
 
Then run the client!
./bitcoin-qt 
 
And there you have it. Should hopefully end up looking a bit like this: http://imgur.com/a/eEHGa
 
Using the Bootstrap can save a while syncing. Download it at: https://www.reddit.com/blackcoin/comments/6b3imq/blackcoin_bootstrapdat_up_to_block_1631800
 
Place the bootstrap.dat file into the ~/.lore directory.
 
Run ./bitcoin-qt again, it will say 'Importing Blocks' rather than 'Synchronising with Network'. My pi sync'ed fully in about 5-6 hours.
 
If you want peace of mind that Lore will always start on bootup into the Jessie w/Pixel desktop (i.e. after a power cycle), then you need to create a .desktop file in the following place.
sudo nano ~/.config/autostart/Lore.desktop 
 
And in it, enter the following (tailoring the Exec line below to the whereabouts of your bitcoin-qt file):
[Desktop Entry] Name=Blackcoin Lore Comment=Mining without the waste Exec=/home/pi/Downloads/lore-raspberrypi-armv7-jessie-pixel/bitcoin-qt Type=Application Encoding=UTF-8 Terminal=false Categories=None; 
 
Power usage and payback time
 
After a good while leaving it going by itself, the CPU load averages got down to almost zero, all of the time. Idling, the Pi uses a bit less than 3 watts. This means it would take two weeks to use one 1Kw/h of electricity.
 
If you pay e.g. 12.5 cents a unit, that's what you'd expect this to cost to run in a fortnight. That's around $0.25 a month or $3 a year. Green and cheap and helping to secure the BLK network. I paid for the year's worth of electricity in 2 days staking with 25k BLK. Makes mining look silly, huh? ;)
 
Securing your Pi
 
With staking, your wallet needs to be unlocked and as such, the keys to your wallet are on the device. In a clean and newly installed environment as described above, and if you don't allow others to use your device and there is no other software or nasties running on it, there is no real cause for concern. However, there are some basic security precautions you can take.
 
Firstly, if you have enabled SSH and are playing with your pi across your LAN (or worse, the Internet), you should immediately change the password for the default 'pi' user (which is preconfigured to be 'raspberry'). Simply log in as normal, then type:
 
passwd 
 
You'll be prompted to enter the old and the new passwords.
 
Security by default
 
Your Pi is likely, by default, to not be exposed to incoming connections from the outside world because your router is likely generating a private address range for your LAN (192.168.x.x or 10.0.x.x or 172.x.x.x) which means all incoming connections are effectively blocked at the router anyway unless you set up a 'port forward' record to allow packets arriving on certain ports to be forwarded to a specific internal IP address.
 
As for accessing your Pi across the internet, if you have set up a port forward, this likely has security ramifications. Even basic old fashioned protocols have proven in recent times to have uncaught flaws, so it's always advisable to lock down your device as much as possible, and even if you only plan to access the Pi over your LAN, install a firewall to configure this. I used one called ufw, because it's literally an uncomplicated firewall.
 
sudo apt-get install ufw sudo ufw allow from 192.168.0.0/16 to any port 22 sudo ufw --force enable 
 
This allows just port 22 (SSH) to be open on the Pi to any device on my LAN's subnet (192.168.0.x). You can change the above to a single IP address if paranoid, or add several lines, if you want to lock it down to your LAN and a specific external static IP address (e.g. a VPN service you use). To find out what subnet your router uses, just type:
 
ifconfig 
 
and you'll see on the interface you are using (either hard wired or wifi) the 192.168 or 10. or 172. prefix. Change the above rule so it matches the first two octets correctly (e.g. 10.0.0.0/16 if you're on a 10.0. address).
 
You may already use VNC to access your Pi's desktop across your LAN, this uses port 5900. Add a line like above to lock it down to an internal address. It's not a good idea to expose this port to the wider world because those connections are not encrypted and potentially could be subjected to a MITM attack.
 
You can query the status of the firewall like this:
ufw status 
 
And of course, try connecting remotely once you change the rules to see what works. You should consult the official documentation for further options: https://help.ubuntu.com/community/UFW
 
Back up & Recovery
 
There are again many ways to tackle this so I'll just speak about my basic precautions in this regard. Don't take it as a be-all-and-end-all!
 
The wallet.dat file is the key file (literally) containing all the private/public keys and transactions. This can be found in:
 
~/.lore 
 
You can navigate there using Jessie w/Pixel's own file manager or in a terminal window (cd ~/.lore). You can copy this file or, if you'd rather keep a plain text file of all your public and private keys, use the 'dumpwallet' command in the console. In Lore, go to Help > Debug Window > Console and type 'dumpwallet myfilename' where myfilename is the file you want it to spit out with all your keys in it. This file will end up in the same place you launch bitcoin-qt from.
 
The instructions earlier on, when running Lore for the first time intentionally left out encrypting your wallet.dat file because in order for the wallet to stake upon startup, it needs to have a decrypted key already. This isn't perfect, but after a power cycle, it would never stake unless you left it decrypted. So the best practice here is as soon as the wallet.dat file has left your device, i.e. you copy it to a USB stick for example, put it in an encrypted folder or drive (or both).
 
In Windows, one way is to use Bitlocker drive encryption for the entire drive. You should follow the instructions here to encrypt your flash drive before your wallet.dat is on there, and don't forget the password!!
http://infosec.nmsu.edu/instructions-guides/how-to-enable-bitlocker-to-go-for-external-hard-drives-and-usb-flash-drives/
 
On the Mac, I use a software package called Concealer to encrypt files I store on the Mac itself: http://www.belightsoft.com/products/conceale   There are almost certainly free packages with similar functionality, I have just used that one for years.
 
Either way, if you want to just make sure your USB drive is encrypted, you can do so in one-click in Finder before you put the sensitive files on it: http://lifehacker.com/encrypt-a-usb-stick-in-finder-with-a-click-1594798016
 
Note that these disk encryption methods may mean having to access the USB stick on a PC or Mac in order to retrieve the files in the event of a disaster. Be aware this may mean exposing them to more security issues if your computer is in any way compromised or someone nefarious has access to your computer. There are more 'manual' ways of backing up and recovering, such as literally writing down private/public key pairs which this guide doesn't go into, but may suit you better if paranoid about your setup.
 
Recovery
 
The wallet.dat file has everything in it you need to recover your wallet, or if you used 'dumpwallet', the file you saved out has all the keys.
 
Wallet.dat method: Install Lore as normal then replace any auto-generated wallet.dat in ~/.lore directory with your backup. If a lot of time has elapsed and many transactions have occurred since your backup, launch lore with:
./bitcoin-qt -rescan 
 
And if that doesn't do the job, do a full reindex of the blockchain:
 
./bitcoin-qt -reindex 
 
If you used the dumpwallet command, install Lore then place the file containing all the keys that you saved out in the same directory as bitcoin-qt. In Lore, go to Help > Debug Window > Console and type 'importwallet myfilename' where myfilename is that file containing all the keys. The wallet should automatically rescan for transactions at that point and you should be good to go.
 
There are a million ways to do effective security and disaster recovery, but I hope this shows you a couple of basic precautionary ways. There are discussions about better ways to stake without compromising too much security which are happening all the time and developments in this regard will happen in time.
 
In the meantime, feel free to comment with your best practices.
 
submitted by patcrypt to blackcoin [link] [comments]

Zeus/Gaw ASIC Setup Guide for Linux/Raspberry Pi

So I recently I became quite interested in mining and cyptocurrencies in general. So interested in fact that I bit the bullet and decided to buy myself a GAW Fury.
I then spent some time doing research on how to set up a GAW or Zeus ASIC on Linux, in particular on a Raspberry Pi, and have found most guides to be awful. The reason they are so bad IMHO is that they assume quite a bit of prior knowledge, either with Linux or mining, and give very little instructions. So I have tried to put together a guide that requires very little prior knowledge.
It is my aim that anyone could get their shiny new asic up and mining in no time using this guide. Anyway, I present...

The Complete Noobs Guide to Setting Up a Zeus or Gaw ASIC on Debian/Ubuntu/Raspberry Pi

Resources

About Cyrptocurrencies and Their Jargon

If you are new to cryptocurrencies and how they work I suggest taking a look at this series of KhanAcademy videos. They are for Bitcoin but the theory is the same. I found them very helpful when it came to understanding what mining actually does and the mechanics of cyrptocurrencies.
Also take a look at sircamm22 his info found here, is great and breaks down a large number of concepts. I slightly disagree with no. 21 regarding preordering. Just exercise common sense.

Linux

If you are new to Linux you could follow along by simply typing in the commands. However I highly recommend taking the time to learn what you are doing. This course is a great place to start.

Computer Setup

By the end of this section you will have your device turned on, fully setup and connected to the internet with.
Note: Commands to be typed into the command line will be displayed like this:
echo Hello World

Desktop/Laptop

For laptops and desktops already running Ubuntu or Debian I will assume you have setup your internet setup as part of the installation.
If not: There are plenty of guides out there and the installation/setup process is very easy. A good place to start for Ubuntu is here.
Now open up a terminal window. Ctrl + alt + t on a standard Ubuntu installation.
If you plan on using this PC without a monitor I would suggest installing an SSH Server.
These commands will be discussed later on in the guide.
sudo apt-get -y install openssh-server
sudo service openssh-server start

Raspberry Pi

The Raspberry Pi Foundation has put together a great guide in PDF format.
Use NOOBS it will save you a lot of trouble. NB: Some SD cards don't support NOOBs but will work fine if the image is put on using a different method.
Here is a great guide for setting up the Raspberry Pi SD card from Elinux.org. In fact it's a great place to start for anything RPi related. Raspberry Pi hub at Elinux.
Once the SD card is setup you will need to insert it into the Raspberry Pi and boot. Install Raspbian from the NOOBs menu and wait.
Follow this guide by Adafruit for first time setup. You will need to enable SSH Server.
I suggest not starting the desktop on boot. It can be easily run from the command line by typing startx.
Follow this guide by Adafruit to setup your network. Found here. No need to do this if you set up previously in the first time config.
We will also at this point want to setup ssh. Again I will point you to an Adafruit guide.
Once done exit back to a standard command line interface. This can be done in LXDE by using the power off menu located in the bottom right corner.

Miner Setup

Installing BFGMiner

If you want to the Raspberry Pi or PC without a monitor go ahead and SSH into your device.
So now you should be staring at a command line interface whether on the device with a monitor or via SSH.
First things first lets make sure we are all up to date. This will update our package list from the repositories and upgrade them to the newest version. "-y" Will simply say yes to any prompts.
sudo apt-get update && sudo apt-get -y upgrade
We are going to need to install some useful tools. Git-core is how we will clone and download BFGMiner from GitHub and Screen allows multiple command line instances and means if we exit out of ssh session or quit Terminal on Ubuntu, BFGMiner will continue to run.
sudo apt-get install git-core screen
We also need to download some other tools/dependencies to ensure that BFGMiner will compile successfully.
sudo apt-get -y install build-essential autoconf automake libtool pkg-config libcurl4-gnutls-dev libjansson-dev uthash-dev libncursesw5-dev libudev-dev libusb-1.0-0-dev libevent-dev libmicrohttpd-dev libc-bin
Ok now change into your home directory.
cd ~
And clone BFGMiner by Darkwinde.
git clone https://github.com/Darkwinde/bfgminer.git
Once the download has completed move into the bfgminer directory.
cd bfgminer
The following steps may take a while.
Now run autogen.sh
sudo ./autogen.sh
You will need to make the configure script execuitable.
sudo chmod +x ./configure
Now configure bfgminer
sudo ./configure CFLAGS="-O3" --enable-scrypt
Now lets make!
sudo make
Install BFGMiner
sudo make install
One more thing...
sudo ldconfig

Running BFGMiner

If you haven't already plug in your ASIC.
Just confirm your system is recognising the ASIC.
lsusb
Its output should look similar to this (no need to type this in):
Bus 001 Device 005: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Yep there it is our ASIC listed as device 005. There is no need to install any drivers, unlike in windows, as they come in the kernel.
Now lets actually start BFGMiner.
You will want to start a screen session to ensure BFGMiner doesn't quite when you exit.
"-S" is the option for starting a new screen session. You can replace "miner" with anything you like.
screen -S miner
Now you can run the commands below.
Here is a sample of what you should type. You will need to replace somethings with your own values.
sudo bfgminer --scrypt -o stratum+tcp://URL:PORT -u USERNAME -p PASSWORD --zeus-cc CHIPCOUNT --zeus-clk 328 -S zeus:/dev/ttyUSB0
Where:
URL:PORT is the address and port of the pool you wih to use. Now I won't suggest a pool. I will leave that decision up to you. If you do wish to mine DOGE take a look at this site for a list of pools and comparisons.
USERNAME this is the username you use on the pool. Every pool is different. Check your pool's website for details. PASSWORD same as above. Specific to your pool, not every pool requires one.
CHIPCOUNT this is specific to which ASIC you are using.
For GAWMiner ASIC's:
  • War Machine: 256
  • Falcon: 128
  • Black Widow: 64
  • Fury: 6
For ZeusMiner ASIC's:
  • Blizzard: 6
  • Cyclone: 96
  • Hurricane X2: 48
  • Hurricane X3: 64
  • Thunder X2: 96
  • Thunder X3: 128
Now to make sure you don't stop mining when you exit ssh or terminal. Press:
ctrl + a + d
To come back to the BFGMiner screen simply run:
screen -r miner
You're done!!

Start on Boot

First off you will want to make sure you have BFGMiner running correctly. Ensure you have the miners set up properly and your pool correctly configured.
Start a BFGMiner instance, detailed above.
Once the instance has started and you are happy with how everything is working press "s" on your keyboard to enter the settings menu.
Now press the "w" key. Don't press enter. We want to specify where our config will go. Type:
/home/USERNAME/bfgminer.conf
Substitute USERNAME for your user. On a standard RPI install its pi. On ubuntu it's what you set during the instillation.
Now press the enter key to return back to the main BFGMiner screen. Press "q" on your keyboard to exit BFGMiner. You should now be back in the command line.
Now we want to edit a file called rc.local. Any commands in this file will be executed on boot.
sudo nano /etc/rc.local
Depending on your system this file may already contain some commands. Be careful not to delete them.
After the last command and before "exit 0" type the following on one line:
sudo -u USERNAME screen -d -m sudo bfgminer --config /home/USERNAME/bfgminer.conf
Where USERNAME = your username
Hit ctrl + x then y to save and exit nano.
The above command will create a new screen session and run bfgminer using the config we created earlier. All while as our username so that we can easily reattach.
Lets reboot to ensure it is working correctly:
sudo reboot
Once rebooted and logged in, show all running screen sessions:
screen -ls
Reattach to the session. You only need to use the numbers before the first dot.
e.g Mine looks like: 2480..hostname (13/07/14 12:02:09) (Detached). So I type:
screen -r 2480
Verify everything worked as expected. Then ctrl + a + d to exit.
You have now setup BFGMiner to restart on reboot.

Power Failure

If you are using a Raspberry Pi and it loses power it will automatically reboot on receiving power again.
For standard desktop PCs there is an option in some BIOS/UEFI to turn the computer on when it receives power. Consult your motherboard's manual and manufacturer's website.

Sources

Here is where I got my info from.
And of course /dogemining

Wrap Up

Congrats you've done it. You have managed to successfully get your shiny new asic mining away.
I do plan to make another guide detailing how to setup and use StarMiner a ready to go RPi mining distro.
So I hope this is helpful for you guys. I have seen lots of posts asking the exact same questions again and again and I have tried to answer these as best I can. I am still learning about this stuff so if there is something I have missed or a mistake I have made please tell me.
Anyway good luck. And I'll see you at the moon.
Cheers Frogsiedoodle
Edit 1: Layout and formatting.
Edit 2: Added instructions for screen which I initially forgot.
Edit 3: Removed 1 unneeded dependency
Edit 4: Added section on start on reboot and power failure.
submitted by Frogsiedoodle to dogemining [link] [comments]

Iquidus Block Explorer Guide

Pre-requisites: - Rent Server - Connect with SSH/PuTTY

Iquidus "An open source block explorer" https://github.com/iquidus/explorer

Node and Iquidus Explorer Setup for Dummies https://gist.github.com/zeronug/5c66207c426a1d4d5c73cc872255c572

1. Install & Configure BiblePay https://www.reddit.com/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/
After Installing the coin, Add RPC & Server settings:
vi biblepay.conf rpcuser=XXXX rpcpassword=XXXX rpcport=XXXX listen=1 server=1 daemon=1 txindex=1 

2. Install MongoDB https://docs.mongodb.com/manual/tutorial/install-mongodb-on-ubuntu/
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv 0C49F3730359A14518585931BC711F9BA15703C6 echo "deb [ arch=amd64,arm64 ] http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.4 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-org-3.4.list sudo apt-get update sudo apt-get install -y mongodb-org sudo service mongod start cd /valog/mongodb tail mongod.log # [initandlisten] waiting for connections on port  # Port 27017 by default 
3. Setup MongoDB
mongo use explorerdb db.createUser( { user: "iquidus", pwd: "3xp!0reR", roles: [ "readWrite" ] } ) exit 
4. Install Node.js
sudo apt-get update sudo apt-get install nodejs nodejs-legacy -y sudo apt-get install npm 
5. Install Iquidis Block Explorer
cd home/username git clone https://github.com/iquidus/explorer explorer # gyp build errors # https://github.com/nodejs/node-gyp/issues/809 sudo apt-get install libkrb5-dev cd explorer && npm install --production cp ./settings.json.template ./settings.json 
5.a Add Custom Fix for vout bug
https://github.com/DeckerSU/explorecommit/ac74e41c6162871fcaa6973d34f09f1cf3e5a1ce https://github.com/cryptorex/bitcoinz-explorecommit/267a0dfd8015bc90488b2b53ae9c49be2da83bff
6. Configure Iquidis
vi settings.json 
a. Name, Symbol, Theme
b. Port (and Open for Firewall)
c. MongoDB Credentials
d. RPC Wallet Credentials
e. Genesis Block (showblock 0, hash=block, tx=tx) https://en.bitcoin.it/wiki/Genesis_block
f. CCEX Market https://support.coinigy.com/hc/en-us/articles/360001143574-How-do-I-find-my-API-key-on-the-C-Cex-Exchange-
e. Icon and Logo /images/logo.png 128x128 /public/favicon.ico 16x16 Upload files online and use "wget URL" command to download http://digitalagencyrankings.com/iconogen/
7. Sync Initial Database
cd home/username/biblepay/src ./biblepayd -daemon -txindex cd home/username/explorer npm start 
Open a 2nd SSH/Putty session and connect, in 2nd window run:
cd home/username/explorer sudo node scripts/sync.js index update 
Open web browser and enter in your servers address: IPAddress:Port
8. Troubleshooting
Ctrl + C to stop npm process
__
If Settings/Config is wrong: Edit exploresettings.json
__
If Database is corrupt:
mongo use explorerdb show collections 
Examples: db.collectionName.find() db.collectionName.remove({}) db.collectionName.drop()
Reset all Database Data:
db.addresses.remove({}) db.addresses.drop() db.coinstats.remove({}) db.coinstats.drop() db.markets.remove({}) db.markets.drop() db.peers.remove({}) db.peers.drop() db.richlists.remove({}) db.richlists.drop() db.txes.remove({}) db.txes.drop() exit 
__
"Trying to reindex and getting error Script already running" https://github.com/iquidus/exploreissues/11
rm tmp/index.pid 
__
Stop Everything:
sudo service mongod stop sudo killall nodejs #Comment out crontab -e 
__
Run npm start in explorer folder to start explorer again
9. Add Crontab and Run!
sudo crontab -e 
Add lines:
*/1 * * * * cd /path/to/explorer && /usbin/nodejs scripts/sync.js index update > /dev/null 2>&1 */2 * * * * cd /path/to/explorer && /usbin/nodejs scripts/sync.js market > /dev/null 2>&1 */5 * * * * cd /path/to/explorer && /usbin/nodejs scripts/peers.js > /dev/null 2>&1 
If the BiblePay isnt already running, run it
cd home/username/biblepay/src ./biblepayd -daemon -txindex 
If Explorer isnt already running, run it
cd home/username/explorer npm start 
Recommendation:*
Add these parameters to biblepay.conf file
daemon=1 txindex=1 
Extra: This Iquidis for Dummides guide also adds: https://gist.github.com/zeronug/5c66207c426a1d4d5c73cc872255c572
Upstart, to have MongoDB auto start after reboots
Forever, to make sure Explorer is always running
Install Forever to keep the js running # sudo npm install forever -g # sudo npm install forever-monitor Start the Explorer # forever start bin/cluster 
Nginx - Reverse Proxy Port 3001 to 80 https://eladnava.com/binding-nodejs-port-80-using-nginx/
BiblePay Daemon set to run Every 2 Minutes with Cron
sudo crontab -e */2 * * * * /home/biblepay/src/biblepayd > /dev/null 2>&1 
Note: In ~/.biblepaycore/biblepay.conf add daemon=1 and txindex=1 Note: > /dev/null 2>&1 will capture both STDOUT (1) and STDERR (2) and send them to /dev/null
Auto Remove index.pid if indexing is complete
#!/bin/bash fname="/home/biblepay/exploretmp/index.pid" if [[ -f "$fname" ]]; then pid=$( /dev/null r=$? echo $r if [ $r -eq 0 ]; then exit 1 else rm $fname fi fi 
-f is checking if the file exists index.pid is the indexing lock file with its process ID number inside of it ps -p checks if the process is running $? is the value of the last output that ran and since the previous value is going to dev/null, its the exit code status "0 for successful executions and 1 or higher for failed executions." and so if the process is still running, the bash script just exits, otherwise the process is done and the index.pid file gets removed the file doesnt need a .sh extension, if you have "#!/bin/bash" at the top then linux knows its a bash script chmod +x to set it as executable
Github Source Code Files:
https://github.com/togoshigekata/biblepay-files/blob/masteexplorer-settings-togo.json
https://github.com/togoshigekata/biblepay-files/blob/masteexplorer-index-resetter-togo.sh
My Crontab:
*/2 * * * * cd /home/explorer && /usbin/nodejs --stack-size=15000 scripts/sync.js index update > /dev/null 2>&1 */6 * * * * cd /home/explorer && /usbin/nodejs scripts/sync.js market > /dev/null 2>&1 */11 * * * * cd /home/explorer && /usbin/nodejs scripts/peers.js > /dev/null 2>&1 */5 * * * * /home/biblepay/src/biblepayd > /dev/null 2>&1 */4 * * * * /home/explorer-index-resetter-togo.sh > /dev/null 2>&1 0 */3 * * * /ussbin/service mongod start > /dev/null 2>&1 
Experimental: https://github.com/iquidus/exploreissues/236
submitted by togoshige to BiblePay [link] [comments]

I'm about to launch my first onion. I would love my setup to be checked for ip leakage, or any other advice.

Hey guys. I'm about to launch my first onion site and I would love my setup to be double checked for ip leakage. It's just a small discussion forum with no Bitcoin,illegal activity, or emails/IPs, so even if it got pwned or shutdown, it wouldn't be that big of a deal.
Here's my setup:
Apache on Ubuntu Server. Phpbb3 forum (with site/cookie name changed to the onion address).
mod_status disabled (I recall there being a different status with fancy graphs that needs to be disabled too). ServerTokens/Signature reduced.
The hidden service is hosted on a different port, with a dummy site on 80. VirtualHost is set to 127.0.0.1:x so that the site only goes through tor. ServerName is set to the onion address. Do I need to use any other apache settings like "Require host"?
Mail functions disabled. SSH/FTP accounts will be limited, and unavailable through the onion address. Mysql limited to local access, and a weak user is used for phpbb3.
Would anyone be interested in taking a quick look for ip leakage if I PM the address? Is there anything I'm missing?
I also need a favor. Would anyone here be willing to create a subreddit for my site and then transferring ownership to one of my accounts? I have an eligible reddit account that I'm 97% sure I've only used through tor, but I don't want to take the risk.
EDIT: Here's a cloned setup people can checkout. I appreciate any help/advice.
http://ijotms5vjd6utvsx.onion
submitted by DesmondPooPoo to onions [link] [comments]

How to start an xt/unlimited node with Google Cloud

Hi, I'm developer and I really care about bitcoin and I want to do something to help, so I made this simple script to start your own bitcoinxt/bitcoinunlimited node. I tried to make it as simple as possible for anyone who has 5 minutes, regardless of your technical ability. It costs $25 a month (first two months free) to vote with your code, so please help out if you care enough to complain. So here's instructions for how to setup a google cloud instance of bitcoinxt/unlimited. Please keep in mind there are cheaper options out there, but they don't usually give you 2 months free.
Get a google cloud account
Create your instance! (Exact flow might be slightly different, use your head and look around!)
Setup the firewall!
Install bitcoinxt/unlimited!
Check that your node is up
Ok thanks for reading, please ask for help if you can't get it to work.
Btw, if you want to prune the blockchain, you can change the
bitcoind &
command to this
bitcoind -prune 4096 &
to only keep 4GB of blockchain.
Please also watch the excellent video by nicolasgramlich
submitted by ganesha1024 to bitcoin_nodes [link] [comments]

Issue's setting up a full node on Ubuntu 16.04. Help?!(Scaleway Hosted Server)

I setup a 'server' using Scaleway (https://www.scaleway.com/) and am having some issues. Firstly, I have only been able to access this server using SSH through Putty, is there no GUI/Desktop that can be accessed, or does everything need to be done via the terminal?
Secondly, I have followed the command line instructions found here (https://bitcoin.org/en/full-node#ubuntu-1410) and have installed bitcoind, however whenever I run the command 'bitcoind' at the end it just sits there...what am I doing wrong?
Here is a screenshot of the terminal and several things I have tried (http://imgur.com/8M1PBAZ). Are there any good videos on this? Ideally I would like to be using core through an actual desktop and not a command line, can this not be done using Scaleway?
Thanks in advance for any advice.
submitted by Kitten-Smuggler to Bitcoin [link] [comments]

Linux headless setup

I'm setting up a mining rig using 3-7950's, and have ran into a little bit of a road block. I've seen a few guides using xubuntu 12.10, but none with xubuntu 13.04.
darth_bunny's guide
cryptobadger's guide
gentoo (bitcoin)
I've tried the first 2 ways on fresh images, but for some reason X never starts...
aticonfig --adapter=0 --od-getclocks ERROR - X needs to be running to perform AMD Overdrive(TM) commands 
Following the darth_bunny's guide way I built to 13.04 instead of 12.10
./amd-driver-installer-catalyst-13.3-beta3-linux-x86.x86_64.run --buildpkg Ubuntu/raring 
On a side note, whenever I plug the ATI cards in, video (connected to onboard), does not output. I'm guessing this is because the ATI cards are primary? It didn't bother me as I ssh in anyway.
I also have some missing lib's when trying to run cgminer, but that is something to worry about later.
Has anyone solved this on 13.04, or should I just downgrade to 12.10?
submitted by atrueresistance to litecoinmining [link] [comments]

Introduction to running a cloud node

So here's instructions for how to setup a google cloud instance of a bitcoin full node.
Get a cloud account
These Instructions are for google cloud, for other cloud services please ask for help below.
Create your instance! (Exact flow might be slightly different, use your head and look around!)
Setup the firewall!
You can leave all other options as the default
Install your preferred bitcoin client * Click the SSH button at the top left above the green check, this should open a new tab with a command line in it. You can type stuff here.
Finally make sure you hit "Enter"
Check that your node is up
Ok thanks for reading, please ask for help if you can't get it to work. Btw, if you want to prune the blockchain, you can change the
bitcoind & 
command to this
bitcoind -prune 4096 & 
to only keep 4GB of blockchain.
All credit for the above goes to ganesha1024
Edit Please also watch the excellent video by nicolasgramlich
submitted by redditchampsys to bitcoin_nodes [link] [comments]

Connect to Ubuntu Server over SSH using Bitvise - YouTube Bitcoin Mining on Ubuntu - YouTube free vps mining bitcoin termux or putty ubuntu server 16 04 enable ssh and connect Learn Ubuntu Server 18.04 - SSH Configuration - YouTube

Commodity Trading Training In Hyderabad Nodes do thisUbuntu Bitcoin work from home calgary kijiji PriceAlso note the dbcache=1000 option. bitcoin cash ubuntu install ThisIf you remove your .bitcoin directory, you are removing your When you run bitcoind , it typically creates a .bitcoin directory in the . Bitcoin Cash Node Installation on Ubuntu ... Just created a new virtual Ubuntu server and I'm in the process of hardening it for production use. I currently have a root account. I want to do the following: Create a new user (let's call them jim for the rest of this). I want them to have a /home/ directory. Give jim SSH access. Allow jim to su to root but not perform sudo operations. Since we want to use an SSH setup, we do not need a GUI for our mining computer. Because of this, I have chosen Ubuntu Server for our Linux distribution. At the time of writing this (4/14/2018) We are about 12 days away from the release of Ubuntu 18.04 LTS. The LTS version of Ubuntu server, is the one we want to download. This is because the LTS version provides updates for about five years ... Initial Server Setup with Ubuntu 18.04 Ubuntu Getting Started Security Initial Server Setup Ubuntu 18.04. By Justin Ellingwood. Posted April 27, 2018 Not using Ubuntu 18.04? Choose a different version or distribution. Introduction. When you first create a new Ubuntu 18.04 server, there are a few configuration steps that you should take early on as part of the basic setup. This will increase ... Download Ubuntu desktop, Ubuntu Server, Ubuntu for Raspberry Pi and IoT devices, Ubuntu Core and all the Ubuntu flavours. Ubuntu is an open-source software platform that runs everywhere from the PC to the server and the cloud.

[index] [37982] [50864] [4886] [28154] [27232] [22654] [50734] [807] [2444] [5832]

Connect to Ubuntu Server over SSH using Bitvise - YouTube

In this quick video I will show you how to install and configure the SSH Server on your Ubuntu desktop Check out my website! https://pentestlife.com This videos shows how to generate an SSH key pair and put the public key in place on a remote server. How to mining Bitcoin with your Ubuntu VPS? Earn 0.0001 BTC per VPS, if you have 10 VPS, you will earn 0.001 BTC per day (~2.5 USD), if you have a lot of VPS, you will earn more BTC per day. Setup ... This is the first in a series of videos designed to help you learn how to be a linux system administrator. In this video, We learn how to SSH, or Secure Shel... Create SSH Server using Termux and Login - Duration: 2 ... How to Bitcoin Miner with Ubuntu VPS - Setup Nicehash Miner via Ubuntu VPS - Duration: 11:33. Cát Dự Trần Recommended for you. 11:33 ...

#