This is a guide to using your Trezor with Bitcoin Core. It may seem like more trouble than it's worth but many applications use Bitcoin Core as a wallet such as LND, EPS, and JoinMarket. Learning how to integrate your Trezor into a Bitcoin Core install is rather useful in many unexpected ways. I did this all through the QT interfaces, but it's simple to script. There is a much simpler guide available from the HWI github, and the smallest Linux TLDR is here
Unfortunately, I don't have access to a Coldcard or Ledger. I'm not sure how the setpin or -stdinpass parameters are handled on that HW.

( A ) Install TrezorCTL, HWI, and build GUI

You only need to set the wallet up once, but may repeat to upgrade

( A.I ) Download extract and install HWI

1. Download and isntall Python
2. Download https://github.com/bitcoin-core/HWI/archive/1.1.2.zip
3. Extract it to a working folder (assumes C:\User\Reddit\src\HWI)
4. Change Directory (cd) to working folder cd "C:\User\Reddit\src\HWI"
5. Setup venv python -m venv .venv
6. Enter venv .venv\Scripts\activate.bat ¹
7. Install dependencies python -m pip install -U setuptools pip wheel
8. Install TrezorCTL python -m pip install trezor[hidapi]
9. Install HWI python -m pip install hwi pyside2
10. Download github.com/libusb/libusb/releases/download/v1.0.23/libusb-1.0.23.7z
11. Extract MS64\dll\libusb-1.0.dll from the archive
12. Copy to pywin copy libusb-1.0.dll .venv\Lib\site-packages\pywin32_system32\

( A.II ) Build the QT UI files

1. Download and install MSYS2
2. Launch a mingw64.exe shell
3. CD to working folder cd "C:\User\Reddit\src\HWI"
4. Enter venv source .venv/Scripts/activate ¹
5. Run UI build bash contrib/generate-ui.sh

( B ) Create a Trezor wallet in Bitcoin Core (testnet)

You only need to set the wallet up once, no private key data is stored, only xpub data

( B.I ) Retrieve keypool from HWI-QT

1. Launch hwi-qt.exe --testnet (assuming testnet)
2. Click Set passphrase (if needed) to cache your passphrase then click Refresh
3. Select you trezor from the list then click Set Pin (if needed)
4. Ensure your Trezor in the dropdown has a fingerprint
5. Select Change keypool options and choose P2WPKH
6. Copy all the text from the Keypool textbox

( B.II ) Create the wallet in Bitcoin QT

