Running staking Lore clients paves the way for some of the future use cases of BLK utilising the Bitcoin 0.12 (and newer) core tech, including colored coins. So I'm going to leave this one going indefinitely to kickstart the number of Lore clients staking. It's certainly not mandatory but it will be good in the longer term to have a nice distribution of Lore staking clients.
The cross-compile which lets you create binaries for multiple platforms didn't work for the QT version on the Pi, so there is more to do than just running the binary unfortunately, as below. There are folks working on some much cleaner solutions than this for the Pi, with a custom front end, and where you won't have to do any mucking about. That is coming soon. In the meantime, if you enjoy a fiddle with such things, here's how to get this QT client working on your Pi.
These instructions assume you are starting from scratch with a completely blank OS.
Note they have since (August 2017) released a version called 'Stretch' which does not work with this guide. I'll see if I can come up with something new for that at some point and link to it here when I have. In the meantime the guide should work with the Jessie image above.
Unzip the file and extract the .img file to burn it onto Fresh SD card to boot from (to be safe, use 16GB or larger), using a tool like win32diskimager or Etcher.
Assuming you have keyboard/mouse and monitor plugged into your pi, boot it up and the Jessie Desktop will show.
Before we do anything else, you should increase the default swap size on the pi, as compiling certain libraries can exhaust the RAM and get stuck otherwise. To do this, launch a Terminal window and type:
sudo nano /etc/dphys-swapfile
and Change the CONF_SWAPSIZE from 100 to:
Exit nano with control + x to write out the file.
Then, run the following to restart the swapfile manager:
(If you prefer to compile it yourself instead, it is possible by following the instructions in the original article by Mindphuk just taking into account this is the newer version of the Lore client than when that was written (https://github.com/janko33bd/bitcoin/releases) and the versions of Boost and the Berkeley DB need to be the same as below.)
Double click the zip and extract the Lore binary files. Yes, at the moment they are all called 'bitcoin', not 'blackcoin' or 'Lore' - this is because the code derives from a recent bitcoin core implementation so this has not yet been updated. You can place these wherever you like.
In the Terminal window, change directory to where you put the binaries, e.g.:
cd Downloads/lore-raspberrypi-armv7-jessie-pixel chmod +x *
That marks the binaries as executable.
Now, we need the Boost libraries installed for any of the Lore binaries to work. The project was done with Boost 1.62.0. Unfortunately the Jessie repository only goes up to 1.55, so we need to download and build 1.62 manually on the device.
wget https://sourceforge.net/projects/boost/files/boost/1.62.0/boost_1_62_0.tar.gz/download tar -xvzf download cd boost_1_62_0 sudo ./bootstrap.sh sudo ./b2 install
(This will take almost 2 hours. Have a nice cup of tea and a sit down.)
When I came to run the binaries, I found they couldn't find Boost. Running this command fixes that:
Now we are going to install the packages which aren't already included in the default OS installation which the binaries need in order to run:
Place the bootstrap.dat file into the ~/.lore directory.
Run ./bitcoin-qt again, it will say 'Importing Blocks' rather than 'Synchronising with Network'. My pi sync'ed fully in about 5-6 hours.
If you want peace of mind that Lore will always start on bootup into the Jessie w/Pixel desktop (i.e. after a power cycle), then you need to create a .desktop file in the following place.
sudo nano ~/.config/autostart/Lore.desktop
And in it, enter the following (tailoring the Exec line below to the whereabouts of your bitcoin-qt file):
[Desktop Entry] Name=Blackcoin Lore Comment=Mining without the waste Exec=/home/pi/Downloads/lore-raspberrypi-armv7-jessie-pixel/bitcoin-qt Type=Application Encoding=UTF-8 Terminal=false Categories=None;
Power usage and payback time
After a good while leaving it going by itself, the CPU load averages got down to almost zero, all of the time. Idling, the Pi uses a bit less than 3 watts. This means it would take two weeks to use one 1Kw/h of electricity.
If you pay e.g. 12.5 cents a unit, that's what you'd expect this to cost to run in a fortnight. That's around $0.25 a month or $3 a year. Green and cheap and helping to secure the BLK network. I paid for the year's worth of electricity in 2 days staking with 25k BLK. Makes mining look silly, huh? ;)
Securing your Pi
With staking, your wallet needs to be unlocked and as such, the keys to your wallet are on the device. In a clean and newly installed environment as described above, and if you don't allow others to use your device and there is no other software or nasties running on it, there is no real cause for concern. However, there are some basic security precautions you can take.
Firstly, if you have enabled SSH and are playing with your pi across your LAN (or worse, the Internet), you should immediately change the password for the default 'pi' user (which is preconfigured to be 'raspberry'). Simply log in as normal, then type:
You'll be prompted to enter the old and the new passwords.
Security by default
Your Pi is likely, by default, to not be exposed to incoming connections from the outside world because your router is likely generating a private address range for your LAN (192.168.x.x or 10.0.x.x or 172.x.x.x) which means all incoming connections are effectively blocked at the router anyway unless you set up a 'port forward' record to allow packets arriving on certain ports to be forwarded to a specific internal IP address.
As for accessing your Pi across the internet, if you have set up a port forward, this likely has security ramifications. Even basic old fashioned protocols have proven in recent times to have uncaught flaws, so it's always advisable to lock down your device as much as possible, and even if you only plan to access the Pi over your LAN, install a firewall to configure this. I used one called ufw, because it's literally an uncomplicated firewall.
sudo apt-get install ufw sudo ufw allow from 192.168.0.0/16 to any port 22 sudo ufw --force enable
This allows just port 22 (SSH) to be open on the Pi to any device on my LAN's subnet (192.168.0.x). You can change the above to a single IP address if paranoid, or add several lines, if you want to lock it down to your LAN and a specific external static IP address (e.g. a VPN service you use). To find out what subnet your router uses, just type:
and you'll see on the interface you are using (either hard wired or wifi) the 192.168 or 10. or 172. prefix. Change the above rule so it matches the first two octets correctly (e.g. 10.0.0.0/16 if you're on a 10.0. address).
You may already use VNC to access your Pi's desktop across your LAN, this uses port 5900. Add a line like above to lock it down to an internal address. It's not a good idea to expose this port to the wider world because those connections are not encrypted and potentially could be subjected to a MITM attack.
You can query the status of the firewall like this:
And of course, try connecting remotely once you change the rules to see what works. You should consult the official documentation for further options: https://help.ubuntu.com/community/UFW
Back up & Recovery
There are again many ways to tackle this so I'll just speak about my basic precautions in this regard. Don't take it as a be-all-and-end-all!
The wallet.dat file is the key file (literally) containing all the private/public keys and transactions. This can be found in:
You can navigate there using Jessie w/Pixel's own file manager or in a terminal window (cd ~/.lore). You can copy this file or, if you'd rather keep a plain text file of all your public and private keys, use the 'dumpwallet' command in the console. In Lore, go to Help > Debug Window > Console and type 'dumpwallet myfilename' where myfilename is the file you want it to spit out with all your keys in it. This file will end up in the same place you launch bitcoin-qt from.
The instructions earlier on, when running Lore for the first time intentionally left out encrypting your wallet.dat file because in order for the wallet to stake upon startup, it needs to have a decrypted key already. This isn't perfect, but after a power cycle, it would never stake unless you left it decrypted. So the best practice here is as soon as the wallet.dat file has left your device, i.e. you copy it to a USB stick for example, put it in an encrypted folder or drive (or both).
On the Mac, I use a software package called Concealer to encrypt files I store on the Mac itself: http://www.belightsoft.com/products/conceale There are almost certainly free packages with similar functionality, I have just used that one for years.
Note that these disk encryption methods may mean having to access the USB stick on a PC or Mac in order to retrieve the files in the event of a disaster. Be aware this may mean exposing them to more security issues if your computer is in any way compromised or someone nefarious has access to your computer. There are more 'manual' ways of backing up and recovering, such as literally writing down private/public key pairs which this guide doesn't go into, but may suit you better if paranoid about your setup.
The wallet.dat file has everything in it you need to recover your wallet, or if you used 'dumpwallet', the file you saved out has all the keys.
Wallet.dat method: Install Lore as normal then replace any auto-generated wallet.dat in ~/.lore directory with your backup. If a lot of time has elapsed and many transactions have occurred since your backup, launch lore with:
And if that doesn't do the job, do a full reindex of the blockchain:
If you used the dumpwallet command, install Lore then place the file containing all the keys that you saved out in the same directory as bitcoin-qt. In Lore, go to Help > Debug Window > Console and type 'importwallet myfilename' where myfilename is that file containing all the keys. The wallet should automatically rescan for transactions at that point and you should be good to go.
There are a million ways to do effective security and disaster recovery, but I hope this shows you a couple of basic precautionary ways. There are discussions about better ways to stake without compromising too much security which are happening all the time and developments in this regard will happen in time.
In the meantime, feel free to comment with your best practices.
Edit: solved! Just needed to wait for indexing to catch up Hi all I'm trying to use btc-rpc-explorer https://github.com/janoside/btc-rpc-explorer I have a full node via bitcoin qt. Can I use qt for block explorer? I launch block explorer and I'm getting rpc error. The webpage states "check rpc connection info" The github project states I need server=1 and txindex=1. Can I make qt run with these settings? I tried adding them to the .conf but how can I confirm qt is running with these options, in console somehow? In case I can't use qt for this I downloaded bitcoind. It looks like I can start the daemon with txindex=1 and server=1 but still getting same connection problem with btc-rpc-explorer. Do I have to do -reindex=1? Can I do that within qt? If not and I use bitcoin cli will it disrupt qt in any way? Thanks Edit: this is on Ubuntu
i created an address in bitcoin core and imported it watching only on electrum. And i dont know how to dumpprivkey for my wallet that i imported there to create from watching only to standart. Also i can't open the wallet on bitcoin core cause it says Prune:error: you need to reindex...
I have an old wallet.dat file from 2013. I downloaded bitcoin core 0.19.0.1 and replaced the wallet file with my old wallet.dat file. Ran bitcoin-qt and got error message mentioning running bitcoin-qt with --reindex command. I did but I now get a warning regarding clock accuracy (laptop battery is dead so windows messes up the clock sometimes). Clock is correct when running bitcoin-qt so I just click OK on the warning but the syncing and program stop and freeze. When I open bitcoin-qt and quickly go to transactions page, before the clock warning shows up, I can see the 5 transactions from 2013 that should leave some btc in the wallet. How can I recover them?
Dear Groestlers, it goes without saying that 2020 has been a difficult time for millions of people worldwide. The groestlcoin team would like to take this opportunity to wish everyone our best to everyone coping with the direct and indirect effects of COVID-19. Let it bring out the best in us all and show that collectively, we can conquer anything. The centralised banks and our national governments are facing unprecedented times with interest rates worldwide dropping to record lows in places. Rest assured that this can only strengthen the fundamentals of all decentralised cryptocurrencies and the vision that was seeded with Satoshi's Bitcoin whitepaper over 10 years ago. Despite everything that has been thrown at us this year, the show must go on and the team will still progress and advance to continue the momentum that we have developed over the past 6 years. In addition to this, we'd like to remind you all that this is Groestlcoin's 6th Birthday release! In terms of price there have been some crazy highs and lows over the years (with highs of around $2.60 and lows of $0.000077!), but in terms of value– Groestlcoin just keeps getting more valuable! In these uncertain times, one thing remains clear – Groestlcoin will keep going and keep innovating regardless. On with what has been worked on and completed over the past few months.
UPDATED - Groestlcoin Core 2.18.2
This is a major release of Groestlcoin Core with many protocol level improvements and code optimizations, featuring the technical equivalent of Bitcoin v0.18.2 but with Groestlcoin-specific patches. On a general level, most of what is new is a new 'Groestlcoin-wallet' tool which is now distributed alongside Groestlcoin Core's other executables. NOTE: The 'Account' API has been removed from this version which was typically used in some tip bots. Please ensure you check the release notes from 2.17.2 for details on replacing this functionality.
Builds are now done through Gitian
Calls to getblocktemplate will fail if the segwit rule is not specified. Calling getblocktemplate without segwit specified is almost certainly a misconfiguration since doing so results in lower rewards for the miner. Failed calls will produce an error message describing how to enable the segwit rule.
A warning is printed if an unrecognized section name is used in the configuration file. Recognized sections are [test], [main], and [regtest].
Four new options are available for configuring the maximum number of messages that ZMQ will queue in memory (the "high water mark") before dropping additional messages. The default value is 1,000, the same as was used for previous releases.
The rpcallowip option can no longer be used to automatically listen on all network interfaces. Instead, the rpcbind parameter must be used to specify the IP addresses to listen on. Listening for RPC commands over a public network connection is insecure and should be disabled, so a warning is now printed if a user selects such a configuration. If you need to expose RPC in order to use a tool like Docker, ensure you only bind RPC to your localhost, e.g. docker run [...] -p 127.0.0.1:1441:1441 (this is an extra :1441 over the normal Docker port specification).
The rpcpassword option now causes a startup error if the password set in the configuration file contains a hash character (#), as it's ambiguous whether the hash character is meant for the password or as a comment.
The whitelistforcerelay option is used to relay transactions from whitelisted peers even when not accepted to the mempool. This option now defaults to being off, so that changes in policy and disconnect/ban behavior will not cause a node that is whitelisting another to be dropped by peers.
A new short about the JSON-RPC interface describes cases where the results of anRPC might contain inconsistencies between data sourced from differentsubsystems, such as wallet state and mempool state.
A new document introduces Groestlcoin Core's BIP174 interface, which is used to allow multiple programs to collaboratively work to create, sign, and broadcast new transactions. This is useful for offline (cold storage) wallets, multisig wallets, coinjoin implementations, and many other cases where two or more programs need to interact to generate a complete transaction.
The output script descriptor (https://github.com/groestlcoin/groestlcoin/blob/mastedoc/descriptors.md) documentation has been updated with information about new features in this still-developing language for describing the output scripts that a wallet or other program wants to receive notifications for, such as which addresses it wants to know received payments. The language is currently used in multiple new and updated RPCs described in these release notes and is expected to be adapted to other RPCs and to the underlying wallet structure.
A new --disable-bip70 option may be passed to ./configure to prevent Groestlcoin-Qt from being built with support for the BIP70 payment protocol or from linking libssl. As the payment protocol has exposed Groestlcoin Core to libssl vulnerabilities in the past, builders who don't need BIP70 support are encouraged to use this option to reduce their exposure to future vulnerabilities.
The minimum required version of Qt (when building the GUI) has been increased from 5.2 to 5.5.1 (the depends system provides 5.9.7)
getnodeaddresses returns peer addresses known to this node. It may be used to find nodes to connect to without using a DNS seeder.
listwalletdir returns a list of wallets in the wallet directory (either the default wallet directory or the directory configured bythe -walletdir parameter).
getrpcinfo returns runtime details of the RPC server. Currently, it returns an array of the currently active commands and how long they've been running.
deriveaddresses returns one or more addresses corresponding to an output descriptor.
getdescriptorinfo accepts a descriptor and returns information aboutit, including its computed checksum.
joinpsbts merges multiple distinct PSBTs into a single PSBT. The multiple PSBTs must have different inputs. The resulting PSBT will contain every input and output from all the PSBTs. Any signatures provided in any of the PSBTs will be dropped.
analyzepsbt examines a PSBT and provides information about what the PSBT contains and the next steps that need to be taken in order to complete the transaction. For each input of a PSBT, analyze psbt provides information about what information is missing for that input, including whether a UTXO needs to be provided, what pubkeys still need to be provided, which scripts need to be provided, and what signatures are still needed. Every input will also list which role is needed to complete that input, and analyzepsbt will also list the next role in general needed to complete the PSBT. analyzepsbt will also provide the estimated fee rate and estimated virtual size of the completed transaction if it has enough information to do so.
utxoupdatepsbt searches the set of Unspent Transaction Outputs (UTXOs) to find the outputs being spent by the partial transaction. PSBTs need to have the UTXOs being spent to be provided because the signing algorithm requires information from the UTXO being spent. For segwit inputs, only the UTXO itself is necessary. For non-segwit outputs, the entire previous transaction is needed so that signers can be sure that they are signing the correct thing. Unfortunately, because the UTXO set only contains UTXOs and not full transactions, utxoupdatepsbt will only add the UTXO for segwit inputs.
getpeerinfo now returns an additional minfeefilter field set to the peer's BIP133 fee filter. You can use this to detect that you have peers that are willing to accept transactions below the default minimum relay fee.
The mempool RPCs, such as getrawmempool with verbose=true, now return an additional "bip125-replaceable" value indicating whether thetransaction (or its unconfirmed ancestors) opts-in to asking nodes and miners to replace it with a higher-feerate transaction spending any of the same inputs.
settxfee previously silently ignored attempts to set the fee below the allowed minimums. It now prints a warning. The special value of"0" may still be used to request the minimum value.
getaddressinfo now provides an ischange field indicating whether the wallet used the address in a change output.
importmulti has been updated to support P2WSH, P2WPKH, P2SH-P2WPKH, and P2SH-P2WSH. Requests for P2WSH and P2SH-P2WSH accept an additional witnessscript parameter.
importmulti now returns an additional warnings field for each request with an array of strings explaining when fields are being ignored or are inconsistent, if there are any.
getaddressinfo now returns an additional solvable Boolean field when Groestlcoin Core knows enough about the address's scriptPubKey, optional redeemScript, and optional witnessScript for the wallet to be able to generate an unsigned input spending funds sent to that address.
The getaddressinfo, listunspent, and scantxoutset RPCs now return an additional desc field that contains an output descriptor containing all key paths and signing information for the address (except for the private key). The desc field is only returned for getaddressinfo and listunspent when the address is solvable.
importprivkey will preserve previously-set labels for addresses or public keys corresponding to the private key being imported. For example, if you imported a watch-only address with the label "coldwallet" in earlier releases of Groestlcoin Core, subsequently importing the private key would default to resetting the address's label to the default empty-string label (""). In this release, the previous label of "cold wallet" will be retained. If you optionally specify any label besides the default when calling importprivkey, the new label will be applied to the address.
getmininginfo now omits currentblockweight and currentblocktx when a block was never assembled via RPC on this node.
The getrawtransaction RPC & REST endpoints no longer check the unspent UTXO set for a transaction. The remaining behaviors are as follows:
If a blockhash is provided, check the corresponding block.
If no blockhash is provided, check the mempool.
If no blockhash is provided but txindex is enabled, also check txindex.
unloadwallet is now synchronous, meaning it will not return until the wallet is fully unloaded.
importmulti now supports importing of addresses from descriptors. A desc parameter can be provided instead of the "scriptPubKey" in are quest, as well as an optional range for ranged descriptors to specify the start and end of the range to import. Descriptors with key origin information imported through importmulti will have their key origin information stored in the wallet for use with creating PSBTs.
listunspent has been modified so that it also returns witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output.
createwallet now has an optional blank argument that can be used to create a blank wallet. Blank wallets do not have any keys or HDseed. They cannot be opened in software older than 2.18.2. Once a blank wallet has a HD seed set (by using sethdseed) or private keys, scripts, addresses, and other watch only things have been imported, the wallet is no longer blank and can be opened in 2.17.2. Encrypting a blank wallet will also set a HD seed for it.
signrawtransaction is removed after being deprecated and hidden behind a special configuration option in version 2.17.2.
The 'account' API is removed after being deprecated in v2.17.2 The 'label' API was introduced in v2.17.2 as a replacement for accounts. See the release notes from v2.17.2 for a full description of the changes from the 'account' API to the 'label' API.
addwitnessaddress is removed after being deprecated in version 2.16.0.
generate is deprecated and will be fully removed in a subsequent major version. This RPC is only used for testing, but its implementation reached across multiple subsystems (wallet and mining), so it is being deprecated to simplify the wallet-node interface. Projects that are using generate for testing purposes should transition to using the generatetoaddress RPC, which does not require or use the wallet component. Calling generatetoaddress with an address returned by the getnewaddress RPC gives the same functionality as the old generate RPC. To continue using generate in this version, restart groestlcoind with the -deprecatedrpc=generate configuration option.
Be reminded that parts of the validateaddress command have been deprecated and moved to getaddressinfo. The following deprecated fields have moved to getaddressinfo: ismine, iswatchonly,script, hex, pubkeys, sigsrequired, pubkey, embedded,iscompressed, label, timestamp, hdkeypath, hdmasterkeyid.
The addresses field has been removed from the validateaddressand getaddressinfo RPC methods. This field was confusing since it referred to public keys using their P2PKH address. Clients should use the embedded.address field for P2SH or P2WSH wrapped addresses, and pubkeys for inspecting multisig participants.
A new /rest/blockhashbyheight/ endpoint is added for fetching the hash of the block in the current best blockchain based on its height (how many blocks it is after the Genesis Block).
A new Window menu is added alongside the existing File, Settings, and Help menus. Several items from the other menus that opened new windows have been moved to this new Window menu.
In the Send tab, the checkbox for "pay only the required fee" has been removed. Instead, the user can simply decrease the value in the Custom Fee rate field all the way down to the node's configured minimumrelay fee.
In the Overview tab, the watch-only balance will be the only balance shown if the wallet was created using the createwallet RPC and thedisable_private_keys parameter was set to true.
The launch-on-startup option is no longer available on macOS if compiled with macosx min version greater than 10.11 (useCXXFLAGS="-mmacosx-version-min=10.11" CFLAGS="-mmacosx-version-min=10.11" for setting the deployment sdkversion)
A new groestlcoin-wallet tool is now distributed alongside Groestlcoin Core's other executables. Without needing to use any RPCs, this tool can currently create a new wallet file or display some basic information about an existing wallet, such as whether the wallet is encrypted, whether it uses an HD seed, how many transactions it contains, and how many address book entries it has.
Since version 2.16.0, Groestlcoin Core's built-in wallet has defaulted to generating P2SH-wrapped segwit addresses when users want to receive payments. These addresses are backwards compatible with all widely used software. Starting with Groestlcoin Core 2.20.1 (expected about a year after 2.18.2), Groestlcoin Core will default to native segwitaddresses (bech32) that provide additional fee savings and other benefits. Currently, many wallets and services already support sending to bech32 addresses, and if the Groestlcoin Core project sees enough additional adoption, it will instead default to bech32 receiving addresses in Groestlcoin Core 2.19.1. P2SH-wrapped segwit addresses will continue to be provided if the user requests them in the GUI or by RPC, and anyone who doesn't want the update will be able to configure their default address type. (Similarly, pioneering users who want to change their default now may set the addresstype=bech32 configuration option in any Groestlcoin Core release from 2.16.0 up.)
BIP 61 reject messages are now deprecated. Reject messages have no use case on the P2P network and are only logged for debugging by most network nodes. Furthermore, they increase bandwidth and can be harmful for privacy and security. It has been possible to disable BIP 61 messages since v2.17.2 with the -enablebip61=0 option. BIP 61 messages will be disabled by default in a future version, before being removed entirely.
The submitblock RPC previously returned the reason a rejected block was invalid the first time it processed that block but returned a generic "duplicate" rejection message on subsequent occasions it processed the same block. It now always returns the fundamental reason for rejecting an invalid block and only returns "duplicate" for valid blocks it has already accepted.
A new submitheader RPC allows submitting block headers independently from their block. This is likely only useful for testing.
The signrawtransactionwithkey and signrawtransactionwithwallet RPCs have been modified so that they also optionally accept a witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output. This is compatible with the change to listunspent.
For the walletprocesspsbt and walletcreatefundedpsbt RPCs, if thebip32derivs parameter is set to true but the key metadata for a public key has not been updated yet, then that key will have a derivation path as if it were just an independent key (i.e. no derivation path and its master fingerprint is itself).
The -usehd configuration option was removed in version 2.16.0 From that version onwards, all new wallets created are hierarchical deterministic wallets. This release makes specifying -usehd an invalid configuration option.
This release allows peers that your node automatically disconnected for misbehaviour (e.g. sending invalid data) to reconnect to your node if you have unused incoming connection slots. If your slots fill up, a misbehaving node will be disconnected to make room for nodes without a history of problems (unless the misbehaving node helps your node in some other way, such as by connecting to a part of the Internet from which you don't have many other peers). Previously, Groestlcoin Core banned the IP addresses of misbehaving peers for a period (default of 1 day); this was easily circumvented by attackers with multiple IP addresses. If you manually ban a peer, such as by using the setban RPC, all connections from that peer will still be rejected.
The key metadata will need to be upgraded the first time that the HDseed is available. For unencrypted wallets this will occur on wallet loading. For encrypted wallets this will occur the first time the wallet is unlocked.
Newly encrypted wallets will no longer require restarting the software. Instead such wallets will be completely unloaded and reloaded to achieve the same effect.
A sub-project of Bitcoin Core now provides Hardware Wallet Interaction (HWI) scripts that allow command-line users to use several popular hardware key management devices with Groestlcoin Core. See their project page for details.
This release changes the Random Number Generator (RNG) used from OpenSSL to Groestlcoin Core's own implementation, although entropy gathered by Groestlcoin Core is fed out to OpenSSL and then read back in when the program needs strong randomness. This moves Groestlcoin Core a little closer to no longer needing to depend on OpenSSL, a dependency that has caused security issues in the past. The new implementation gathers entropy from multiple sources, including from hardware supporting the rdseed CPU instruction.
On macOS, Groestlcoin Core now opts out of application CPU throttling ("app nap") during initial blockchain download, when catching up from over 100 blocks behind the current chain tip, or when reindexing chain data. This helps prevent these operations from taking an excessively long time because the operating system is attempting to conserve power.
How to Upgrade?
Windows If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer. OSX If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), run the dmg and drag Groestlcoin Core to Applications. Ubuntu http://groestlcoin.org/forum/index.php?topic=441.0
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.
Groestlcoin Mainnet & Testnet supported
Multiple wallet support
Electrum - Support for both random and custom peers
Biometric + Pin authentication
Custom fee selection
Import mnemonic phrases via manual entry or scanning
BIP39 Passphrase functionality
Support for Segwit-compatible & legacy addresses in settings
Support individual private key sweeping
UTXO blacklisting - Accessible via the Transaction Detail view, this allows users to blacklist any utxo that they do not wish to include in their list of available utxo's when sending transactions. Blacklisting a utxo excludes its amount from the wallet's total balance.
Ability to Sign & Verify Messages
Support BitID for password-free authentication
Coin Control - This can be accessed from the Send Transaction view and basically allows users to select from a list of available UTXO's to include in their transaction.
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.
Simplified payment verification for fast mobile performance
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.
If a word is wrong, the tool will try to suggest the closest option.
If a word is missing or unknown, please type "?" instead and the tool will find all relevant options.
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).
Fixed size arithmetic
Fast Modular Inversion (Delayed Right Shift 62 bits)
SecpK1 Fast modular multiplication (2 steps folding 512bits to 256bits using 64 bits digits)
Use some properties of elliptic curve to generate more keys
SSE Secure Hash Algorithm SHA256 and RIPEMD160 (CPU)
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).
Ability to continue finding keys after first one is found
Includes warning on start-up if connected to the internet
Ability to output keys to a text file (And shows button to open that directory)
Show and hide the private key with a simple toggle switch
Show full output of commands
Ability to choose between Processor (CPU) and Graphics Card (GPU) ( NVidia ONLY! )
Features both a Light and Dark Material Design-Style Themes
Free software - MIT. Anyone can audit the code.
Written in C# - The code is short, and easy to review.
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.
Works via TOR or SOCKS5 proxy
Can use bootstrap.dat format as blockchain database
Import/Export blockchain to/from bootstrap.dat
Import wallet.dat from Groestlcoin-qt wallet
Export wallet to wallet.dat
Use both groestlcoin-wpf and groestlcoin-qt with the same addresses in parallel. When you send money from one program, the transaction will automatically be visible on the other wallet.
Rescan blockchain with a simple mouse click
Works as a full node and listens to port 1331 (listening port can be changed)
Fast Block verifying, parallel processing on multi-core CPUs
Mine Groestlcoins with your CPU by a simple mouse click
All private keys are kept encrypted on your local machine (or on a USB stick)
Lite - Has a lightweight "thin client" mode which does not require a new user to download the entire Groestlcoin chain and store it
Free and decentralised - Open Source under GNU license
Fixed Import/Export to wallet.dat
Rescan wallet option
Change wallet password option
Address type and Change type options through *.conf file
Import from bootstrap.dat - It is a flat, binary file containing Groestlcoin blockchain data, from the genesis block through a recent height. All versions automatically validate and import the file "grs.bootstrap.dat" in the GRS directory. Grs.bootstrap.dat is compatible with Qt wallet. GroestlCoin-Qt can load from it.
In Full mode file %APPDATA%\Groestlcoin-WPF\GRS\GRS.bootstrap.dat is full blockchain in standard bootstrap.dat format and can be used with other clients.
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.
Use your own node
Uses less CPU and RAM than ElectrumX
Used intermittently rather than needing to be always-on
Doesn't require an index of every Groestlcoin address ever used like on ElectrumX
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.
Add confidence messages, helping users to understand the confidence state of their payments.
Handle edge case when restoring via an external app.
Count devices with a memory class of 128 MB as low ram.
Introduce dark mode on Android 10 devices.
Reduce memory usage of PIN-protected wallets.
Tapping on the app's version will reveal a checksum of the APK that was installed.
Fix issue with confirmation of transactions that empty your wallet.
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.
I set txindex=1 in the bitcoin.conf file and restarted Bitcoin-QT. I see it reindexing but it's taking days instead of hours to finish. Meanwhile, I have to start up Bisq to finalize a trade before the trade times out. However, Bisq always connects to a local full node if it detects one and Bisq warns never to start it if your full node is not up to date yet. So, here's my question. Can I shutdown Bitcoin-QT while it's still reindexing its local copy of the blockchain without consequences? Or, if I interrupt it before completion, am I corrupting my downloaded copy of the blockchain and I'll have to start over the full node setup?
Trying to get eclair (lightning serveapp gui) to run and having issues. Seems I need to run qt in server mode so it can run the RPC server. Doing this in the command line however launches Bitcoin qt again and it attempts to reindex the whole blockchain (even though it's run from same location)... What am I doing wrong? Interested also if anyone is running qt on Ubuntu and also attempting to experiment with lightning ...tips tricks etc..
I know this is frequently posted, but I'm incensed at how absurdly slow reindexing becomes. There's got to be something wrong with the sync mechanism. I was 100% synced a week ago on my MacBook Pro. Latest version of the client (v0.17.0.1). I rsync'd the whole bitcoin dir (blocks, chainstate, index, etc) to another disk, ran a node on another machine using that copy for a couple of hours, then I stopped the node and rsync'd back to the Mac. Bitcoin-qt did not like the updated blockchain. The other machine didn't like its blockchain either. Oh well, I thought, maybe it didn't shutdown properly and borked the last block. I'll let it reindex, in a few minutes it'll be grand. But no. Bitcoin-qt decided that it was time to start over from scratch, ignoring the flawless 99.999% of data on disk. Yay. That was 10 days ago. At one point several days ago it was about 3 hours from finishing, with a progress of around 19% per hour. A day later progress was at 0.25%. This can't be right, I thought, maybe there's a bug, a memory leak or something. I'll shut it down and restart it. Of course it's going to restart from where it left, right? Right? No. It started from 0% again. Several days later, it's at 0.14% and predicting it'll finish sometime next week. CPU is 96% idle, RAM is at 25%, bandwidth is 120 Mb/s and the disk is used by bitcoin-qt and nothing else. It's the only thing running on this Mac and has been for the past two weeks. NOTHING is different between 19% and 0.14% in terms of bandwidth, CPU, RAM, or disk I/O. This very machine, under the exact same conditions, was able to process 19% of the blockchain in one hour. In the meantime, I can't move my BTC because my wallet, which has all the blocks including the ones containing the transactions with my BTC in them, doesn't believe the blocks are there. Bitcoin-qt is broken in more ways than one. First, something is causing this absurd variation in performance. Second, it's not saving state, which is particularly painful when it takes ages to get to the end to the blockchain. Is state only kept in RAM? I've seen other threads suggesting a change in the config (dbcache seems to be the main one), but I can't just change the setting without restarting, and restarting is not an option because I'll lose everything again. Sorry, this is extremely frustrating. I'm thinking of extracting the private key and abandoning the idea of running my own wallet. It's unusable.
Expose CLTV protocol feature at the GUI level. Using bitcoin-qt it is possible to create and send transactions not spendable until a certain block or time in the future
Expose OP_RETURN protocol feature at the GUI level. Using bitcoin-qt it is possible to create and send transaction with a "public label" -- that is, a string that is embedded in your transaction
Fix sig validation bug related to pre-fork transaction
Improve reindexing performances
Adapt the qa tools (functional and unit tests) to work in a post-fork scenario
Introduce new net magic set. For a period of time the client will accept both set of net magic bits (old and new). The mid term plan is to deprecate the old sets, in the mean time leverage the NODE_CASH service bit (1 << 5) to do preferential peering (already included in 1.1.0)
Avoid forwarding non replay protected transactions and signing new transaction only with the new SIGHASH_FORKID scheme.
Many fixes and small enhancements: orphan pool handling, extend unit tests coverage, improve dbcache performances.
I keep reading people say bitcoin development is stalled
But in practice there's more going on right now than there's ever been in the last few years. You just have to look in the right places. Here's a few days of documented github activity from the bitcoin slack and I've a feeling there are hundreds more people working on Bitcoin projects outside of the work being done by core: github BOT [6:28 PM] [bitcoin:master] 2 new commits by Daniel Kraft and 1 other: f93c2a1 net: Avoid duplicate getheaders requests. - Daniel Kraft 8e8bebc Merge #8054: net: Avoid duplicate getheaders requests. - Wladimir J. van der Laan [6:28] [bitcoin/bitcoin] Pull request closed: #8054 net: Avoid duplicate getheaders requests. by laanwj [6:31] [bitcoin:master] 6 new commits by Pieter Wuille and 1 other: d253ec4 Make ProcessNewBlock dbp const and update comment - Pieter Wuille 316623f Switch reindexing to AcceptBlock in-loop and ActivateBestChain afterwards - Pieter Wuille fb8fad1 Optimize ActivateBestChain for long chains - Pieter Wuille d3d7547 Add -reindex-chainstate that does not rebuild block index - Pieter Wuille b4d24e1 Report reindexing progress in GUI - Pieter Wuille Show more... [6:31] [bitcoin/bitcoin] Pull request closed: #7917 Optimize reindex by laanwj Joshua Unseth [9:55 PM] joined #commit-activity. Also, @sjors joined and left. ----- May 19th ----- github BOT [12:08 AM] [bitcoin/bitcoin] Pull request submitted by EthanHeilman
8070 Remove non-determinism which is breaking net_tests #8069
If addrmanUncorrupted does not have the same nKey every time it will map addrs to different bucket positions and occasionally cause a collision between two addrs, breaking the test. github BOT [1:00 AM] [bitcoin/bitcoin] Pull request closed: #7716 [0.11] Backport BIP9 and softfork for BIP's 68,112,113 by morcos Eragmus You Should Probably Stop Modding [1:12 AM] joined #commit-activity. Also, @buttmunch joined, @icandothisallday joined, @misnomer joined, @coreneedstostop joined, @xchins joined, @jbeener joined, @jbleeks joined, @whalepanda joined, @grinny joined, @alex_may joined, @mr_e joined. github BOT [2:46 PM] [bitcoin:master] 5 new commits by Warren Togami and 1 other: 00678bd Make failures to connect via Socks5() more informative and less unnecessarily scary. - Warren Togami 0d9af79 SOCKS5 connecting and connected messages with -debug=net. - Warren Togami 94fd1d8 Make Socks5() InterruptibleRecv() timeout/failures informative. - Warren Togami bf9266e Use Socks5ErrorString() to decode error responses from socks proxy. - Warren Togami 18436d8 Merge #8033: Fix Socks5() connect failures to be less noisy and less unnecessarily scary - Wladimir J. Show more... [2:46] [bitcoin/bitcoin] Pull request closed: #8033 Fix Socks5() connect failures to be less noisy and less unnecessarily scary by laanwj github BOT [3:56 PM] [bitcoin:master] 3 new commits by EthanHeilman and 2 others: f4119c6 Remove non-determinism which is breaking net_tests #8069 - EthanHeilman 2a8b358 Fix typo adddrman to addrman as requested in #8070 - Ethan Heilman 7771aa5 Merge #8070: Remove non-determinism which is breaking net_tests #8069 - Wladimir J. van der Laan [3:56] [bitcoin/bitcoin] Pull request closed: #8070 Remove non-determinism which is breaking net_tests #8069 by laanwj github BOT [5:18 PM] [bitcoin/bitcoin] Pull request submitted by MarcoFalke
8072 travis: 'make check' in parallel and verbose
• 'make check' in parallel, since the log will take care of clean output • 'make check' verbose, so that test failure causes aren't hidden Fixes: #8071 github BOT [7:56 PM] [bitcoin/bitcoin] Pull request submitted by rat4
8073 qt: askpassphrasedialog: Clear pass fields on accept
This is usability improvement in a case if user gets re-asked passphrase. (e.g. made a typo) Victor Broman [8:01 PM] joined #commit-activity. Also, @bb joined, @ziiip joined. ----- May 20th ----- github BOT [12:34 PM] [bitcoin/bitcoin] Pull request submitted by jsantos4you
debug.data.txt [12:37] [bitcoin/bitcoin] Pull request closed: #8075 0.12 by sipa github BOT [3:37 PM] [bitcoin/bitcoin] Pull request closed: #7082 Do not absolutely protect local peers and make eviction more aggressive. by gmaxwell github BOT [3:44 PM] [bitcoin:master] 2 new commits by Cory Fields and 1 other: 401ae65 travis: 'make check' in parallel and verbose - Cory Fields 1b87e5b Merge #8072: travis: 'make check' in parallel and verbose - MarcoFalke [3:44] [bitcoin/bitcoin] Pull request closed: #8072 travis: 'make check' in parallel and verbose by MarcoFalke github BOT [3:58 PM] [bitcoin/bitcoin] Pull request closed: #7093 Address mempool information leak and resource wasting attacks. by gmaxwell github BOT [6:11 PM] [bitcoin/bitcoin] Pull request submitted by sdaftuar
8076 VerifyDB: don't check blocks that have been pruned
If a pruning node ends up in a state where it has very few blocks on disk, then a node could fail to start up in VerifyDB. This pull changes the behavior for pruning nodes, so that we will just not bother trying to check blocks that have been pruned. I don't expect this edge case to be triggered much in practice currently; this is a preparatory commit for segwit (to deal with the case of pruning nodes that upgrade after segwit activation). @sipa Erik Hedman [6:20 PM] joined #commit-activity github BOT [8:46 PM] [bitcoin/bitcoin] Pull request submitted by jtimon
8077 Consensus: Decouple from chainparams.o and timedata.o
Do it for the consensus-critical functions: • CheckBlockHeader • CheckBlock • ContextualCheckBlockHeader Show more... github BOT [9:26 PM] [bitcoin:master] 3 new commits by MarcoFalke: fac9349 [qa] Remove hardcoded "4 nodes" from test_framework - MarcoFalke fad68f7 [qa] Reduce node count for some tests - MarcoFalke 8844ef1 Merge #8056: [qa] Remove hardcoded "4 nodes" from test_framework - MarcoFalke [9:27] [bitcoin/bitcoin] Pull request closed: #8056 [qa] Remove hardcoded "4 nodes" from test_framework by MarcoFalke github BOT [9:48 PM] [bitcoin/bitcoin] Pull request submitted by petertodd
8078 Disable the mempool P2P command when bloom filters disabled
Only useful to SPV peers, and attackers... like bloom is a DoS vector as far more data is sent than received. null radix [10:15 PM] joined #commit-activity github BOT [11:34 PM] [bitcoin:master] 2 new commits by MarcoFalke: fab5233 [qa] test_framework: Set wait-timeout for bitcoind procs - MarcoFalke 37f9a1f Merge #8047: [qa] test_framework: Set wait-timeout for bitcoind procs - MarcoFalke [11:34] [bitcoin/bitcoin] Pull request closed: #8047 [qa] test_framework: Set wait-timeout for bitcoind procs by MarcoFalke github BOT [11:48 PM] [bitcoin/bitcoin] Pull request closed: #7826 [Qt] show conflicts of unconfirmed transactions in the UI by jonasschnelli [11:50] [bitcoin/bitcoin] Pull request re-opened: #7826 [Qt] show conflicts of unconfirmed transactions in the UI by jonasschnelli ----- May 21st ----- Rentaro Matsukata [1:56 AM] joined #commit-activity. Also, @evilone joined, @cryptop joined, @thomas5 joined. github BOT [1:54 PM] [bitcoin/bitcoin] Pull request submitted by gmaxwell
8080 Do not use mempool for GETDATA for tx accepted after the last mempool req.
The ability to GETDATA a transaction which has not (yet) been relayed is a privacy loss vector. The use of the mempool for this was added as part of the mempool p2p message and is only needed to fetch transactions returned by it. github BOT [5:48 PM] [bitcoin/bitcoin] Pull request submitted by gmaxwell
8082 Defer inserting into maprelay until just before relaying.
Also extend the relaypool lifetime by 1 minute (6%) to 16 minutes. This reduces the rate of not founds by better matching the far end expectations, it also improves privacy by removing the ability to use getdata to probe for a node having a txn before Show more... Sergey Ukustov [9:17 PM] joined #commit-activity. Also, @stoicism joined. ----- Yesterday May 22nd, 2016 ----- github BOT [5:59 AM] [bitcoin/bitcoin] Pull request submitted by jonasschnelli
8083 Add support for dnsseeds with option to filter by servicebits
Opposite part of https://github.com/sipa/bitcoin-seedepull/36. Including new testnet seed that supports filtering. Required for SW #7910. Junseth Sock Puppet Account [6:13 AM] joined #commit-activity github BOT [1:59 PM] [bitcoin/bitcoin] Pull request submitted by gmaxwell
8084 Add recently accepted blocks and txn to AttemptToEvictConnection.
This protect any not-already-protected peers who were the most recent to relay transactions and blocks to us. This also takes increases the eviction agressiveness by making it willing to disconnect a netgroup with only one member. github BOT [5:04 PM] [bitcoin/bitcoin] Pull request submitted by theuni
8085 p2p: Begin encapsulation
This work creates CConnman. The idea is to begin moving data structures and functionality out of globals in net.h and into an instanced class, in order to avoid side-effects in networking code. Eventually, an (internal) api begins to emerge, and as long as the conditions of that api are met, the inner-workings may be a black box. For now (for ease), a single global CConnman is created. Down the road, the instance could be passed around instead. Also, CConnman should be moved out of net.h/net.cpp, Show more... github BOT [5:14 PM] [bitcoin/bitcoin] Pull request submitted by sipa
8086 Use SipHash for node eviction
github BOT [5:50 PM] [bitcoin/bitcoin] Pull request closed: #6844 [REST] Add send raw transaction by lclc ----- Today May 23rd, 2016 ----- yannie888 [5:21 AM] joined #commit-activity. Also, @myco joined, @er_sham joined, @ethdealer joined. github BOT [3:23 PM] [bitcoin/bitcoin] Pull request submitted by pstratem
8087 Introduce CBlockchain and move CheckBlockHeader
[3:23] [bitcoin/bitcoin] Pull request submitted by pstratem
8088 Avoid recalculating vchKeyedNetGroup in eviction logic.
Lazy calculate vchKeyedNetGroup in CNode::GetKeyedNetGroup.
This release is compatible with the Bitcoin Cash with the upcoming planned hard fork that will take place on Nov 13th
The main change of this release is the introduction of a new difficulty adjustment algorithm (DAA) that replaced the old EDA (Emergency Difficulty Adjustment). If you are interested in more detail about the new DAA you could find more details in the technical specification. Another major change is the introduction of a new format to store the UTXO (chainstate) database. The UTXO storage has been indexed per output rather than per transaction. The code has been ported from the Bitcoin Core project. This feature brings advantages both in terms of a faster reindex and IBD operation, lower memory consumption, on the other hand the on-disk space requirement increased of about 15%. Other notable changes:
implementation of BIP 146 as an HF (LOW_S, NULLFAIL)
fix some UI inconsistencies introduced by the Coin Freeze feature
migrate and separate QT settings for BUCash nodes
only request blocks via HEADERS and not by INV (BIP 130)
various improvements to Xthin code
add a flag to return txns count rather than list them all for getblock RPC
Is there any way to make an ABC node sync faster? Anything really?
This has been so painful to use that I'm likely killing it altogether. It has been for days on and off and I already had blockchain data from bitcoin core Qt stored up to mid 2017. Now it is stuck syncing with the network in jan 2016 with an ETA of 11 days. Anything to make this faster? Do -rescan -reindex do anything useful at all? EDIT: I'm not a really "upgrade" guy so I never upgrade unless I need to, so I was still using windows 8.0 with a lot of "capped" stuff to improve security and speed. It so happens that one of the problems there was that windows 8.0 was NOT ending properly the client when closing it and I needed to manually kill it (also RAM handling was poorer). After some research I decided to upgrade to windows 10 (still possible to get for free even if you had a windows 8.0 license like mine for when it comes installed in your machine already - send a msg here if you want to know the best procedure). Windows 10 properly handles ending the process, cleaning up RAM, and calling it back. Also, it seems to consume less resources to run ABC client. Just some hints here: windows 10 now uses PowerShell, not the old command shell, but PowShell does not accept commands such as -rescan -reindex as a default, so if you need to run a batch or start the client (or anything else like compiling c/c++ libraries, etc, etc) call cmd.exe instead, not worth the pain to read power shell documentation to execute pedestrian commands.
Help appreciated: bitcoin-qt runs fine on mac, copy dir to linux, bitcoind doesn't like it.
TL;DR: It's ok to ignore this post, you're not my personal tech support. :) I've been running a full bitcoin-qt core node on and off on my mac without issues for years (well, until I hosed my blockchain, had to reindex and came here to vent about how slow it was - fixed thanks to yogibreakdance). I'm trying to move it to a Raspberry Pi so I can have it running full time inside a closet and have the blockchain always up to date, available to sync back to the mac to move my BTC when I need to. After copying the whole bitcoin dir to the RPI, bitcoind immediately throws "Error initializing block database", removes most of the chainstate contents and stops. I tried changing file permissions, deleting everything except the blocks and chainstate dirs, using a config file appropriate for the RPI... No change. If I run bitcoind -reindex-chainstate, it seems to work. At least it starts reindexing, but I don't have the patience to wait till it finishes, it might take months. Some possibly relevant info: On the mac side the blockchain is stored on a 4 TB Mac OS Extended external disk, on the RPI side it's stored on a 1TB Ext4 external disk, published through samba and mounted on the mac. I use "rsync -rt --size-only" to move the files. Both bitcoin clients are v0.17.0.1. Empty wallet on both sides. On the RPI side, dirs are 777 and files 600 (I tried 777 too). A couple of weeks ago I had it running, the only difference was that the RPI drive was formatted as NTFS. I switched to Ext4 because NTFS was slow and didn't play nice with the mac. My google-fu got me nowhere. Hoping someone here might point me in the right direction.
This release is optional but recommended. The latest mandatory upgrade is v188.8.131.52, but if you have any problems with earlier versions the latest version is recommended. If you are running an older version, gracefully 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/PIVX-Qt (on Mac) or pivxd/pivx-qt (on Linux). There are no special steps needed like config file changes but a backup is always a good idea. A note from presstab in case it gets buried in the comments Command line install and upgrade guide
(but you should still read the release notes on Github)
Automated Database Corruption Repair
There have been cases of blockchain database corruption that can occur when PIVX client is not closed gracefully. The most common cases of corruption have been identified and the wallet will now automatically fix most of these corruptions. Certain corruption states are still unable to be fixed, but now provide more detailed error messages to the user as well as prompting the user to reindex their database.
More Accurate Error Messages
Some error messages in the wallet have been too vague and done little to help developers and the support team properly identify issues. Error messages have been refined and are now more specific.
Reduction of Debug Log Spam
Many 3rd party services have reported that their debug logs have been overloaded with messages about unknown transaction types. This log spam has been fixed.
Removal of Heavy Running Transaction Search Code
Many areas of the block validation code use a "slow" transaction search, which searches redundantly for transactions. This "slow" search has been removed upstream in Bitcoin and is now removed in PIVX. This provides a more efficient syncing process and generally better performing wallet.
Sync Fix for Block 908000
Many wallets were having trouble getting past block 908000. This block recalculates certain aspects of the money supply and zPIV transactions, and is known to take longer to sync. Code has been added to allow block 908000 to be validated without the user needing to enter any special commands into the debug console.
Testnet is now accessible with this release of the wallet. Testnet can be accessed using the -testnet startup flag.
zPIV Spending Fix
zPIV that were minted between block 891730 and 895400 were experiencing an error initializing the accumulator witness data correctly, causing an inability to spend those mints. This has been fixed.
Thanks to everyone who directly contributed to this release:
As well as everyone that helped translating on Transifex.
[dev] Dogecoin 1.10 IS OUT NOW. This is not a drill. You can tell by the lack of drilling noises
Yes, finally, after months of development and beating on it with hammers, Dogecoin Core 1.10 is out now: https://github.com/dogecoin/dogecoin/releases/tag/v1.10.0 - for Windows users you probably want to grab the setup-unsigned.exe versions (the .zip files are for anyone who just wants the binaries). BACK UP YOUR WALLET BEFORE YOU UPGRADE. We've had zero problems with upgrades so far, but still, just to be safe. You will have to reindex on first run of Dogecoin Core 1.10, which will take 2-3 hours. I suggest running it overnight. If you use the QT (graphical) client, it will prompt you to reindex. If you run the daemon, use the "-reindex" option when you launch to start the reindex process. Again, this only has to be done once while the index format is updated to add more sanity checks. Your wallet balance will reflect the blocks that have been reindexed, while the process runs, don't panic. Do not attempt to send coins while the reindex runs, however, or you may find you've sent invalid transactions. This is a major update and a critical security update. If you use Dogecoin Core, you MUST update to 1.10 to remain secure. If you for whatever reason absolutely cannot update (i.e. cannot take a service down to reindex) you can use Dogecoin Core 1.8.3, which contains the most critical fixes: https://github.com/dogecoin/dogecoin/releases/tag/v1.8.3 . Even then, we highly recommend updating later if at all possible. This release includes all of the changes in Bitcoin Core 0.9 and 0.10, including a huge speed boost to download/sync, a broad range of security fixes, and the framework for future improvements such as blockchain trimming and smart contracts (yes, you read that right, smart contracts). If you're an individual user please update NOW. If you're a merchant, exchange, payment processor or service provider, please test and update as soon as possible. If you're a miner, please update after the 17th so we have time for the new client to be deployed. This update introduces version 3 blocks (BIP 66 for those who know what that is), which are part of the security fixes, and the more clients update before they're mined, the easier the rollout will be. To re-iterate - seriously, you need to update. This client has been in testing for literal months, it's stable, there isn't another update just around the corner, get this one. Lastly, for anyone who wants to run a Dogeparty wallet server (mostly this means coinwarp), there's a modified version of 1.10 with extensions to support Dogeparty wallets. Unless you need this version (i.e. someone tells you you need it), just get 1.10 from above instead. If you do need it, it's at https://github.com/dogecoin/dogecoin/releases/tag/v1.10.0-dogeparty.
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).
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:
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.
TECH HELP: Wallet conflict! Need help retrieving missing BTC from Bitcoin Core Qt wallet after trying to also install and sync BitcoinABC Qt wallet.
Hey guys, It seems I'm one of those newbies who's dove into the pool before learning how to swim. A couple of weeks ago I installed the Bitcoin Core wallet and deposited a small amount of BTC to get it off the exchange. After buying some BCH I decided to download ABC Qt wallet to store my BCH. After installing and running ABC, I noticed the wallet had a transaction in its history showing the exact denomination I had deposited into my BTC wallet, but in BCH!!! (so not the same value) And it was already encrypted. After waiting a night for it to sync with the network ('processing blocks on disk', and then 'reindexing blocks on disk') the syncing stalled at 81ish percent and I decided to give up on it. I closed the program and opened up the preexisting Bitcoin Core wallet to find that the value had dropped to 0, and it also could not connect to the network and has its network progress stuck at 81ish percent. There seems to be a conflict between the two that's causing the problem because the I was running a full node the the Bitcoin Core wallet which was 100 percent synced last night! During installation, I noticed the ABC wallet had a transaction in its history showing the exact denomination I had deposited into my BTC wallet, but in BCH!!! (so not the same value) It seems that the computer recognises the two programs as the same. And now the funds are stuck in limbo. How the hell can I resolve the issue to at least retrieve my funds? I haven't deleted the ABC app yet in case that makes my funds irretrievable. (fyi: using an MacBook Pro)
I would like to run a Bitcoin Cash full node to support the network. I've done the following steps:
I've downloaded Bitcoin Classic 1.3.6 With Bitcoin Cash.
I've copied the data directory of Bitcoin Core into the data directory of Bitcoin Cash to bootstrap the synchronization.
I've started the Bitcoin Classic client (bitcoin-qt) with the "-reindex" parameter.
My client seemed to be syncing without any issue until the first Bitcoin Cash block (478558). After this block the the synchronization stopped. I haven't modified the default "Bitcoin-Qt.conf" file. My client is connected currently to 8 other nodes (6xBitcoin ABC, 1xBUCash and 1xBitcoinUnlimited). The debug log is huge it is about 100MB. At the end of the log file there are few messages like this: AcceptBlockHeader: block is marked invalid or [Net] Id: 1434 0 => 100 Ban threshold exceeded Any idea why is my client stuck at block 478558?
IRC Log from Ravencoin Open Developer Meeting - Aug 10, 2018
[16:01] <@Wolfsokta> Todays topics: DGW implementation, segfault, Q&A, feedback on IRC [16:01] <@Wolfsokta> Just to set the stage here, this is a developer meeting where developers that have contributed source code to the Ravencoin project can meet and chat about items they are working on. Please be respectful to one another. For the sake of staying on target, please limit interactions to questions and comments on code or projects that you are working on. Any time left over at the end can be opened up for general Q&A. [16:02] <@Wolfsokta> FYI - I'm RavencoinDev, and lets get started. [16:03] <@Wolfsokta> @Tron, can you talk about where we are at with DGW on testnet and mainnet? [16:03] <@Tron> Sure. [16:03] can someone volunteer to take notes and post also? [16:03] <@Tron> We are building binaries that will activate DGW-180 at block 338778 [16:04] <@Tron> It looks back 180 blocks to calculate the diff. [16:04] I will copy the text from the meeting into a file that can be archived later. I can also make summary notes after like BTC core does. [16:04] I'll save a log of the whole meeting and can post it on the subreddit thread. [16:04] <@Wolfsokta> We have setup testnet4 in order to test the new binaries. [16:04] great [16:05] <@Wolfsokta> We plan to release the binaries later today. [16:05] @Tron have you looked into the timestamp attack concerns of DGW? [16:05] https://github.com/zawy12/difficulty-algorithms/issues/30 [16:06] <@Tron> Yes. And for that reason, we've tightened up the timestamps that will be accepted for valid blocks. [16:06] <@Tron> Moved from 2h to 12 minutes. [16:06] nice [16:06] Oh wow okay [16:06] <@Tron> Its also the reason we went from 60 blocks (lookback) to 180 blocks. [16:07] why would 2h ever be acceptable? lol [16:07] 2h was originally used for daylight savings shenanigans I believe [16:07] <@Tron> It was from bitcoin, and it factors in clock skew, and variance in finding blocks on 10 minute intervals, and block propagation time. [16:07] makes sense [16:08] what about the segmentation fault when reindexing? [16:08] any fix yet? [16:08] @Tron 12 minutes seems to be pretty small window for clock skew [16:08] I assume it was chosen due to 1/10th scaling from BTC? [16:09] <@Wolfsokta> Not yet ruski, we'll cover that in a bit. [16:09] <@Tron> We did divide existing by 10. [16:10] <@Wolfsokta> Any further questions about DGW on testnet or on mainnet? [16:10] What block is it activating on mainnet? [16:10] <@Wolfsokta> 338778 [16:11] And will there be the need to update binaries twice (for DGW fork and asset layer fork)? [16:11] <@Tron> We are activating DGW by block height because headers sync first, and the BIP9 activation flag sets a flag, and we need to look at either block height or version to know which diff algo. [16:11] <@Wolfsokta> Calculated to be near the end of the month so we have some time with DGW on testnet. [16:11] Someone on discord asked this a while back, but why Was DGW chosen over something like digishield or anyother algo [16:11] <@Tron> And block version can be changed (tampering) and still make it on the chain. [16:12] Binaries will need to be updated as more asset layer stuff get completed and tested. Not by the end of the month though. [16:12] <@Tron> We looked at DGW and LWMA. LWMA has a lot of constants that must be tuned right. [16:13] <@Tron> We were impressed with the amount of work on LWMA to analyze how it responds, but it wasn't straightforward to understand the nuances of how/why it works. [16:13] zawy was in the #development channel on Discord. He's an expert on DAAs. I'm sure he would help with tuning LWMA if you asked. [16:14] <@Tron> Either will be much better that what we have. Even at the extremes, it will adjust smoothly. [16:14] Are there any issues or comments on the DGW code that should be addressed? [16:14] @devs in general [16:15] <@Wolfsokta> Thanks @brianmct, we did look extensively at the DGW code to ensure we weren't going to see the same issues that happened to Verge. [16:16] so i guess you would have to make way more blocks with false timestamps to be able to exploit our version of dgw right? [16:16] because of the 12 minute timestamp thing? [16:16] <@Wolfsokta> With X16R, and with the changes Tron talked about we feel confident that this will address the swings without being able to be exploited. [16:17] nice [16:17] @russki Yeah, pretty much. [16:17] verge is a different type of situation - but overall asics and mining are a risk always [16:18] <@Wolfsokta> Okay, anything else on the difficulty targeting change? [16:19] <@Wolfsokta> Cool, blondfrogs wanted to talk about subassets that were added. [16:19] ooh yeah i saw those github commits [16:19] looking good [16:19] We also want to let everyone know that you can now create sub assets with the new binaries that will be posted soon. You can create these subassets using the issue rpc call. Qt will be built shortly. This will allow users to make an asset PARENT [16:20] <@Wolfsokta> Basic overview. If you own an asset you can create sub-assets by including a '/ [16:20] nice [16:20] And then make any of the following PARENT/A PARENT/B .... PARENT/Z [16:20] <@Tron> We'll post a FAQ on assets later today. [16:21] <@Wolfsokta> And it only is 100 Raven for a subasset [16:21] on testnetv4 it still says asset activation status: waiting [16:21] why? [16:21] <@Tron> Yep, it needs to be voted in. [16:21] <@Wolfsokta> We wanted to test the BIP9 activation process again as well. The more testing the better. [16:21] We wanted to make sure that we follow the same process the Mainnet is going to go through. [16:21] ok nice [16:22] <@Wolfsokta> Any questions about subassets? [16:23] are they unique? [16:23] <@Tron> No [16:23] <@Wolfsokta> Yes, they behave the same way as a normal asset, just live under an owned asset. [16:23] <@Tron> Maybe I misunderstood the question. Unique with parent. [16:23] Each subasset can have their own number issued? So PARENT/A can have 1,000 and PARENT/B can be 50? [16:23] yes [16:23] oooh ok that makes more sense [16:23] <@Wolfsokta> Exactly thanks traysi [16:24] <@Tron> And, not the same thing as "Unique Assets" [16:24] <@Wolfsokta> The individual unique asset support is included in an upcoming phase. [16:25] Moving onto the Segfault issue ----------------------->>>>>>>>>>> SEGFAULT [16:25] Are we able to changes the properties of subassets after they have been created? Or is something like that specified when creating them? [16:25] <@Tron> Yes [16:25] can sub-assets be reassigned to other addresses while retaining control of the parent asset elsewhere? [16:25] So basically it has all the features of a normal asset, but live under an asset's top-level namespace? [16:25] satoshi corbie @russkidooski [16:25] So basically it has all the features of a normal asset, but live under an asset's top-level namespace? [16:26] <@Tron> Sub-assets are identical to assets after creation. [16:26] <@Tron> Just cheaper to create, and in your "owned" namespace. [16:26] Okay cool [16:26] will subassets eventually have a unqiue tag? eg ASSET/SUB:1 [16:26] We have found an issue with our testnet binaries and are still looking to the issue. The issue presents itself when a user performs a reindexing of the chain. We think we have pinpointed the where the problem is and are currently working a fix. This fix will be out shortly. [16:26] plan is to make default reissue=true and units=0 and allow increase in units on reissue [16:26] How much is it going to be for a sub-asset? [16:27] 100 [16:27] <@Wolfsokta> Okay, let's now focus on the SegFault issue that was discovered by Under. [16:28] do you know what the issue was? [16:28] <@Wolfsokta> It seems to be a build problem with the boost library. [16:28] Still looking into though. :) [16:29] <@Wolfsokta> We have been able to reproduce it on linux internally with 2.0.3 [16:29] yea i get the same issue on windows 10 [16:30] I saw a Bitcoin thread a while back about the seg fault error. I had it because I had conflicting versions of BDB [16:30] static compiled on ubuntu 18.04 [16:30] <@Wolfsokta> We really appreciate you guys pulling down master and helping test. [16:30] @Trap we will look into that also [16:30] no problem, im just curious lol [16:32] <@Wolfsokta> We haven't been able to build a windows version that doesn't have the segfault issue. [16:32] <@Tron> We're dropping Windows support ;) [16:32] lol [16:33] Just finished setting up a new Windows test environment so we can test and validate the solution as we are working on it. [16:33] The bdb issue is a known issue that has been around for some time. We are pretty certain it is a boost library issue, and are working quickly to get a windows build that fixes the issue. [16:34] what did you guys do to fix the linux version? [16:34] Once we have binaries for all supported platforms ready, hopefully tonight. No promises. We will make an announcement [16:34] The issue has been fixed on Linux and Mac though? [16:34] (oops sorry already answered) [16:34] <@Wolfsokta> If anybody else gets there first with Windows please let us know what you found. [16:34] Built the binairies on a Ubuntu 16.04 box. [16:34] that was it? [16:35] Yeah, we think so. 16.04 has boost 1.58 which seems to fix the issue. The build on 18.04 use boost 1.67 which seems to cause the issue. [16:35] is there a boost 1.58 repo on 18.04? [16:35] 18.04 used 1.65*** [16:36] I've built with boost 1.68 on arch Linux [16:36] It worked [16:37] wallet 2.0.x? [16:37] @Trap, the issue is when -reindex is used. [16:37] Oh sorry my bad [16:37] Wallet 2.0.3 [16:38] <@Wolfsokta> For those that joined late we're discussing https://github.com/RavenProject/Ravencoin/issues/208 [16:38] 1 sec im going to boot into ubuntu and try compiling with 1.58 on 18.04 [16:39] Any other questions pertaining to the segfault? [16:40] <@Wolfsokta> Alright, thanks everybody. Before we start the Q&A I would like to get some quick feedback on using IRC for this meeting. [16:41] If we're going to use IRC we should take some measures to at least hide people's IPs when they join [16:42] Yea. It is very hard to read this back. [16:42] Also no message history [16:42] If you disconnect and reconnect [16:42] <@Tron> I'll throw in a vote for Discord. [16:43] <@Wolfsokta> If you use a decent IRC client instead of the website it's not bad. [16:43] Some of us used a VPN before we connected to IRC [16:43] If needed we can restrict channel to Developer roles, etc for the developer meeting and open it up for general Q&A [16:43] https://www.strawpoll.me/16247952 [16:43] poll [16:43] Make a discord when only mods can submit links [16:43] Where* [16:45] Discord won the poll 5 to 2 [16:45] <@Wolfsokta> There are also a lot of IRC tools that can be used to track the meetings. [16:45] we know [16:46] <@Wolfsokta> We also want any developer to be able to speak. [16:48] <@Wolfsokta> We're open to try Discord next week. [16:48] <[kai]> perhaps you could even get a feed from this irc to discord? [16:49] <[kai]> a feed would enable discordians to view the chat, but only contribute if they take the extra steps to come here. [16:49] <@Wolfsokta> That's a good idea kai... Has anybody seen that working? [16:50] <[kai]> https://github.com/reactiflux/discord-irc [16:50] <[kai]> im sure you could make this a one way deal. [16:51] <@Wolfsokta> I like that idea, let's try that for next week. So we'll meet here in IRC again, but it should be broadcast to Discord. [16:53] <@Wolfsokta> Okay, we'll go with IRC next week with the broadcast to discord and re-visit for next week. [16:54] <@Wolfsokta> Okay, let's do open Q&A for the next few mins. [16:54] <[kai]> just a quickey, more for my curioisty, did you look at digishield? [16:54] <[kai]> DGW solution seems solid. [16:55] <[kai]> was just curious if it was one of the four solutions you looked at. [16:55] <@Wolfsokta> Tron is answering... Any others Q? [16:55] <@Tron> We briefly looked at Digishield, but our analysis was between DGW and LWMA. [16:55] <[kai]> right on. [16:56] <[kai]> cheers guys, see you next time. [16:56] OPen the gates for the last 4 minutes for any other questions? [16:58] <@Wolfsokta> Alright, thank you all for being here today and please join the development effort with us. If you have an idea, or a fix for an issue write it up and submit a pull request. [16:59] <@Wolfsokta> Thanks again for all those that have contributed their time and effort to make Ravencoin successful. We have the BEST community. [16:59] ^ 6:59] You devs are pretty cool [16:59] did the burn get discussed? [16:59] <@Wolfsokta> Special thanks to Bruce, really glad you could make it with the short notice. [17:00] <@Tron> Thanks everyone!
Bitcoin Core (formerly Bitcoin-Qt) is the third Bitcoin client, developed by Wladimir van der Laan based on the original reference code by Satoshi Nakamoto. It has been bundled with bitcoind since version 0.5. Bitcoin-Qt has been rebranded to Bitcoin Core since version 0.9.0 .. Bitcoin Core can be used as a desktop client for regular payments or as a server utility for merchants and other ... Install Bitcoin-Qt Since version 0.9, Bitcoin-Qt was renamed to Bitcoin Core t o reduce confusion between Bitcoin-the-network and Bitcoin-the-software. Bitcoin Core is a full Bitcoin client. It is a thick client, meaning it requires the full blockchain (explained below) on local disk to operate and expose blockchain back to the network to help relay and verify transactions. Keep a copy (sync ... As the current "restart with -reindex" is fine for bitcoind, but very confusing for GUI users. Skip to content. Sign up Why GitHub? ... Bitcoin-Qt: ask user to rebuild database in case of db corruption #2202. Open sipa opened this issue Jan 22, 2013 · 13 comments Open Bitcoin-Qt: ask user to rebuild database in case of db corruption #2202. sipa opened this issue Jan 22, 2013 · 13 comments ... Bitcoin-Qt ist ein Open-Source-Projekt und derzeit einer der sichersten Vertreter unter den Mining-Clients. Hier müssen Sie sich nicht um eventuelle Angriffe auf Ihr virtuelles Geld sorgen. Ebenfalls Open-Source und vertrauenswürdig ist Electrum.Das Tool punktet mit einer 2-Faktor-Authentifizierung, dem Support von Add-ons und der Möglichkeit, Ihre Keys jederzeit in andere Bitcoin-Clients ... Bitcoin Core ist ein gemeinschaftliches, freies Software-Projekt, veröffentlicht unter der MIT-Lizenz. Release-Signaturen überprüfen Download über Torrent Quelltext Versionshistorie anzeigen. Bitcoin Core Release Signierschlüssel v0.8.6 - 0.9.2.1 v0.9.3 - 0.10.2 v0.11.0+ Oder wählen Sie Ihr Betriebssystem . Windows exe - zip. Mac OS X dmg - tar.gz. Linux (tgz) 64 bit. ARM Linux 64 bit ...
How to fix Zcoin no block source error in QT wallet
This short tutorial explains what a Bitcoin wallet backup is and how to create it on 3 different wallets: Blockchain.info, Bitcoin-QT and MultiBit. For more information and tutorials about Bitocin ... Installing Bitcoin-Qt - Duration: 5:46. super3boy 3,795 views. 5:46. The RPiCluster - Duration: 8:03. Josh Kiepert Recommended for you. 8:03. Things you can make from old, dead laptops - Duration ... This tutorial explains the steps necessary to install the Masterchest Windows wallet. The process requires the re-indexing of the Bitcoin-Qt database and it ... Commands to resync and reindex Civitas wallet: "C:\Program Files\Civitas\civitas-qt.exe" -reindex "C:\Program Files\Civitas\civitas-qt.exe" -resync Use code "hL0QlW" and get 3% off every purchase ... Hello everyone, just a quick video about the details around the newest bitcoin core QT wallet version and why you should update. Forum Post: https://bitcoint...