bitcoind-rpc
bitcoind-rpc copied to clipboard
bitpay
A client library to connect to Bitcoin Core RPC in JavaScript.
Bumps [async](https://github.com/caolan/async) from 0.9.2 to 2.6.4. Release notes Sourced from async's releases. v2.3.0 Added support for ES2017 async functions. Wherever you can pass a Node-style/CPS function that uses a callback,...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
The RPC method `importDescriptors` [requires an object](https://developer.bitcoin.org/reference/rpc/importdescriptors.html#argument-1-requests) and not a string, this PR fixes that.
I am having to wrap everything I use in promises to work with es6 style code, it would be great if we could get bitcoind-rpc to return promises
Bumps [extend](https://github.com/justmoon/node-extend) from 3.0.1 to 3.0.2. Changelog Sourced from extend's changelog. 3.0.2 / 2018-07-19 [Fix] Prevent merging __proto__ property (#48) [Dev Deps] update eslint, @ljharb/eslint-config, tape [Tests] up to node...
Bumps [handlebars](https://github.com/wycats/handlebars.js) from 4.1.2 to 4.7.7. Changelog Sourced from handlebars's changelog. v4.7.7 - February 15th, 2021 fix weird error in integration tests - eb860c0 fix: check prototype property access in...
add member(path) to RpcClient to support specify a wallet; add 'signRawTransactionWithKey' function;
Got this error logged, any idea how to avoid such error? ``` /mynode/node_modules/bitcoind-rpc/lib/index.js:70 buf += data; ^ RangeError: Invalid string length at IncomingMessage. (/mynode/node_modules/bitcoind-rpc/lib/index.js:70:14) at emitOne (events.js:77:13) at IncomingMessage.emit (events.js:169:7)...
Travis made breaking changes to using Xvfb back in January ([source](https://changelog.travis-ci.com/ubuntu-xenial-16-04-build-environment-update-86123)), this fixes the Travis builds using the updated instructions ([source](https://docs.travis-ci.com/user/gui-and-headless-browsers/#using-services)).
If we want to use this library on for remote RPC, timeout and retry are must-have feature. Will RpcClient(config) support retry and timeout in the future?
