server should exit if bitcoind is pruning
We could check for output of the 2nd ever transaction: bitcoind getrawtransaction 0e3e2357e806b6cdb1f70b54c3a3a17b6714ee1f0e68bebb44a74b1efd512098 1
if it returns error: {"code":-5,"message":"No information available about transaction"} there is pruning happening at bitcoind level.
It currently works fine with a patched bitcoind and txindex=0, but who knows about the future
A better tx is f4184fc596403b9d638783cf57adfe4c75c605f6356fbc91338530e9831e9e16 in block 170 because it's actually spent
If bitcoind getrawtransaction f4184fc596403b9d638783cf57adfe4c75c605f6356fbc91338530e9831e9e16 0 170 returns raw output there is no pruning active and the patch to bitcoind is applied. If it returns no information, electrum server should bail out and notify that bitcoind either being run as pruning or the database is corrupted or the patch not applied