1. Launch Bitcoin Core (testnet) (non-pruned) ²
2. Select Console from the Window menu
3. Create a wallet createwallet "hwi" true
4. Ensure that hwi is selected in the console wallet dropdown
5. Verify walletname using the getwalletinfo command
6. Import keypool importmulti '' (note ' caging)
7. Rescan if TXNs are missing rescanblockchain ³

( C.I ) Grab Tesnet coins

1. Select the Receive tab in Bitcoin Core (testnet)
2. Ensure that the Wallet dropdown has hwi selected
3. Select Create new receiving address and copy address
4. Google "bitcoin testnet faucet" and visit a few sites
5. Answer captcha and input your addressed copied from C.I.3

( D ) Spending funds with HWI

This is how you can spend funds in your Trezor using Bitcoin Core (testnet)

( D.I ) Create an unsigned PSBT

1. Select the Send tab in Bitcoin Core (testnet)
2. Ensure that the Wallet dropdown has hwi selected
3. Verify your balance in Watch-only balance
4. Rescan if balance is wrong (see B.II.7) ³
5. Craft your TXN as usual, then click Create Unsigned
6. Copy the PSBT to your clipboard when prompted

( D.II ) Sign your PSBT

1. In HWI-QT click Sign PSBT
2. Paste what you copied in D.I.6 in PSBT to Sign field
3. Click Sign PSBT
4. Copy the text for PSBT Result

( D.III ) Broadcast your TXN

1. Select the Console window in Bitcoin Core (testnet)
2. Ensure that the Wallet dropdown has hwi selected
3. Finalize PSBT: finalizepsbt
4. Copy the signed TXN hex from the hex field returned
5. Broadcast TXN: sendrawtransaction

Final Thoughts

I did this all through the GUI interfaces for the benefit of the Windows users. Windows console is fine, but the quote escaping in windows console is nightmarish. Powershell would be good, but that throws this on a whole another level for most Windows folks.
There is also the need to use HWI-QT due to a bug in blank passphrases on the commandline. You can work around it by toggling passphrase off or on, but again, it's more than I wanted to spell out.
^Footnotes:

• ^{1. - Later version of python put the activate script under 'bin' instead of 'Script'}
• ^{2. - You can run pruned, but you need to have a fresh wallet}
• ^{3. - Rescan is automatic on 'importmulti' but I was pruned so it was wierd}

I was previously using bitcoin-qt.exe, emulated on my Linux machine. I have lost the ability to emulate that. (I won't go into details.) I therefore downloaded the Ubuntu version of Bitcoin Core, and am about to try to install that.
It is asking me where I want to download the entire 300 GB blockchain, again. I have already downloaded it. I don't have room on my computer to download a second copy of it. It's already taking up 300 GB of space on my harddrive.
Do I have to delete my previous copy of the blockchain? Or can I tell Bitcoin Core where to find it, so that it doesn't have to redownload it all over again?
(I am also hoping this will save time; but time is less important to me than disk space.)

Reddcoin (RDD) Core Wallet v3.0.1 - January 09, 2020
Version 3.0.1 is the official release version of Reddcoin Core. It is available for download at Reddcoin Core's Github repository here: https://github.com/reddcoin-project/reddcoin/releases/tag/v3.0.1
This release features PoSV v2.supermajority activation and new staking ruleset (and minor misc fixes). v3.0.1 is still not yet MacOS Catalina compatible. We are still working and should have that fix issued very soon. Sincere apologies to our Mac-using ReddHeads.
It is particularly important that all users upgrade, as once PoSV v2 is enforced, version 4 blocks will be rejected from the network entirely.
Therefore v3.0.1 is a "strongly recommended" update for all users. Note: If you have already installed v3.0.0, this upgrade is not required. If you have not yet upgraded from v2.0.x or earlier, this is a REQUIRED upgrade. Please install the newest version v3.0.1 to avoid losing functionality during supermajority activation of PoSV v2.
Reddcoin Core version 3.0.1 is now available from: https://github.com/reddcoin-project/reddcoin/releases Release Notes are available here and replicated below in this announcement: https://github.com/reddcoin-project/reddcoin/blob/mastedoc/release-notes.md
This is a new major version release of Reddcoin.
Previously, the original and subsequent versions of Reddcoin were taken from a fork of the Litecoin code base.
With the release of Reddcoin V2.0.0, the code was based directly from a fork of Bitcoin. This allows for better source control and feature implementation from upstream changes into the future
With the release of Reddcoin V3.0.0, the PoSV stake reward has been improved to allow for a target 5% network growth, in process re-incentivizing individual network stakers and providing for integrated dev support.
Upgrading to this release is strongly recommended and required for continued operation. Once a supermajority of 90% is reached, old wallets will no longer accept the new v5 blocks.
Please report bugs using the issue tracker at github:
https://github.com/reddcoin-project/reddcoin/issues
How to Upgrade
If you are running an older version of Reddcoin, shut it down. Wait until it has completely shut down (which may take a few minutes for older versions). Run the installer (on Windows) or just copy over /Applications/Reddcoin-Qt (on Mac) or reddcoind/reddcoin-qt (on Linux).
Start wallet. All done!

Reddcoin v3.0.0 introduced an updated PoSV method to better distribute staking rewards and target a overall 5% network growth. Staking and relay policy enhancements 

To implement PoSV v2, Reddcoin Core's block templates are now for version 5 blocks only. When PoSV v2 consensus (Supermajority 9000/10000) is reached, only v5 blocks will be accepted by the network.This equates to approximately 90% of blocks being generated over 1 week period. Status at any time may be viewed in node debug.log
Blockchain Download:
Blockchain data for both testnet and mainnet along with instructions can be downloaded from github. https://github.com/reddcoin-project/bootstrap_files
3.0.1 changelog
*83e212838 - John Nash, 2020-01-09 : really delete these files *3a1458ecd - Oliver Webb, 2020-01-08 : Added missing dependency libminiupnpc-dev for Jessie *d21915431 - Tiago Peralta, 2019-06-21 : Add vout to listtransactions/gettransaction *8d58ea7cf - Oliver Webb, 2020-01-08 : Script for downloading pre compiled binaries for Raspbian Jessie, Stretch or Buster *d4eced1bc - Oliver Webb, 2020-01-08 : Delete reddcoin_core_download_raspbian_stretch.sh *c5e9f91cf - Oliver Webb, 2020-01-08 : Delete reddcoin_core_download_raspbian_jessie.sh *5d5771b00 - Oliver Webb, 2020-01-08 : Delete reddcoin_core_download_raspbian_buster.sh *75c6ae91b - Oliver Webb, 2020-01-05 : add reddcoin-qt and remove starting daemon process *54c501787 - Oliver Webb, 2020-01-05 : add reddcoin-qt and remove starting daemon process *acb30a2b6 - Oliver Webb, 2020-01-05 : script files for Raspbian Jessie (also Stakebox) *cfddbe594 - John Nash, 2020-01-05 : Update copyright year and version *e46e5e7de - John Nash, 2020-01-05 : download script for pre compiled wallet *37386790a - John Nash, 2020-01-05 : change libssl deb packages links to github *9dbc772e6 - Oliver Webb, 2020-01-03 : download script for pre compiled wallet *857d697fd - Oliver Webb, 2020-01-03 : change libssl deb packages links to github *2cb74b9a8 - John Nash, 2019-12-31 : update copyright year *c641a1ab3 - Oliver Webb, 2019-12-30 : Raspberry Pi build script files for v3 wallet *a3f21a4a4 - John Nash, 2019-12-30 : add install script for building db4 update instructions for unix, osx, arm building using the db4 install script *5f6299b2a - John Nash, 2019-12-28 : docs: Update build notes for arm processors *465716c01 - John Nash, 2019-12-28 : test for arm devices *3fec3a535 - John Nash, 2018-02-02 : build: update source paths *5f6031ab4 - John Nash, 2019-12-28 : Scrypt n=1024 Pow hash based upon Colin Percival's Tarnsnap (2009) Modified by Artforz, coblee, pooler, wtogami, Nikolay Belikov, reddink *2fd4d91a0 - John Nash, 2019-12-24 : update copyright year *326828b36 - John Nash, 2019-12-24 : set release state true *8ebede0a6 - John Nash, 2019-12-24 : release notes *36df6fdfb - John Nash, 2019-12-23 : add check explictly for v5 blocks or greater *874dc1f0c - John Nash, 2019-12-17 : remove hardcoded global variable rearrange debug log output *763b25db8 - John Nash, 2019-12-17 : move copyright to new line *536baf635 - John Nash, 2019-12-17 : update version and set release state to false *cde9009f3 - John Nash, 2019-12-17 : update copyright year *ae41b7ed3 - John Nash, 2019-12-17 : set isSuperMajority to 90% for mainnet *e43e1c8ed - John Nash, 2019-12-10 : additional logging to verify isSuperMajority in the debug.log output *e31783cac - John Nash, 2019-12-05 : add/update public key for mainnet *405c6f002 - John Nash, 2019-12-05 : add log output for current inflation rate *9cc43c3f7 - John Nash, 2019-12-02 : determine calculated stake based on posv version *7baa3bf75 - John Nash, 2019-11-25 : check the posv transaction for correct pubkey *9ffa7ca38 - John Nash, 2019-11-21 : check for posv v1 or posv v2 blocks when calculating stake reward *39f7aad68 - John Nash, 2019-11-14 : add logging *0e283e6c3 - John Nash, 2019-11-13 : correct maths *74cbdeffd - John Nash, 2019-11-11 : use new posv v2 functions addidtional logging *35d7413b5 - John Nash, 2019-11-11 : add new proofofstakereward *3d917216c - John Nash, 2019-11-11 : get inflation adjustment *f63d17443 - John Nash, 2019-11-08 : add the developer output split fund output *ca263c9c9 - John Nash, 2019-11-05 : add dev key to chainparams *df6996ab0 - John Nash, 2019-11-05 : add block version checking *14b663479 - John Nash, 2019-11-05 : increase block version
Credits
Thanks to everyone who contributed to coding, testing and feedback for this release, notably:

@cryptognasher @techadept @chris @cryptobuze @harmonyq @mindredder @paxtech @Tiago Peralta 

Stake on!!
-Reddcoin (RDD) Core Development Team

Moderately long post, tl;dr at the bottom.
I've seen lightning transaction gifs and videos over and over. Today, I decided to fire up a lightning node on my laptop and give it a shot.
I followed this walk-through for mac (I adapted it to Arch Linux) for setting up Bitcoin TestNet Node with Eclair Lightning (it's practically the same as Mac, except for the installation process). Running on Arch caused the problem of accidentally installing the latest dev version of Bitcoin Core (AUR:bitcoin-git) - also had some compilation issues because upstream moved some files and this hadn't been updated in the PKGBUILD.
The latest dev version of Bitcoin Core included the SegWit address generation by default, which was very nice, didn't have any bugs using it in the brief period I used it.
After a couple of hours of syncing the TestNet blocks on my laptop, I started up Eclair and got Eclair and Bitcoin Core connected (had to use bitcoin-qt --deprecatedrpc=addwitnessaddressbecuase Eclair calls a soon-to-be deprecated function), sent myself some tBTC, and started opening up channels. Once I had about 3 channels open, I went to everyone's favorite online coffee shop and rewarded myself with some imaginary coffee.
My mind was absolutely blown at how fast the transaction went through and how insanely low the fees were (10 sat).
I went to test a transaction with a couple more hops, bought myself an imaginary 100eur Steam voucher, paid 100 sat in fees, near instant transaction (my Eclair client took a couple seconds to find a route to bitrefill)
Lightning truly is an incredible addition to Bitcoin, big things are coming.
tl;dr - Saw a couple lightning transaction videos and gifs, didn't really sink in how amazing this really is, decided to give it a shot on linux, mind=blown
Edit: I've done a little further testing and noticed that Eclair doesn't warn you if you're opening a duplicate channel (open a second channel with the same node)

The good thing of loosing a post, is that you have to retype everything and this means that you are able to shorten the post.
So. TLDR, I have 2 hdd, 80gb and 320, the second one has only, all the Blockchain info, from another already running node. I am not able to tell BTC Core program that the files are already there so he does not need to download 300gb. After hours of Google and linux forums, I am stuck in this issue. Every time I type "bitcoin-qt" on my terminal, it shows as a first download. Any help will be appreciate.
​
Full story.
English is not my first language, and this is being typed for second time (please have mercy on my grammar or misspelling mistakes), because I posted the question on linux subreddit nobody give a f..... so I decided to bring it here, posted a short post with the link and the automatic bot deleted because the of the link. I erased both the linux and the bitcoin post, and made a third one new, here, with plain text, copy pasting the info from the linux post. Never appeared on the "new" section of this sub. So hours of typing lost, and here we are.
Old Notebook. 80gb drive, and noob to Linux. Although I have some pc and logic knowledge, installed MINT due to a recommendation from a Bitcoin community, but since I have a friend with an already running node, with Ubuntu switched to this one, just to have the same system.
Once Ubuntu installed, on the 80gb and pc running, I copy and pasted the whole bitcoin folder from my friends pc to my 320 gb. Up to here all was good. But here is the problem
​
My friend, who does not understand nothing about linux, is owner of a company and has an IT guy who made everything for him, but would not be willing to help me a lot, (just to be good with his boss but right now it is not reachable for me), but when we where on my pc he told me that Linux is very sensitive to ports, in other words, a small usb change, will do a program to loose the path for the files. SO, instead of using the 320gb disk on USB i installed on this notebook second Hdd bay (its an old high end laptop with 2 sata connectors), he was able to set the program and everything went well for a couple of hours, Bitcoin Core program started synchronizing, downloading very little info.
​
I needed to turn of the pc to move it, so closed the program (waited until bitcoin core program told me was safe to) and turn it off, then turn it on again, and the problem was there, bitcoin core program started trying to download the whole blockchain in the spare 2gb of the 320 gb disk.
So what it seemed to happen is that even when the disk is installed on a sata bay from the motherboard, as I did not installed ubunutu with this disk connected it's route (adress?) is dinamyc and that is why BTC Core Program lost the files and does not recognize it.
After hours of google, linux forums and "askubuntu" i was able to, mount the 320gb disk, first editing the fstab ( i followed the guide in "askubuntu.com/questions/125257/how-do-i-add-an-additional-hard-drive") by the way. Trying to use VIM editor was a pain, it is REALLY difficult to type something there, and save it without pressing a wrong key. I had to cancel and start over at least a dozen times (plus reading several guides), but still was not able to mount the disk (Actually after following the steps, the hdd (320) disappeared from the GUI). went back, erased, and the did the NANO steps, and I THINK that now the hard drive it is fixed (before, any change,when restarting the second hdd took some time to appear, now it seems that is mounted and to a fixed adress). Well, after mounting the hdd, I tryed to call the bitcoin-qt and the initial download page appear and again tries to download from the initial block. I searched over hours "file association in ubuntu", "program files path" etc etc and the only thing I found is how to set up the desired software to open a file.
​
For you to understand my mess, when I did the "user:user" thing, I did not understand completely what I was doing, (yes I had to be in sudo) BUT i think I managed to did the correct thing as both hdd are shown in the Ubuntu GUI.
​
Some additional data is
Both hard drives are formated in Ext4
I have (I think that) a fstab.bak before any changes
​
I knwo that linux users sometimes ask for details on the system, just tell me the commands and i can run them to stick any info needed.
​
Thanks for the help in advance.

Introduction

Dear Groestlers, it goes without saying that 2020 has been a difficult time for millions of people worldwide. The groestlcoin team would like to take this opportunity to wish everyone our best to everyone coping with the direct and indirect effects of COVID-19. Let it bring out the best in us all and show that collectively, we can conquer anything.
The centralised banks and our national governments are facing unprecedented times with interest rates worldwide dropping to record lows in places. Rest assured that this can only strengthen the fundamentals of all decentralised cryptocurrencies and the vision that was seeded with Satoshi's Bitcoin whitepaper over 10 years ago. Despite everything that has been thrown at us this year, the show must go on and the team will still progress and advance to continue the momentum that we have developed over the past 6 years.
In addition to this, we'd like to remind you all that this is Groestlcoin's 6th Birthday release! In terms of price there have been some crazy highs and lows over the years (with highs of around $2.60 and lows of $0.000077!), but in terms of value– Groestlcoin just keeps getting more valuable! In these uncertain times, one thing remains clear – Groestlcoin will keep going and keep innovating regardless. On with what has been worked on and completed over the past few months.

UPDATED - Groestlcoin Core 2.18.2

This is a major release of Groestlcoin Core with many protocol level improvements and code optimizations, featuring the technical equivalent of Bitcoin v0.18.2 but with Groestlcoin-specific patches. On a general level, most of what is new is a new 'Groestlcoin-wallet' tool which is now distributed alongside Groestlcoin Core's other executables.
NOTE: The 'Account' API has been removed from this version which was typically used in some tip bots. Please ensure you check the release notes from 2.17.2 for details on replacing this functionality.

• Builds are now done through Gitian
• Calls to getblocktemplate will fail if the segwit rule is not specified. Calling getblocktemplate without segwit specified is almost certainly a misconfiguration since doing so results in lower rewards for the miner. Failed calls will produce an error message describing how to enable the segwit rule.
• A warning is printed if an unrecognized section name is used in the configuration file. Recognized sections are [test], [main], and [regtest].
• Four new options are available for configuring the maximum number of messages that ZMQ will queue in memory (the "high water mark") before dropping additional messages. The default value is 1,000, the same as was used for previous releases.
• The rpcallowip option can no longer be used to automatically listen on all network interfaces. Instead, the rpcbind parameter must be used to specify the IP addresses to listen on. Listening for RPC commands over a public network connection is insecure and should be disabled, so a warning is now printed if a user selects such a configuration. If you need to expose RPC in order to use a tool like Docker, ensure you only bind RPC to your localhost, e.g. docker run [...] -p 127.0.0.1:1441:1441 (this is an extra :1441 over the normal Docker port specification).
• The rpcpassword option now causes a startup error if the password set in the configuration file contains a hash character (#), as it's ambiguous whether the hash character is meant for the password or as a comment.
• The whitelistforcerelay option is used to relay transactions from whitelisted peers even when not accepted to the mempool. This option now defaults to being off, so that changes in policy and disconnect/ban behavior will not cause a node that is whitelisting another to be dropped by peers.
• A new short about the JSON-RPC interface describes cases where the results of anRPC might contain inconsistencies between data sourced from differentsubsystems, such as wallet state and mempool state.
• A new document (https://github.com/groestlcoin/groestlcoin/blob/mastedoc/groestlcoin-conf.md) about the groestlcoin.conf file describes how to use it to configure Groestlcoin Core.
• A new document introduces Groestlcoin Core's BIP174 interface, which is used to allow multiple programs to collaboratively work to create, sign, and broadcast new transactions. This is useful for offline (cold storage) wallets, multisig wallets, coinjoin implementations, and many other cases where two or more programs need to interact to generate a complete transaction.
• The output script descriptor (https://github.com/groestlcoin/groestlcoin/blob/mastedoc/descriptors.md) documentation has been updated with information about new features in this still-developing language for describing the output scripts that a wallet or other program wants to receive notifications for, such as which addresses it wants to know received payments. The language is currently used in multiple new and updated RPCs described in these release notes and is expected to be adapted to other RPCs and to the underlying wallet structure.
• A new --disable-bip70 option may be passed to ./configure to prevent Groestlcoin-Qt from being built with support for the BIP70 payment protocol or from linking libssl. As the payment protocol has exposed Groestlcoin Core to libssl vulnerabilities in the past, builders who don't need BIP70 support are encouraged to use this option to reduce their exposure to future vulnerabilities.
• The minimum required version of Qt (when building the GUI) has been increased from 5.2 to 5.5.1 (the depends system provides 5.9.7)
• getnodeaddresses returns peer addresses known to this node. It may be used to find nodes to connect to without using a DNS seeder.
• listwalletdir returns a list of wallets in the wallet directory (either the default wallet directory or the directory configured bythe -walletdir parameter).
• getrpcinfo returns runtime details of the RPC server. Currently, it returns an array of the currently active commands and how long they've been running.
• deriveaddresses returns one or more addresses corresponding to an output descriptor.
• getdescriptorinfo accepts a descriptor and returns information aboutit, including its computed checksum.
• joinpsbts merges multiple distinct PSBTs into a single PSBT. The multiple PSBTs must have different inputs. The resulting PSBT will contain every input and output from all the PSBTs. Any signatures provided in any of the PSBTs will be dropped.
• analyzepsbt examines a PSBT and provides information about what the PSBT contains and the next steps that need to be taken in order to complete the transaction. For each input of a PSBT, analyze psbt provides information about what information is missing for that input, including whether a UTXO needs to be provided, what pubkeys still need to be provided, which scripts need to be provided, and what signatures are still needed. Every input will also list which role is needed to complete that input, and analyzepsbt will also list the next role in general needed to complete the PSBT. analyzepsbt will also provide the estimated fee rate and estimated virtual size of the completed transaction if it has enough information to do so.
• utxoupdatepsbt searches the set of Unspent Transaction Outputs (UTXOs) to find the outputs being spent by the partial transaction. PSBTs need to have the UTXOs being spent to be provided because the signing algorithm requires information from the UTXO being spent. For segwit inputs, only the UTXO itself is necessary. For non-segwit outputs, the entire previous transaction is needed so that signers can be sure that they are signing the correct thing. Unfortunately, because the UTXO set only contains UTXOs and not full transactions, utxoupdatepsbt will only add the UTXO for segwit inputs.
• getpeerinfo now returns an additional minfeefilter field set to the peer's BIP133 fee filter. You can use this to detect that you have peers that are willing to accept transactions below the default minimum relay fee.
• The mempool RPCs, such as getrawmempool with verbose=true, now return an additional "bip125-replaceable" value indicating whether thetransaction (or its unconfirmed ancestors) opts-in to asking nodes and miners to replace it with a higher-feerate transaction spending any of the same inputs.
• settxfee previously silently ignored attempts to set the fee below the allowed minimums. It now prints a warning. The special value of"0" may still be used to request the minimum value.
• getaddressinfo now provides an ischange field indicating whether the wallet used the address in a change output.
• importmulti has been updated to support P2WSH, P2WPKH, P2SH-P2WPKH, and P2SH-P2WSH. Requests for P2WSH and P2SH-P2WSH accept an additional witnessscript parameter.
• importmulti now returns an additional warnings field for each request with an array of strings explaining when fields are being ignored or are inconsistent, if there are any.
• getaddressinfo now returns an additional solvable Boolean field when Groestlcoin Core knows enough about the address's scriptPubKey, optional redeemScript, and optional witnessScript for the wallet to be able to generate an unsigned input spending funds sent to that address.
• The getaddressinfo, listunspent, and scantxoutset RPCs now return an additional desc field that contains an output descriptor containing all key paths and signing information for the address (except for the private key). The desc field is only returned for getaddressinfo and listunspent when the address is solvable.
• importprivkey will preserve previously-set labels for addresses or public keys corresponding to the private key being imported. For example, if you imported a watch-only address with the label "coldwallet" in earlier releases of Groestlcoin Core, subsequently importing the private key would default to resetting the address's label to the default empty-string label (""). In this release, the previous label of "cold wallet" will be retained. If you optionally specify any label besides the default when calling importprivkey, the new label will be applied to the address.
• getmininginfo now omits currentblockweight and currentblocktx when a block was never assembled via RPC on this node.
• The getrawtransaction RPC & REST endpoints no longer check the unspent UTXO set for a transaction. The remaining behaviors are as follows:
  1. If a blockhash is provided, check the corresponding block.
  2. If no blockhash is provided, check the mempool.
  3. If no blockhash is provided but txindex is enabled, also check txindex.
• unloadwallet is now synchronous, meaning it will not return until the wallet is fully unloaded.
• importmulti now supports importing of addresses from descriptors. A desc parameter can be provided instead of the "scriptPubKey" in are quest, as well as an optional range for ranged descriptors to specify the start and end of the range to import. Descriptors with key origin information imported through importmulti will have their key origin information stored in the wallet for use with creating PSBTs.
• listunspent has been modified so that it also returns witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output.
• createwallet now has an optional blank argument that can be used to create a blank wallet. Blank wallets do not have any keys or HDseed. They cannot be opened in software older than 2.18.2. Once a blank wallet has a HD seed set (by using sethdseed) or private keys, scripts, addresses, and other watch only things have been imported, the wallet is no longer blank and can be opened in 2.17.2. Encrypting a blank wallet will also set a HD seed for it.
• signrawtransaction is removed after being deprecated and hidden behind a special configuration option in version 2.17.2.
• The 'account' API is removed after being deprecated in v2.17.2 The 'label' API was introduced in v2.17.2 as a replacement for accounts. See the release notes from v2.17.2 for a full description of the changes from the 'account' API to the 'label' API.
• addwitnessaddress is removed after being deprecated in version 2.16.0.
• generate is deprecated and will be fully removed in a subsequent major version. This RPC is only used for testing, but its implementation reached across multiple subsystems (wallet and mining), so it is being deprecated to simplify the wallet-node interface. Projects that are using generate for testing purposes should transition to using the generatetoaddress RPC, which does not require or use the wallet component. Calling generatetoaddress with an address returned by the getnewaddress RPC gives the same functionality as the old generate RPC. To continue using generate in this version, restart groestlcoind with the -deprecatedrpc=generate configuration option.
• Be reminded that parts of the validateaddress command have been deprecated and moved to getaddressinfo. The following deprecated fields have moved to getaddressinfo: ismine, iswatchonly,script, hex, pubkeys, sigsrequired, pubkey, embedded,iscompressed, label, timestamp, hdkeypath, hdmasterkeyid.
• The addresses field has been removed from the validateaddressand getaddressinfo RPC methods. This field was confusing since it referred to public keys using their P2PKH address. Clients should use the embedded.address field for P2SH or P2WSH wrapped addresses, and pubkeys for inspecting multisig participants.
• A new /rest/blockhashbyheight/ endpoint is added for fetching the hash of the block in the current best blockchain based on its height (how many blocks it is after the Genesis Block).
• A new Window menu is added alongside the existing File, Settings, and Help menus. Several items from the other menus that opened new windows have been moved to this new Window menu.
• In the Send tab, the checkbox for "pay only the required fee" has been removed. Instead, the user can simply decrease the value in the Custom Fee rate field all the way down to the node's configured minimumrelay fee.
• In the Overview tab, the watch-only balance will be the only balance shown if the wallet was created using the createwallet RPC and thedisable_private_keys parameter was set to true.
• The launch-on-startup option is no longer available on macOS if compiled with macosx min version greater than 10.11 (useCXXFLAGS="-mmacosx-version-min=10.11" CFLAGS="-mmacosx-version-min=10.11" for setting the deployment sdkversion)
• A new groestlcoin-wallet tool is now distributed alongside Groestlcoin Core's other executables. Without needing to use any RPCs, this tool can currently create a new wallet file or display some basic information about an existing wallet, such as whether the wallet is encrypted, whether it uses an HD seed, how many transactions it contains, and how many address book entries it has.
• Since version 2.16.0, Groestlcoin Core's built-in wallet has defaulted to generating P2SH-wrapped segwit addresses when users want to receive payments. These addresses are backwards compatible with all widely used software. Starting with Groestlcoin Core 2.20.1 (expected about a year after 2.18.2), Groestlcoin Core will default to native segwitaddresses (bech32) that provide additional fee savings and other benefits. Currently, many wallets and services already support sending to bech32 addresses, and if the Groestlcoin Core project sees enough additional adoption, it will instead default to bech32 receiving addresses in Groestlcoin Core 2.19.1. P2SH-wrapped segwit addresses will continue to be provided if the user requests them in the GUI or by RPC, and anyone who doesn't want the update will be able to configure their default address type. (Similarly, pioneering users who want to change their default now may set the addresstype=bech32 configuration option in any Groestlcoin Core release from 2.16.0 up.)
• BIP 61 reject messages are now deprecated. Reject messages have no use case on the P2P network and are only logged for debugging by most network nodes. Furthermore, they increase bandwidth and can be harmful for privacy and security. It has been possible to disable BIP 61 messages since v2.17.2 with the -enablebip61=0 option. BIP 61 messages will be disabled by default in a future version, before being removed entirely.
• The submitblock RPC previously returned the reason a rejected block was invalid the first time it processed that block but returned a generic "duplicate" rejection message on subsequent occasions it processed the same block. It now always returns the fundamental reason for rejecting an invalid block and only returns "duplicate" for valid blocks it has already accepted.
• A new submitheader RPC allows submitting block headers independently from their block. This is likely only useful for testing.
• The signrawtransactionwithkey and signrawtransactionwithwallet RPCs have been modified so that they also optionally accept a witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output. This is compatible with the change to listunspent.
• For the walletprocesspsbt and walletcreatefundedpsbt RPCs, if thebip32derivs parameter is set to true but the key metadata for a public key has not been updated yet, then that key will have a derivation path as if it were just an independent key (i.e. no derivation path and its master fingerprint is itself).
• The -usehd configuration option was removed in version 2.16.0 From that version onwards, all new wallets created are hierarchical deterministic wallets. This release makes specifying -usehd an invalid configuration option.
• This release allows peers that your node automatically disconnected for misbehaviour (e.g. sending invalid data) to reconnect to your node if you have unused incoming connection slots. If your slots fill up, a misbehaving node will be disconnected to make room for nodes without a history of problems (unless the misbehaving node helps your node in some other way, such as by connecting to a part of the Internet from which you don't have many other peers). Previously, Groestlcoin Core banned the IP addresses of misbehaving peers for a period (default of 1 day); this was easily circumvented by attackers with multiple IP addresses. If you manually ban a peer, such as by using the setban RPC, all connections from that peer will still be rejected.
• The key metadata will need to be upgraded the first time that the HDseed is available. For unencrypted wallets this will occur on wallet loading. For encrypted wallets this will occur the first time the wallet is unlocked.
• Newly encrypted wallets will no longer require restarting the software. Instead such wallets will be completely unloaded and reloaded to achieve the same effect.
• A sub-project of Bitcoin Core now provides Hardware Wallet Interaction (HWI) scripts that allow command-line users to use several popular hardware key management devices with Groestlcoin Core. See their project page for details.
• This release changes the Random Number Generator (RNG) used from OpenSSL to Groestlcoin Core's own implementation, although entropy gathered by Groestlcoin Core is fed out to OpenSSL and then read back in when the program needs strong randomness. This moves Groestlcoin Core a little closer to no longer needing to depend on OpenSSL, a dependency that has caused security issues in the past. The new implementation gathers entropy from multiple sources, including from hardware supporting the rdseed CPU instruction.
• On macOS, Groestlcoin Core now opts out of application CPU throttling ("app nap") during initial blockchain download, when catching up from over 100 blocks behind the current chain tip, or when reindexing chain data. This helps prevent these operations from taking an excessively long time because the operating system is attempting to conserve power.

How to Upgrade?

Windows
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer.
OSX
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), run the dmg and drag Groestlcoin Core to Applications.
Ubuntu
http://groestlcoin.org/forum/index.php?topic=441.0

Other Linux

http://groestlcoin.org/forum/index.php?topic=97.0

Download

Download the Windows Installer (64 bit) here
Download the Windows Installer (32 bit) here
Download the Windows binaries (64 bit) here
Download the Windows binaries (32 bit) here
Download the OSX Installer here
Download the OSX binaries here
Download the Linux binaries (64 bit) here
Download the Linux binaries (32 bit) here
Download the ARM Linux binaries (64 bit) here
Download the ARM Linux binaries (32 bit) here

Source

ALL NEW - Groestlcoin Moonshine iOS/Android Wallet

Built with React Native, Moonshine utilizes Electrum-GRS's JSON-RPC methods to interact with the Groestlcoin network.
GRS Moonshine's intended use is as a hot wallet. Meaning, your keys are only as safe as the device you install this wallet on. As with any hot wallet, please ensure that you keep only a small, responsible amount of Groestlcoin on it at any given time.

Features

• Groestlcoin Mainnet & Testnet supported
• Bech32 support
• Multiple wallet support
• Electrum - Support for both random and custom peers
• Encrypted storage
• Biometric + Pin authentication
• Custom fee selection
• Import mnemonic phrases via manual entry or scanning
• RBF functionality
• BIP39 Passphrase functionality
• Support for Segwit-compatible & legacy addresses in settings
• Support individual private key sweeping
• UTXO blacklisting - Accessible via the Transaction Detail view, this allows users to blacklist any utxo that they do not wish to include in their list of available utxo's when sending transactions. Blacklisting a utxo excludes its amount from the wallet's total balance.
• Ability to Sign & Verify Messages
• Support BitID for password-free authentication
• Coin Control - This can be accessed from the Send Transaction view and basically allows users to select from a list of available UTXO's to include in their transaction.
• Ability to Broadcast raw transactions

Download

iOS
Android

Source

ALL NEW! – HODL GRS Android Wallet

HODL GRS connects directly to the Groestlcoin network using SPV mode and doesn't rely on servers that can be hacked or disabled.
HODL GRS utilizes AES hardware encryption, app sandboxing, and the latest security features to protect users from malware, browser security holes, and even physical theft. Private keys are stored only in the secure enclave of the user's phone, inaccessible to anyone other than the user.
Simplicity and ease-of-use is the core design principle of HODL GRS. A simple recovery phrase (which we call a Backup Recovery Key) is all that is needed to restore the user's wallet if they ever lose or replace their device. HODL GRS is deterministic, which means the user's balance and transaction history can be recovered just from the backup recovery key.

Features

• Simplified payment verification for fast mobile performance
• No server to get hacked or go down
• Single backup phrase that works forever
• Private keys never leave your device
• Import password protected paper wallets
• Payment protocol payee identity certification

Download

Main Release (Main Net)
Testnet Release

Source

ALL NEW! – GroestlcoinSeed Savior

Groestlcoin Seed Savior is a tool for recovering BIP39 seed phrases.
This tool is meant to help users with recovering a slightly incorrect Groestlcoin mnemonic phrase (AKA backup or seed). You can enter an existing BIP39 mnemonic and get derived addresses in various formats.
To find out if one of the suggested addresses is the right one, you can click on the suggested address to check the address' transaction history on a block explorer.

Features

• If a word is wrong, the tool will try to suggest the closest option.
• If a word is missing or unknown, please type "?" instead and the tool will find all relevant options.

Live Version (Not Recommended)

https://www.groestlcoin.org/recovery/

Download

https://github.com/Groestlcoin/mnemonic-recovery/archive/master.zip

Source

ALL NEW! – Vanity Search Vanity Address Generator

NOTE: NVidia GPU or any CPU only. AMD graphics cards will not work with this address generator.
VanitySearch is a command-line Segwit-capable vanity Groestlcoin address generator. Add unique flair when you tell people to send Groestlcoin. Alternatively, VanitySearch can be used to generate random addresses offline.
If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then VanitySearch is the right choice for you to create a more personalized address.
VanitySearch is a groestlcoin address prefix finder. If you want to generate safe private keys, use the -s option to enter your passphrase which will be used for generating a base key as for BIP38 standard (VanitySearch.exe -s "My PassPhrase" FXPref). You can also use VanitySearch.exe -ps "My PassPhrase" which will add a crypto secure seed to your passphrase.
VanitySearch may not compute a good grid size for your GPU, so try different values using -g option in order to get the best performances. If you want to use GPUs and CPUs together, you may have best performances by keeping one CPU core for handling GPU(s)/CPU exchanges (use -t option to set the number of CPU threads).

Features

• Fixed size arithmetic
• Fast Modular Inversion (Delayed Right Shift 62 bits)
• SecpK1 Fast modular multiplication (2 steps folding 512bits to 256bits using 64 bits digits)
• Use some properties of elliptic curve to generate more keys
• SSE Secure Hash Algorithm SHA256 and RIPEMD160 (CPU)
• Multi-GPU support
• CUDA optimisation via inline PTX assembly
• Seed protected by pbkdf2_hmac_sha512 (BIP38)
• Support P2PKH, P2SH and BECH32 addresses
• Support split-key vanity address

Usage

https://github.com/Groestlcoin/VanitySearch#usage

Download

Source

ALL NEW! – Groestlcoin EasyVanity 2020

Groestlcoin EasyVanity 2020 is a windows app built from the ground-up and makes it easier than ever before to create your very own bespoke bech32 address(es) when whilst not connected to the internet.
If you're tired of the random, cryptic bech32 addresses generated by regular Groestlcoin clients, then Groestlcoin EasyVanity2020 is the right choice for you to create a more personalised bech32 address. This 2020 version uses the new VanitySearch to generate not only legacy addresses (F prefix) but also Bech32 addresses (grs1 prefix).

Features

• Ability to continue finding keys after first one is found
• Includes warning on start-up if connected to the internet
• Ability to output keys to a text file (And shows button to open that directory)
• Show and hide the private key with a simple toggle switch
• Show full output of commands
• Ability to choose between Processor (CPU) and Graphics Card (GPU) ( NVidia ONLY! )
• Features both a Light and Dark Material Design-Style Themes
• Free software - MIT. Anyone can audit the code.
• Written in C# - The code is short, and easy to review.

Download

Source

Remastered! – Groestlcoin WPF Desktop Wallet (v2.19.0.18)

Groestlcoin WPF is an alternative full node client with optional lightweight 'thin-client' mode based on WPF. Windows Presentation Foundation (WPF) is one of Microsoft's latest approaches to a GUI framework, used with the .NET framework. Its main advantages over the original Groestlcoin client include support for exporting blockchain.dat and including a lite wallet mode.
This wallet was previously deprecated but has been brought back to life with modern standards.

Features

• Works via TOR or SOCKS5 proxy
• Can use bootstrap.dat format as blockchain database
• Import/Export blockchain to/from bootstrap.dat
• Import wallet.dat from Groestlcoin-qt wallet
• Export wallet to wallet.dat
• Use both groestlcoin-wpf and groestlcoin-qt with the same addresses in parallel. When you send money from one program, the transaction will automatically be visible on the other wallet.
• Rescan blockchain with a simple mouse click
• Works as a full node and listens to port 1331 (listening port can be changed)
• Fast Block verifying, parallel processing on multi-core CPUs
• Mine Groestlcoins with your CPU by a simple mouse click
• All private keys are kept encrypted on your local machine (or on a USB stick)
• Lite - Has a lightweight "thin client" mode which does not require a new user to download the entire Groestlcoin chain and store it
• Free and decentralised - Open Source under GNU license

Remastered Improvements

• Bech32 support
• P2sh support
• Fixed Import/Export to wallet.dat
• Testnet Support
• Rescan wallet option
• Change wallet password option
• Address type and Change type options through *.conf file
• Import from bootstrap.dat - It is a flat, binary file containing Groestlcoin blockchain data, from the genesis block through a recent height. All versions automatically validate and import the file "grs.bootstrap.dat" in the GRS directory. Grs.bootstrap.dat is compatible with Qt wallet. GroestlCoin-Qt can load from it.
• In Full mode file %APPDATA%\Groestlcoin-WPF\GRS\GRS.bootstrap.dat is full blockchain in standard bootstrap.dat format and can be used with other clients.

Download

Source

ALL NEW! – BIP39 Key Tool

Groestlcoin BIP39 Key Tool is a GUI interface for generating Groestlcoin public and private keys. It is a standalone tool which can be used offline.

Features

• Selection options for 3-24 words (simply putting the space separated words in the first word box will also work) along with a bip39 passphrase
• User input for total number of addresses desired
• Creation of P2PKH, P2SH, P2WPKH and P2WSH addresses along with xpriv and xpub as per BIP32 spec, using a word list as the starting point following the BIP39 standard.
• Pre-sets for BIP44, BIP49, BIP84 and BIP141 standards, along with custom user input for derivation path
• Option for Hardened or non-hardened addresses
• Option for Testnet private and public keys
• Output containing derivation path, private key in WIF, integer and hex format, public key address, public point on curve and scriptpubkey
• Results are output in a file titled 'wallet.txt' with the time addresses were generated, along with all information presented onscreen

Download

Windows
Linux :

 pip3 install -r requirements.txt python3 bip39\_gui.py 

Source

ALL NEW! – Electrum Personal Server

Groestlcoin Electrum Personal Server aims to make using Electrum Groestlcoin wallet more secure and more private. It makes it easy to connect your Electrum-GRS wallet to your own full node.
It is an implementation of the Electrum-grs server protocol which fulfils the specific need of using the Electrum-grs wallet backed by a full node, but without the heavyweight server backend, for a single user. It allows the user to benefit from all Groestlcoin Core's resource-saving features like pruning, blocks only and disabled txindex. All Electrum-GRS's feature-richness like hardware wallet integration, multi-signature wallets, offline signing, seed recovery phrases, coin control and so on can still be used, but connected only to the user's own full node.
Full node wallets are important in Groestlcoin because they are a big part of what makes the system be trust-less. No longer do people have to trust a financial institution like a bank or PayPal, they can run software on their own computers. If Groestlcoin is digital gold, then a full node wallet is your own personal goldsmith who checks for you that received payments are genuine.
Full node wallets are also important for privacy. Using Electrum-GRS under default configuration requires it to send (hashes of) all your Groestlcoin addresses to some server. That server can then easily spy on your transactions. Full node wallets like Groestlcoin Electrum Personal Server would download the entire blockchain and scan it for the user's own addresses, and therefore don't reveal to anyone else which Groestlcoin addresses they are interested in.
Groestlcoin Electrum Personal Server can also broadcast transactions through Tor which improves privacy by resisting traffic analysis for broadcasted transactions which can link the IP address of the user to the transaction. If enabled this would happen transparently whenever the user simply clicks "Send" on a transaction in Electrum-grs wallet.
Note: Currently Groestlcoin Electrum Personal Server can only accept one connection at a time.

Features

• Use your own node
• Tor support
• Uses less CPU and RAM than ElectrumX
• Used intermittently rather than needing to be always-on
• Doesn't require an index of every Groestlcoin address ever used like on ElectrumX

Download

Windows
Linux / OSX (Instructions)

Source

UPDATED – Android Wallet 7.38.1 - Main Net + Test Net

The app allows you to send and receive Groestlcoin on your device using QR codes and URI links.
When using this app, please back up your wallet and email them to yourself! This will save your wallet in a password protected file. Then your coins can be retrieved even if you lose your phone.

Changes

• Add confidence messages, helping users to understand the confidence state of their payments.
• Handle edge case when restoring via an external app.
• Count devices with a memory class of 128 MB as low ram.
• Introduce dark mode on Android 10 devices.
• Reduce memory usage of PIN-protected wallets.
• Tapping on the app's version will reveal a checksum of the APK that was installed.
• Fix issue with confirmation of transactions that empty your wallet.

Download

Main Net
Main Net (FDroid)
Test Net

Source

UPDATED – Groestlcoin Sentinel 3.5.06 (Android)

Groestlcoin Sentinel is a great solution for anyone who wants the convenience and utility of a hot wallet for receiving payments directly into their cold storage (or hardware wallets).
Sentinel accepts XPUB's, YPUB'S, ZPUB's and individual Groestlcoin address. Once added you will be able to view balances, view transactions, and (in the case of XPUB's, YPUB's and ZPUB's) deterministically generate addresses for that wallet.
Groestlcoin Sentinel is a fork of Groestlcoin Samourai Wallet with all spending and transaction building code removed.

Changes

• Removed Cryptopia
• Added adaptive icons for Android 8 and above
• Add block book block explorer

Download

Source

UPDATED – P2Pool Test Net

Changes

• Add compatibility for Groestlcoin Core 2.18.2

Download

Pre-Hosted Testnet P2Pool is available via http://testp2pool.groestlcoin.org:21330/static/

Source

I have the skills to implement this if wanted.
Possible User Experience
This is a proposal, i.e. not implemented yet. Instructions for users, simplified.
How to install monero using apt-get
Download the repository signing key.
wget https://www.getmonero.org/monero.asc
Add the signing key.
sudo apt-key --keyring /etc/apt/trusted.gpg.d/monero.gpg add ~/monero.asc
Add APT repository.
echo "deb https://deb.getmonero.org buster main" | sudo tee /etc/apt/sources.list.d/monero.list
Update your package lists.
sudo apt-get update
Install monero.
sudo apt-get install monero
A few technical implementation details
I would simply grab the binaries provided by getmonero.org, download them, check software (gpg) signatures, put these into deb packages, add these to a repository, and upload the repository.
What I would not do is creating the binaries during package creation. While this is nice to have, it doesn't help user experience and blocks the progress on reaching this goal. See next chapter.
Why simply put the pre-build Monero binaries into a deb package?
1) After bitcoin existing for more than 10 years, being popular and being in Debian unstable (sid) it still never made its way into Debian testing, let alone stable. Reason being explained that a difference in underlying libraries (even just security fixes) during compilation may result in a network split. Binaries compiled during packaging on different versions of Linux distributions might have different libraries that might cause a network fork / chain split.
References:

• https://packages.debian.org/search?keywords=bitcoin-qt
• https://packages.debian.org/sid/bitcoin-qt
• upstream does not support stable releases (block migration to testing)

(Note: above website saying Tags: fixed-upstream is probably a mistake as discussion at bottom says.)
2) The github issue of packaging monero stalled.
3) By shipping the same binaries as provided by getmonero.org reduces the chances of introducing a backdoor.
Many Options

• By adding Monero to Whonix repository, a effort for creating a separate Monero repository could be saved. I.e. instead of deb https://deb.getmonero.org buster main users could do deb https://deb.whonix.org buster main. It's really just about the upload location. By providing DNS, even upload to Whonix server can offer https://deb.getmonero.org.
  
• Either I create the build instructions and source code of this implementation (Debian package and repository creation) the long term maintenance of putting new binaries into updated packages or only create build instructions and source code and someone from Monero team could create the actual deb packages and deb repository.
  
• gpg signed debs. Either gpg signed debs or an apt repository. Or both. Your choice.
  
• I'd start with Debian and perhaps Ubuntu packages for 64bit. Perhaps also 32bit. Potentially I could also do packaging for Feodra based distributions.
  

Timeline
Doable quickly. The electrum (bitcoin) AppImage was recently added to a Debian package (binaries-freedom) by me and is now easily installable in Whonix. Pre-installed in testers version of Whonix already.
About Me
I am the founder of Whonix, which I am maintaining at present for more than 7 years.
Whonix (formerly TorBOX) is a Debian GNU/Linux–based security-focused Linux distribution. It aims to provide privacy, security and anonymity on the internet.
You can see an overview of packages I am maintaining on my github profile.
To proof that this forum account adrelanos corresponds the same person maintaining whonix.org, it is added here.
Questions
What happened to, what is the successor of the forum funding system?

Thank you for running your own full Vertcoin node and supporting VTC network! We currently have 518 Full Nodes running.
Official node scanner list: https://scanner.vertcoin.org/nodes
Since every full VTC node can only serve so many clients, it's important to do your part for the Vertcoin network and run your own full node.
Q: WHAT IS A FULL NODE? A: Full nodes maintain a copy of the blockchain/ledger, distribute it to those downloading it, confirm transactions, and further spread out all of the previous functions to make the network more resilient. https://bitcoin.org/en/full-node
Q: Do I need to be a miner? A: No, you don't need to be a miner. Miners create new blocks. Full nodes simply share existing blocks (the entire VTC blockchain) with the rest of VTC wallet users.
Q: How do I run a Full VTC node on Intel NUC? A: Intel NUC Vertcoin full node installation done using Windows guide: https://github.com/vertcoin-project/VertDocs/blob/mastedocs/FullNodes/intel-nuc.md
Q: How do I run a Full VTC node? A: It's actually quite easy to do. If you run Vertcoin-QT (Vertcoin Core Wallet) on your PC/MAC desktop, keep it active in the systray. Then, make sure that you map the public port 5889 of your router to the port 5889 on the machine running Vertcoin-QT or vertcoind. For people running a public p2pool node this should be a no-brainer: you already have a synchronized vertcoind. So if you haven't opened port 5889 do it now - it's all you have to do. Your node is then public and can serve blocks and relay transactions.This makes our network much stronger and will help it to perform better. Any old or low power computer is good enough to run a full VTC node. If you have a Raspberry Pi or any old PC lying around, install vertcoind and run it in the background.
Q: How do I know if my Full Node is working correctly? A: To be a full node, you have to check to make sure you are accepting incoming connections. To do that, go under Help -> Debug Window. In the first tab, "Information", there is a Network "Number of Connections" which will show both incoming and outgoing connections. If the "In" is 0, then you are not a full node. If the "In" is greater than 0, you are acting as a full node and supporting VTC blockchain! Thank you!
What is Vertcoin? | Lightning Network SEGWIT Enabled ASIC resistant money https://www.youtube.com/watch?v=86-oMyHDCNc
Linux instructions: https://www.cryptocurrencyfreak.com/2017/09/06/setup-vertcoin-full-node-ubuntu-16-04/

Thank you for running your own full Vertcoin node and supporting VTC network! We currently have 518 Full Nodes running.
Since every full VTC node can only serve so many clients, it's important to do your part for the Vertcoin network and run your own full node.
Q: WHAT IS A FULL NODE? A: Full nodes maintain a copy of the blockchain/ledger, distribute it to those downloading it, confirm transactions, and further spread out all of the previous functions to make the network more resilient. https://bitcoin.org/en/full-node
Q: Do I need to be a miner? A: No, you don't need to be a miner. Miners create new blocks. Full nodes simply share existing blocks (the entire VTC blockchain) with the rest of VTC wallet users.
Q: How do I run a Full VTC node on Intel NUC? A: Intel NUC Vertcoin full node installation done using Windows guide: https://github.com/vertcoin-project/VertDocs/blob/mastedocs/FullNodes/intel-nuc.md
Q: How do I run a Full VTC node? A: It's actually quite easy to do. If you run Vertcoin-QT (Vertcoin Core Wallet) on your PC/MAC desktop, keep it active in the systray. Then, make sure that you map the public port 5889 of your router to the port 5889 on the machine running Vertcoin-QT or vertcoind. For people running a public p2pool node this should be a no-brainer: you already have a synchronized vertcoind. So if you haven't opened port 5889 do it now - it's all you have to do. Your node is then public and can serve blocks and relay transactions.This makes our network much stronger and will help it to perform better. Any old or low power computer is good enough to run a full VTC node. If you have a Raspberry Pi or any old PC lying around, install vertcoind and run it in the background.
Q: How do I know if my Full Node is working correctly? A: To be a full node, you have to check to make sure you are accepting incoming connections. To do that, go under Help -> Debug Window. In the first tab, "Information", there is a Network "Number of Connections" which will show both incoming and outgoing connections. If the "In" is 0, then you are not a full node. If the "In" is greater than 0, you are acting as a full node and supporting VTC blockchain! Thank you!
Q: Vertnode - An automated solution for installing Vertcoin node(s) on Single Board Computers A: https://www.reddit.com/vertcoin/comments/901e6a/vertnode_an_automated_solution_for_installing/
What is Vertcoin? | Lightning Network SEGWIT Enabled ASIC resistant money https://www.youtube.com/watch?v=86-oMyHDCNc
Official node scanner list (NOT RELIABLE, current node count could be much much higher. If you are a developer, please help us make a better Node Scanner): https://scanner.vertcoin.org/nodes
Linux instructions: https://www.cryptocurrencyfreak.com/2017/09/06/setup-vertcoin-full-node-ubuntu-16-04/

Thank you for running your own full Vertcoin node and supporting VTC network! We currently have 500+ Full Nodes running.
Official node scanner list (NOT RELIABLE, current node count could be much much higher. If you are a developer, please help us make a better Node Scanner): https://scanner.vertcoin.org/nodes
Since every full VTC node can only serve so many clients, it's important to do your part for the Vertcoin network and run your own full node.
Q: WHAT IS A FULL NODE? A: Full nodes maintain a copy of the blockchain/ledger, distribute it to those downloading it, confirm transactions, and further spread out all of the previous functions to make the network more resilient. https://bitcoin.org/en/full-node
Q: Do I need to be a miner? A: No, you don't need to be a miner. Miners create new blocks. Full nodes simply share existing blocks (the entire VTC blockchain) with the rest of VTC wallet users.
Q: How do I run a Full VTC node on Intel NUC? A: Intel NUC Vertcoin full node installation done using Windows guide: https://github.com/vertcoin-project/VertDocs/blob/mastedocs/FullNodes/intel-nuc.md
Q: How do I run a Full VTC node? A: It's actually quite easy to do. If you run Vertcoin-QT (Vertcoin Core Wallet) on your PC/MAC desktop, keep it active in the systray. Then, make sure that you map the public port 5889 of your router to the port 5889 on the machine running Vertcoin-QT or vertcoind. For people running a public p2pool node this should be a no-brainer: you already have a synchronized vertcoind. So if you haven't opened port 5889 do it now - it's all you have to do. Your node is then public and can serve blocks and relay transactions.This makes our network much stronger and will help it to perform better. Any old or low power computer is good enough to run a full VTC node. If you have a Raspberry Pi or any old PC lying around, install vertcoind and run it in the background.
Q: How do I know if my Full Node is working correctly? A: To be a full node, you have to check to make sure you are accepting incoming connections. To do that, go under Help -> Debug Window. In the first tab, "Information", there is a Network "Number of Connections" which will show both incoming and outgoing connections. If the "In" is 0, then you are not a full node. If the "In" is greater than 0, you are acting as a full node and supporting VTC blockchain! Thank you!
What is Vertcoin? | Lightning Network SEGWIT Enabled ASIC resistant money https://www.youtube.com/watch?v=86-oMyHDCNc
Linux instructions: https://www.cryptocurrencyfreak.com/2017/09/06/setup-vertcoin-full-node-ubuntu-16-04/

Hey guys!
I'm fairly new to this sub and to having a home lab in general and I found this community to be so kind and helping, I wanted to give back what I've learned. I'm seeing a lot of questions asked around on improvements and on what to do with x extra hardware so I thought it would be nice to have a thread to regroup that.
 
I'll put here some stuff I gathered and the most common questions I've seen, feel free to contribute and i'll update the post along.
 
Latest Additions

• oVirt -> Viurtualization
• Hurrcane Electric DNS -> Dynamic DNS
• No-IP -> DynamicDNS
• SpiceWorks -> Misc
• ERPXE -> Backup

 
Homelab Dashboard
Posts about dashboards have been growing lately and here are some of the best that were kind enough to provide us with their sources.

User	Screenshot	Source
yours truly	http://imgur.com/a/GhCNH	https://github.com/Gabisonfire/dashboard-q
lastditchefrt	http://i.imgur.com/5zQdao4.png	https://github.com/d4rk22/Network-Status-Page
_SleepingBag_	http://i.imgur.com/Ql9ZM4W.png	https://github.com/jsank/homelabdash
NiknakSi	https://niknak.org/extras/sysinfo	TBA
DainBramaged	http://imgur.com/jYNlUEQ	https://github.com/gordonturneBigBoard
michaelh4u	https://i.imgur.com/XkZwMKj.png	https://github.com/michaelh4u/homelabfrontpage
spigotx	http://imgur.com/a/1zMht	https://github.com/spigotx/HomeLab2
SirMaster	https://nicko88.com/	https://github.com/dashbad/plex-server-status
yourofl10	http://imgur.com/a/AyROa	TBA
TheBobWiley	http://imgur.com/a/oU6d3	https://github.com/TheBobWiley/ManageThis-LandingPages
0110010001100010	http://i.imgur.com/iwtQcsL.jpg	https://github.com/danodemano/monitoring-scripts
mescon & SyNiK4L	https://i.imgur.com/gqdVM6p.jpg	https://github.com/mescon/Muximux
ak_rex	http://i.imgur.com/a/RJkrT	https://github.com/ak-rex/homelab-dashboard

 
Or build yours from scratch: PRTG API, ELK, Grafana, freeboard, JumpSquares
 
Some other resources: Custom Monitoring Scripts by 0110010001100010
 
Credits to apt64 for his original post
= Pi specific =

• Pi-hole Prevents ads from even reaching you by blocking dns queries. Works as a relay between your isp's dns server (or whichever you choose). Can also work as a local dns.
• RetroPie From their website: The RetroPie Project is a collection of works that all have the overall goal to turn the Raspberry Pi into a dedicated retro-gaming console.
• raspnode Tutorials for installing cryptocurrency nodes on a Raspberry Pi. Participate in the Bitcoin, Litecoin, or Ethereum network. Full nodes, SPV wallets, cold storage, offline transaction signing.
• flightradar24 is a flight tracking service that provides you with real-time info about thousands of aircraft around the world.
• The Plane Finder is the easiest and most accurate way to share your ADS-B and MLAT data with us.
• PiAware is the world's largest flight tracking data company and provides over 10,000 aircraft operators and service companies as well as over 12,000,000 passengers with global flight tracking solutions.

 
= Download Automation =

• Torrent clients: Transmission, qBittorrent, uTorrent(sorry), Azureus, rTorrent, TransmissionQT to name a few Most torrent clients will support a "Black Hole" function where it will monitor a specific folder for .torrent files and automatically download them.
  
• CouchPotato is an wesome PVR for usenet and torrents. Just fill in what you want to see and CouchPotato will add it to your "want to watch"-list. Every day it will search through multiple NZBs & Torrents sites, looking for the best possible match. If available, it will download it using your favorite download software.
  
• SickBeard is a PVR for newsgroup users (with limited torrent support). It watches for new episodes of your favorite shows and when they are posted it downloads them, sorts and renames them, and optionally generates metadata for them.
  
• SickRage Automatic Video Library Manager for TV Shows. It watches for new episodes of your favorite shows, and when they are posted it does its magic.
  
• Sonarr is a PVR for Usenet and BitTorrent users.
  
• FlexGet is a multipurpose automation tool for content like torrents, nzbs, podcasts, comics, series, movies, etc.
  
• sabnzbd makes Usenet as simple and streamlined as possible by automating everything we can.
  
• nzbget is a binary downloader, which downloads files from Usenet based on information given in nzb-files.
  
• headphones is an automated music downloader for NZB and Torrent, written in Python. It supports SABnzbd, NZBget, Transmission, µTorrent and Blackhole.
  

 
= Virtualization =

• XenServer is an open source project and community managed by Citrix. The project develops open source software for securely running multiple operating systems and applications on a single device, enabling hardware consolidation and automation to reduce costs and simplify IT management of servers and applications.
  
• vmWare vSphere is a free bare-metal hypervisor that virtualizes servers so you can consolidate your applications on less hardware. - See more at: http://www.vmware.com/products/vsphere-hyperviso#sthash.nxaz6a9Y.dpuf
  
• Proxmox is a complete open source server virtualization management software. It is based on KVM virtualization and container-based virtualization and manages KVM virtual machines, Linux containers (LXC), storage, virtualized networks, and HA clusters.
  
• VirtualBox is a general-purpose full virtualizer for x86 hardware, targeted at server, desktop and embedded use.
  
• SmartOS is a hypervisor lean enough to run entirely in memory, powerful enough to run as much as you want to throw at it.
  
• KVM is a full virtualization solution for Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-V).
  
• oVirt is free, open-source virtualization management platform. It was founded by Red Hat as a community project on which Red Hat Enterprise Virtualization is based.
  

 
= Monitoring =

• Nagios is a powerful monitoring system that enables organizations to identify and resolve IT infrastructure problems before they affect critical business processes.
• OMD avoids the tedious work of manually compiling and integrating Nagios addons while at the same time avoiding the problems of pre-packaged installations coming with your Linux distribution
• Pandorafms is the most flexible monitoring software in the market. With a single tool, Pandora FMS can monitor everything: infrastructure, applications, services, and business progress.
• PRTG Monitoring is a network monitoring software that is powerful and easy to use. Free for 100 sensors.
• Zabbix is the ultimate enterprise-level software designed for real-time monitoring of millions of metrics collected from tens of thousands of servers, virtual machines and network devices.
• Observium is a low-maintenance auto-discovering network monitoring platform supporting a wide range of device types, platforms and operating systems.
• LibreNMS is a fully featured network monitoring system that provides a wealth of features and device support.
• Cacti is a complete network graphing solution designed to harness the power of RRDTool's data storage and graphing functionality.
• Munin surveys all your computers and remembers what it saw. It presents all the information in graphs through a web interface.
• ZenOSS is an award winning, open source monitoring product that automatically discovers resources, without the use of agents, and provides visibility across all aspects of your IT environment whether physical, virtual or in the cloud.
• AlienVault OSSIM is an open source security information and event management system. OSSIM combines Snort, OpenVAS, Nagios, OSSEC, and other tools into a single portal with log collection and correlation.
• Graylog Centralize and aggregate all your log files for 100% visibility. Use our powerful query language to search through terabytes of log data to discover and analyze important information.

 
= Media Center =

• Plex organizes your video, music, and photo collections and streams them to all of your screens.
• Kodi, if a free and open source (GPL) software media center for playing videos, music, pictures, games, and more.
• Emby brings all of your home videos, music, and photos together into one place.
• OpenMediaVault is the next generation network attached storage (NAS) solution based on Debian Linux. It contains services like SSH, (S)FTP, SMB/CIFS, DAAP media server, RSync, BitTorrent client and many more.
• PlexPy is a tool to easily monitor and receive notify playback events from Plex.
• MediaGoblin is a free software media publishing platform that anyone can run. You can think of it as a decentralized alternative to Flickr, YouTube, SoundCloud, etc.

 
= Remote access =

• Guacamole is a clientless remote desktop gateway. It supports standard protocols like VNC and RDP.
• Chrome Remote Desktop allows users to remotely access another computer through Chrome browser or a Chromebook.
• mRemoteNG is a fork of mRemote, an open source, tabbed, multi-protocol, remote connections manager. mRemoteNG adds bug fixes and new features to mRemote.

 
= VOIP =

• Elastix is an Open Source Software to establish Unified Communications. About this concept, Elastix goal is to incorporate all the communication alternatives, available at an enterprise level, into a unique solution.
• Asterisk is an open source framework for building communications applications. Asterisk turns an ordinary computer into a communications server.
• FreePBX is a web-based open source GUI (graphical user interface) that controls and manages Asterisk (PBX)

 
= Networking =

• pfSense is an open-source firewall/router computer software distribution based on FreeBSD.
• Open vSwitch is a production quality, multilayer virtual switch licensed under the open source Apache 2.0 license.
• SophosUTM Complete Unified Threat Management protection for your network, web, email, applications, and users.
• SohposXG is a fully equipped software version of the Sophos XG firewall, available at no cost for home users.
• feeloadbalancer is offering the Free LoadMaster to help small companies and developers by providing them with a robust and proven load balancing option.
• NetWorx is a simple and free, yet powerful tool that helps you objectively evaluate your bandwidth consumption situation.
• VyOS is a community fork of Vyatta, a Linux-based network operating system that provides software-based network routing, firewall, and VPN functionality.
• freeIPA is an integrated Identity and Authentication solution for Linux/UNIX networked environments.
• Metiix Blockade Network-Wide Malware, Tracking, & Ad Blocking (Can also run on Raspbian)
• OpenVPN is an open-source software application that implements virtual private network (VPN) techniques for creating secure point-to-point or site-to-site connections in routed or bridged configurations and remote access facilities. It uses a custom security protocol that utilizes SSL/TLS for key exchange.
• Smoothwall is a Free and Open Source firewall that includes its own security-hardened GNU/Linux operating system and an easy-to-use web interface.
• ClearOS is an operating system for your Server, Network, and Gateway systems. It is designed for homes, small to medium businesses, and distributed environments. ClearOS is commonly known as the Next Generation Small Business Server, while including indispensable Gateway and Networking functionality.

 
= File Servers/Storage/RAID =

• DrivePool is a disk pooling software
• DriveBender is the class leading storage pooling technology for Microsoft Windows. Developed by Division-M, Drive Bender allows for file redundancy via file duplication, and unlike RAID, does not require any proprietary drive format or complicated setup. (Now free)
• CloudExtender is local Windows storage, powered by the cloud... with optional, state of the art TNO (trust no one) file encryption built right in. Create a Windows drive or folder that maps directly to your favorite storage platform in minutes.
• SnapRAID is a backup program for disk arrays. It stores parity information of your data and it recovers from up to six disk failures.
• flexRAID is a family of storage data protection products that provide great flexibility and various innovations. The current product line includes: RAID over File System (RAID-F) Transparent RAID (tRAID).
• freeNAS is an operating system that can be installed on virtually any hardware platform to share computer data storage over a computer network.
• Rockstor is a free and open source NAS(Network Attached Storage) solution. It's a software solution and can be installed on any hardware or a virtual machine satisfying these minimum requirements.
• nas4free The NAS4Free operating system can be installed on virtually any hardware platform to share computer data storage over a computer network.
• Xpenology is the name of a Linux boot image, which allows to run operating system Sinology DSM on almost any hardware (not just Synology).
• owncloud is a self-hosted file sync and share server.
• openFiler provides a simple way to deploy and manage networked storage.
• openATTIC openATTIC combines open source storage tools in such a way that their entire functionality can be managed through a central interface. Carefully matched components ensure both stability and security. Its open interface enables you to integrate openATTIC to provisioning, monitoring and backup systems.

 
= Cameras =

• iSpy is the world’s most popular open source video surveillance application.
• ZoneMinder is intended for use in single or multi-camera video security applications.
• motioneyeOS is a Linux distribution that turns your single board computer into a video surveillance system.
• Blue Iris is security camera manager. It's not free (60$ for the full version) but it was highly recommended and there doesn't seem to be any comparable free alternatives.

 
= Documentation =

• DokuWiki is a simple to use and highly versatile Open Source wiki software that doesn't require a database.
• gollum is a simple, Git-powered wiki with a sweet API and local frontend.
• BookStack is a simple, self-hosted, easy-to-use platform for organising and storing information.
• phpIPAM is an open-source web IP address management application (IPAM).
• Paperwork aims to be an open-source, self-hosted alternative to services like Evernote ®, Microsoft OneNote ® or Google Keep ®.

 
= Dynamic DNS =

• duckdns free dynamic DNS hosted on Amazon VPC
• afraid Free DNS Hosting, Dynamic DNS Hosting, Static DNS Hosting, subdomain and domain hosting.
• No-IP's mission is to provide useful, reliable and powerful services that help home users, small and large businesses and even fortune 500 companies take control over all aspects of their DNS and domain services.
• Hurricane Electric DNS allows you to easily manage and maintain your forward and reverse DNS.

 
= Backup =

• xapi-back is a simple backup tool for XenServer or XCP – xen hypervisors using xapi toolstack. xapi-back is a command line tool with simple and clear interface (command + options). Tool is written in python.
• Veeam Endpoint Backup Free provides a simple solution for backing up Windows-based desktops and laptops.
• FOG is a free, open source computer cloning solution.
• ERPXE is a complete PXE solution featuring a broad range of recovery tools and various OS installations in one box.

 
= Creating network diagrams =

• draw.io Free online diagram creating with export/save functions!
• Gliffy Create professional-quality Flowcharts, Wireframes, UML diagrams, and more.
• rackdiag Simple diagrams for racks.
• blockdiag Simple diagrams for networks.
• RackTables is a nifty and robust solution for datacenter and server room asset management.

 
= Guides =

• IConrad's how to be a Linux sysadmin
• gex80's how to be a Windows sysadmin

 
= Misc =

• Pushover Send notifications to your mobile device using a simple curl request.
• Awesome-selfhosted Collection of self-hosted softwares
• Awesome-sysadmin Collection of system administrating tools
• Visio Cafe is an independent non-profit web site for the gathering together of IT industry Visio collections.
• Rancher is a software platform for deploying a private container service.
• GateOne is an HTML5-powered terminal emulator and SSH client
• squid is a caching proxy for the Web supporting HTTP, HTTPS, FTP, and more. It reduces bandwidth and improves response times by caching and reusing frequently-requested web pages.
• Gogs is a painless self-hosted Git service.
• LetsEncrypt is a new Certificate Authority. It’s free, automated, and open.
• Certbot Automatically enable HTTPS on your website with EFF's Certbot, deploying Let's Encrypt certificates.
• freedcamp is a social work collaboration platform with emphasis in project management. I use it to manage what I want to do on my homelab.
• SpiceWorks Multiple Free IT tools, from network monitoring to inventory.

 
That's all I could come up with on top of my head + some research, passing over to you guys so we can get a nice complete list!
 
Let's try and stick with free(or mostly) softwares, let me know if you guys feel otherwise.

I keep my bitcoin on a wallet on my Linux partition; recently, it failed to synchronize. I've tried sending a small test transaction to a wallet I have on my Windows partition; but the transaction never arrived.
Is there any way to access my bitcoin from my Windows wallet, without needing to send it over in the form of a transaction?

A lot of user asked lately, how to run Reddcoin on the popular Raspberry Pi platform. Raspberry Pi is a cheap ARM computer (using junk leftover chips with 10 year lag in technology) but it has enough RAM and consumes around 5 watts, so its ideal to use it for Reddcoin Staking.
This tutorial is not from me, i take NO RESPONSIBILITY about these binaries or the accuracy. This tutorial is created by cryptoBUZE, a fellow member of the Reddcoin community.
Before attempting to follow this tutorial, do a sudo apt-get update
The following commands must be run to install dependencies:
sudo apt-get install libboost-thread-dev
sudo apt-get install libboost-program-options-dev
sudo apt-get install libboost-filesystem-dev
sudo apt-get install libboost-system-dev
Download and install older libssl version - bitcoin clones are using this glorious and fantastic communist product of openssl so it naturally does not works. Its getting totally incompatible after each relase even with itself. Therefore, you must install this, which is the compatible one with the wallet software (no, you cant even compile the code with the newer one) :
wget http://apt.screenlyapp.com/raspbian/pool/main/o/openssl/libssl1.0.0_1.0.1t-1%2Bdeb8u6_armhf.deb
wget http://apt.screenlyapp.com/raspbian/pool/main/o/openssl/libssl-dev_1.0.1t-1%2Bdeb8u6_armhf.deb
sudo dpkg -i libssl1.0.0_1.0.1t-1+deb8u6_armhf.deb
sudo dpkg -i libssl-dev_1.0.1t-1+deb8u6_armhf.deb
Download the wallet software itself:
wget https://github.com/cryptoBUZE/reddcoin/releases/download/raspberrypi/reddcoind
wget https://github.com/cryptoBUZE/reddcoin/releases/download/raspberrypi/reddcoin-cli
wget https://github.com/cryptoBUZE/reddcoin/releases/download/raspberrypi/reddcoin-qt
chmod +x reddcoin\*
When speaking about compatibility, ARM is similar to x86 if you are running user mode applications. You know that every arm based chip needs a different kernel due to the lack of an unified IO system thankfully for the glorious clueless egoistic communist developers at ARM, who succesfully bankrupted the corporation after 25 or so years, and the company got acquired by the japanese softbank. But in user mode, its sort of backward compatible if you have all the proper libraries installed. This means that this will run on any other newer ARM based machine as well (not just raspberry pi-s, on every other arm stuff, chromebooks, or android phones hacked to work with linux).

Hi!
Happy if this guide helps you.
Tip if you want: 19656Uwdwko5RjtnuwQENpjBwE3ChzD59v
UPDATE 04/06/17
Add 'uacomment=UASF-SegWit-BIP148' into your bitcoin.conf if you want to signal UASF.
UPDATE 03/13/17
ADDED a tl;dr; Version at the end of this Post.
UPDATE 03/12/17:
Just to test it - I reinstalled all on 8GB SD and it works as well. But maybe you should use at least 16GB for the beginning.
Using a 128GB card for the first version was a little bit stupid - so I reinstalled everything on a 8GB SD card. Including Linux and a pruned blockchain - and it works.
I used prune=550 and Jessie Lite (headless / command line) - without wallet and gui.
The SD is almost full, but it works so far
I also updated the whole manual a bit to make things more clear. Thank you for all your feedback!
Just started my Bitcoin Node today and wanted to share the way I did it with people who are interested in running their own full node. It took some time to write everything down - hopefully correct so far.
I am sure, many people around bitcoin are way more informed and educated as I am - I am the noob. So I wrote this manual to help users like me - noobs, to get started with a cheap, simple bitcoin node on raspberry pi.
Have fun!
I wanted to get my Raspberry Pi 3 working as a node to support the network. Actually the process of installing and running the node was more or less easy - but for Noobs (like I am) it might be a bit tricky to start the whole thing, because there are different ways.
Did you - like me - think you would need +120GB on the raspi, external USB HDD to be a full node? You won't!
If you have a Raspberry and you know what Bitcoin is, I guess, you are a little bit aware of linux, networks and of course bitcoin - so I won't go into detail too much.
This guide is just a little helper to get a full node running on your raspberry pi. Thanks to the help of the nice people in this sub and of course the documentation by the developers, I got it working - and of course also special thanks to raspnode.com - as I followed their tutorial to start - I went some other ways here and there - so please read carefully.
For the Part 2 I would suggest to have http://raspnode.com/diyBitcoin.html open and read through my manual.
I split the tutorial in 2 Parts - PART ONE is about installing the client on your PC and downloading the Blockchain.
PART TWO is about the setup of the raspberryPi and transferring the pruned blockchain to the pi and run it as a full node!
The first thing to be aware of is: You actually need to download the whole blockchain to get this working - if you already have your bitcoin client synced on the PC / MAC great you can reuse it!
Now you might think "but you said less than 16GB in the title!"
Yes, but the good thing is you won't need to download it on your Raspberry, neither you need to sync it completely on your raspberry which took ages (weeks!) before. When you finished this Guide, you will just have a max. 4GB Blockchain on your Raspberry Pi - but it still is a full node! The magic word is Pruning.
Maybe even a 8GB SD Card works just fine including Linux (jessie lite)!
So, if you already have a full node on your PC - Great you can almost skip PART ONE - BUT have at how to Prune in PART ONE if you don't know about it.
For PART TWO you'll need a Raspberry Pi 2 or 3 (I used 3) min. 8GB (works also) or better 16GB SD Card. (I used a 128GB for the first version of this manual - which is way too big)

PART ONE

This is the manual how to get started on you PC / MAC / Linux (I did it on Win7)
Go to: https://bitcoin.org/en/download and download the core Client for your Machine (I used win64).
Install it and configure it to save the Blockchaindata to the directory of your choice - so instead getting 120GB on your C drive, I would suggest to download it to another place like a USB drive.
You can set this up during the install. Standard folder for the blockchain folder is "%APPDATA%\Bitcoin" on Windows.
or you can do it after the install by creating a bitcoin.conf file inside your installation folder / or %APPDATA%\Bitcoin and add

datadir=l:\yourfolder

to the file. Line by line.
By the way here you could also just add dbcache - to use more memory to speed up the process a bit:

dbcache=4096

if you don't want to use the settings inside the program. (you can also set this inside the program under settings! If you have this inside the bitcoin.conf you will see the amount you set there from inside the program - it overrides the values)
You can check inside the windows client under settings, if you can see a manual dbcache is set by having a look at the left footer area. When your dbcache value shows up, everything is fine.
So the Blockchain download process will take time - maybe a few days! Depending on your machine, internet connection and HDD.
The Blockchain is huge as it contains every single transaction of the past until today. You won't need to keep your PC running all the time, you can turn it off and on and it will resync automatically when you start bitcoin-qt.exe!
Make sure to close the client always via "quit" - ctrl+q.
After you have your bitcoin core installed, the blockchain downloaded and synced - you are ready to PRUNE!
First - close the Client and let it close smoothly. After it is really closed you can follow these steps:

By pruning, your blockchain will dramatically shrink. From 120GB to just a few GB.

Be aware, that you will lose your Downloaded Blockchain as pruning will erase a big chunk of it! If you have enough space, you could of course keep the full blockchain saved somewhere on another HDD.
You can prune by editing your bitcoin.conf file by adding:

prune=550

I used prune=1024 - not sure where the differences are right now (min. prune=550). (for my 8GB version I used 550! I suggest to use this.)
Save the bitcoind.conf file and restart your windows client.
It will now clean up the Blockchain. So just the latest blocks are saved. The client should start without any problems. Maybe it takes some time to prune the blockchain data.
Check if everything works normally (the client opens as usual, you can see an empty wallet) than close the client.
Inside the Bitcoin Folder, you'll find two folders called:

blocks chainstate

those are the interesting folders containing the important data (now pruned) - and we will transfer those two to the raspberry later!
Now you are good to start the raspi transfer explained in the next part.

PART 2

Here is what I did:
1) I installed Raspian Pixel (https://www.raspberrypi.org/downloads/raspbian/) using a 128 GB SD - which is not needed because of "Pruning" - I think a 16GB card might work, too! (You can also install Raspian Jessie Lite - which saves you even more space, as it runs headless - only command line) (Updated: It is better to use Jessie Lite to save a lot of space - when you are fine with only command line)
2) I followed partly this tutorial to get everything running and setup:

