bitcoin/build-windows.md at master · bitcoin/bitcoin · GitHub

PSA: Enable Tor as a simple way to make your node reachable.

Become one of the 10% of node operators that receive incoming connections.
Installing bitcoin core is easy, and with pruning it really isn't the space sink it is characterized as. Even a modest computer can complete the initial block download (IBD) and become a full node. But what some users (90%) find a bit more challenging, is how to become a listening node. Listening nodes are an important part of the network, and are simple enough to enable. I can think of 4 ways to do it:
  1. Operate on an OS and Network that support uPnP, allowing bitcoin to open the ports for you.
  2. Subscribe to a VPN that allows you to open ports through their service.
  3. Manually configure your OS and network to forward port 8333 and 18333.
  4. Run Tor and direct bitcoin to listen through it.
I'll discuss #4. Obviously #1 or #2 are easier, but require a VPN subscription or uPnP enabled HW. And if you live in a dorm or don't control the network, Tor may be the only free option available.
As a bit of background, bitcoin supports three networks that your node can listen on:
Obviously, the more you enable, the better, but here are the basic steps for Tor in broad strokes. If you have any questions post them here and I'll see if we can't help you out:
  1. Download, verify1 and install Gpg4win
  2. Download, verify2, install, and launch Tor Browser
  3. Download, verify3, install, and launch Bitcoin Core
  4. Launch and Admin command console in the directory containing tor.exe
  5. Install the Tor service: tor.exe --service install
  6. CD to service dir: cd %windir%\ServiceProfiles\LocalService\AppData\Roaming\tor
  7. Create and edit a file called torrc with the contents suggested below
  8. Restart tor: tor.exe --service stop && tor.exe --service start
  9. Record the hostname: type .\HiddenService\hostname as
  10. Add the bitcoin.conf options suggested below
  11. Restart the bitcoin-qt program
  12. (Optional) Activate the bitnodes crawler at https://bitnodes.io/nodes/-8333/
It may take a while for your node to show up on bitnodes. I've found the check button sometimes has trouble with onions. Of course you don't need to do it, but it can provide a simple way to check status once your on the list.

torrc file: (replace c:\windows with the proper path as needed)

```

Change to C:\Windows\ServiceProfiles\LocalService\AppData\Roaming

Log notice file \tor\service.log

Bridges may be needed if the Gov't shuts down Tor exit nodes. Get Bridges by

emailing [email protected] from Gmail (only) and uncomment as follows:

Bridge obfs4 : cert= iat-mode=

HiddenServiceDir \tor\HiddenService HiddenServiceVersion 2 HiddenServicePort 8333 127.0.0.1:8333 HiddenServicePort 18333 127.0.0.1:18333 ```

bitcoin.conf file: (entries to be ADDED)

```

Change to what you recorded earlier

onion=127.0.0.1:9050 listen=1 externalip= discover=1 ```
Footnotes:
  • 1 Cert: {Subject: Intevation GmbH; SHA1: c13a65963ad53e78694dd223d518007791a05fe4}
  • 2 PGP Signing Key: 0xEF6E286DDA85EA2A4BA7DE684E2C6E8793298290
  • 3 PGP Signing Key: 0x01EA5486DE18A882D4C2684590C8019E36C2E964
submitted by brianddk to Bitcoin [link] [comments]

Windows / Linux Guide to using Trezor with Bitcoin Core (HWI)

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 1
  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 1
  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
  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 3

( 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) 3
  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
submitted by brianddk to Bitcoin [link] [comments]

Windows Guide to using Trezor with Bitcoin Core (HWI)

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 TLDR is here

