Bitcoin Core Not Syncing - Mello TV

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]

(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]

PSA: Clearing up some misconceptions about full nodes

It's time to clear up some misconceptions floating around about full nodes.
Myth: There are only about 5500 full nodes worldwide
This number comes from this site and it measured by trying to probe every nodes on their open ports.
Problem is, not all nodes actually have open ports that can be probed. Either because they are behind firewalls or because their users have configured them to not listen for connections.
Nobody knows how many full nodes there are, since many people don't know how to forward ports behind a firewall, and bandwidth can be costly, its quite likely that the number of nodes with closed ports is at least another several thousand.
Nodes with open ports are able to upload blocks to new full nodes. In all other ways they are the same as nodes with closed ports. But because open-port-nodes can be measured and closed-port-nodes cannot, some members of the bitcoin community have been mistaken into believing that open-port-nodes are that matters.
Myth: This number of nodes matters and/or is too low.
Nodes with open ports are useful to the bitcoin network because they help bootstrap new nodes by uploading historical blocks, they are a measure of bandwidth capacity. Right now there is no shortage of bandwidth capacity, and if there was it could be easily added by renting cloud servers.
The problem is not bandwidth or connections, but trust, security and privacy. Let me explain.
Full nodes are able to check that all of bitcoin's rules are being followed. Rules like following the inflation schedule, no double spending, no spending of coins that don't belong to the holder of the private key and all the other rules required to make bitcoin work (e.g. difficulty)
Full nodes are what make bitcoin trustless. No longer do you have to trust a financial institution like a bank or paypal, you can simply run software on your own computer. To put simply, the only node that matters is the one you use
Myth: There is no incentive to run nodes, the network relies on altruism
It is very much in the individual bitcoin's users rational self interest to run a full node and use it as their wallet.
Using a full node as your wallet is the only way to know for sure that none of bitcoin's rules have been broken. Rules like no coins were spent not belonging to the owner, that no coins were spent twice, that no inflation happens outside of the schedule and that all the rules needed to make the system work are followed (e.g. difficulty.) All other kinds of wallet involve trusting a third party server.
All these checks done by full nodes also increase the security. There are many attacks possible against lightweight wallets that do not affect full node wallets.
This is not just mindless paranoia, there have been real world examples where full node users were unaffected by turmoil in the rest of the bitcoin ecosystem. The 4th July 2015 accidental chain fork effected many kinds of wallets. Here is the wiki page on this event https://en.bitcoin.it/wiki/July_2015_chain_forks#Wallet_Advice
Notice how updated node software was completely unaffected by the fork. All other wallets required either extra confirmations or checking that the third-party institution was running the correct version.
Full nodes wallets are also currently the most private way to use Bitcoin, with nobody else learning which bitcoin addresses belong to you. All other lightweight wallets leak information about which addresses are yours because they must query third-party servers. The Electrum servers will know which addresses belong to you and can link them together. Despite bloom filtering, lightweight wallets based on BitcoinJ do not provide much privacy against nodes who connected directly to the wallet or wiretappers.
For many use cases, such privacy may not be required. But an important reason to run a full node and use it as a wallet is to get the full privacy benefits.
Myth: I can just set up a node on a cloud server instance and leave it
To get the benefits of running a full node, you must use it as your wallet, preferably on hardware you control.
Most people who do this do not use a full node as their wallet. Unfortunately because Bitcoin has a similar name to Bittorrent, some people believe that upload capacity is the most important thing for a healthy network. As I've explained above: bandwidth and connections are not a problem today, trust, security and privacy are.
Myth: Running a full node is not recommended, most people should use a lightweight client
This was common advice in 2012, but since then the full node software has vastly improved in terms of user experience.
If you cannot spare the disk space to store the blockchain, you can enable pruning. In Bitcoin Core 0.12, pruning being enabled will leave the wallet enabled. Altogether this should require less than 900MB of hard disk space.
If you cannot spare the bandwidth to upload blocks to other nodes, there are number of options to reduce or eliminate the bandwidth requirement. These include limiting connections, bandwidth targetting and disabling listening. Bitcoin Core 0.12 has the new option -blocksonly, where the node will not download unconfirmed transaction and only download new blocks. This more than halves the bandwidth usage at the expense of not seeing unconfirmed transactions.
Synchronizing the blockchain for a new node has improved since 2012 too. Features like headers-first and libsecp256k1 have greatly improved the initial synchronization time.
It can be further improved by setting -dbcache=3000 which keeps more of the UTXO set in memory. It reduces the amount of time reading from disk and therefore speeds up synchronization. Tests showed that the entire blockchain can now be synchronized in less than 3 and a half hours (Note that you'll need Bitcoin Core 0.12 or later to get all these efficiency improvements) Another example with 2h 25m
How to run a full node as your wallet.
I think every moderate user of bitcoin would benefit by running a full node and using it as their wallet. There are several ways to do this.
So what are you waiting for? The benefits are many, the downsides are not that bad. The more people do this, the more robust and healthy the bitcoin ecosystem is.
Further reading: http://www.truthcoin.info/blog/measuring-decentralization/
submitted by belcher_ to Bitcoin [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 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]

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

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]

Let me love the Bitcoin, please.

After reading tiny snippets about Bitcoin all the time I decided to take a closer look at it ... and I was floored.
Please don't get me wrong, I really really really want to love the concept, but it seems to be more or less unusable. There are some huge upsides to it: Built on mistrust, fixed amount of money, decentralized system, anonymity and so on. But my reality looked something like this:
Now as you might say, I should have read up on the details (blockchain!) before - but getting started seems to be a big hurdle for the non-geeks out there. Nothing like "get started in seconds!". Even I had some trouble grasping the concept, and I'm sitting in front of a computer for about two decades now.
But wait, there's more! Since my connection is still under heavy load from the client, I could read up on all the things I have missed, and I found some inherent flaws:
For me, Bitcoins could be an awesome form of worldwide, internet-based form of micropayments. The biggest market would be developing countries. But there are technical and legal barriers which push it into a corner for geeks who see conspiracies everywhere and want to crash the system ... which is exactly not what it should be. I read about Ripple, it seems to be a better alternative just because of the possibility for easy money exchanges - and it includes Bitcoin, too.
So, is there something I just don't get yet? I get the impression Bitcoin is a great idea, but just the prototype for something better.
submitted by surfersbeware to Bitcoin [link] [comments]

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

Thank you for running your own full Vertcoin node and supporting VTC network! We currently have 900 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 450 Full Nodes running.

Thank you for running your own full Vertcoin node and supporting VTC network! We currently have 450 Full Nodes running.
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!
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]

Basic Bitcoin security guide

Hello,
This post is to give you a quick introduction into Bitcoin security. While nobody can guarantee you 100% security, I hope to mitigate some problems you can run into. This is the “20% of effort to get you to 80% safe”.
First of all, you have to determine how much money you want to hold in Bitcoin and how much effort are you willing to put in. If you are happy just holding a few dollars worth and don’t care if you lose them, that’s one approach to take. For everyone else, lets get started.
Password strength
A lot of the times how secure your money is will be determined by the strength of your password. Since in the worst case scenario we are talking about someone trying to brute force your wallet, casual online passwords are too weak. Under 10 characters is too weak. Common words and phrases are too weak. Adding one number to a password at the end is too weak.
Moreover, you can consider your password much weaker if you:
If you want a really strong password:
Wallet security
Now we are getting to the meat of things.
There are a number of wallets available to store your hard earned bitcoins. If you have a decent amount of coins to store, you should look into software wallets - BitcoinQT, MultiBit, Armory or Electrum. They are among the best place to store your money safely (provided your computer is secure as well). Chose one you think best suits you, install it and encrypt your wallet file with your strong password. You should take your wallet file and back it up (location of the file is different for different clients, so you have to do some research as to where to find that file). Back it up on a CD, safe USB drive or the like. Keep them safe. If you lose that file, you will lose your money.
A quick word on deterministic wallets. Electrum and Armory allow you to create wallets from a seed. If you use the same seed later, you can recreate your wallet on other machines. With deterministic wallets, you only need to keep that seed secure to have access to your money.
In comparison, in BitcoinQT's traditional wallet, every address you use is random, meaning that after you send 50-100 outgoing transactions your backups can be obsolete. Always keep an up-to-date backup of such wallet file if possible.
Okay, sometimes you need to have your Bitcoins with you when you leave your computer. In this case, you should look into either online or mobile wallets. A staple for both of those is Blockchain.info, but there are others to chose from.
A good rule of thumb with these is to not store more money in them than you can afford to lose. They are best used as a convenient way of accessing some money, not storing your savings. Online wallets are especially vulnerable to their servers getting hacked and people’s money getting stolen.
What to keep in mind while using online wallets:
  • Use a secure password (the more money you have in them the stronger the password should be)
  • Always keep a backup of your wallet in case you need to recover your money
  • Whenever possible, enable two factor authentication
  • Don’t use your online wallets from unsafe computers
