bitcore-node | Extensible full node using Bitcore | Cryptocurrency library
kandi X-RAY | bitcore-node Summary
kandi X-RAY | bitcore-node Summary
There is no upgrade path from previous versions of Bitcore Node due to the removal of the included Bitcoin Core software. By installing this version, you must resynchronize the indexes from scratch.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of bitcore-node
bitcore-node Key Features
bitcore-node Examples and Code Snippets
Community Discussions
Trending Discussions on bitcore-node
QUESTION
OS: Ubuntu Server 16.04
MongoDB Server: v3.4.22
Node.js: v10.16.3
I'm running a bitcoin-abc(bitcoin cash) node.
And I'm running a bitcore node to connect to the bitcoin-abc node.
The bitcoin-abc node is fully synchronized with the all blocks. It's got all the latest blocks.
and I checked that the rpc server is working fine.
But when I query to the bitcore
api server(e.g. http://localhost:3000/api/BCH/mainnet/tx?blockHash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f),
it returns an empty array([]
).
And on the bitcore
terminal, it keeps printing this message below:
{"message":"Waiting until BTC syncs before BCH mainnet","level":"info"}
{"message":"Waiting until BTC syncs before BCH mainnet","level":"info"}
{"message":"Waiting until BTC syncs before BCH mainnet","level":"info"}
I want to know why this message(
"Waiting until BTC syncs before BCH mainnet"
) keeps showing. Maybe the bitcore node is still synchronizing? is it normal to see that message until the synchronization is complete?I want to use the Bitcore APIs.
- these are logs from the
bitcoin-abc
node.
ANSWER
Answered 2020-Mar-02 at 06:29I found out what was wrong in my configuration.
In bitcore.config.json
I removed parentChain
and forkHeight
. And it works perfectly now.
I didn't know exactly what those properties were for.
I referred to this example template(bitcore.config.json).
That's why I put those properties in it.
Anyone who runs only bitcoin-abc
node should Not include parentChain
and forkHeight
properties in bitcore.config.json
.
You can find the related answer here (https://github.com/bitpay/bitcore/issues/2742).
QUESTION
I am developing a wallet for HappyCoin which is similar but different fork of Bitcoin.
Since this coin doesn't have addressindex rpc methods(getaddressbalance, getaddressdeltas, getaddressmempool, getaddresstxids, getaddressutxos), I can't get utxos and transactions for a specific address.
Since it is quite different from Bitcoin I can't use bitcore-lib or bitcore-node.
How can I get utxos and transactions related to a specific address using legacy rpc methods?
Here are the rpc methods this coin supports.
I've tried with listunspent and listtransactions but these only work with local wallet address not other addresses.
...ANSWER
Answered 2019-Sep-05 at 03:39You could try first importing the address as a watch-only address into your wallet using:
importaddress
[label]
Once the rescan is complete (it has to scan the entire blockchain for all transactions related to this address), which can take over an hour.
You should then be able to use the wallet commands to list unspent and tx'es.
QUESTION
I have tried to installed zcash insight ui & api in my local machine (ubuntu OS) and it is completed all the steps but I m facing issue while start services in frontground.
Let me share with you command, config file.
...ANSWER
Answered 2018-Jul-06 at 13:45Check out this line the README.
Install npm install -g zcash-bitcore-node zcash-bitcore-node start
To install Zcash, follow the Zcash Beta Guide. Point your zcash-bitcore-node.json to $DIR/zcash/src/zcashd.
After installing the zcashd separately and then changing the exec path in my config file to point to that location, it worked properly:
QUESTION
I'm trying to run a bitcoin network on regtest with this version of bitcoin node so I can test out bitpay's insight-ui block explorer.
Running on regtest I get this repeating error
...ANSWER
Answered 2017-May-23 at 15:48Okay I figured it out. What was happening is there were some other bitcoind processes that had zombied out and were listening on the port this process was trying to access. I ran this command to kill the other processes
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install bitcore-node
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page