http://raspnode.com/diyBitcoin.html

Please have a look at it - I have copied the Headlines in capitals to let you know what I did, and what I skipped.
On Tutorial Page: Start with RASPBIAN (OPTIONAL) CONFIG OPTIONS.
Set You RasPi up including "EDITING FILES" to save your Layout at the tutorial page and come back here.
I skipped the CONFIGURE USB AND SET AUTOMOUNT process, as we are going to use PRUNING to reduce the 120GB to a tiny filesize - so USB Devices are not needed here!
It was necessary to ENLARGE SWAP FILE to install bitcoin core - otherwise it didn't went through which ended in a frozen raspi.
So have a close look by following the raspnode tutorial at: ENLARGE SWAP FILE.
I have my raspi running via cable to router - but you can also WiFi setup everything described under NETWORKING ON THE RASPBERRY PI.
Now comes the interesting part: Follow the steps at DOWNLOADING BITCOIN CORE DEPENDENCIES - they work fine for 0.14.0 too. Git should be on Board already when you installed Pixel - otherwise you would need to install it.

sudo apt-get install git -y (only jessy lite)

I skipped the next command lines - as I don't use bitcoin-qt wallet. If you want to use it as wallet - do the step.

mkdir ~/bin cd ~bin

Now you are in the folder you want your bitcoin core data be downloaded to via git. I didn't Downloaded the Berkeley Database source code - so I also skipped the whole next command lines
[email protected]~/bin$ wget http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz [email protected]~/bin$ tar -xzvf db-4.8.30.NC.tar.gz [email protected]~/bin$ cd db-4.8.30.NC/build_unix/ [email protected]~/bin/db-4.8.30.NC/build_unix$ ../dist/configure --enable-cxx [email protected]~/bin/db-4.8.30.NC/build_unix$ make -j4
and went on with "INSTALLING BITCOIN"!
I followed the first part but instead downloading 0.13 I took of course the latest version:0.14