Cold storage
Sometimes you want to store your bitcoins for a long time in a safe place. This is called “cold storage”. There are a few ways one can do this.
First of all, paper wallets. They are nice for giving people small bitcoin gifts, but also for long-term storage if properly used. What you want to do is generate and print them offline. You can save the linked page for example and run that offline. If you are really paranoid, you can put it on read-only media and access that from a different computer. For really long term storage, use archival-grade paper.
Another approach to take is using a separate computer for storing your money that is offline 99+% of the time. You could set one up easily by buying an old laptop, reformatting it, installing Linux and a Bitcoin client. Generate an address on that machine and send money to it from your main wallet. Depending on how paranoid you are you can connect that computer to the Internet afterwards to synchronize data with the Bitcoin Network and then turn it off and put it away somewhere safe until it’s needed.
Brain wallets
Don’t. They are not for you. Unless you are a security-conscientious programmer, those are not for you.
Diversifying
Keeping all of your eggs in one basket is never a good thing. You should look into diversifying some of your Bitcoin assets in case your other storage methods fail. Some ways you can diversify:
  • Buy a physical Bitcoin. As long as you trust the coin creator such coins can be an effective cold storage
  • Invest - I wouldn’t recommend this for more than some trivial amount unless you know what you are doing, but investing in some Bitcoin stocks could be a way to get more money out of your bitcoins
How not to diversify:
  • Avoid keeping your bitcoins at exchanges or other online sites that are not your online wallets. Such sites can be closed down or disappear along with your money.
  • Alt-coins - there are few cryptocurrencies that are worthwhile, but most of them are just Bitcoin clones. If a currency brings nothing new, it’s worthless in comparison to Bitcoin. Namecoin is a distributed domain name server (although recently it had a fatal flaw uncovered, so be warned), Ripple is a distributed currency exchange and payment system. Litecoin will only be useful in case Bitcoin’s hashing algorithm gets compromised (very unlikely at this time). Beyond that there are few if any alt-coins that are a worthwhile way of diversifying.
Accepting payments and safety
We’ve covered safe ways to store money, now a quick note about bitcoin payments and their safety.
First of all, when you are sending a transaction, pay your fees. Transactions without fees can take forever to propagate, confirm and clear. This can cause you a lot of stress, so pay your fees.
Secondly, when accepting large Bitcoin payments (say you want to suddenly cash in a gold bar into bitcoins), wait for at the very least 1 confirmation on those transactions. 6 is best, but having even 1 confirmations is a lot better than having none. This is mainly a rule of thumb for the paranoid (I wouldn’t be doing this for most casual transaction), but maybe it will save you if you are dealing with some shady people.
Wrapping up...
That should cover the basics. If you want to read more about Bitcoin’s security in general, here is my master thesis on the subject. A lot of questions about Bitcoin and security have also been answered on Bitcoin StackExchange - be sure to check it out.
Comments and improvement suggestions welcome.
EDITS:
  • Removed link to insecure site
  • Removed random article section
  • Added information about deterministic wallets
submitted by ThePiachu to Bitcoin [link] [comments]

Bitcoin Core 0.10.1 Released

Bitcoin Core version 0.10.1 is now available from:
https://bitcoin.org/bin/bitcoin-core-0.10.1/
This is a new minor version release, bringing bug fixes and translation updates. If you are using 0.10.0, it is recommended to upgrade to this version.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues

Upgrading and downgrading

How to Upgrade

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 (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on Linux).

Downgrade warning

Because release 0.10.0 and later makes use of headers-first synchronization and parallel block download (see further), the block files and databases are not backwards-compatible with pre-0.10 versions of Bitcoin Core or other software:
If you want to be able to downgrade smoothly, make a backup of your entire data directory. Without this your node will need start syncing (or importing from bootstrap.dat) anew afterwards. It is possible that the data from a completely synchronised 0.10 node may be usable in older versions as-is, but this is not supported and may break as soon as the older version attempts to reindex.
This does not affect wallet forward or backward compatibility.

Notable changes

This is a minor release and hence there are no notable changes. For the notable changes in 0.10, refer to the release notes for the 0.10.0 release at https://github.com/bitcoin/bitcoin/blob/v0.10.0/doc/release-notes.md

0.10.1 Change log

Detailed release notes follow. This overview includes changes that affect external behavior, not code moves, refactors or string updates.
RPC:
Block (database) and transaction handling:
P2P protocol and network code:
Validation:
Build system:
Wallet:
GUI:
Tests:
Miscellaneous:

Credits

Thanks to everyone who contributed to this release:
As well as everyone that helped translating on Transifex.
submitted by harda to Bitcoin [link] [comments]

How to create a Litecoin wallet.

This will be a guide on how to create a Litecoin wallet.
I will try to make this as noob friendly as possible.
The wallet we will be using will be the Litecoin-qt wallet. This wallet is made by the Litecoin dev team and is pretty much the same thing as the Bitcoin-qt wallet except for Litecoins. This is a local wallet that will reside on your computer and not online.
Having a wallet on your computer is the best way to store your coins. You dont have to put trust in anyone else to keep your coins safe. Almost every online Bitcoin wallet has been hacked leading to user funds being stolen. NEVER, EVER, EVER trust anyone to hold your coins except yourself. That being said by storing your own coins you do have to take some precautions to keep them safe. I will instruct you on how to encrypt your wallet but there are still better ways to lock your wallet down. I will write another tutorial on this subject at at a later time.
So to start you need to download the Litecoin wallet. You get this from https://litecoin.org/ ONLY DOWNLOAD THE LITECOIN WALLET FROM THIS ADDRESS. If you download it from anywhere else it could be corrupted and you could have your coins stolen. https://litecoin.org/ is the website run by the Litecoin dev team.
On the main page you will see links to download Windows, MAC, and Linux versions of the wallet. Download whichever one corresponds to the OS you use. I will assume Windows for this guide but for using a Mac you should install it like you do any other application.
Once you download it open the file and follow the prompts clicking next etc.
Once you are finished open up the Litecoin client. It should have put an icon on your desktop.
Once you open it up you will see the Litecoin-qt client. It might take a few seconds to load.
At the bottom you should see a bar with "Synchronizing with network" next to it. This means that the client is downloading all of the blocks in the blockchain. It will take a while to download all of the blocks (about 2.5GB worth) the first time. After the first time when you open the client it will only download the blocks that have been created since last time you used the client. When it is finished you will see the bar disappear and there will be a green check mark in the bottom right hand corner.
While we are at the bottom right hand corner if you hover your mouse over the signal bar looking icon it will tell you how many connections you have to the Litecoin network. So if for some reason you are not downloading any blocks then check this to make sure you are connected to the network.
To encrypt your wallet
At the top click Settings > Encrypt Wallet. Follow the prompt entering your password and make it a good one. After you encrypt your wallet you will see a padlock at the bottom right next to where the green check and the signal bars are.
WARNING IF YOU LOSE OR FORGET YOUR PASSWORD YOUR COINS ARE GONE FOREVER!!!
Now to send coins you click the send button and you enter the address, amount, and if you want to label the trans you do can do that also. Then you click send. You will have to enter your password if your wallet is encrypted.
To receive coins click the receive button. You will already have one address there. You can give this address to anyone or enter it in any service and you will receive coins to this wallet. If you want to make a separate address you click new address and give it a label and it will create a new address for you.
If you click the transactions tab you will see all of the transactions you have made both sending and receiving. If you hover over the box to the left of the date/time of the transaction you will see how many confirms it has.
Backing up your wallet
The Litecoin-qt client while called a wallet by some isnt really a wallet. Its a client used to access your wallet. The actual wallet is a file called a wallet.dat. This file has the public and private keys that let you spend your coins. (More on this in another topic).
If you want to backup your wallet (YOU SHOULD) then you simply need to copy this wallet.dat file onto something else like a USB flash drive. I suggest making several copies and putting at least one off site from your computer like at a family members house or in a safety deposit box. Make sure when you do this that you COPY the file and NOT move it.
submitted by Edwardlots to litecoinforbeginners [link] [comments]

How long should it take for Bitcoin QT to catch up?

I downloaded the latest bootstrap.dat from here: https://bitcoin.org/en/download
Placed the completed bootstrap.dat into the data folder (Windows 8) and started Bitcoin QT. It ran for some time saying importing blocks and it has completed as far as I can see.
For the last 24 hours it has said: "Synchronizing with network ... 265 weeks behind"
The blocks folder is 14.1GB. The last block file seems to be getting modified regularly but I am surprised the overall status has not moved from 265 weeks. Its name is: blk00112.dat 14-02-06 5:35PM (about seven minutes ago)
submitted by Dimtar to Bitcoin [link] [comments]

