Help - installing Bitcoin Core node on Ubuntu using ...

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.
-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:
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]

Lore v2 QT on Raspberry Pi

To follow up to mindphuk's excellent piece on building the headless client on Raspberry Pi (, 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:
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:
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:!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 ( 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 tar -xvzf download cd boost_1_62_0 sudo ./ 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 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!
And there you have it. Should hopefully end up looking a bit like this:
Using the Bootstrap can save a while syncing. Download it at:
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:
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 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:
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. 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:
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:
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!!
On the Mac, I use a software package called Concealer to encrypt files I store on the Mac itself:   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:
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.
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]

Using Electrum and Bootable Ubuntu USB to Create a Secure Cold Storage Wallet

Here is a short guide that is hopefully newb friendly for creating a cold-storage wallet with Electrum. All you will need is at least one USB flash drive with at least 2 GB of free space, your PC, and pen & paper.
You will need The Universal USB Installer, as well as the Ubuntu .iso image file. Choose the 32 bit version to be safe. Download both, plug in your USB flash drive, and launch the installer. Select Ubuntu in Step 1 in the installer. Then in Step 2 browse and locate the Ubuntu .iso image file you downloaded. Then in Step 3 select the drive you have inserted, as well as click the box to format the drive and erase contents. Do NOT set a persistence as this will reduce the security. Then click create and wait for it to finish.
Once booted into Ubuntu, make sure to click "try ubuntu". You are only trying it out on the USB, and not installing it onto your main hard drive. The reason for using the bootable drive is everything exists in memory and mostly disappears when you shut down Ubuntu.
(It would be more ideal to install electrum in a complete cold environment, but I have heard that could cause some problems with Electrum at this time and it is best to install it while connected to the internet. But if you want true cold storage you must have zero internet connection at the time of creating the wallet. Since we are disconnecting before Electrum creates the seed, we should be good.)
At this point you are done, just shut down Ubuntu to make sure the evidence of the seed is erased. Then you can send Bitcoins to your cold storage wallet. You have effectively created a very secure cold storage wallet, in my opinion. To restore the cold wallet, just launch electrum and choose "restore wallet" option, type in your seed, and voila you have a hot wallet ready to spend again.
Extra: Using Truecrypt Encryption
Bonus tutorial is if you would prefer to save your seed on another USB or digital device. It is not recommended to do this, unless the seed in encrypted. Even then I would only leave it on a USB and not plug it into any hot device just to be safe. I would recommend Truecrypt although its possible the NSA has hacked Truecrypt, so use at your own risk.
sudo add-apt-repository ppa:stefansundin/truecrypt
sudo apt-get update
sudo apt-get install truecrypt
Hit enter after each command. If it asks permission, press y. Sometimes I had problems getting commands to work in the past. For some reason first installing flash from the software center fixes the problem, but I have no idea why.
Choose a size for the file, probably 5 MB is enough, but by all means choose more if you want to hold more files. Click next and make sure to choose a SECURE password for the file. If you don't pick a good enough password it will be brute forced easily. Use numbers, letters, capitals, lowercase, symbols, and make it long as possible. Try to have it something you can memorize if possible. Then click next. Then format it as FAT, and click next. Move your mouse around for entropy and then click Format, and your truecrypt container has been created.
I think this is a decent easy to follow tutorial. Hopefully this can help some newbies out, if I made any mistakes please feel free to correct me.
Edit: Sorry formatting sucks.
submitted by btcfreedom to Bitcoin [link] [comments]

The straightforward Bitcoin safety and security guide

Seen those posts of people who come here to commiserate about how they got their coins robbed?
OK, let's make sure that does not happen to you.

Make sure your computer is safe

