Is there a "print to file" parameter or its equivalent for bitcoin-cli; so that results from the daemon are recorded

Is there a "print to file" parameter or its equivalent for bitcoin-cli; so that results from the daemon are recorded

Is there any way to "print to file" the queried results of the bitcoin-cli. This would be most helpful in my basic cross platform integration of a program I am making with QB64.

https://ift.tt/2OjuRsA

Comments

Post a Comment

Popular posts from this blog

Lightning network (lnd): What's the best way to report lnd server issues/ask for help with channels that won't close?

Lightning network (lnd): What's the best way to report lnd server issues/ask for help with channels that won't close? I've been running a lnd/bitcoind node (mainnet) for a few months now. I had a couple open channels, made a couple purchases, things seemed pretty stable. But then I moved cross country, and in the process backed up my server and restored my drives to a new machine with a different IP (I might have lost about 3-4 days worth of data in the process). But now neither of my channels seem willing to close (they've been stuck with a decently sized limbo balance in the 'waiting_close_channels' state for like two weeks now). How do I properly report an issue? What site should I use? What log files need to be available? What other information should I provide? Thanks! https://ift.tt/2BwmcMl
Read more

Is there any python library could be used to decodescript in output

Is there any python library could be used to decodescript in output For example decode the ScriptPubKey like 4104678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb649f6bc3f4cef38c4f35504e51ec112de5c384df7ba0b8d578a4c702b6bf11d5fac to some data like this { "result": { "asm": "04678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb649f6bc3f4cef38c4f35504e51ec112de5c384df7ba0b8d578a4c702b6bf11d5f OP_CHECKSIG", "reqSigs": 1, "type": "pubkey", "addresses": [ "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa" ], "p2sh": "3DjjKyU38gSfuVxajV43MUy4vHkg1JVL7T" }, "error": null, "id": null } In general, something like the function in decodescript rpc. http://chainquery.com/bitcoin-api/decodescript https://ift.tt/2PH91gl
Read more

How to discover startup flags or command-line options for bitcoind?

How to discover startup flags or command-line options for bitcoind? I'd like to query the Bitcoin daemon (bitcoind) to find out what startup flags (command-line options) were sent to it on startup (or the current state if it has changed, e.g. -server=0/1 changing). For example, I may want to know if -addresstype, -disablewallet, -rescan, or -uacomment=<cmt> or some other flag has been set. Or for Namecoin, it would be very useful to know if -namehistory has been set. Is there an RPC or any other method to find out? Or, to ask the question a different way... src/bitcoind.cpp's bool AppInit(int argc, char* argv[]) method calls ParseParameters(argc, argv);, which is in src/util.cpp. In src/util.cpp we have: map<string, string> mapArgs; static map<string, vector<string> > _mapMultiArgs; const map<string, vector<string> >& mapMultiArgs = _mapMultiArgs; To store flags/options/args. I'd basically just like to get whatever is in tho...
Read more