git clone -b 0.14 https://github.com/bitcoin/bitcoin.git cd bitcoin ./autogen.sh

this might take some time to start.
If you have trouble with hanging RESOLVING DELTAS - just restart the Raspberry Pi and remove the bitcoin folder inside /~bin using

rm -rf bitcoin

this command will delete the folder and you can reuse

git clone -b 0.14 https://github.com/bitcoin/bitcoin.git

For some reason RESOLVING DELTAS is a common problem with different downloads - so just retry it and at least after 3 times it should work!

as I didn't use the GUI/ Wallet, I ran

./configure --enable-upnp-default --disable-wallet

as I don't need the wallet functionality.
I didn't need to use "MAKE" which saves you maybe up to 2.5 hours.
instead you can just go ahead with:

sudo make install

(If I am wrong in doing so - please let me know)
The install takes some time - and just a heads up: when it gets stuck somewhere - just redo the installation process - it took three times to went through - stuck at some processing.
After the installation took place you can finally get your Raspberry Pi Node running in no time!
To test if the the installation went through - you can just start bitcoind using:

bitcoind &

than check if everything is working so far:

bitcoin-cli getinfo

after a few seconds you should see version: etc...
if not, something went wrong. Try to redo the steps in the raspnode tutorial.
(don't give up if it failed - retry! Ask your questions here)
IMPORTANT: you need to stop bitcoin on your raspberry now!

bitcoin-cli stop

If you don't need an external USB Drive - what I hope - as we are going to use pruning just go ahead and skip the USB part and create a file inside (or follow the raspnode tutorial on how to setup the USB drive):

cd .bitcoin
sudo nano bitcoin.conf

and enter the exact same pruning size you have used on your Desktop Machine to prune. I used 1024 but the minimum is 550. (used 550 for the 8GB SD card on PC and Raspberry)

prune=550

That's it for the raspi.
update: To signal UASF enter in a new line:

uacomment=UASF-SegWit-BIP148

TRANSFER

Now you have to transfer the two folders CHAINSTATE and BLOCKS from your PC bitcoind directory to your raspberry.
I am using a program called "WINSCP" - it is free and easy to use: https://winscp.net/eng/download.php
We need this to transfer the files to the Raspberry pi. Pretty sure you can also do it via SSH - but I am the noob. So let's keep it simple.
Open Winscp and put in the IP Address of your Raspberry Pi, User and Password (same as in SSH)
You should now see the directories on your Raspberry Pi. There is a folder called

.bitcoin

enter it and you will see the two folders

blocks & chainstate

you can delete them on the raspberry as they have some data from your previous test inside.
Make sure you can also see the bitcoin.conf file in that directory, which needs to contain the exact same prune line, like the one on your desktop machine. If not, make sure to edit it via SSH. The line "datadir=l:\yourfolder" is obviously not needed in the Raspberry bitcoin.conf file.
Now grab the two folders CHAINSTATE and BLOCKS from your PC and copy them to your .bitcoind folder.
I also copied banlist.dat, fee_estimation.dat, mempool.dat and peers.dat to the folder - not really knowing if needed! Not needed.
The whole copy process might take some minutes (against some weeks in the old way).
After copying is finished, you can now start bitcoind on the Raspberry.

bitcoind &

the & symbol let you still use the command line while the process is running btw.
The process - if succesfull - will take some time to finish.

bitcoin-cli getinfo

Will give you some informations what is going on right now. When you can see, that it is checking the blocks, this is good!
If you get an error - double check - if you have the correct prune size (same as on desktop machine) - in bitcoin.conf and that this file is inside .bitcoin on RaspberryPi. It took me some time, to find my mistakes.
Congrats! You are almost a part of the network!
To make your node now a fullnode, you will need to go to your router (often 192.168.1.1) and enable portforwarding for your raspberry pi - and open ports 8333 - that's it!
You can now go to: https://bitnodes.21.co/nodes/
scroll down to "JOIN THE NETWORK" and check check if your node IP is connected!
It will show up as soon as the blocks are checked and the raspi is running.
Well done!
Now you are running a full node, with a small Blockchain and got it working in Minutes, not weeks!
I really hope, my little tutorial worked for you and your are part of the Node network now.
If you have problems or I made a mistake in this helper tut, just let me know and I will try to make it better.
Have fun and NODL!
the noob
tl;dr; (if you are a real noob start with the non-tl;dr version!)
tl;dr; PART ONE
1) Download & install / setup bitcoincore @ https://bitcoin.org/de/download
2) change dbcache to something smaller than your memory and download the whole Blockchain (120GB).
3) create a file called bitcoin.conf put the line prune=550 (or higher) in to activate pruning on win inside %appData%/bitcoin
4) Open ports 8333 on your Router to make this a full node with a smaller Blockchain.
You are running a full node on your PC.
tl;dr; PART TWO
1) Install jessie lite and the needed dependencies on your SDCard - Raspberry
( >git clone -b 0.14 https://github.com/bitcoin/bitcoin.git )

• see tutorial for more info.

2) create a file called bitcoin.conf inside .bitcoin and add the same prune=Number you had on your PC.
3) transfer the pruned folders BLOCKS and CHAINSTATE to the Raspberry Folder .bitcoin
4)Start "bitcoind &"
5) let everything sync
6) Make sure you have port 8333 opened on your router.
You are running a full node on your Raspberry with a super small Blockchain (I put all on a 8GB SDcard)
Tip if you want : 19656Uwdwko5RjtnuwQENpjBwE3ChzD59v
updated 03/12 - will update more, soon.
updated 03/12.2 - I updated the whole process a bit and also added some improvements.
updated 03/14/ Added a tl;dr version at the end.

