It’s advertised on the page below that Fulcrum works with pruned Bitcoin Core on StartOS.
However, after fully syncing Bitcoin Core in pruned mode the Fulcrum service seems to require the pruned setting to be set to 0, which is greyed out - thus not working. Thoughts?
That documentation is incorrect. Fulcrum requires a full non-pruned node (see: GitHub - cculianu/Fulcrum: A fast & nimble SPV Server for BCH, BTC, and LTC · GitHub)
Actually, sorry, I’m wrong. StartOS has some facilities to still make this possible, but it will become very slow I think.
The current Fulcrum package seems to enforce prune=0
So while technically possible, it would seem we didn’t try to implement it on StartOS.
StartOS posts a critical task on Bitcoin Core to apply these settings if they are not already in place. After you install Fulcrum, you’ll need to resolve any critical task that appears on Bitcoin Core to enforce the required settings. It will take some time for Fulcrum to index, as it still needs to index the entire blockchain via on-demand block fetching. You’ll be able to connect wallets to Fulcrum with this configuration, but you cannot run the Mempool block explorer. I would be curious to know how well Sparrow’s block explorer feature works in this configuration.
My post was based on what I read in the documentation, and a conversation with Start Bbot. But if the documentation is wrong, so is my explanation.
Right, the critical task requires to set pruning to 0, which is disabled by bitcoin core service I presume. So can’t go forward with this.
It’s a bit confusing. Fulcrum itself requires a full node. But StartOS has a ‘btc rpc proxy’ that fills the gap between a pruned and full node. This was made specifically for electrs back in 0.3.5
Technically, I think Fulcrum on StartOS can use this too (it will require testing), but it hasn’t been done yet in the Fulcrum for StartOS package.
So yes, currently, fulcrum on startos requires a full node. I posted a message on the dev matrix to see if it’s feasable to change this.
So is electrs supposed to work currently with StartOS pruned node? Cause I’m getting same issue as with Fulcrum
That may have been missed in the 0.4 version. Thanks for the report, I’ll pass it on.
