satstack icon indicating copy to clipboard operation
satstack copied to clipboard

Support connecting to a pruned Bitcoin node

Open onyb opened this issue 5 years ago • 2 comments

It may be possible to run satstack with a pruned chain state, which can significantly reduce the disk usage to just a few GBs. The downside is that historical transactions won't show up on Ledger Live.

This feature should be accompanied by Ledger Live displaying an appropriate message to the user if the Bitcoin node is pruned.

Ref: https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-0.12.0.md#wallet-pruning

onyb avatar Oct 03 '20 21:10 onyb

Yup, txindex=1 is not compatible with -prune=XXX therefore you get sth like this when running lss.exe: image

pablos91 avatar Sep 10 '21 21:09 pablos91

FATAL Failed to initialize Bus error=failed to detect txindex: failed to get block I hacked my way pass that error by setting txIndexEnabled to always true. txindex=1 is not mandatory according to the readme.

But then I got:

[2022/04/17 - 02:18:16]  INFO worker: #RunTheNumbers successful                     actualSupply=19013535.93066619 BTC expectedSupply=19013743.75 BTC height=732199
[GIN] 2022/04/17 - 02:18:18 | 200 |    475.8226ms |       127.0.0.1 | GET      "/blockchain/v3/explorer/status"
[GIN] 2022/04/17 - 02:18:18 | 200 |    127.1599ms |       127.0.0.1 | GET      "/blockchain/v3/explorer/status"
[GIN] 2022/04/17 - 02:18:19 | 200 |      80.418ms |       127.0.0.1 | GET      "/blockchain/v3/explorer/status"
[2022/04/17 - 02:18:19] ERROR worker: Failed while importing descriptors            error=-4: This type of wallet does not support this command
[2022/04/17 - 02:18:19] FATAL worker: Failed to send INTERRUPT signal               error=not supported by windows pid=21488

I haven't looked enough to see if satstack has a chance to work with pruned nodes.

dzid26 avatar Apr 17 '22 01:04 dzid26