Intro

This thread is an update to my first Reddcoin staking tutorial that was written 7 months ago.
 
The reason for the update
My Reddcoin Core software crashed and became unusable. My Raspberry Pi 3B would lag and freeze, I couldn't stake anymore.
 
Instead of just redoing everything the same way, I wanted to see if I could improve on 3 points:

• Use an OS that was lighter
• Update the Reddcoin Core software (2.0.0.0 => 2.0.1.2)
• Make improvements to the configuration.

 
The updates

• OS: using Lubuntu instead of Ubuntu MATE. Lubuntu uses less resources (130 MB RAM vs. 190 MB RAM on initial boot).  
• Reddcoin Core: v2.0.1.2-a8767ba-beta instead of v2.0.0.0-92768f9-beta.  
• Swap: using a swap partiton instead of a swap file. Also adjusting the swap size: from 1 GB to 2 GB, after reading the comments to my previous tutorial.  
• All data to USB: Blockchain data and the swap are now stored on the USB drive, instead of the SD card.  
• Private keys: added instructions on how to backup the private keys of your Reddcoin addresses!

 
If you would like to tip me
Writing a tutorial like this takes time and effort; tips are appreciated. My Reddcoin address: RqvdnNX5MTam855Y2Vudv7yVgtXdcYaQAW.
     

