kajoseph

The insight API is not public. It's blocking your domain (localhost?) from accessing it. You could try the bitcore-node API at https://api.bitcore.io/api/BTC/mainnet/address//txs?unspent=1 See https://github.com/bitpay/bitcore/blob/master/packages/bitcore-node/src/routes/api/address.ts for details on address endpoints

It's hard to say without seeing the full implementation. Are you running this in a browser? Are you sure `newwallet` is being called? Try using console.log instead of alert

The problem referenced in #3358 still applies to the `.every` method on the Array prototype. We should fix it in here

Currently, the pruning service (`packages/bitcore-node/src/services/pruning.ts`) only prunes invalid and old mempool transactions. The only setting for it is the age at which you want to prune the old mempool txs...

Ah, in that case the only things bitcore-node goes to the eth node for that I'm aware of are an address' balance and ERC-20 events. The balance is not a...

@Xiechengqi Have you tried with Node v11? Currently, bitcore is known to throw errors for Node v12+

Hi @benjamintshi, this is a work in progress that is still on my radar but unfortunately has fallen behind some other more pressing priorities at the moment. I'm hoping to...

Hey @benjamintshi , unfortunately not. It was overshadowed by our launch of lightning at first and now we're getting ready for the pending ETH merge. This is still front of...

I merged in https://github.com/bitpay/bitcore/pull/3349 to ensure no merge conflicts. Since it and this will require Node version increases, and thus a major version bump, they should be merged into master...

Oh ok, I was thrown off by the title of the PR being about removing the `signingMethod` param in the `toBuffer/toDER` function. That's fine if you're just wanting to change...