New answers tagged

0

My favorate tool to test an API endpoint is always curl curl --user user --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getblockchaininfo", "params": [] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/ source: https://en.bitcoin.it/wiki/API_reference_(JSON-RPC)#...


0

To avoid a race condition with getblockcount, you could use getblockheader with the bestblock result from gettxout and get its height. Then do the height calculation with the number of confirmations to get the block hash to pass to getrawtransaction.


0

After you sign the message there isn't much left to do assuming your signature is already base64 encoded. Most people then post the message and signature on a forum or similar while labeling the message, and signature clearly. Example: ----BEGIN BITCOIN SIGNED MESSAGE---- asdf ----BEGIN SIGNATURE---- 1someBitcoinAddressIOwn H9L5yLFjti0QTHhPyFrZCT1V/...


0

Is it possible to configure c-lightning cookie based authentication to bitcoind as opposed to rpcuser/rpcpassword? Yes it works with .cookie now. It is automatic, it is the positive side effect of c-lightning invoking bitcoin-cli to communicate with bitcoind instead of handling RPC and authentication itself. Does lightning.conf read the rpcuser/rpcpassword ...


Top 50 recent answers are included