Overview

• Hardware: Raspberry Pi 3 Model B.  
• OS: Lubuntu 16.04.2 (Xenial).  
• Storage space: I am using an 8 GB microSD card for the OS, and a 128 GB USB drive for data. Minimums I would recommend: 8GB SD card and 32 GB USB drive.  
• Reddcoin Core client version: v2.0.1.2-a8767ba-beta (most recent version at this moment). ↳ Screenshot

 

Steps

• You need the OS; Lubuntu. Download Lubuntu (707 MB) for the Raspberry Pi: https://ubuntu-pi-flavour-maker.org/download/. It's a .torrent download, so you will need a BitTorrent client. Message me or post in this thread if you need help with this.
   
  You can also use my personal mirror and download with your browser: https://zargon.stackstorage.com/s/6464PUYBHWGCxhB.
  

 

• You need software to write the OS to the SD card. I use Etcher. Download Etcher: https://etcher.io/.
  
  • Run Etcher.  
  • Select image: select the lubuntu-16.04.2-desktop-armhf-raspberry-pi.img.xz file.  
  • Select drive: select your microSD card.  
  • Flash.

 

• Plug the SD card into your Raspberry Pi and power it up.
  
  • Lubuntu should boot up.  
  • Set up Lubuntu, connect to the internet (wired or wireless). ↳ As username, I chose "rpi3b". You will see this username throughout this whole tutorial.  
  • Make sure date and time are correct ([Menu] > System Tools > Time and Date). ↳ Click on Unlock to make changes. I personally change Configuration to "Keep synchronized with Internet servers". ↳ Screenshot  
  • Reboot ([Menu] > Logout > Reboot). I am connected to wifi, but have issues getting wifi to work on initial boot. A reboot solves this issue.

 