( 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 1
  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
  3. CD to working folder cd "C:\User\Reddit\src\HWI"
  4. Enter venv source .venv/Scripts/activate 1
  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
  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 3

( 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) 3
  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
submitted by brianddk to TREZOR [link] [comments]

Bitcoin Tor

Subject: PSA: Make your node reachable by using Tor
There is usually a post every few months with someone asking for tips on how to make their node reachable. It's always a hard question to answer since its impossible to know what type of routers and firewalls they are going to have to punch through. This is especially difficult in college dorms. One cheap (and easy) way around it is to to just jump through a few extra steps to make your bitcoin node a bitcoin onion node. Tor is great about traversing routers and firewalls like a hot knife through butter.
  1. Download, verify1, install and initialize Gpg4win
  2. Download, verify2, install, and launch Tor Browser
  3. Download, verify3, install, and launch Bitcoin Core
  4. Launch an Admin command console in the directory with tor.exe
  5. Install the Tor service: tor.exe --service install
  6. CD to service dir: cd %windir%\ServiceProfiles\LocalService\AppData\Roaming\tor
  7. Create and edit a file called torrc with the contents suggested below
  8. Restart tor: tor --service stop && tor --service start
  9. Record your onion hostname: type .\HiddenService\hostname as
  10. Add the bitcoin.conf options suggested below
  11. Restart the bitcoin-qt program
  12. Verify node connectivity at https://bitnodes.io/nodes/-8333/

torrc file: (replace c:\windows with the proper path as needed)

```

Change to C:\Windows\ServiceProfiles\LocalService\AppData\Roaming

Log notice file \tor\service.log HiddenServiceDir \tor\HiddenService HiddenServiceVersion 2 HiddenServicePort 8333 127.0.0.1:8333 HiddenServicePort 18333 127.0.0.1:18333 ```

bitcoin.conf file: (entries to be ADDED)

```

Change to what you recorded earlier

onion=127.0.0.1:9050 listen=1 externalip= discover=1 ```
Footnotes:
  • 1 - Cert-Subject: "Intevation GmbH"  ;  Cert-SHA1: c13a65963ad53e78694dd223d518007791a05fe4
  • 2 - PGP Signing Key: 0xEF6E286DDA85EA2A4BA7DE684E2C6E8793298290
  • 3 - PGP Signing Key: 0x01EA5486DE18A882D4C2684590C8019E36C2E964
submitted by brianddk to brianddk [link] [comments]

#Reddcoin ($RDD) Core Wallet Release 3.0.1 - PosV v2 SuperMajority Consensus Upgrade at 45.6% - Required Upgrade

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
submitted by TechAdept to reddCoin [link] [comments]

Groestlcoin 6th Anniversary Release

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.

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

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

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

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

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

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

Remastered Improvements

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

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

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

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

Download

Source

UPDATED – P2Pool Test Net

Changes

Download

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

Source

submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

cold storage compatibility issues

Hello, I have been a fan of electrum because of its offline capability. I like that I can use Bitcoin while storing my private keys on a computer that has the wifi card removed and hot glue stuffed in the Ethernet port. However it looks like maybe the electrum developers have over-promised and under-delivered in this regard. Or, maybe they simply do not have the time, energy, resources to make this work in real life.
Let me explain. I have an old-ass computer that is running Ubuntu 12 (precise), this computer has electrum 2.5.4 installed with a cold-storage wallet that has my private key.
I want to send some bitcoin from that address to a new wallet on my desktop so I can spend the bitcoin. So I installed electrum (newest version 3.3.8) on my desktop, imported the bitcoin address, and created a transaction. Then I sent the transaction to the offline computer out of band, and verified that the out-of-band transmission worked by comparing the hash of the txn file on both the offline and online machines. Then I tried to open the txn file on the offline machine with Electrum 2.5.4. Well, guess what, it didn't work. Electrum 2.5.4 printed to the console:
Traceback (most recent call last):
File "/uslocal/lib/python2.7/dist-packages/Electrum-2.5.4-py2.7.egg/electrum_gui/qt/main_window.py", line 2261, in do_process_from_file
self.show_transaction(tx)
File "/uslocal/lib/python2.7/dist-packages/Electrum-2.5.4-py2.7.egg/electrum_gui/qt/main_window.py", line 577, in show_transaction
show_transaction(tx, self, tx_desc)
File "/uslocal/lib/python2.7/dist-packages/Electrum-2.5.4-py2.7.egg/electrum_gui/qt/transaction_dialog.py", line 37, in show_transaction
d = TxDialog(tx, parent, desc, prompt_if_unsaved)
File "/uslocal/lib/python2.7/dist-packages/Electrum-2.5.4-py2.7.egg/electrum_gui/qt/transaction_dialog.py", line 48, in __init__
self.tx.deserialize()
File "/uslocal/lib/python2.7/dist-packages/Electrum-2.5.4-py2.7.egg/electrum/transaction.py", line 523, in deserialize
d = deserialize(self.raw)
File "/uslocal/lib/python2.7/dist-packages/Electrum-2.5.4-py2.7.egg/electrum/transaction.py", line 454, in deserialize
d[inputs] = list(parse_input(vds) for i in xrange(n_vin))
OverflowError: Python int too large to convert to C long
That's pretty frustrating, the first thing I tried was to install Electrum 2.5.4 on my Desktop and try to create a new unsigned transaction with Electrum 2.5.4. However, this is a no-go because old versions of Electrum cannot connect to Electrum servers any more. So I have to try to update the Electrum on the Offline computer. But I'm not even sure if this is possible considering how ubuntu 12 it's definitely out of support at this point and the offline computer does not even have python3 installed, let alone the GTK stuff or whatever is probably required to run Electrum.
I'm starting to regret choosing a GUI-based wallet for my offline storage considering how hard it is to actually use this and how it simply melts over time... even just 5 years is is enough time to completely melt and destroy this software and make it un-usable. Time Catches All. So now I have to go out and buy a new computer that can run the updated OS, so I can install the new version of Electrum, so I can access my bitcoin.
Do you have any other ideas? Has anyone else experienced anything like this?
submitted by throwaway_23f32f to Electrum [link] [comments]

Help setting up Bitcoin Core node with Tor hidden service

I am trying to run a full node with Bitcoin Core and get it running as a Tor hidden service but the steps I am following are from many sources and I feel like I have been missing steps in between, not to mention that my technical skills are fairly basic.
Here's where I'm at (Windows):
Can someone please tell me if I've missed something or if I've done it right then how to check that I have?
Thanks!
Update: Currently I have a "work-around" by running tails in a VM and running bitcoin-qt inside that. Because it's a livecd if it gets shutdown for any reason I'd have to set it up each time so I would still like to get the full node running with Tor on Windows.
I am using bitcoin-qt.exe from the Windows installation of Bitcoin Core and using any combination of the network settings to get it to use Tor and it does connect to onion addresses, sometimes one or two and the remaining of the eight are normal nodes.
I can't figure out how to make Bitcoin Core only connect Tor nodes instead of none or a mixture.
Update 2: Instead of using the Tails in a VM workaround, I have the windows Bitcoin Core Node running properly over Tor now. I still have to wait a few days at least to see if I can get more than two incoming connections.
I read in many places that port 8333 had to be opened in order to receive incoming connections but I have been assured that doesn't apply to onion nodes and that checking getnetworkinfo with bitcoin-qt console shows onion as reachable is proof.
There was also an issue with Tor not working with the CookieAuth when that set was added to torrc. Simply CookieAuthFile needed to be added.
I'm adding these notes in case any other windows user has trouble getting their node running with Tor.
SYD4uo was a huge help and I appreciate those others that took the time to give advice. Cheers!
This was also very helpful
submitted by Slayer3608 to Bitcoin [link] [comments]

(Updated) [Staking] Reddcoin Core client GUI wallet on a Raspberry Pi Model 3B

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:
 
The updates
 
If you would like to tip me
Writing a tutorial like this takes time and effort; tips are appreciated. My Reddcoin address: RqvdnNX5MTam855Y2Vudv7yVgtXdcYaQAW.
     

Overview

 

Steps

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
     

Video

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

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!
 
 
   
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.
   
Minimization options
Adjust minimization options, so you can safely press on the X button (the close/exit button on the upper right corner).
   
RealVNC VNC Viewer (client) and VNC Connect (server): To remote connect to the Raspberry Pi, I use VNC Viewer ad VNC Connect from RealVNC.
 
   
Chromium as browser: The updates break Firefox, the browser crashes when you try to run it. Install another browser, Chromium, to solve this issue.
   
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.  
     

Credits:

   
Credits in previous tutorial:
submitted by Yavuz_Selim to reddCoin [link] [comments]

Thank you for running your own full Vertcoin node and supporting VTC network! We currently have 518 Full Nodes running.

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/
submitted by blockchaintechnology to vertcoin [link] [comments]

Thank you for running your own VTC node and supporting VTC network! We now have 1394 Full Nodes, more than Litecoin

You guys are amazing! :) Thank you for running your own full VTC node and supporting VTC network! We now have 1394 Full Nodes :)
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? 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. If you have a Raspberry Pi or any old PC lying around, install vertcoind and run it in the background. 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.
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!
Why Vertcoin? Learn about why ASIC Resistance matters! https://www.youtube.com/watch?v=UHXqfZWjuHI
Linux instructions: https://www.cryptocurrencyfreak.com/2017/09/06/setup-vertcoin-full-node-ubuntu-16-04/
submitted by blockchaintechnology to vertcoin [link] [comments]