Pirated Windows? You're gonna have a bad time.
Those pirated copies normally have slipstreamed key logger software and remote control software. If you receive bitcoins or log into an exchange there, you will lose your money. Also think of our bank accounts and credit card numbers.
How to recover from this situation? Back up your data, blow away your computer's disk, install original Windows from the CD, install drivers from the CD, install Windows updates.
Never use that Windows machine to browse for porn or warez. Do not install software you did not get from the manufacturer. Disable Flash (or use Chrome's sandboxed Flash) and do not think of installing Java. Do not visit sites whose security has been compromised (Chrome will tell you).
"Too expensive"? Install Ubuntu then, possibly dual-booting Windows too. Make sure to encrypt your disk (the Ubuntu installer can do that automatically, so choose full disk encryption by default).
The password must not be your login password. It should be a long phrase with made-up words that makes sense only to you. Take measures to keep a copy of that password somewhere you and only you can access. Bank safes are not safe -- they are the first place governments subpoenapilfer private info from.
Then do Ubuntu updates, weekly.
When you are on Ubuntu, do your normal Bitcoin stuff. Refrain from doing any of that while on Windows. Refrain from using "browser sync" of Firefox or Chrome under Windows.
If you behave like this, then Windows programs can't see the Ubuntu data, and Windows malware generally can't jump into Ubuntu and watch what you do, so you are safe that way. Ubuntu by default also locks your screen after a few minutes of inactivity, so there's more security out of the box. You can also Ctrl+Alt+L to lock it by hand.
This way you can watch your furry porn on Windows while keeping your money safe.
"Too hard"? Well then, I'm sure being robbed possibly hundreds of thousands will be easier for you. Irresponsibility costs you and your family, be prepared to pay.

Encrypt your wallet

Whatever choice of wallet software you use, encrypt it from the start. You did not encrypt it? You're gonna have a bad time.
Encrypting your wallet makes it so malicious people who obtain access to your wallet.dat file, cannot spend it. They need the password as well.
The password must not be your login password, or your disk encryption password. It should be a long phrase with made-up words that makes sense only to you. Take measures to keep a copy of that password somewhere you and only you can access. Bank safes are not safe -- they are the first place governments subpoenapilfer private info from.

Never leave money floating in exchanges

Exchanges fail (some because the owners are frauds, most of the time because of government sabotage). Left lots of money on those exchanges? You're gonna have a bad time.
Always transfer as much as you can to your computer walled. Once you have it in your computer, and your computer is secure, it will be very hard for anyone to rob you without threatening or initiating physical violence against you.
In the Bitcoin world, exchanges are not banks. Your computer is. Trust first the environment you control, over the environment strangers control.

Don't squawk about your holdings

You don't blabber about your bank account balances or your credit purchasing power.
Don't do it about Bitcoin either.
This is just common sense.
Now for the tech advice: whenever you receive Bitcoin from anybody, use a new address every time. This prevents any single address from pooling enormous amounts of bitcoins.
Why is that something you want do prevent? Because the balance of addresses will be visible to the next person you send money to, as he can see the size of the transaction inputs.
You are the owner of what you keep to yourself, and a slave to what you say.

Back your data up

At the very least, back up your user profile / home directory. Regularly. Optimally after receiving or sending money.
Make sure your backup is encrypted too. A smallish external hard disk is not hard to buy. You can encrypt, unlock and mount, and lock and eject the disk, using the Disks tool that ships with Ubuntu.
You can do the backup by hand if you know what files to copy, or you can use a simple terminal command like rsync -av --delete $HOME/ /mnt/whereverthediskwasmounted/ which will back everything up in your home directory.
Stay away from El Cheapo USB sticks, as they can eat your data silently. Never remove the disk while on the middle of writing data to it. Make sure it is safe to remove before unplugging it. The Disks utility will allow you to know, for sure, when that is safe.
Try to keep the disk away from the computer. Computers catch fire sometimes.


You have the tools necessary to protect yourself from theft of invaluable assets. Use them. Or pay the price.
Feel free to ask me any questions.
submitted by throwaway-o to Bitcoin [link] [comments]

$750 Quadruple Monitor Linux Rig

I'm using the same formatting here as suggested by the Tek Syndicate forums. Thanks for the help guys, it is much needed!
I don't know much about building computers, yet, so thanks for reading this. I need a computer that can push four monitors. I use Linux which complicates things. Choosing the graphics card seems to be the hardest part for me. I'd like to get a graphics card that is either supported on Linux by the manufacturer with proprietary drivers or one that is supported with open source drivers. Whichever is fine, I just want it to work. Eyefinity support would be great too, I have 3 1920x1200 monitors in portrait mode so I'd like to run them all as one display when I watch movies (this way I can watch 4K content).
Budget. How much are you willing to spend?
$750. Spending less would be nice. I will spend more than $750 if need be.
Where do you live (what country), and what currency do you use?
United States. I live in a big city so I also have plenty of physical stores near by (microcenter, best buy, etc.)
Is there a retailer you prefer?
Newegg/Amazon (I have free 2 day shipping on those sites). I will buy wherever is the cheapest though.
Do you need or already have peripherals? (this can add to costs)
I already have these items:
What will you be using your future computer for? Gaming? Rendering? Mix of both? Or is this a home media PC?
Web browsing, photoshop, watching video (not editing video), and programming. I don't game so I won't need as powerful of a computer. I really need something that can push all 4 monitors while Web browsing, photoshop, watching video, and programming at the same time.
Do you overclock or want to get into overclocking?
Overclocking isn't a priority for me. If the CPU and graphics cards can be overclocked then I will if cooling isn't a problem.
Do you plan on going for custom watercooling now, or in the future?
OS. Do you need a new one?
No. I use Ubuntu, Debian, and Arch. I will also be installing Windows 7 Home Premium with a license key I have.
Do you plan on mining bitcoin?
Yes! If cooling isn't a problem I certainly will be mining bitcoin or litecoin.
Do you render movies or photshop pictures?
I edit photos with GIMP but I may move to Abode Photoshop. I don't edit much video.
If there are any parts that you must have, and you don't want to be swayed against, such as a particular graphics card cooler, or a certain SSD, case, etc., then please specify that.
I'd like to get a 128gb SSD. I don't need any additonal storage.
I'd like to get 8gb of FAST ddr3 ram.
3 of my monitors have displayport which helps for picking a graphics card!
I want the motherboard to have USB 3.0. Front or back ports is fine with me.
I'd like to get a Fractal Design case. Cheaper black minimal cases work for me as well.
I have these parts from an old desktop I scrapped if they are useful:
submitted by weehooherod to buildapc [link] [comments]

[Security] I worked on my BTC security last night. How did I do?

I am getting to the point now where I have a substantial amount of BTC (not massively life changing, but it has turned into more than I have in fiat, which I have accepted and I am ok with.)
I wanted to secure these coins for long term safe-keeping, and I have a few questions for you very smart folks.
  1. Would you diversify your coins into multiple security methods, or are you comfortable with using 1 method that you know and trust for all of your coins?
  2. Please pick apart the process I used below to secure my coins:
This was all done on the same computer with the exception of using another computer to add a public key to
How did I do? I am a bit nervous about having all of my eggs in one basket.
submitted by btcthrowaway5 to Bitcoin [link] [comments]

INSTALLING Ubuntu 14.04 ONTO AN EXTERNAL HDD Install Ubuntu 16.04 on an external drive - YouTube Installing Ubuntu 16.10 to External Harddrive to be Portable on other Machines (by Fajar Purnama) Install Ubuntu to a External HDD HOW TO INSTALL UBUNTU WITH PERSISTENCE ON AN EXTERNAL HARD ...

OS: Windows 7. I want install Linux Ubuntu on portable external Hard Drive USB 2.0. I read a variety of methods, but I'm confused by contradictory advices and methods. Actually, installing Ubuntu on anything other than clean PC looks much more complicated than installing Windows. I need to have Ubuntu package + Python 2.7 + C compiler installed ... Next copy the renamed bitcoin data directory to a destination of your choice. This can be the same hard drive, an external hard drive, or a removable medium such as USB drive or SD card. Copying data may require only a few minutes or a couple of hours, depending on how up-to-date your copy of the block chain is and the speed of your hardware. I'm trying to install Ubuntu on my external hard-disk. Since I already have some files on that HDD, I created unallocated free space in order to install Linux on there. I am able to install it, however, I have to make a separate EFI partition - it does not allow me to install without it. But, in the end, I cannot boot Linux from the HDD as it ... 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 In this tutorial I’ve split them into groups per the build documentation on Github for Ubuntu, as I’ve tried to combine them before ... Do not leave debug set to 1 indefinitely or your log file will grow larger than the entire blockchain and fill up your hard drive. This is also where you can optionally set your node to prune the blockchain as it goes along. Right now the entire blockchain ...

[index] [724] [38981] [1371] [25206] [9102] [10801] [17152] [42764] [41106] [15638]


Step by step instructions for installing Ubuntu on an external drive. How to Install Ubuntu to a External disc. Clicking hard drive dis-assembly. How to and what to expect. 500GIG Western Digital USB storage. The video shows step by step procedure how to install Ubuntu with persistence on an extenal Hard Drive Do you want Ubuntu or Linux or opens us on your usb flash drive or portable(external) hard drive. carry your Ubuntu operating system in a USB connect to any ... ThE tutorial is for completely installing Ubuntu to the external HDD. Get a Live cd or the bootable pendrive and reboot the computer to bios... To make a bootable ubuntu... do this GET-- universal ...