Contents:
Some functional tests are known to fail spuriously with varying probability. Issue , and a fuller listing in Possible out-of-memory error when starting bitcoind with high excessiveblocksize value Issue There are obstacles building the current version on Ubuntu These are worked around by our packaging system, but users trying to build the software from scratch are advised to either upgrade to more recent Ubuntu, or retrofit the necessary toolchains and perform the same build steps for Xenial as registered in our packaging repository, or build in a VM using the gitian build instructions, or run our reproducible binary release builds.
It has an option to calculate average hashrate "since last difficulty change" and wrongly assumes difficulty changes every blocks. This irrelevant option will likely be removed in the next release. A problem was observed on scalenet where nodes would sometimes hang for around 10 minutes, accepting RPC connections but not responding to them see This is because code style checking is currently a work in progress while we adjust it to our own project requirements see Issue There are also RPC parameter type inconsistencies that flag linting checks see We remind that the 0.
Users must upgrade to a release in the Installing this version is optional, but we recommend that users of Added configuration to access new DNS seeders from loping. This release implements the 'extversion' extended versioning handshake protocol ref. BCHN merge requests!
A new indexdir configuration option allows the user to specify a path under which the leveldb 'index' folder is stored. The use case for this new option is to store the index on a separate volume of faster access media while the blocks can be stored on slower media. A new finalizeheaders configuration option enabled by default rejects block headers which are below the finalized block height if a block has indeed been finalized already.
Finalized blocks are not supposed to be re-organized under any circumstances just like checkpointed blocks. There is therefore no need to accept headers for alternate chains below the last finalized block.
JSON-RPC library for use with Bitcoin Cash Nodes, promise-based and let bch = new bchRPC(host, username, password, port, timeout. So you must determine the PORT in the config file for one or both of them like this: For BitcoinCash: server=1 daemon=1 rpcuser=xxx rpcpassword=zzz.
Nodes which submit such blocks are penalized according to a penalty score determined by the finalizeheaderspenalty option default is , meaning such nodes will be disconnected. In practice this works to quickly disconnect nodes from old chains like the "Clashic" network which sometimes submit headers of forked off chains with vastly lower block heights. No new RPC methods are added in this release, however some argument aliases are added to existing calls for backward compatibility and a new optional parameter is added to the sendtoaddress method for improved coin selection performance.
An optional coin selection 'coinsel' argument has been added to the sendtoaddress RPC method. An alias dummy has been added for the parameters argument of the submitblock call, for backward compatibility. User who are running any of our previous releases 0. The update to Bitcoin Cash Node As of version Hence our version numbers no longer start with a zero. Semantic versioning makes it easy to tell from the change in version number what are the impacts on interfaces and backward compatibility:.
A major version first number change indicates that an interface changed in a way that makes the new software incompatible with older releases. A patch version third number change indicates that a new release only contains bug fixes which are backward compatible.
Automatic bans are now referred to as "discouraged" in log output, as they're not and weren't even before strictly banned: incoming connections are still allowed from them as was the case before this change , but they're preferred for eviction. Automatic bans will no longer time-out automatically after 24 hours. Depending on traffic from other peers, automatic bans may time-out at an indeterminate time.
Automatic bans will no longer be persisted across restarts. Only manual bans will be persisted. Automatic bans can no longer be lifted with the setban remove RPC command. If you need to remove an automatic ban, you must clear all automatic bans with the clearbanned false true RPC command, or restart the software to clear automatic bans. All extant automatic bans "node misbehaving" that are currently stored in the node's banlist. The regression test chain, that can be enabled by the -regtest command line flag, now requires transactions to not violate standard policy by default.
Making the default the same as for mainnet, makes it easier to test mainnet behavior on regtest. Be reminded that the testnet still allows non-standard txs by default and that the policy can be locally adjusted with the -acceptnonstdtxn command line flag for both test chains. A mechanism has been added to this version such that it will gracefully expire on May 15, , at the time of the network upgrade which is tentatively scheduled to occur then.
This feature has been added as a safety measure to prevent this version of the node software from mining or otherwise transacting on an incompatible chain, should an upgrade take place on May 15th, This version will begin to warn via RPC "warnings", via a GUI message, and via periodic messages to the log starting 30 days prior to May 15th, Once the future consensus rules of the May 15th, upgrade to the Bitcoin Cash network have been determined, a new version of Bitcoin Cash Node will be made available well in advance of May 15th, It is recommended that all users of Bitcoin Cash Node update their nodes at that time so as to ensure uninterrupted operation.
The autotools build system autogen , configure , CMake is the replacement build system, look at the documentation for the build instructions. To continue using the autotools build system, pass the --enable-deprecated-build-system flag to configure. The bitcoin-tx tool has fully supported CashAddr since v0. Version The medianfeerate field in getblockstats output has been removed. Bitcoin Cash Node In earlier versions, it already was inactive due to no available proposals to vote on. The empty softforks field in getblockchaininfo has been removed. The Avalanche prototype features have been removed from this release pending specification and evaluation.
Users that wish to build for 32 bits Windows should be aware that this will not be tested by the Bitcoin Cash Node team and be prepared to resolve issues on their own. The sigops and sigoplimit values returned by the getblocktemplate and getblocktemplatelight methods are now calculated according to the SigChecks specification. The clearbanned method now optionally can take two additional boolean arguments both default to true if unspecified.
These arguments can be used to control whether manual or automatic bans are to be cleared or both. The listbanned method's results array has changed slightly. The "node misbehaving" value for this key will never appear. This key is now deprecated and may be removed altogether in a future release of BCHN. The setban method can no longer lift individual automatic bans.
Use clearbanned instead to clear all bans, or clearbanned false true to clear all automatic bans while preserving all manual bans. One file in doc also violates the lint tool Issue This release of Bitcoin Cash Node contains many corrections and improvements that we feel are useful, but it is strictly an optional installation for those already running previous v0. With the network upgrade behind us, Bitcoin Cash Node starts to pursue its own roadmap of improvement and innovation.
This release delivers performance improvements and a new mining RPC, the getblocktemplatelight and submitblocklight calls. Two new light-weight RPC calls were added: getblocktemplatelight and submitblocklight. These RPCs reduce the round-trip time for mining software when retrieving new block templates. Transaction data is never sent between mining software and bitcoind. A full description and specification for this facility accompanies this release. I'm running a bitcoin server and I validate its working by running bitcoin-cli getinfo.
Stack Overflow for Teams is now free for up to 50 users, forever. Block or report someone. In version 2 of compact blocks , shortids should use the wtxid instead of txid as defined by BIP The TXID of the transaction holding the output to spend. A library for serializing and deserializing Json will make your life a lot easier:.
I have a new bitcoin-cash server which basically sets up the same but when I run a cli command it errors. When I run this command from the server;. I get this result; error: Could not locate RPC credentials. No authentication cookie could be found, and RPC password is not set. See -rpcpassword and -stdinrpcpass. No matter the flags I use on bitcoin-cli I get the same error.
As it turns out, you can't connect to the rpc server while the server is still downloading blocks. Once it finishes, you can connect to the server. Using bitcoin-cli getinfo was the original problem.
Chaincore is designed to be watch-only, therefore no rescan happens following an address import. First, install ws via the following command: npm install ws - then, subscribe to channels and receive events like so:. Now you must wait for Bitcoin to sync The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. The npm package chaincore-node receives a total of 31 weekly downloads. As such, chaincore-node popularity was classified as limited.
Visit the popularity section on Snyk Advisor to see the full health analysis. While scanning the latest version of chaincore-node, we found that a security review is needed. A total of 13 vulnerabilities or license issues were detected. See the full security scan results. We found indications that chaincore-node is an Inactive project. See the full package health analysis to learn more about the package maintenance status.
Security review needed.