Thank you for running your own full Vertcoin node and supporting VTC network! We currently have 811 Full Nodes running.

Thank you for running your own full Vertcoin node and supporting VTC network! We currently have 811 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? 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!
Why Vertcoin? Learn about why ASIC Resistance matters! https://www.youtube.com/watch?v=UHXqfZWjuHI
Linux instructions: https://www.cryptocurrencyfreak.com/2017/09/06/setup-vertcoin-full-node-ubuntu-16-04/
submitted by blockchaintechnology to vertcoin [link] [comments]

Thank you for running your own full Vertcoin node and supporting VTC network! We currently have 518 Full Nodes running.

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/
submitted by blockchaintechnology to vertcoin [link] [comments]

[PSA] Dogecoin Wallet version 1.4 released. You must update.

WARNING: DO NOT send your wallet.dat file or dogecoin folder to anyone. There have been reports of people offering to help others by asking them to send their files to them so they can help. DO NOT do this. Scam attempt picture
Always encrypt your wallet! I can't express this enough. You should use a strong password longer than 15 characters. This password should contain numbers, symbols, and some capitalization! There is no need to have your wallet open 24 hours a day. Open it only when you need it. See - 'Getting Started' on the side bar.
This entire post has been written to be as close to ELI5 (Explain it like I'm 5) as possible - By request! If anyone wants to add/fix/correct anything in this message, please send a message to the mods <<-- Click blue text.
All blue text in this post can be clicked on. The blue text is a link to a picture, site or download file.
A very important message/reminder below.
25 Jan 1.5 pre-releases have started.
http://www.reddit.com/dogecoin/comments/1uhpwf/dogecoin_for_mac_14_topic_thread/
OLD VERSIONS The 1.4 update for the dogecoin wallet has been released. This update addresses the block chain error that occurred. This update is mandatory meaning you have to do this update. Also further down the page you can read up about the block chain. You MUST make sure you're on the correct block chain and the old block chain has been removed.
For a Windows computer the version must be 1.4. - 1.4.1 just released! See below
For a Apple Mac Computer the version must be 1.4
Download links:
[Windows Download Link](https://github.com/dogecoin/dogecoin/releases/download/1.4/dogecoin-qt-v14-Win.zip) <<--Click to start download
Windows Download Link 1.4.1 UPDATED 19JAN
Mac Download Link <<--Click to start download
Mac users can join this thread if there are any problems
Android (phone): Please see This post
To update, simply download the new version from the download link above. Open the downloaded file and extract the contents of the downloaded file into any new folder or location on your computer. If you put the files into a folder you can name the folder anything you want but make sure you remember that this is the latest version of the software.
You don't have to remove your folder containing the old version of the wallet. You can place it in a folder called 'Old versions of dogecoin wallet' if you like.
Now you can click on the Dogecoin icon contained in the new folder to open your version 1.4 wallet.
What happens if I get an error when I open the new wallet?
An error was reported called "11DbException"
If this happens Download this file and place it in the same folder as your updated wallet. Open the file you just downloaded called "Dogecoin OPEN' and wait. This might take 2 or 3 minutes.
Also jtlarousse has found a solution that worked on Windows. Please follow carefully and make backups before starting.
Reebzy might have found a solution for Apple Mac
Blockchain fork 101: The block chain is a ledger or document created containing every transaction that has ever happened. This file can be quite large. Bitcoins ledger is over 15GB. At some point this document/ledger split into two separate documents known as a fork.
How do I know if I am on the right block chain?
Go to your newly updated dogecoin wallet and open it. Click on Help>>Debug next Observe the current block number
*Note the example numbers in the pictures might be out of date by the time you read them
Now go over to http://dogechain.info/chain/Dogecoin . This website is the official Dogecoin blockchain website. Check the block number they're reporting
The number you found in your wallet and the number reported on the website should close. There might be a difference of 100 blocks depending on when you last refreshed your wallet or how long it took for you to get from one step to the next step in this guide and if the dogechain website is lagging.
I'M NOT ON THE CORRECT BLOCK CHAIN
My numbers are very different. How do I get back onto the right block chain?
IMPORTANT
For windows:
1)Close down the Dogecoin wallet client.
2)Go to your data folder: C:\Users[your windows log-in name]\AppData\Roaming\DogeCoin
3)Delete the Dogecoin.conf file. Do not delete the wallet.dat file!
4)Download this update file and place it into the Dogecoin folder where the other file was deleted.
For Apple Mac:
1)Close down the Dogecoin wallet client.
2)Go to your data folder: ~/Libarary/Application Support/Dogecoin
3)Delete the Dogecoin.conf file. Do not delete the wallet.dat file!
4)Download this update file and place it into the Dogecoin folder where the other file was deleted.
Next visit this post by Netcodepool for instructions on how to manually download the correct block chain and install it.
Much Thanks. 
Edit: Some posts were removed from this thread. To limit confusion.
Check this post for details about mining pools that were/are using the wrong fork.
Did you send coins only to find out you're on the wrong chain? See this post to get them back
An Apple Mac support thread has been made by voidref (The mac developer). If you're having troubles please see this thread
Some shibes have reported their wallets wont sync. Please check to make sure your firewall, antivirus, malware scanner or similar programs are not blocking it the wallet. You can add rules to these programs to allow the wallet to make contact with the internet. It's not advised but possible to also disable the software for a short amount of time. Don't forget to enable the software again afterwards.
Is your wallet crashing? Try this helpful tip from gandhikahn or if you're using windows try the 1.4.1 update above.
submitted by 42points to dogecoin [link] [comments]