• Make sure system is up-to-date, install never versions.
  
  • Open LXTerminal ([Menu] > System Tools > LXTerminal). ↳ Screenshot  
  • Enter the following in LXTerminal: sudo apt update && sudo apt upgrade ↳ Screenshot  
  • You will be asked if you really want to continue. Enter Y (yes).  
  • Updates are being installed! Wait until it's finished.  

 

• Install programs that will be used in this tutorial.
  
  • GParted: to partition the USB drive.
  • Htop: to see the amount of memory (RAM) and swap that is in use.  
  • Enter the following in LXTerminal to install these 2 programs. sudo apt install gparted && sudo apt install htop ↳ Screenshot  

 

• Create 2 partitions on the USB drive: 1) Swap partition 2) data partition (for the Reddcoin blockchain)   The swap partition is necessary: The Reddcoin wallet can be memory intensive. To prevent any crashes or freezes, add 2 GB of 'virtual' memory by creating a swap partition.  
  
  • Important: Backup your USB drive if needed. The USB drive will be formatted, so the data on the USB drive will be wiped.
  • Please use the USB drive solely for this purpose, do not combine it with other stuff.
  • Keep your USB drive plugged in, do not (randomly) plug it out.  
  • Plug your USB drive in.  
  • GParted will be used to create the partititons. Start GParted via LXTerminal: sudo gparted ↳ Screenshot  
  • In GParted, switch from your SD card (default) to your USB drive. ↳ Screenshot ↳ Screenshot  
  • You will now see the all the partition on USB drive. Delete every partition (right mouse click). If you can't select Delete, do an Unmount first. ↳ Screenshot ↳ Screenshot  
  • After deleting all partition, you will only see 'unallocated' space on your USB drive. ↳ Screenshot  
  • Create the first partition: the swap partition. Right click on the blank space, select New and enter the following:
    • New size (MiB): 2048
    • File System: linux-swap
    • Click on Add. ↳ Screenshot  
  • Create the second partition: the data (blockchain) partition. Richt click, select New and enter:
    • File system: ext4
    • Label: usb
    • Click on Add. ↳ Screenshot  
  • Apply the changes. Click on the check mark or select Edit > Apply All Operations. ↳ Screenshot ↳ Screenshot  
  • Important: The name of the swap partition is needed later, so please write it down. Mine is /dev/sda1 (first partition on first drive (drive 'a')). ↳ Screenshot  
  • Reboot. After the reboot, the data partition you just created should be visible on your desktop. ↳ Screenshot  

 

• The swap partition is created, so now we can enable and use it.
  
  • The swap in use can be monitored with the program Htop. Open Htop ([Menu] > System Tools > Htop) to see the 'Swp' (swap) in use. ↳ Screenshot   By default, swap is not used, so 0K. ↳ Screenshot   You can leave Htop open.  
  • To enable the swap partition, open LXTerminal and enter the following commands: (Assuming /dev/sda1 is your swap partition.)  
    • sudo mkswap /dev/sda1 ↳ Screenshot ↳ Screenshot  
    • sudo swapon /dev/sda1 ↳ Screenshot  
  • You've enabled the swap partition. Switch back to Htop and check the 'Swp' (swap) value. It should read '2.0G'. ↳ Screenshot  

 

