Topic: bitpay bitcore node & node libs (Read 250 times)

i am not really familiar with bitcore myself so if i am wrong hopefully someone will correct me, but i believe that you can do both. meaning a standalone Bitcore as your full node or just add it on top of another full node (bitcoin core) and use it. what Bitcore does is basically indexing the blockchain so it becomes easier/faster to find things like a block explorer finding any address balance. which is why it takes a bigger size.
https://bitcore.io/guides/full-node/

I thought Bitcore itself wasn't a node, but that it required an actual bitcoin-compatible node as a backend.

>  If you don't have a preferred block source (trusted peer), Bcoin will be started automatically and synchronized with the mainnet chain.

(From https://github.com/bitpay/bitcore-node/blob/master/README.md)

what do you mean by "third party node"?!!!
bitcore is also a full verifying node just like bitcoin core but it is written in Javascript and by other developers and it is open source like any other full node: https://github.com/bitpay/bitcore-node
it is just that it doesn't seem to be active any more.

Is a bad idea to work with a 3rd party node, i would recommend you to install your own node. as you can see in the top of this site there is a link to download it ( https://bitcoin.org/en/download )

isn't easy to work with your own node, but once you get familiarized with the commands and download those +200Gb you will be able to do anything you want. You can start learning about bitcoin-cli commands to work with your node. Good luck.

My suspicion is that Bitpay is still using bitcore internally but they`re keeping the code private. even if the original team left they could have had new people joining the team and continuing development. Looking at https://coin.dance/nodes it seems that the bitcore nodes count has been decreasing this year and I suspect this is because users outside of Bitpay move to other solutions and since the node is not maintained anymore there are no new users.

@lautaro.dragan I think I might have a solution although i`m not sure how well it scales. I am using rpc importaddress with bitcoind, this adds the address to the wallet to 'watch' and parses the blockchain for transactions associated with it. this will take a while.. but after that you can query bitcoind with rpc listtransactions and the account name under which you imported the address. As i said I don`t know how well this scales: scanning the blockchain for each address can take minutes depending on the machines (but bitcoind is responsive) and I imagine this adds to the wallet db so this will start using storage if a lot of addresses are imported.

I still have to test some things but it seems like a workable solution for querying txs by address (not sure about utxo yet). The alternative would be a fully fledged explorer like bitcore/insight but this soaks up large amounts of work and people will keep these solutions private most of the time.. it`s a shame bitcore is not maintained anymore

I think they aren't. Most (if not all) the core members left a long time ago (now founders of Decentraland, Zeppelin, Yours.org, etc).

I've had some pains with bitcore-lib and trying to get bitcore-node up and running in the past.

At Po.et we simply decided to move away from Insight API in general and just use the Bitcoin Core wallet.

I'd also love to know if there's a good alternative to bitcore that indexes transactions and utxo by address. Would be amazing if bitcoind itself had that as a configuration option.

Is the Bitpay bitcore node&libs still supported? They look pretty much dead on github although I could start and sync mainnet&testnet nodes. Does anyone know why did they abandon the project? (possibly by keeping following versions private)

Also does anyone know of a node implementation that has similar features to bitcore, i.e. I am most interested in being able to query it for all the transactions to or from an address.