Thanks, I also just discovered now how to set specific logging with bitcoin-cli, for example:


includes all categories, except tor.

So I've been running a (pruned) node for about a week. All the status related functions (getinfo, getnettotals, getnetworkinfo etc), as well as wallet operations and all seem to be working ok.

When I'm watching debug.log, I don't see a lot takes place though. I can mostly see the regular UpdateTip messages, and similar "housekeeping" notifications, but not much more.

How can I figure out more about what my node is doing? if it verifies transactions sent from elsewhere, is it logged anywhere? I can see the mempool, that's ok, but is there a deeper level of monitoring that can be done?

Thanks @nc50lc and @BitCryptex, I guess I'll have to find some suitable hardware then.

ElectrumX docs mention a non-pruning bitcoin daemon is a must.

https://electrumx.readthedocs.io/en/latest/HOWTO.html#prerequisites

Is there a way to run Electrum server (either ElectrumX or another project) on a pruned node?

I currently run a pruned node, with the


option set in bitcoin.conf

If I now want to turn my node to be unpruned, what should I do?

Just remove this option from the file and restart bitcoind, or anything else?

The "restore" command works in the console, command line and through an RPC call. It takes a text that can have various formats including a mnemonic word list or a master private key.

See lines 151-166 in https://github.com/spesmilo/electrum/blob/master/electrum/commands.py

With Curl:
curl --data-binary '{"id":"curltext","method":"restore","params":{"text":"word1 word2 word3...""}}' http://user:password@127.0.0.1:7777

As for working with multiple wallets, that's a bit hacky but I figured out switching between them can be done by using the "setconfig" command. For example:

curl --data-binary '{"id":"curltext","method":"setconfig","params":{"key":"wallet_path","value":"path/to/wallet1"}}' http://user:password@127.0.0.1:7777

switches to wallet1 file. It's then possible to work with any number of wallet files without restarting the electrum daemon (as I previously thought will be necessary).

I wish they'd publish a full reference for the RPC API, it is tricky to figure out what goes where.

Thanks a lot, I'll check that one as well.

Electrum can restore a HD wallet but indeed it's tricky to handle multiple wallets at the same time there.

Another way is do it with a python library. I see that https://github.com/primal100/pybitcointools
 is archived and not maintained any longer. Any good alternatives?

Anyone? 

I want to set up a server that will receive http requests (using a simple protocol I define) and perform some simple bitcoin related operations, including import of a HD wallet and pushing transactions.

I wonder what is a good way to do it. I will use an NGINX web server to receive the requests and process them with PHP (I'm also comfortable with python, just for background).

As for the operations themselves, I thought about the following options:
- Run a full bitcoin node on the server and send JSON-RPC requests to bitcoind
- Run a full node + an electrum server and send the requests to the electrum server (with electrum dameon)
- Send them to electrum daemon. No full node / electrum server.
- Don't run anything locally (except the web server) - use a third party API, such as of blockchain.com. Problem is I didn't see an api that allows import / restore of a HD wallet.

I assume there are other options I didn't think. I will appreciate your input on this.