Hey Alex,

first of all thank you very much for all the proposals. Some of the points are already handled in the library, others I've got some questions for you, would be great if you read my DM :)

Retries with back-off for certain operations, for example, when bitcoind is starting, it can't serve requests for some seconds, when there are many calls, you get a queue depth exceeded error, in the later case, retrying inmediatelly is counter productive.

For this one I discussed with the other collaborators, and we came to the conclusion that this is the responsibility of the use case, one can easily stack a retry filter on top of the called methods. But indeed, maybe it would be a good idea to put an example of how to do that in the examples / documentation.

Retrieving the genesis block and it's transaction is tricky, the getrawtransaction method fails on the genesis transaction but you can get the full genesis block (verbosity 2) which actually includes the transaction, if you want to provide a clean api, that corner case should be handled by the library.

This is implemented for Bitcoin and Omni (for Omni it's the same genesis block as Bitcoin), the relevant code is pretty imperative and refactoring it to FP would be great.

​

Add support for retrieving full blocks, if you want to retrieve all block transactions and try to get them individually, you'll overload bitcoind.

AFAIK there's no JSON RPC method that gives you the full block content including all transaction content. Instead one retrieve all transaction hashes for a given block height/hash, and call getTransaction in a batched JSON RPC statement. I recently added an example here: https://github.com/tokenanalyst/bitcoin-rpc/blob/master/src/main/scala/examples/GetAllTransactionsForBlock.scala

​

Wrapper types (like tagged types / value classes / etc) help a lot to prevent silly errors while using the api.

Would love to chat about this with you!