Clearing up some misconceptions about full nodes | Chris Belcher | Feb 10 2016

Chris Belcher on Feb 10 2016:
I've been asked to post this to this mailing list too. It's time to
clear up some misconceptions floating around about full nodes.
=== Myth: There are only about 5500 full nodes worldwide ===
This number comes from this and similar sites: https://bitnodes.21.co/
and it measured by trying to probe every nodes on their open ports.
Problem is, not all nodes actually have open ports that can be probed.
Either because they are behind firewalls or because their users have
configured them to not listen for connections.
Nobody knows how many full nodes there are, since many people don't know
how to forward ports behind a firewall, and bandwidth can be costly, its
quite likely that the number of nodes with closed ports is at least
another several thousand.
Nodes with open ports are able to upload blocks to new full nodes. In
all other ways they are the same as nodes with closed ports. But because
open-port-nodes can be measured and closed-port-nodes cannot, some
members of the bitcoin community have been mistaken into believing that
open-port-nodes are that matters.
=== Myth: This number of nodes matters and/or is too low. ===
Nodes with open ports are useful to the bitcoin network because they
help bootstrap new nodes by uploading historical blocks, they are a
measure of bandwidth capacity. Right now there is no shortage of
bandwidth capacity, and if there was it could be easily added by renting
cloud servers.
The problem is not bandwidth or connections, but trust, security and
privacy. Let me explain.
Full nodes are able to check that all of bitcoin's rules are being
followed. Rules like following the inflation schedule, no double
spending, no spending of coins that don't belong to the holder of the
private key and all the other rules required to make bitcoin work (e.g.
difficulty)
Full nodes are what make bitcoin trustless. No longer do you have to
trust a financial institution like a bank or paypal, you can simply run
software on your own computer. To put simply, the only node that matters
is the one you use.
=== Myth: There is no incentive to run nodes, the network relies on
altruism ===
It is very much in the individual bitcoin's users rational self interest
to run a full node and use it as their wallet.
Using a full node as your wallet is the only way to know for sure that
none of bitcoin's rules have been broken. Rules like no coins were spent
not belonging to the owner, that no coins were spent twice, that no
inflation happens outside of the schedule and that all the rules needed
to make the system work are followed (e.g. difficulty.) All other kinds
of wallet involve trusting a third party server.
All these checks done by full nodes also increase the security. There
are many attacks possible against lightweight wallets that do not affect
full node wallets.
This is not just mindless paranoia, there have been real world examples
where full node users were unaffected by turmoil in the rest of the
bitcoin ecosystem. The 4th July 2015 accidental chain fork effected many
kinds of wallets. Here is the wiki page on this event
https://en.bitcoin.it/wiki/July_2015_chain_forks#Wallet_Advice
Notice how updated node software was completely unaffected by the fork.
All other wallets required either extra confirmations or checking that
the third-party institution was running the correct version.
Full nodes wallets are also currently the most private way to use
Bitcoin, with nobody else learning which bitcoin addresses belong to
you. All other lightweight wallets leak information about which
addresses are yours because they must query third-party servers. The
Electrum servers will know which addresses belong to you and can link
them together. Despite bloom filtering, lightweight wallets based on
BitcoinJ do not provide much privacy against nodes who connected
directly to the wallet or wiretappers.
For many use cases, such privacy may not be required. But an important
reason to run a full node and use it as a wallet is to get the full
privacy benefits.
=== Myth: I can just set up a node on a cloud server instance and leave
it ===
To get the benefits of running a full node, you must use it as your
wallet, preferably on hardware you control.
Most people who do this do not use a full node as their wallet.
Unfortunately because Bitcoin has a similar name to Bittorrent, some
people believe that upload capacity is the most important thing for a
healthy network. As I've explained above: bandwidth and connections are
not a problem today, trust, security and privacy are.
=== Myth: Running a full node is not recommended, most people should use
a lightweight client ===
This was common advice in 2012, but since then the full node software
has vastly improved in terms of user experience.
If you cannot spare the disk space to store the blockchain, you can
enable pruning as in:
https://bitcoin.org/en/release/v0.11.0#block-file-pruning. In Bitcoin
Core 0.12, pruning being enabled will leave the wallet enabled.
Altogether this should require less than 1.5GB of hard disk space.
If you cannot spare the bandwidth to upload blocks to other nodes, there
are number of options to reduce or eliminate the bandwidth requirement
found in https://bitcoin.org/en/full-node#reduce-traffic . These include
limiting connections, bandwidth targetting and disabling listening.
Bitcoin Core 0.12 has the new option -blocksonly, where the node will
not download unconfirmed transaction and only download new blocks. This
more than halves the bandwidth usage at the expense of not seeing
unconfirmed transactions.
Synchronizing the blockchain for a new node has improved since 2012 too.
Features like headers-first
(https://bitcoin.org/en/release/v0.10.0#faster-synchronization) and
libsecp256k1 have greatly improved the initial synchronization time.
It can be further improved by setting -dbcache=6000 which keeps more of
the UTXO set in memory. It reduces the amount of time reading from disk
and therefore speeds up synchronization. Tests showed that the entire
blockchain can now be synchronized in less than 3 and a half hours
(See
https://github.com/bitcoin/bitcoin/pull/6954#issuecomment-154993958)
Note that you'll need Bitcoin Core 0.12 or later to get all these
efficiency improvements.
=== How to run a full node as your wallet ===
I think every moderate user of bitcoin would benefit by running a full
node and using it as their wallet. There are several ways to do this.
(https://bitcoinarmory.com/) or JoinMarket
(https://github.com/AdamISZ/JMBinary/#jmbinary)
Multibit connecting only to your node running at home, Electrum
connecting only to your own Electrum server)
So what are you waiting for? The benefits are many, the downsides are
not that bad. The more people do this, the more robust and healthy the
bitcoin ecosystem is.
original: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-February/012435.html
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

Bitcoin ABC node can't synchronize passed the fork block. Would adding other Cash nodes explicitly on my peer list help?

I'm trying to get my Bitcoin ABC node, which is running behind Tor in case that makes any difference, to synchronize. But it can't get passed the fork point. What makes sense since all my peers seem to be BSCore nodes...
Is there a list of trustworthy Bitcoin Cash nodes I could manually add in order to get the good chain?
Also, for some reason, even though I added the -listen option, my node isn't going above 8 connections. Shouldn't it automatically configure a hidden service, or do I still need to do it manually?
This is the list of command line parameters I run my node with:
./bitcoin-qt -bind=127.0.0.1 -proxy=127.0.0.1:9050 -listen -datadir=PATH_TO_BITCOINCASH_DATADIR -checkblocks=1 
Finally, another question: I saw Bitcoin ABC has a PPA, but it uses the same package names of Bitcoin Unlimited, which I'm using to connect to the Bitcoin Settlement network. Names which come from BSCore packages, actually. Would you guys mind having a different package name like BitcoinXT has? (I'm not using them either because they haven't updated their PPA with the Cash release, and because I wanted to check on this ABC implementation)
Thanks!
submitted by VedadoAnonimato to btc [link] [comments]

Bitcoin qt not downloading blockchain

Hi /Bitcoin
I have a problem with my bitcoin qt client, I have used my wallet on the client to send and receive bitcoins several times, but recently it has just stopped downloading the blockchain, it is stuck on 282 weeks, since I have bitcoins on the wallet I'm not really happy to lose it.
Here is a list of what I have tried
  1. Downloading the blockchain (bootstrap.dat) from a torrent and moving it to C:\Users\"USER"\AppData\Roaming\Bitcoin, but this just renames the file to bootstrap.dat.old after a while.
  2. Downloading the new bitcoin qt version(v0.9.1.0)
  3. Letting it download for several hours
Nothing works and it just keeps saying "Synchronizing with network" and "282 weeks behind"
submitted by StuckInProcess to Bitcoin [link] [comments]

How to Nvidia GPU mine CannaCoin on Windows

I thought would put together another tutorial for anyone looking to get started with mining CannaCoin's. it is a bit of a plug for my own mining pool ccn.surmine.com, but you're free to mine of another pool, the process is pretty much the same.
Once broken down into individual parts the whole process is quite simple and should only take less than half an hour to start mining.
The process can be broken down into the following stages:

Stage 1: Setup CannaCoin Wallet

  1. Go to [cannacoin.cc](cannacoin.cc) , click on download wallet then Download and select the windows client and save to your PC. Setup Image 1
  2. Open the CannaCoin wallet you downloaded and browse to the Cannacoin-QT folder. Setup Image 2
  3. Drag the contents into the Cannacoin folder you created on your C drive. Setup Image 3
  4. Double Click cannacoin-qt, you will asked to allow access to through your firewall, click "Allow access". Setup Image 4
  5. Your CannaCoin wallet is now running. It may show "No block source available" in the bottom left corner, give it 15 mins and it should connect to the network, if not check your firewall settings. Once you see "Synchronizing with network" in the bottom left you know you are good. Setup Image 5
  6. Click the Receive tab and write down your CannaCoin address, this is your address to receive coins. Setup Image 6

Stage 2: Create Mining Pool account.

There are multiple pools you can choose from but as I run a mining pool I might as well plug my own ccn.suremine.com , If you would like to use another the following steps will work with another pool.
  1. Point your browser at ccn.suremine.com, in the top right hand corner of the page click "Guest" then "Sign Up". Account Image 1
  2. Complete the registration form, make sure you choose a good password that is unique to this poll, write down the PIN, as if you lose it you lose your coins! Account Image 2
  3. Check your email and Click the email verification link, if you can't see the email check your spam folder.
  4. Login to your account and Click "My Account" then click "Edit Account" On the Left Hand Nav. Enter your PIN and click unlock. This will create a confirmation email you will need to click. Account Image 3
  5. Check your email and Click the email verification link, if you can't see the email check your spam folder.
    • Set your payment address ( the one you copied down when you created your wallet).
    • Set your Donation Percentage ( this helps keep the pool running).
    • Set your automatic payout threshold ( low to start with to see the funds come through).
    • Insert your pin again.
    • Click Update Account. Account Image 4
  6. On the Left Hand Navigation bar click "My Account" then "My Workers". Enter a worker name and password (these can be anything you like). Account Image 5
  7. Click Add New Worker and the page will refresh with your worker details, note both the worker login and worker password down. you will need both of these later. Account Image 7

Stage 3: Install CPU Miner

Before you install the GPU Mining Application you want to make sure you are running off the latest Nvidia Drivers.
  1. Go to the Cuda miner page on BitCoin talk and download the latest package.
  2. Create a folder in C:/ called GPUminer. Install Image 1
  3. Once Downloaded, unzip the file, go into to cduaminer-2014-02-28 then into x86 and drag the contents of the zip file into the GPUminer folder. By the time you're doing this the date of 2014-02-28 may have changed to a newer version, that's good news!) Install Image 2
  4. Open up notepad and insert the following text, you want to replace the worker login and the worker password with the values you noted down earlier. cudaminer.exe -o stratum+tcp://uk.suremine.com:6666 -u USERACCOUNT.WORKERUSER -p WORKERPASS pause Install Image 3
  5. Select File > Save as then save the file to c:/GPUmine as gpuminer.bat. Install Image 4

Stage 4: Mine

  1. From the C:/GPUminer double click gpuminer.bat this will open a window. after a few minutes you should start seeing accepted transactions. All accepted transactions are good. Mine Image 1
Debugging

Performance Tuning

If you are looking to get the most out of your Nvidia card you can update gpuminer.bat with config from the Nvidia Comparison Table
submitted by suremine to cannacoin [link] [comments]

Bootstrapping a bitcoin core wallet

Hi,
I haven't run my wallet (bitcoin-qt) in quite some time and today I decided to open it up. My local copy of the blockchain is 40 weeks behind (yeah, life get's in the way sometimes), and it looks like it will take several days to get up to date.
So I've been looking for the bootstrap.dat file and had a hard time finding it. According to a quora article the reason it's no longer available is that since version 0.10.0 synchronization is faster than downloading and processing the bootstrap file.
I'm running the latest version (0.13.1) and in about 3 hours it got from 40 to 39 weeks behind. I do have quite a hefty pipe at 250 Mbps, so bandwidth shouldn't be an issue. I thought that maybe the new "fast synch" doesn't play well with an existing blockchain and only kicks in when it starts from zero, so I renamed the bitcoin dir and started from a new empty one. After seeing it crawl through a couple thousand blocks at roughly the same speed it did with the 40 week-old blockchain, it was clear it wouldn't end in a reasonable time.
So I'm now downloading a bootstrap.dat file I found in this bitcointalk post, but it could very well be a bogus or invalid file. Of course if that's the case it won't sync with the network, but it's a lot of bandwidth and time just to find out, isn't it?
So, my question is: Why isn't the fast synch working? How are unsuspecting newbies supposed to use the core client? If the community is generating boostrap files, why not publish them where they can easily be found?
Meh, I'll have it working in a few hours, but this experience put me in a foul mood. Sorry for the rant.
submitted by jungle to Bitcoin [link] [comments]

Bitcoin Core 0.10.0 released | Wladimir | Feb 16 2015

Wladimir on Feb 16 2015:
Bitcoin Core version 0.10.0 is now available from:
https://bitcoin.org/bin/0.10.0/
This is a new major version release, bringing both new features and
bug fixes.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues
The whole distribution is also available as torrent:
https://bitcoin.org/bin/0.10.0/bitcoin-0.10.0.torrent
magnet:?xt=urn:btih:170c61fe09dafecfbb97cb4dccd32173383f4e68&dn;=0.10.0&tr;=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.publicbt.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.ccc.de%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr;=udp%3A%2F%2Fopen.demonii.com%3A1337&ws;=https%3A%2F%2Fbitcoin.org%2Fbin%2F
Upgrading and downgrading

How to Upgrade
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 (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or
bitcoind/bitcoin-qt (on Linux).
Downgrading warning
Because release 0.10.0 makes use of headers-first synchronization and parallel
block download (see further), the block files and databases are not
backwards-compatible with older versions of Bitcoin Core or other software:
  • Blocks will be stored on disk out of order (in the order they are
received, really), which makes it incompatible with some tools or
other programs. Reindexing using earlier versions will also not work
anymore as a result of this.
  • The block index database will now hold headers for which no block is
stored on disk, which earlier versions won't support.
If you want to be able to downgrade smoothly, make a backup of your entire data
directory. Without this your node will need start syncing (or importing from
bootstrap.dat) anew afterwards. It is possible that the data from a completely
synchronised 0.10 node may be usable in older versions as-is, but this is not
supported and may break as soon as the older version attempts to reindex.
This does not affect wallet forward or backward compatibility.
Notable changes

Faster synchronization
Bitcoin Core now uses 'headers-first synchronization'. This means that we first
ask peers for block headers (a total of 27 megabytes, as of December 2014) and
validate those. In a second stage, when the headers have been discovered, we
download the blocks. However, as we already know about the whole chain in
advance, the blocks can be downloaded in parallel from all available peers.
In practice, this means a much faster and more robust synchronization. On
recent hardware with a decent network link, it can be as little as 3 hours
for an initial full synchronization. You may notice a slower progress in the
very first few minutes, when headers are still being fetched and verified, but
it should gain speed afterwards.
A few RPCs were added/updated as a result of this:
  • getblockchaininfo now returns the number of validated headers in addition to
the number of validated blocks.
  • getpeerinfo lists both the number of blocks and headers we know we have in
common with each peer. While synchronizing, the heights of the blocks that we
have requested from peers (but haven't received yet) are also listed as
'inflight'.
  • A new RPC getchaintips lists all known branches of the block chain,
including those we only have headers for.
Transaction fee changes
This release automatically estimates how high a transaction fee (or how
high a priority) transactions require to be confirmed quickly. The default
settings will create transactions that confirm quickly; see the new
'txconfirmtarget' setting to control the tradeoff between fees and
confirmation times. Fees are added by default unless the 'sendfreetransactions'
setting is enabled.
Prior releases used hard-coded fees (and priorities), and would
sometimes create transactions that took a very long time to confirm.
Statistics used to estimate fees and priorities are saved in the
data directory in the fee_estimates.dat file just before
program shutdown, and are read in at startup.
New command line options for transaction fee changes:
  • -txconfirmtarget=n : create transactions that have enough fees (or priority)
so they are likely to begin confirmation within n blocks (default: 1). This setting
is over-ridden by the -paytxfee option.
  • -sendfreetransactions : Send transactions as zero-fee transactions if possible
(default: 0)
New RPC commands for fee estimation:
  • estimatefee nblocks : Returns approximate fee-per-1,000-bytes needed for
a transaction to begin confirmation within nblocks. Returns -1 if not enough
transactions have been observed to compute a good estimate.
  • estimatepriority nblocks : Returns approximate priority needed for
a zero-fee transaction to begin confirmation within nblocks. Returns -1 if not
enough free transactions have been observed to compute a good
estimate.
RPC access control changes
Subnet matching for the purpose of access control is now done
by matching the binary network address, instead of with string wildcard matching.
For the user this means that -rpcallowip takes a subnet specification, which can be
  • a single IP address (e.g. 1.2.3.4 or fe80::0012:3456:789a:bcde)
  • a network/CIDR (e.g. 1.2.3.0/24 or fe80::0000/64)
  • a network/netmask (e.g. 1.2.3.4/255.255.255.0 or fe80::0012:3456:789a:bcde/ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff)
An arbitrary number of -rpcallow arguments can be given. An incoming connection will be accepted if its origin address
matches one of them.
For example:
| 0.9.x and before | 0.10.x |
|--------------------------------------------|---------------------------------------|
| -rpcallowip=192.168.1.1 | -rpcallowip=192.168.1.1 (unchanged) |
| -rpcallowip=192.168.1.* | -rpcallowip=192.168.1.0/24 |
| -rpcallowip=192.168.* | -rpcallowip=192.168.0.0/16 |
| -rpcallowip=* (dangerous!) | -rpcallowip=::/0 (still dangerous!) |
Using wildcards will result in the rule being rejected with the following error in debug.log:
 Error: Invalid -rpcallowip subnet specification: *. Valid are a single IP (e.g. 1.2.3.4), a network/netmask (e.g. 1.2.3.4/255.255.255.0) or a network/CIDR (e.g. 1.2.3.4/24). 
REST interface
A new HTTP API is exposed when running with the -rest flag, which allows
unauthenticated access to public node data.
It is served on the same port as RPC, but does not need a password, and uses
plain HTTP instead of JSON-RPC.
Assuming a local RPC server running on port 8332, it is possible to request:
In every case, EXT can be bin (for raw binary data), hex (for hex-encoded
binary) or json.
For more details, see the doc/REST-interface.md document in the repository.
RPC Server "Warm-Up" Mode
The RPC server is started earlier now, before most of the expensive
intialisations like loading the block index. It is available now almost
immediately after starting the process. However, until all initialisations
are done, it always returns an immediate error with code -28 to all calls.
This new behaviour can be useful for clients to know that a server is already
started and will be available soon (for instance, so that they do not
have to start it themselves).
Improved signing security
For 0.10 the security of signing against unusual attacks has been
improved by making the signatures constant time and deterministic.
This change is a result of switching signing to use libsecp256k1
instead of OpenSSL. Libsecp256k1 is a cryptographic library
optimized for the curve Bitcoin uses which was created by Bitcoin
Core developer Pieter Wuille.
There exist attacks[1] against most ECC implementations where an
attacker on shared virtual machine hardware could extract a private
key if they could cause a target to sign using the same key hundreds
of times. While using shared hosts and reusing keys are inadvisable
for other reasons, it's a better practice to avoid the exposure.
OpenSSL has code in their source repository for derandomization
and reduction in timing leaks that we've eagerly wanted to use for a
long time, but this functionality has still not made its
way into a released version of OpenSSL. Libsecp256k1 achieves
significantly stronger protection: As far as we're aware this is
the only deployed implementation of constant time signing for
the curve Bitcoin uses and we have reason to believe that
libsecp256k1 is better tested and more thoroughly reviewed
than the implementation in OpenSSL.
[1] https://eprint.iacr.org/2014/161.pdf
Watch-only wallet support
The wallet can now track transactions to and from wallets for which you know
all addresses (or scripts), even without the private keys.
This can be used to track payments without needing the private keys online on a
possibly vulnerable system. In addition, it can help for (manual) construction
of multisig transactions where you are only one of the signers.
One new RPC, importaddress, is added which functions similarly to
importprivkey, but instead takes an address or script (in hexadecimal) as
argument. After using it, outputs credited to this address or script are
considered to be received, and transactions consuming these outputs will be
considered to be sent.
The following RPCs have optional support for watch-only:
getbalance, listreceivedbyaddress, listreceivedbyaccount,
listtransactions, listaccounts, listsinceblock, gettransaction. See the
RPC documentation for those methods for more information.
Compared to using getrawtransaction, this mechanism does not require
-txindex, scales better, integrates better with the wallet, and is compatible
with future block chain pruning functionality. It does mean that all relevant
addresses need to added to the wallet before the payment, though.
Consensus library
Starting from 0.10.0, the Bitcoin Core distribution includes a consensus library.
The purpose of this library is to make the verification functionality that is
critical to Bitcoin's consensus available to other applications, e.g. to language
bindings such as [python-bitcoinlib](https://pypi.python.org/pypi/python-bitcoinlib) or
alternative node implementations.
This library is called libbitcoinconsensus.so (or, .dll for Windows).
Its interface is defined in the C header [bitcoinconsensus.h](https://github.com/bitcoin/bitcoin/blob/0.10/src/script/bitcoinconsensus.h).
In its initial version the API includes two functions:
  • bitcoinconsensus_verify_script verifies a script. It returns whether the indicated input of the provided serialized transaction
correctly spends the passed scriptPubKey under additional constraints indicated by flags
  • bitcoinconsensus_version returns the API version, currently at an experimental 0
The functionality is planned to be extended to e.g. UTXO management in upcoming releases, but the interface
for existing methods should remain stable.
Standard script rules relaxed for P2SH addresses
The IsStandard() rules have been almost completely removed for P2SH
redemption scripts, allowing applications to make use of any valid
script type, such as "n-of-m OR y", hash-locked oracle addresses, etc.
While the Bitcoin protocol has always supported these types of script,
actually using them on mainnet has been previously inconvenient as
standard Bitcoin Core nodes wouldn't relay them to miners, nor would
most miners include them in blocks they mined.
bitcoin-tx
It has been observed that many of the RPC functions offered by bitcoind are
"pure functions", and operate independently of the bitcoind wallet. This
included many of the RPC "raw transaction" API functions, such as
createrawtransaction.
bitcoin-tx is a newly introduced command line utility designed to enable easy
manipulation of bitcoin transactions. A summary of its operation may be
obtained via "bitcoin-tx --help" Transactions may be created or signed in a
manner similar to the RPC raw tx API. Transactions may be updated, deleting
inputs or outputs, or appending new inputs and outputs. Custom scripts may be
easily composed using a simple text notation, borrowed from the bitcoin test
suite.
This tool may be used for experimenting with new transaction types, signing
multi-party transactions, and many other uses. Long term, the goal is to
deprecate and remove "pure function" RPC API calls, as those do not require a
server round-trip to execute.
Other utilities "bitcoin-key" and "bitcoin-script" have been proposed, making
key and script operations easily accessible via command line.
Mining and relay policy enhancements
Bitcoin Core's block templates are now for version 3 blocks only, and any mining
software relying on its getblocktemplate must be updated in parallel to use
libblkmaker either version 0.4.2 or any version from 0.5.1 onward.
If you are solo mining, this will affect you the moment you upgrade Bitcoin
Core, which must be done prior to BIP66 achieving its 951/1001 status.
If you are mining with the stratum mining protocol: this does not affect you.
If you are mining with the getblocktemplate protocol to a pool: this will affect
you at the pool operator's discretion, which must be no later than BIP66
achieving its 951/1001 status.
The prioritisetransaction RPC method has been added to enable miners to
manipulate the priority of transactions on an individual basis.
Bitcoin Core now supports BIP 22 long polling, so mining software can be
notified immediately of new templates rather than having to poll periodically.
Support for BIP 23 block proposals is now available in Bitcoin Core's
getblocktemplate method. This enables miners to check the basic validity of
their next block before expending work on it, reducing risks of accidental
hardforks or mining invalid blocks.
Two new options to control mining policy:
  • -datacarrier=0/1 : Relay and mine "data carrier" (OP_RETURN) transactions
if this is 1.
  • -datacarriersize=n : Maximum size, in bytes, we consider acceptable for
"data carrier" outputs.
The relay policy has changed to more properly implement the desired behavior of not
relaying free (or very low fee) transactions unless they have a priority above the
AllowFreeThreshold(), in which case they are relayed subject to the rate limiter.
BIP 66: strict DER encoding for signatures
Bitcoin Core 0.10 implements BIP 66, which introduces block version 3, and a new
consensus rule, which prohibits non-DER signatures. Such transactions have been
non-standard since Bitcoin v0.8.0 (released in February 2013), but were
technically still permitted inside blocks.
This change breaks the dependency on OpenSSL's signature parsing, and is
required if implementations would want to remove all of OpenSSL from the
consensus code.
The same miner-voting mechanism as in BIP 34 is used: when 751 out of a
sequence of 1001 blocks have version number 3 or higher, the new consensus
rule becomes active for those blocks. When 951 out of a sequence of 1001
blocks have version number 3 or higher, it becomes mandatory for all blocks.
Backward compatibility with current mining software is NOT provided, thus miners
should read the first paragraph of "Mining and relay policy enhancements" above.
0.10.0 Change log

Detailed release notes follow. This overview includes changes that affect external
behavior, not code moves, refactors or string updates.
RPC:
  • f923c07 Support IPv6 lookup in bitcoin-cli even when IPv6 only bound on localhost
  • b641c9c Fix addnode "onetry": Connect with OpenNetworkConnection
  • 171ca77 estimatefee / estimatepriority RPC methods
  • b750cf1 Remove cli functionality from bitcoind
  • f6984e8 Add "chain" to getmininginfo, improve help in getblockchaininfo
  • 99ddc6c Add nLocalServices info to RPC getinfo
  • cf0c47b Remove getwork() RPC call
  • 2a72d45 prioritisetransaction
  • e44fea5 Add an option -datacarrier to allow users to disable relaying/mining data carrier transactions
  • 2ec5a3d Prevent easy RPC memory exhaustion attack
  • d4640d7 Added argument to getbalance to include watchonly addresses and fixed errors in balance calculation
  • 83f3543 Added argument to listaccounts to include watchonly addresses
  • 952877e Showing 'involvesWatchonly' property for transactions returned by 'listtransactions' and 'listsinceblock'. It is only appended when the transaction involves a watchonly address
  • d7d5d23 Added argument to listtransactions and listsinceblock to include watchonly addresses
  • f87ba3d added includeWatchonly argument to 'gettransaction' because it affects balance calculation
  • 0fa2f88 added includedWatchonly argument to listreceivedbyaddress/...account
  • 6c37f7f getrawchangeaddress: fail when keypool exhausted and wallet locked
  • ff6a7af getblocktemplate: longpolling support
  • c4a321f Add peerid to getpeerinfo to allow correlation with the logs
  • 1b4568c Add vout to ListTransactions output
  • b33bd7a Implement "getchaintips" RPC command to monitor blockchain forks
  • 733177e Remove size limit in RPC client, keep it in server
  • 6b5b7cb Categorize rpc help overview
  • 6f2c26a Closely track mempool byte total. Add "getmempoolinfo" RPC
  • aa82795 Add detailed network info to getnetworkinfo RPC
  • 01094bd Don't reveal whether password is <20 or >20 characters in RPC
  • 57153d4 rpc: Compute number of confirmations of a block from block height
  • ff36cbe getnetworkinfo: export local node's client sub-version string
  • d14d7de SanitizeString: allow '(' and ')'
  • 31d6390 Fixed setaccount accepting foreign address
  • b5ec5fe update getnetworkinfo help with subversion
  • ad6e601 RPC additions after headers-first
  • 33dfbf5 rpc: Fix leveldb iterator leak, and flush before gettxoutsetinfo
  • 2aa6329 Enable customising node policy for datacarrier data size with a -datacarriersize option
  • f877aaa submitblock: Use a temporary CValidationState to determine accurately the outcome of ProcessBlock
  • e69a587 submitblock: Support for returning specific rejection reasons
  • af82884 Add "warmup mode" for RPC server
  • e2655e0 Add unauthenticated HTTP REST interface to public blockchain data
  • 683dc40 Disable SSLv3 (in favor of TLS) for the RPC client and server
  • 44b4c0d signrawtransaction: validate private key
  • 9765a50 Implement BIP 23 Block Proposal
  • f9de17e Add warning comment to getinfo
Command-line options:
  • ee21912 Use netmasks instead of wildcards for IP address matching
  • deb3572 Add -rpcbind option to allow binding RPC port on a specific interface
  • 96b733e Add -version option to get just the version
  • 1569353 Add -stopafterblockimport option
  • 77cbd46 Let -zapwallettxes recover transaction meta data
  • 1c750db remove -tor compatibility code (only allow -onion)
  • 4aaa017 rework help messages for fee-related options
  • 4278b1d Clarify error message when invalid -rpcallowip
  • 6b407e4 -datadir is now allowed in config files
  • bdd5b58 Add option -sysperms to disable 077 umask (create new files with system default umask)
  • cbe39a3 Add "bitcoin-tx" command line utility and supporting modules
  • dbca89b Trigger -alertnotify if network is upgrading without you
  • ad96e7c Make -reindex cope with out-of-order blocks
  • 16d5194 Skip reindexed blocks individually
  • ec01243 --tracerpc option for regression tests
  • f654f00 Change -genproclimit default to 1
  • 3c77714 Make -proxy set all network types, avoiding a connect leak
  • 57be955 Remove -printblock, -printblocktree, and -printblockindex
  • ad3d208 remove -maxorphanblocks config parameter since it is no longer functional
Block and transaction handling:
  • 7a0e84d ProcessGetData(): abort if a block file is missing from disk
  • 8c93bf4 LoadBlockIndexDB(): Require block db reindex if any blk*.dat files are missing
  • 77339e5 Get rid of the static chainMostWork (optimization)
  • 4e0eed8 Allow ActivateBestChain to release its lock on cs_main
  • 18e7216 Push cs_mains down in ProcessBlock
  • fa126ef Avoid undefined behavior using CFlatData in CScript serialization
  • 7f3b4e9 Relax IsStandard rules for pay-to-script-hash transactions
  • c9a0918 Add a skiplist to the CBlockIndex structure
  • bc42503 Use unordered_map for CCoinsViewCache with salted hash (optimization)
  • d4d3fbd Do not flush the cache after every block outside of IBD (optimization)
  • ad08d0b Bugfix: make CCoinsViewMemPool support pruned entries in underlying cache
  • 5734d4d Only remove actualy failed blocks from setBlockIndexValid
  • d70bc52 Rework block processing benchmark code
  • 714a3e6 Only keep setBlockIndexValid entries that are possible improvements
  • ea100c7 Reduce maximum coinscache size during verification (reduce memory usage)
  • 4fad8e6 Reject transactions with excessive numbers of sigops
  • b0875eb Allow BatchWrite to destroy its input, reducing copying (optimization)
  • 92bb6f2 Bypass reloading blocks from disk (optimization)
  • 2e28031 Perform CVerifyDB on pcoinsdbview instead of pcoinsTip (reduce memory usage)
  • ab15b2e Avoid copying undo data (optimization)
  • 341735e Headers-first synchronization
  • afc32c5 Fix rebuild-chainstate feature and improve its performance
  • e11b2ce Fix large reorgs
  • ed6d1a2 Keep information about all block files in memory
  • a48f2d6 Abstract context-dependent block checking from acceptance
  • 7e615f5 Fixed mempool sync after sending a transaction
  • 51ce901 Improve chainstate/blockindex disk writing policy
  • a206950 Introduce separate flushing modes
  • 9ec75c5 Add a locking mechanism to IsInitialBlockDownload to ensure it never goes from false to true
  • 868d041 Remove coinbase-dependant transactions during reorg
  • 723d12c Remove txn which are invalidated by coinbase maturity during reorg
  • 0cb8763 Check against MANDATORY flags prior to accepting to mempool
  • 8446262 Reject headers that build on an invalid parent
  • 008138c Bugfix: only track UTXO modification after lookup
P2P protocol and network code:
  • f80cffa Do not trigger a DoS ban if SCRIPT_VERIFY_NULLDUMMY fails
  • c30329a Add testnet DNS seed of Alex Kotenko
  • 45a4baf Add testnet DNS seed of Andreas Schildbach
  • f1920e8 Ping automatically every 2 minutes (unconditionally)
  • 806fd19 Allocate receive buffers in on the fly
  • 6ecf3ed Display unknown commands received
  • aa81564 Track peers' available blocks
  • caf6150 Use async name resolving to improve net thread responsiveness
  • 9f4da19 Use pong receive time rather than processing time
  • 0127a9b remove SOCKS4 support from core and GUI, use SOCKS5
  • 40f5cb8 Send rejects and apply DoS scoring for errors in direct block validation
  • dc942e6 Introduce whitelisted peers
  • c994d2e prevent SOCKET leak in BindListenPort()
  • a60120e Add built-in seeds for .onion
  • 60dc8e4 Allow -onlynet=onion to be used
  • 3a56de7 addrman: Do not propagate obviously poor addresses onto the network
  • 6050ab6 netbase: Make SOCKS5 negotiation interruptible
  • 604ee2a Remove tx from AlreadyAskedFor list once we receive it, not when we process it
  • efad808 Avoid reject message feedback loops
  • 71697f9 Separate protocol versioning from clientversion
  • 20a5f61 Don't relay alerts to peers before version negotiation
  • b4ee0bd Introduce preferred download peers
  • 845c86d Do not use third party services for IP detection
  • 12a49ca Limit the number of new addressses to accumulate
  • 35e408f Regard connection failures as attempt for addrman
  • a3a7317 Introduce 10 minute block download timeout
  • 3022e7d Require sufficent priority for relay of free transactions
  • 58fda4d Update seed IPs, based on bitcoin.sipa.be crawler data
  • 18021d0 Remove bitnodes.io from dnsseeds.
Validation:
  • 6fd7ef2 Also switch the (unused) verification code to low-s instead of even-s
  • 584a358 Do merkle root and txid duplicates check simultaneously
  • 217a5c9 When transaction outputs exceed inputs, show the offending amounts so as to aid debugging
  • f74fc9b Print input index when signature validation fails, to aid debugging
  • 6fd59ee script.h: set_vch() should shift a >32 bit value
  • d752ba8 Add SCRIPT_VERIFY_SIGPUSHONLY (BIP62 rule 2) (test only)
  • 698c6ab Add SCRIPT_VERIFY_MINIMALDATA (BIP62 rules 3 and 4) (test only)
  • ab9edbd script: create sane error return codes for script validation and remove logging
  • 219a147 script: check ScriptError values in script tests
  • 0391423 Discourage NOPs reserved for soft-fork upgrades
  • 98b135f Make STRICTENC invalid pubkeys fail the script rather than the opcode
  • 307f7d4 Report script evaluation failures in log and reject messages
  • ace39db consensus: guard against openssl's new strict DER checks
  • 12b7c44 Improve robustness of DER recoding code
  • 76ce5c8 fail immediately on an empty signature
Build system:
  • f25e3ad Fix build in OS X 10.9
  • 65e8ba4 build: Switch to non-recursive make
  • 460b32d build: fix broken boost chrono check on some platforms
  • 9ce0774 build: Fix windows configure when using --with-qt-libdir
  • ea96475 build: Add mention of --disable-wallet to bdb48 error messages
  • 1dec09b depends: add shared dependency builder
  • c101c76 build: Add --with-utils (bitcoin-cli and bitcoin-tx, default=yes). Help string consistency tweaks. Target sanity check fix
  • e432a5f build: add option for reducing exports (v2)
  • 6134b43 Fixing condition 'sabotaging' MSVC build
  • af0bd5e osx: fix signing to make Gatekeeper happy (again)
  • a7d1f03 build: fix dynamic boost check when --with-boost= is used
  • d5fd094 build: fix qt test build when libprotobuf is in a non-standard path
  • 2cf5f16 Add libbitcoinconsensus library
  • 914868a build: add a deterministic dmg signer
  • 2d375fe depends: bump openssl to 1.0.1k
  • b7a4ecc Build: Only check for boost when building code that requires it
Wallet:
  • b33d1f5 Use fee/priority estimates in wallet CreateTransaction
  • 4b7b1bb Sanity checks for estimates
  • c898846 Add support for watch-only addresses
  • d5087d1 Use script matching rather than destination matching for watch-only
  • d88af56 Fee fixes
  • a35b55b Dont run full check every time we decrypt wallet
  • 3a7c348 Fix make_change to not create half-satoshis
  • f606bb9 fix a possible memory leak in CWalletDB::Recover
  • 870da77 fix possible memory leaks in CWallet::EncryptWallet
  • ccca27a Watch-only fixes
  • 9b1627d [Wallet] Reduce minTxFee for transaction creation to 1000 satoshis
  • a53fd41 Deterministic signing
  • 15ad0b5 Apply AreSane() checks to the fees from the network
  • 11855c1 Enforce minRelayTxFee on wallet created tx and add a maxtxfee option
GUI:
  • c21c74b osx: Fix missing dock menu with qt5
  • b90711c Fix Transaction details shows wrong To:
  • 516053c Make links in 'About Bitcoin Core' clickable
  • bdc83e8 Ensure payment request network matches client network
  • 65f78a1 Add GUI view of peer information
  • 06a91d9 VerifyDB progress reporting
  • fe6bff2 Add BerkeleyDB version info to RPCConsole
  • b917555 PeerTableModel: Fix potential deadlock. #4296
  • dff0e3b Improve rpc console history behavior
  • 95a9383 Remove CENT-fee-rule from coin control completely
  • 56b07d2 Allow setting listen via GUI
  • d95ba75 Log messages with type>QtDebugMsg as non-debug
  • 8969828 New status bar Unit Display Control and related changes
  • 674c070 seed OpenSSL PNRG with Windows event data
  • 509f926 Payment request parsing on startup now only changes network if a valid network name is specified
  • acd432b Prevent balloon-spam after rescan
  • 7007402 Implement SI-style (thin space) thoudands separator
  • 91cce17 Use fixed-point arithmetic in amount spinbox
  • bdba2dd Remove an obscure option no-one cares about
  • bd0aa10 Replace the temporary file hack currently used to change Bitcoin-Qt's dock icon (OS X) with a buffer-based solution
  • 94e1b9e Re-work overviewpage UI
  • 8bfdc9a Better looking trayicon
  • b197bf3 disable tray interactions when client model set to 0
  • 1c5f0af Add column Watch-only to transactions list
  • 21f139b Fix tablet crash. closes #4854
  • e84843c Broken addresses on command line no longer trigger testnet
  • a49f11d Change splash screen to normal window
  • 1f9be98 Disable App Nap on OSX 10.9+
  • 27c3e91 Add proxy to options overridden if necessary
  • 4bd1185 Allow "emergency" shutdown during startup
  • d52f072 Don't show wallet options in the preferences menu when running with -disablewallet
  • 6093aa1 Qt: QProgressBar CPU-Issue workaround
  • 0ed9675 [Wallet] Add global boolean whether to send free transactions (default=true)
  • ed3e5e4 [Wallet] Add global boolean whether to pay at least the custom fee (default=true)
  • e7876b2 [Wallet] Prevent user from paying a non-sense fee
  • c1c9d5b Add Smartfee to GUI
  • e0a25c5 Make askpassphrase dialog behave more sanely
  • 94b362d On close of splashscreen interrupt verifyDB
  • b790d13 English translation update
  • 8543b0d Correct tooltip on address book page
Tests:
  • b41e594 Fix script test handling of empty scripts
  • d3a33fc Test CHECKMULTISIG with m == 0 and n == 0
  • 29c1749 Let tx (in)valid tests use any SCRIPT_VERIFY flag
  • 6380180 Add rejection of non-null CHECKMULTISIG dummy values
  • 21bf3d2 Add tests for BoostAsioToCNetAddr
  • b5ad5e7 Add Python test for -rpcbind and -rpcallowip
  • 9ec0306 Add CODESEPARATOFindAndDelete() tests
  • 75ebced Added many rpc wallet tests
  • 0193fb8 Allow multiple regression tests to run at once
  • 92a6220 Hook up sanity checks
  • 3820e01 Extend and move all crypto tests to crypto_tests.cpp
  • 3f9a019 added list/get received by address/ account tests
  • a90689f Remove timing-based signature cache unit test
  • 236982c Add skiplist unit tests
  • f4b00be Add CChain::GetLocator() unit test
  • b45a6e8 Add test for getblocktemplate longpolling
  • cdf305e Set -discover=0 in regtest framework
  • ed02282 additional test for OP_SIZE in script_valid.json
  • 0072d98 script tests: BOOLAND, BOOLOR decode to integer
  • 833ff16 script tests: values that overflow to 0 are true
  • 4cac5db script tests: value with trailing 0x00 is true
  • 89101c6 script test: test case for 5-byte bools
  • d2d9dc0 script tests: add tests for CHECKMULTISIG limits
  • d789386 Add "it works" test for bitcoin-tx
  • df4d61e Add bitcoin-tx tests
  • aa41ac2 Test IsPushOnly() with invalid push
  • 6022b5d Make script_{valid,invalid}.json validation flags configurable
  • 8138cbe Add automatic script test generation, and actual checksig tests
  • ed27e53 Add coins_tests with a large randomized CCoinViewCache test
  • 9df9cf5 Make SCRIPT_VERIFY_STRICTENC compatible with BIP62
  • dcb9846 Extend getchaintips RPC test
  • 554147a Ensure MINIMALDATA invalid tests can only fail one way
  • dfeec18 Test every numeric-accepting opcode for correct handling of the numeric minimal encoding rule
  • 2b62e17 Clearly separate PUSHDATA and numeric argument MINIMALDATA tests
  • 16d78bd Add valid invert of invalid every numeric opcode tests
  • f635269 tests: enable alertnotify test for Windows
  • 7a41614 tests: allow rpc-tests to get filenames for bitcoind and bitcoin-cli from the environment
  • 5122ea7 tests: fix forknotify.py on windows
  • fa7f8cd tests: remove old pull-tester scripts
  • 7667850 tests: replace the old (unused since Travis) tests with new rpc test scripts
  • f4e0aef Do signature-s negation inside the tests
  • 1837987 Optimize -regtest setgenerate block generation
  • 2db4c8a Fix node ranges in the test framework
  • a8b2ce5 regression test only setmocktime RPC call
  • daf03e7 RPC tests: create initial chain with specific timestamps
  • 8656dbb Port/fix txnmall.sh regression test
  • ca81587 Test the exact order of CHECKMULTISIG sig/pubkey evaluation
  • 7357893 Prioritize and display -testsafemode status in UI
  • f321d6b Add key generation/verification to ECC sanity check
  • 132ea9b miner_tests: Disable checkpoints so they don't fail the subsidy-change test
  • bc6cb41 QA RPC tests: Add tests block block proposals
  • f67a9ce Use deterministically generated script tests
  • 11d7a7d [RPC] add rpc-test for http keep-alive (persistent connections)
  • 34318d7 RPC-test based on invalidateblock for mempool coinbase spends
  • 76ec867 Use actually valid transactions for script tests
  • c8589bf Add actual signature tests
  • e2677d7 Fix smartfees test for change to relay policy
  • 263b65e tests: run sanity checks in tests too
Miscellaneous:
  • 122549f Fix incorrect checkpoint data for testnet3
  • 5bd02cf Log used config file to debug.log on startup
  • 68ba85f Updated Debian example bitcoin.conf with config from wiki + removed some cruft and updated comments
  • e5ee8f0 Remove -beta suffix
  • 38405ac Add comment regarding experimental-use service bits
  • be873f6 Issue warning if collecting RandSeed data failed
  • 8ae973c Allocate more space if necessary in RandSeedAddPerfMon
  • 675bcd5 Correct comment for 15-of-15 p2sh script size
  • fda3fed libsecp256k1 integration
  • 2e36866 Show nodeid instead of addresses in log (for anonymity) unless otherwise requested
  • cd01a5e Enable paranoid corruption checks in LevelDB >= 1.16
  • 9365937 Add comment about never updating nTimeOffset past 199 samples
  • 403c1bf contrib: remove getwork-based pyminer (as getwork API call has been removed)
  • 0c3e101 contrib: Added systemd .service file in order to help distributions integrate bitcoind
  • 0a0878d doc: Add new DNSseed policy
  • 2887bff Update coding style and add .clang-format
  • 5cbda4f Changed LevelDB cursors to use scoped pointers to ensure destruction when going out of scope
  • b4a72a7 contrib/linearize: split output files based on new-timestamp-year or max-file-size
  • e982b57 Use explicit fflush() instead of setvbuf()
  • 234bfbf contrib: Add init scripts and docs for Upstart and OpenRC
  • 01c2807 Add warning about the merkle-tree algorithm duplicate txid flaw
  • d6712db Also create pid file in non-daemon mode
  • 772ab0e contrib: use batched JSON-RPC in linarize-hashes (optimization)
  • 7ab4358 Update bash-completion for v0.10
  • 6e6a36c contrib: show pull # in prompt for github-merge script
  • 5b9f842 Upgrade leveldb to 1.18, make chainstate databases compatible between ARM and x86 (issue #2293)
  • 4e7c219 Catch UTXO set read errors and shutdown
  • 867c600 Catch LevelDB errors during flush
  • 06ca065 Fix CScriptID(const CScript& in) in empty script case
Credits

Thanks to everyone who contributed to this release:
  • 21E14
  • Adam Weiss
  • Aitor Pazos
  • Alexander Jeng
  • Alex Morcos
  • Alon Muroch
  • Andreas Schildbach
  • Andrew Poelstra
  • Andy Alness
  • Ashley Holman
  • Benedict Chan
  • Ben Holden-Crowther
  • Bryan Bishop
  • BtcDrak
  • Christian von Roques
  • Clinton Christian
  • Cory Fields
  • Cozz Lovan
  • daniel
  • Daniel Kraft
  • David Hill
  • Derek701
  • dexX7
  • dllud
  • Dominyk Tiller
  • Doug
  • elichai
  • elkingtowa
  • ENikS
  • Eric Shaw
  • Federico Bond
  • Francis GASCHET
  • Gavin Andresen
  • Giuseppe Mazzotta
  • Glenn Willen
  • Gregory Maxwell
  • gubatron
  • HarryWu
  • himynameismartin
  • Huang Le
  • Ian Carroll
  • imharrywu
  • Jameson Lopp
  • Janusz Lenar
  • JaSK
  • Jeff Garzik
  • JL2035
  • Johnathan Corgan
  • Jonas Schnelli
  • jtimon
  • Julian Haight
  • Kamil Domanski
  • kazcw
  • kevin
  • kiwigb
  • Kosta Zertsekel
  • LongShao007
  • Luke Dashjr
  • Mark Friedenbach
  • Mathy Vanvoorden
  • Matt Corallo
  • Matthew Bogosian
  • Micha
  • Michael Ford
  • Mike Hearn
  • mrbandrews
  • mruddy
  • ntrgn
  • Otto Allmendinger
  • paveljanik
  • Pavel Vasin
  • Peter Todd
  • phantomcircuit
  • Philip Kaufmann
  • Pieter Wuille
  • pryds
  • randy-waterhouse
  • R E Broadley
  • Rose Toomey
  • Ross Nicoll
  • Roy Badami
  • Ruben Dario Ponticelli
  • Rune K. Svendsen
  • Ryan X. Charles
  • Saivann
  • sandakersmann
  • SergioDemianLerner
  • shshshsh
  • sinetek
  • Stuart Cardall
  • Suhas Daftuar
  • Tawanda Kembo
  • Teran McKinney
  • tm314159
  • Tom Harding
  • Trevin Hofmann
  • Whit J
  • Wladimir J. van der Laan
  • Yoichi Hirai
  • Zak Wilcox
As well as everyone that helped translating on [Transifex](https://www.transifex.com/projects/p/bitcoin/).
Also lots of thanks to the bitcoin.org website team David A. Harding and Saivann Carignan.
Wladimir
original: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-February/007480.html
submitted by bitcoin-devlist-bot to bitcoin_devlist [link] [comments]

6. bitcoin-qt Syncing bitconnect wallet with network. Bitconnect wallet (not sync) *fix*. Bitcoin Core Wallet sync 100% result BITCOIN PRICE , BITCOIN FUTURE in doubt Bitconnect QT Wallet on MAC - NOT SYNCING - FIX!!!

Hello, My Bitcoin wallet is having major problems. My wallet states that it isSynchronizing with Network at 99.7% and last block generated 62 days ago. I have had my bincoin wallet up 5 days and there has not been any movement. I am real... I am using Bitcoin QT. I do not think my wallet can synchronize to the network. I have left it on connecting for hours. I have only transferred 0.01 BTC to it but it would be nice to be able to use it. Screenshot: Bitcoin is a distributed, worldwide, decentralized digital money. Bitcoins are issued and managed without any central authority whatsoever: there is no government, company, or bank in charge of Bitcoin. You might be interested in Bitcoin if you like cryptography, distributed peer-to-peer systems, or economics. Bitcoin, Dash, Litecoin and every Altcoins has its own core wallet. While the looks of each and every wallet may vary slightly its functionalities remain the same. Whenever you open your QT wallet the first thing your wallet does is; it starts scanning all the recent blocks on the blockchain and tries to catch up with the network. For the last 32 hours my bitcoin-qt has been unable to sync with the network even with my firewall and VPN switched off. Any ideas what else to check? Using Windows 7 SP1 x64 and have rebooted the machine. Internet connection is fine, plenty of space for the blockchain.

[index] [8344] [26708] [21572] [7188] [13899] [29767] [9768] [13243] [12944] [29890]

6. bitcoin-qt

Syncing bitconnect wallet with network. Bitconnect wallet (not sync) *fix*. ... Backup And Restore A Bitcoin Wallet. Or, ... How to Setup and Sync Bitconnect-Qt Wallet on macOS - Duration: ... Syncing your Bitconnect QT wallet NEW updated 10/27/2018 - Duration: 20:02. ... Increase slow download and sync of bitcoin blockchain on Mac - Duration: 2:01. Daniel's Tutorials 893 views. bitcoin p=np forum.bitcoin. pl bitcoin qt bitcoin qr code bitcoin qt synchronizing with network bitcoin qt wallet location bitcoin qt import wallet bitcoin qt synchronizing with network slow ... Just to show how Bitcoin Core Wallet after done sync 100% ... Network Printer - Duration: ... How to Repair a Qt Wallet that won't Sync. - Duration: 7:21. ... How to Recover Missing Bitcoins / Not Showing Up While Wallet Syncing - Duration: 7:03. m1xolyd1an 39,529 views. 7:03. Bitcoin-QT wallet ... 9:49. Lightning Network #4 - Zap wallet - Duration ...

Flag Counter