Thank you for running your own full Vertcoin node and supporting VTC network! We currently have 867 Full Nodes running.

Thank you for running your own full Vertcoin node and supporting VTC network! We currently have 867 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? 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/
submitted by blockchaintechnology to vertcoin [link] [comments]

Thank you for running your own full Vertcoin node and supporting VTC network! We currently have 500+ Full Nodes running.

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/
submitted by blockchaintechnology to vertcoin [link] [comments]

Dogecoin Core 1.7.0 released - Check in here for all info you need

Hi shibes!
The Dogecoin developers are proud to announce the final version of Dogecoin Core 1.7! After lots of coding, testing and swearing this is the next version of our reference client. It brings Dogecoin one big step forward on the technical side of things, with moving to the Bitcoin 0.9 codebase.
The full release notes are available here: https://github.com/dogecoin/dogecoin/releases/tag/v1.7.0
TL;DR of the release notes
Is this mandatory? No, you can stay on 1.6 if you want for now. This update adds quite a few new features you'd miss out on.
How to update?
  1. Backup your wallet! This is very important! Go to File -> Backup Wallet, and save this file in at least two safe places for a good backup.
  2. Exit the client you're running now.
  3. Install the update
    1. For Windows, use the setup.exe to update. If you are using the new 64bit version you'll need to uninstall 1.6 afterwards.
    2. For Mac just overwrite the version you currently have in you Applications folder.
    3. For Linux you'd overwrite your current dogecoin-qt binary with the new one.
  4. Start the client. That's it :)
