Bitcoind rpc thread in production

[yanganto]

The bitcoind service and kld service should be one to one.

The send_transaction is defined here, but nowhere using it now. And it clones the client and also causes a lot of upstream structure to wrap with Arc
https://github.com/kuutamolabs/lightning-knd/blob/bf5ade093a0baa164dd37a93c794ef2924f2fab4/kld/src/bitcoind/bitcoind_client.rs#L78-L81

Is there a possible kld need to have multiple queries on bitcoind at the same time?

• If there is always one query at the same time, why do we just use the reference of the client?
• If it is possible but rare, why not make a lock on the client?
• If it is possible and often why not make a queue or suitable channel for the transactions? Such that when the request reaches the concurrent limitation we can handle it.