• To make sure the swap file is persistent (so it survives a reboot), you have to add a line to the /etc/fstab file.
  
  • In LXTerminal, enter the following command to open the file in Leafpad (text editor): sudo leafpad /etc/fstab ↳ Screenshot  
  • In Leafpad, add this text in a new line: /dev/sda1 swap swap defaults 0 0 ↳ Screenshot (I've added spaces to vertically align the text.)  
  • Save and close the file.  
  • Reboot your Pi.  
  • To see if the swap partition is in use after a reboot, open Htop ([Menu] > System Tools > htop) and check the 'Swp' (swap) value. It should read '2.0G'. ↳ Screenshot  

 

• So, the swap partition is enabled and in use, and the data partition is prepared. We now can install the necessary software for the Reddcoin wallet; enter the following commands into LXTerminal:
  
  • sudo apt-get update && sudo apt-get install git build-essential libqt4-dev libprotobuf-dev protobuf-compiler libtool autotools-dev autoconf libssl-dev libboost-all-dev wget pkg-config ↳ Screenshot  
  • sudo add-apt-repository ppa:bitcoin/bitcoin ↳ Screenshot  
    • Press Enter to confirm. ↳ Screenshot ↳ Screenshot  
  • sudo apt-get update  
  • sudo apt-get install db4.8 ↳ Screenshot ↳ Screenshot  
  • sudo apt-get install libminiupnpc-dev ↳ Screenshot  
  • sudo apt-get install libqrencode-dev ↳ Screenshot  
  • Reboot your Raspberry Pi.  

 

• After the reboot, open LXTerminal again. Download, unpack, configure, build and install Berkeley DB.
  
  • Set the working directory to your USB drive: cd /media/rpi3b/usb (rpi3b is the username I chose; if you have a different username, change it to yours.) ↳ Screenshot  
  • sudo wget http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz ↳ Screenshot ↳ Screenshot  
  • sudo tar xfvz db-4.8.30.NC.tar.gz ↳ Screenshot  
  • cd db-4.8.30.NC  
  • cd build_unix  
  • sudo ../dist/configure --enable-cxx  
  • sudo make This took about 10 minutes for me.  
  • sudo make install  

 

• Set BerkeleyDB variables (in LXTerminal):
  
  • export CPATH="/uslocal/BerkeleyDB.4.8/include" ↳ Screenshot  
  • export LIBRARY_PATH="/uslocal/BerkeleyDB.4.8/lib" ↳ Screenshot  
  • sudo leafpad /etc/ld.so.conf.d/daemon-libs.conf ↳ Screenshot  
  • Add this line in Leadpad: /uslocal/BerkeleyDB.4.8/lib/ ↳ Screenshot  
  • Save and close the file.  
  • Back in LXTerminal: sudo ldconfig ↳ Screenshot  

 

• Download the source of the Reddcoin wallet and build it.
  
  • Set the working directory to your USB drive: cd /media/rpi3b/usb (rpi3b is the username I chose; if you have a different username, change it to yours.)  
  • Download Reddcoin Core source files: sudo wget https://github.com/reddcoin-project/reddcoin/archive/arm_support_v2.zip ↳ Screenshot ↳ Screenshot  
  • Unzip the file: sudo unzip arm_support_v2.zip ↳ Screenshot  
  • rename the folder from ''unzip arm_support_v2'' to ''reddcoin'' (easier to use when needed) sudo mv reddcoin-arm_support_v2/ reddcoin/ ↳ Screenshot  
  • cd reddcoin ↳ Screenshot  
  • sudo ./autogen.sh ↳ Screenshot  
  • sudo ./configure --disable-tests --enable-sse2=no ↳ Screenshot  
  • sudo make ↳ Screenshot ↳ Screenshot ↳ Screenshot (This will take some time; with me it took just over 1 hour.)  
  • sudo make install ↳ Screenshot ↳ Screenshot  

 

• Speed up synchronizing with the Reddcoin blockchain by bootstrapping.
  
  • Set the working directory to your USB drive: cd /media/rpi3b/usb (rpi3b is the username I chose; if you have a different username, change it to yours.)  
  • Download the bootstrap file (1.45 GB): sudo wget https://github.com/reddcoin-project/reddcoin/releases/download/v2.0.1.2/bootstrap.dat.xz ↳ Screenshot ↳ Screenshot  
  • Unpack the file (large file, takes around 15 minutes to unpack): sudo xz -d bootstrap.dat.xz ↳ Screenshot  
  • After a successful unpack, your will find the file bootstrap.dat in your USB root folder. ↳ Screenshot  

 

• On the first run of the Reddcoin Core client, it will ask for a data directory to store the blockchain and wallet data.
  
  • Start the Reddcoin Core client: sudo /media/rpi3b/usb/reddcoin/src/qt/reddcoin-qt ↳ Screenshot  
  • The welcome screen will appear and ask you about the data directory. I suggest a new folder on your USB drive, I picked blockchain. The directory will be created with all the necessary files. ↳ Screenshot  
    • Select Use a custom data directory. ↳ Screenshot  
    • Click on the three dots (...) on the right. ↳ Screenshot  
    • Click on Create Folder at the upper right corner. Type and enter in the folder name. (In my case: blockchain.) Click on Open. ↳ Screenshot ↳ Screenshot ↳ Screenshot    
  • After selecting the directory, the Reddcoin Core client will start. Wait till it's fully loaded and close it.  

 

• Move the bootstrap.dat file to your data directory you selected in the previous step. By doing this, Reddcoin Core will use the bootstrap.dat file to import the blockchain, which speeds up syncing. sudo mv bootstrap.dat /media/rpi3b/usb/blockchain/ (Assuming blockchain as data directory.) ↳ Screenshot

 

• The Reddcoin Core client set up is completed, but you still have to sync fully with the blockchain before you can send, receive and stake.
  
  • Launch the Reddcoin Core client again: sudo /media/rpi3b/usb/reddcoin/src/qt/reddcoin-qt ↳ Screenshot ↳ Screenshot  
  • Keep the client running until it's fully synchronized. It will use the bootstrap file first, and download the rest of the blockchain to complete the sync. This can take some time (it took 2 days for me). Syncing the blockchain uses a lot of resources, so the software may react slow.  
  • You can see the progress in the debug window (Help > Debug window). ↳ Screenshot  
  • When the synchronization is completed, the red (out of sync) will disappear on the Overview screen! ↳ Screenshot  

 

• When synchronization is complete, you can start staking your Reddcoins.
  
  • For staking, your wallet needs to be encrypted: Settings > Encrypt... Do not forget your password! ↳ Screenshot ↳ Screenshot ↳ Screenshot ↳ Screenshot ↳ Screenshot  
    • Your wallet will be encrypted, and the Reddcoin Core client will be closed. Launch the Reddcore Client again. sudo /media/usb/reddcoin/src/qt/reddcoin-qt  
  • To start stake, you need to unlock your wallet (by entering your password).
    • Settings > Unlock Wallet... ↳ Screenshot  
    • Make sure "For staking only" is checked before clicking OK. ↳ Screenshot  
  • You can only stake with Reddcoins that have matured: coins have to be at least 8 hours in your wallet to mature.  
  • The grey arrow at the bottom should be green when staking. Hover over that icon to see the progress of staking. ↳ Screenshot  

     

Video

https://www.youtube.com/watch?v=Snr5e8bzftI
This video shows how long it takes to start Reddcoin Core.   TL;DR:

• [01:11] Reddcoin Core started (sudo password entered).
• [01:13] Message shown on screen: Loading block index...
• [10:14] Message shown on screen: Verifying blocks...
• [10:18] Message shown on screen: Loading wallet...
• [12:49] Message shown on screen: Done loading
• [13:13] Reddcoin Core ready to use.

     

Extra

Backup
Backup your wallet to prevent losing the RDDs in your wallet! There are two methods to backup, do both. Make new backups if you create a new receiving address!
 

• Method 1: Backup your wallet.dat. Open Reddcoin Core. Use the menu to backup: File > Backup Wallet... ↳ Screenshot

 

• Method 2: Backup your private keys. In case you lose your wallet.dat backup, you still can import your private keys later when needed.  
  
  • To extract your private keys:
    • If you have a passphrase on your wallet, unlock your wallet first. Settings -> Unlock Wallet... (make sure 'For staking only' is not checked) ↳ Screenshot ↳ Screenshot  
    • Extract your private keys. Debug window -> Console -> dumpprivkey ↳ Screenshot  
    • You can write down your private key or copy and save it in a document. Make sure you save it somewhere only you can access it.    
  • To import later: Debug window -> Console -> importprivkey [label] [label] is optional. ↳ Screenshot (without a label) ↳ Screenshot (with a label)

   
Boot with only 1 USB drive plugged in:
Make sure only the USB drive (with the swap partition and data partition) is plugged in when you boot up your Raspberry Pi. This to make sure the swap partition (/dev/sda1) is recognized correctly.   If you boot up with multiple USB drives, Lubuntu might see the USB drive with the swap partition as the second drive (instead of the first drive), and ignore the 2 GB swap partition. If this happens, starting Reddcoin can render the Raspberry Pi unresponsive.
   
Connection issues If you have issues syncing the blockchain because you have 0 network connections, please follow the instructions in this thread.
   
Start Reddcoin Core easier
Run a shell script (.sh file), so you can start Reddcoin just by double clicking on an icon on your Desktop.

• Right Click on your Desktop and select Create New -> Empty File. ↳ Screenshot  
  
• Enter a file name, make sure it ends with .sh, and click on OK. I've chosen for Reddcoin.sh. ↳ Screenshot   The file will be created on your Desktop. ↳ Screenshot  
  
• Add the command to start Reddcoin to the file.
  
  • Right click on the file, select Leafpad (to open the file in a text editor). ↳ Screenshot  
  • Add the following to the file and save the file: sudo /media/rpi3b/usb/reddcoin/src/qt/reddcoin-qt ↳ Screenshot  
• To be able to execute the shell script (.sh), it has to have 'execute permissions'.
  
  • Right click on the file, and select Properties. ↳ Screenshot  
  • Click on the Permissions tab.  
  • For Execute, select Anyone, and click on OK. ↳ Screenshot  
• To start Reddcoin Core, double click on the file. A new window will pop-up, asking you what you want. Execute in Terminal is what we want, so you can click on enter. ↳ Screenshot   Reddcoin Core will now start. Do not close the Terminal window, you can minimize it if needed.
  

   
Minimization options
Adjust minimization options, so you can safely press on the X button (the close/exit button on the upper right corner).

• Activate 'Minimize on close'. Settings -> Options... -> Window (tab) -> Minimize on close. ↳ Screenshot   Reddcoin will still run when you click on the X button.   To close/exit Reddcoin, right click on the Reddcoin icon in the system tray (bottom right corner). ↳ Screenshot

   
RealVNC VNC Viewer (client) and VNC Connect (server): To remote connect to the Raspberry Pi, I use VNC Viewer ad VNC Connect from RealVNC.

• On your Raspberry Pi:
  
  • Download VNC Connect from the RealVNC website: https://www.realvnc.com/en/connect/download/vnc/raspberrypi/.  
  • After your download is finished, open the file and click Install Package. ↳ Screenshot  
  • To run the VNC Connect once:
    
    • Open [Menu] > Run, and enter: vncserver-x11 ↳ Screenshot  
  • To auto run on startup:
    
    • Open Default applications for LXSession ([Menu] > Preferences > Default applications for LXSession). ↳ Screenshot  
    • In LXSessions configuration, select Autostart in the menu left.  
    • Under Manual autostarted applications, enter vncserver-x11 and click on + Add. ↳ Screenshot ↳ Screenshot  
    • Reboot your Raspberry Pi and check if VNC Connect is started automatically after the reboot.  
  • When VNC Connect is running, you'll see a VNC icon on the right bottom corner. Double click the icon to open VNC Connect and to see the IP address you need to enter to connect to your Raspberry Pi. ↳ Screenshot
    

 

• On your computer:
  
  • Download and install VNC Viewer https://www.realvnc.com/en/connect/download/viewe.
  • Connect to he IP address of your Raspberry Pi.

   
Chromium as browser: The updates break Firefox, the browser crashes when you try to run it. Install another browser, Chromium, to solve this issue.

• In LXTerminal, enter: sudo apt install chromium-browser ↳ Screenshot  
  
• You can run Chromium via [Menu] > Internet -> Chromium Web Browser ↳ Screenshot
  

   
Updates / Upgrades
If Software Updater shows up and tells you that there is updated software available, do not install the updates using Software Updater. Use LXTerminal to update Lubuntu.  

• Open LXTerminal and enter this command to update: sudo apt update && sudo apt upgrade ↳ Screenshot

     

Credits:

• cryptoBUZE on reddit.com; for getting the official arm_support_v2.zip to work.
  
• worstkaas on reddit.com; for his suggestion of using 2 GB instead of 1 GB for the swap space.
  

   
Credits in previous tutorial:

• My main source: damsal01 on reddcointalk.org. His RDD address for donation: Rqd8xDv6oV9BYFaVrLdkWcR5JU6sPPZTKs.
  
• hieplenet on reddit.com. His RDD address for donation: RaF3TeWqgTzAdnaZQffnsxS74dag13zsAY.
  
• joroob on Github.com. He made some adjustments to the reddcoin wallet source code so it will compile on ARM cpus. His RDD address for donation: Rb8754QZvpbw6DjrMV1qX9SnHzYnSyXRMC.