About going back to 1.6 Once you go to 1.7 there is no easy way back to 1.6. That's why it's important to have a backup of your wallet. Just in case. Be aware that a backup goes out of date after 100 transactions! Several people have been running 1.7 for a while now and see no problem with it, so you probably don't want to go back anyway ;)
Downloads (Listing here this time to make it easier to find)
Changes from RC1
Staying up to date If you want to easily stay up to date with releases, you can subscribe to the mailing list right here: http://sourceforge.net/p/dogecoin/mailman/dogecoin-releases/ That's especially advised if you are a service provider!
General comments For anyone running an exchange, please also note that in light of the 51% attack against Reddcoin last night, the Dogecoin developers now recommend a minimum of 10 confirmations for payments into an exchange.
Thanks Thanks to everyone who contributed so far! Especially leofidus-ger, rnicoll and patricklodder, who have done by far the most of the work for this release. But of course thanks to everyone else who contributed, may it be advice or code or whatever. Also thanks to the Bitcoin developers. And of course thanks to the Dogecoin community! You are what makes it fun to work on all this ;)
submitted by langer_hans to dogecoin [link] [comments]

What is up with all these Bitcoin devs who think that their job includes HARD-CODING CERTAIN VALUES THAT ARE SUPPOSED TO BE USER-CONFIGURABLE (eg: "seed servers")?

