All responses are missing hash/id fields about bitcore-node HOT 17 CLOSED

This looks like the output from block.toObject(), which doesn't include the hash (since it's a computed property). We may either want to add the hash to the toObject() result, or have the API responses for v1 include a custom JSON format.

from bitcore-node.

Transaction doesn't either, and it sure would be nice to have the addresses base58enc there in the txs too.

Whats the release schedule look like on this project - I was hoping to use it for developing a personal project. Should I look into insight-api instead? I hesitate to do that because it won't support my latest node version according to the docs (out of order blocks).

Alternatively, I can enhance this myself with these missing pieces... What about the events API - is that fully functional? Any project status page would be helpful.

from bitcore-node.

Sorry for an off-topic question but how were you able to sync the blockchain? What version of bitcore are you using? Thanks.

from bitcore-node.

npm install
npm start

I'm sure I got a slew of errors or such on the install that I had to google and install dependencies or tweak the command line. I can't recall specifics. If you're having an issue, maybe post the issue and we can help.

from bitcore-node.

Unfortunately that didn't work for me. The initial sync runs to about 60% and crashes every time #72

I've tried on three different computers, i7, SSD, 36GB memory etc. I tried with bitcoin core 0.10.0 and 0.10.1 and the older 0.9 version. Any suggestions?

from bitcore-node.

Oh, it hasn't completed yet. Ha. Probably won't. It's taking forever. I've started investigating insight instead

from bitcore-node.

I was under the impression that Bitcore-node is the new / eventual replacement for Insight. How many % did yours sync?

from bitcore-node.

I'm moving the heavy lifting onto another machine right now. It got to about 36% on my raspberry pi and an old desktop. Throwing it on an i7 now to see if I can get it to go 100%, then I'll look into the code to tweak it to my liking. Alternatively, I may just go with insight since it's good out of the box. @braydonf - any timeframe details available for this replacing insight-api?

from bitcore-node.

I don't know the internal timeline for this, but I wouldn't hold my breath.
The two main contributors to this project are no longer employed at BitPay,
and there's indication that the intent is to turn bitcore-node into its own
full node of sorts, which is IMO significantly more difficult than an
insight-api-like web service layer on top of bitcoind. See
#57, for example.

On Sat, May 30, 2015 at 2:39 PM Dana Hanna [email protected] wrote:

I'm moving the heavy lifting onto another machine right now. It got to
about 36% on my raspberry pi and an old desktop. Throwing it on an i7 now
to see if I can get it to go 100%, then I'll look into the code to tweak it
to my liking. Alternatively, I may just go with insight since it's good out
of the box. @braydonf https://github.com/braydonf - any timeframe
details available for this replacing insight-api?

—
Reply to this email directly or view it on GitHub
#74 (comment).

from bitcore-node.

Thanks @carnesen. Yeah, a wrapper for bitcoind's library, not a true full node in js. Definitely sounds like someone's baby that they're probably not going to finish now. Thanks.

@kentdome mine got stuck at:
0000000000000948161fcdb06d515c124a9d8589afa57f138f8be9f8d0d8b8ea 128296 vel 0 b/s 35.75557252504083% synced
However, after a restart it's continuing on past that spot. I'm going to try and get it to 100%, then see if I can tweak the code to have the right fields, then do some benchmarks for this vs Insight.

from bitcore-node.

Hey, sorry for getting off-topic to this issue. But yes, as @carnesen has mentioned, there is intention to run Bitcoin Core code in a Node.js process, and we're currently working on making progress in that area.

from bitcore-node.

Thanks, to refocus this actual issue for anyone scrolling down:

Objects are missing ids/hashes

Previously diagnosed:

This looks like the output from block.toObject(), which doesn't include the hash (since it's a computed property). We may either want to add the hash to the toObject() result, or have the API responses for v1 include a custom JSON format.

I may try and tackle this if my instance ever completely syncs. The speed in which it initial syncs is very concerning.

from bitcore-node.

Any luck with the sync?

from bitcore-node.

Please take a look at chainlib-bitcoin, which we can integrate with bitcore-node, the sync should be working.

from bitcore-node.

@kentdome I did not ever get it to sync, and instead switched to using insight-api with RPC syncing.

from bitcore-node.

Spawned an issue at Bitcore: bitpay/bitcore#1308

from bitcore-node.

Fixed in: bitpay/bitcore#1311

from bitcore-node.