Recently, the developer of SegWit2x / BTC1, Jeff Garzik, caused some controversy by hard-coding the "seed servers" which Bitcoin uses to first start hunting for "peers".
Worse than that: apparently one of the "seeds" is a company he started, variously named Chainalysis / Skry / Bloq - which apparently specializes in de-anonymizing Bitcoin transactions and performing KYC/AML - and which also has apparently entered into agreements with Interpol.
Seriously, WTF???
This is what "Bitcoin devs" still consider to be part of their "job" - hard-coding parameters like this, which affect everyone else on the network - and which could easily be "exposed" to be made user-configurable - instead of being baked into the source code and requiring a friggin' recompile to change???
This recent event has refocused attention on the fact all these past years, most of these seed servers in "the" existing (legacy) client running on most of the network have _also been hard-coded - to domains under the control of "devs associated with Blockstream".
I don't like the list of seed servers in Bitcoin Core
Pieter Wuille - does not support BIP148 - works for Blockstream
Matt Corallo - does not support BIP148 - works for Blockstream
Luke Dashjr - supports BIP148 - works for Blockstream
Christian Decker - supports BIP148 - works for Blockstream
Jonas Schnelli - supports BIP148
Peter Todd - supports BIP148 - worked for Samson Mow who works for Blockstream
https://np.reddit.com/btc/comments/6nd50h/i_dont_like_the_list_of_seed_servers_in_bitcoin/
The corporate takeover of bitcoin illustrated in 1 commit
In The corporate takeover of bitcoin illustrated in 1 commit a user complains that btc1 changing the seed servers to servers run by some companies (see commit) equals a "corporate takeover of bitcoin". I never really took much care who runs these seed server, although they do posses a certain power over the network as correctly pointed out by P. Todd in the same thread:
...and the key thing with that is being able to control what nodes a node connects to can be a very powerful tool to attack new nodes, as it lets you prevent a node from learning about the valid chain with the most work.
[...]
4 out of 5 people running the bitcoin networks seed servers are directly associated with Blockstream!
I don't even believe that Blockstream is actually plotting an evil, forceful takeover of bitcoin using the seed servers. However it beautifully counteracts Adam's "decentralization is everything" arguments. What is most troublesome to me, is that this simple information is not allowed to appear on r\bitcoin at all.
https://np.reddit.com/btc/comments/6n8vqc/the_corporate_takeover_of_bitcoin_illustrated_in/
Seriously?
Bitcoin is almost 9 years old - and most people are still running clients which use hard-coded values (which require an inconvenient recompile to reconfigure) for the "seed servers"??
Maybe this is, in some sense, part of the reason why people like BlueMatt and Luke-Jr and Pieter Wiulle think they can lord it over us and tell everyone else what to do? ...because they have quietly (and unfairly / incompetently) hard-coded their own friggin' server domain names directly into everyone else's client code, as our "seed servers"?
Is the low level of "quality" we - as a community - have become accustomed to from our devs?
Do other clients (Bitcoin Classic, Bitcoin Unlimited and Bitcoin ABC) also gratuitously hard-code their "seed servers" like this?
Here's a post from a year ago regarding "seed servers" in Classic:
How come "classic" uses the same alert keys/DNS seeds as Core?
https://np.reddit.com/btc/comments/44atsp/how_come_classic_uses_the_same_alert_keysdns/
Meanwhile, here's the main question:
Why are any "serious" Bitcoin clients still "gratuitously" hard-coding any values like this?
Why has our "ecosystem" / "community" not naturally evolved to the point where we have some public "wiki" pages listing all the "good" (community-recognized, popular) seed servers - and every user configures their own client software by choosing who they want from this list?
(Maybe because we've been distracted by bullshit for these past few years, fighting with these very same devs because they've refused provide any support for users who want bigger blocks?)
What would users have to do if (God forbid) something were to happen to the servers of those 4-5 seed servers which are currently hard-coded into nearly everyone's clients?
In that situation (assuming some "new" seed servers quickly appeared) people would be have two options:
  • Edit their C++ source code and download/install a (trusted, verified) C++ compiler (if they don't already have one), and recompile the friggin' code; or
  • Wait until new binaries got posted online - and download them (and verify them).
Seriously?
This unnecessary "centralization point" (or major inconvenience / bottleneck) has been sitting in our code this entire time - while these supposedly knowledgeable devs keep beating us over their head with their mantra of "decentralization" - which they have actually been doing so little to maximize?
Psycho-Socio-Economic Side Bar
Serious (but delicate/senstive) question: How many of these "devs" have developed (possibly unconscious?) behaviors in life where they try to make users dependent on them?
"Vendor lock-in" is a thing - a very bad thing, which certain Bitcoin devs have exhibited a tendency to inflict on users - in many cases due to rather obvious (psychological, social, and/or economic) reasons.
We should gently (but firmly) reject these tendencies whenever any dev exhibits them.
Our community should expect and demand an accessible, user-friendly interface for all user-configurable parameters - to maximize decentralization and autonomy
  • In "command-line" versions of the client program, these kind of parameters should be:
    • in a separate config file - using some ultra-simple, standard format such as YAML or JSON
    • also configurable via options (eg, --seed-server) upon invocation on the command-line
  • In GUI versions version of the client program (using some popular cross-platform standard such as Qt, HTML, etc.) these kind of parameters should be exposed as user-configurable options.
Yes, these user-configurable values for things like "seed servers" (or "max blocksize") could come pre-configured to "sensible defaults - so that the software will work "out of the box" (immediately upon downloading and installing) - with no initial configuration required by the user.
Yes: Even the blocksize has always been user-configurable - but most users don't know this, because most devs have been hiding this fact from us.
Three recent posts by u/ForkiusMaximus explained how Adjustable-Blocksize-Cap (ABC) Bitcoin clients shatter this illusion:
Adjustable-blocksize-cap (ABC) clients give miners exactly zero additional power. BU, Classic, and other ABC clients are really just an argument in code form, shattering the illusion that devs are part of the governance structure.
https://np.reddit.com/btc/comments/614su9/adjustableblocksizecap_abc_clients_give_miners/
Adjustable blocksize cap (ABC) is dangerous? The blocksize cap has always been user-adjustable. Core just has a really shitty inferface for it.
https://np.reddit.com/btc/comments/617gf9/adjustable_blocksize_cap_abc_is_dangerous_the/
Clearing up Some Widespread Confusions about BU
https://np.reddit.com/btc/comments/602vsy/clearing_up_some_widespread_confusions_about_bu/
Note about Bitcoin ABC vs Bitcoin Unlimited:
There is a specific new Bitcoin client called Bitcoin ABC, which functions similar to Bitcoin Unlimited - with the important difference that Bitcoin ABC is _guaranteed to hard-fork to bigger blocks on August 1_.
(Please correct me if I'm wrong about this. Documentation for the behavior of these various hard-forks is currently still rather disorganized :-)
All serious devs should be expected to provide code which does not require a "recompile" to change these "initial, sensible" default parameters.
I mean - come on. Even back in the 80s people had "*.INI" files on DOS and Windows.
Nearly all users understand and know how to set user-configurable values - for decades.
How many people are familiar with using a program which has a "Preferences" screen? (Sometimes you may have to close and re-open the program in order for your new preferences to take effect.) This is really basic, basic functionality which nearly all software provides via a GUI (and or config file and/or command-line options).
And nearly all devs have been offering this kind of functionality - in either command-line parameters, config files, and/or graphic user interfaces (GUIs).
Except most Bitcoin devs.
The state of "software development" for Bitcoin clients seems really messed up in certain ways like this.
As users, we need to start demanding simple, standard features in our client software - such as accessible, user-friendly configurability of parameter values - without the massive inconvenience of a recompile.
What is a "Bitcoin client"?
After nearly 9 years in operation, our community should by now have a basic concept or definition of what a "Bitcoin client" is / does - probably something along the lines of:

A Bitcoin client is a device for reading (and optionally appending to) the immutable Bitcoin Blockchain.

Based on that general concept / definition, a program which does all of the above and also gratuitously "hard-codes" a bunch of domain names for "seed servers" is not quite the same thing as a "a Bitcoin client".
Such an "overspecialized" client actually provides merely a subset of the full functionality of a true "Bitcoin client", eg:
  • An "overspecialized" client only enables connecting to certain "seed servers" upon startup (in accordance with the "gratuitous opinion" of the dev who (mis)translated the community's conceptual specifications to C++ code)
  • An "overspecialized" client only enables mining blocks less that a certain size (in accordance with the "gratuitous opinion" of the dev who (mis)translated the community's conceptual specifications to C++ code)
One of the main problems with nearly all Bitcoin clients developed so far is that they are gratuitously opinionated: they "gratuitously" hard-code particular values (eg, "max blocksize", "seed servers") which are not part of the whitepaper, and not part of the generally accepted definition of a "Bitcoin client".
This failure on the part of devs to provide Bitcoin clients which behave in accordance with the community's specification of "Bitcoin clients" is seriously damaging Bitcoin - and needs to be fixed as soon as possible.
Right now is a good opportunity - with so many new Bitcoin clients popping up, as the community prepares to fork.
All devs working on various Bitcoin client software offerings need to wake up and realize that there is about to be a major battle to find out which Bitcoin client software offering performs "best" (in the user-interface sense - and ultimately in the economic sense) at:

reading (and optionally appending to) the immutable Bitcoin Blockchain

The Bitcoin client software offerings which can optimally (and most simply and securely :-) "satisfy" the above specification (and not merely some gratuitously overspecialized "subset" of it) will have the most success.
submitted by ydtm to btc [link] [comments]

Run a 0.14 Full-Node on RaspberryPi3 Pruned(less than 16GB SD needed)

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.
submitted by I-am-the-noob to Bitcoin [link] [comments]

4. Installing Bitcoin Core on Linux How to install a Bitcoin Wallet How to Install A Litecoin Wallet On Windows How to run Bitcoin Core 0.9.2.1 on external Hard Drive Installing Bitcoin Armory

Finally, install Bitcoin core itself. Enter “Y” when asked asked for permission to continue: $ sudo apt-get install bitcoin-qt This last command may take some time, during which both Bitcoin Core and all of its dependencies will be installed. Run Bitcoin Core. Bitcoin Core can be started from the command line with: $ bitcoin-qt Bitcoin-Qt is the so – called" official " client of the network, which is developed and promoted by Bitcoin Foundation, a non-profit organization uniting core developers and responsible for the community's contacts with corporations and governments.Bitcoin Foundation branches are opened in several dozens of countries around the world. Bitcoin Core ist ein gemeinschaftliches, freies Software-Projekt, veröffentlicht unter der MIT-Lizenz. Release-Signaturen überprüfen Download über Torrent Quelltext Versionshistorie anzeigen Bitcoin Core Release Signierschlüssel v0.8.6 - 0.9.2.1 v0.9.3 - 0.10.2 v0.11.0+ WINDOWS BUILD NOTES. Below are some notes on how to build Bitcoin Core for Windows. The options known to work for building Bitcoin Core on Windows are: On Linux, using the Mingw-w64 cross compiler tool chain. Ubuntu Bionic 18.04 is required and is the platform used to build the Bitcoin Core Windows release binaries. Bitcoin is a form of decentralized cryptocurrency that was created in 2009. Because it is decentralized, it doesn't use a bank or a single administrator. Each transaction occurs without a middleman being involved. bitcoin can be used with a number of organizations (such as booking hotels and purchasing goods and services). However, the use of bitcoin does require a network to work upon.

[index] [48957] [8379] [11690] [39869] [19214] [32251] [18315] [19722] [32514] [37433]

4. Installing Bitcoin Core on Linux

This video is unavailable. Watch Queue Queue. Watch Queue Queue This video will show you how too install the Litecoin Qt wallet on Windows so that you can send and receive litecoins. I accidentally said Bitcoins a few times in the video instead of litecoins ... Bitcoin-QT is a Bitcoin wallet and does some other functions. Running this software is the backbone to the entire Bitcoin system. You may need to open port 8333 in your firewall. For more info see sudo add-apt-repository ppa:bitcoin/bitcoin sudo apt-get update sudo apt-get install bitcoin-qt bitcoind Linux terminal new stuff: clear, ll, cd, touch, echo, cat, shutdown www.bitcoinhackers.org Episode 1 : Bitcoin Series In this video I teach you how to install a digital wallet to contain your Bitcoins. I also teach you how to utilize the Bitcoin Faucet to get your first free coin.

#