Wallets cannot retrieve transactions

[cairesantos]

I have just setup Fulcrum 1.9.7 on MacOS BigSur and it is running fine apparently. I tried to connect with both wallets Sparrow and Electrum, but neither of them could retrieve transactions from the server.

I made some ss from the terminal and sparrow (as ithe GUI gives more info than electrum).

Any help would be appreciated.

SS below shows Sparrow connected to the wallet

SS below shows Sparrow processing errors when reloading the wallet

SS below shows my other laptop successfully connected to Fulcrum

[cculianu]

Make sure you run your Bitcoin node with -txindex=1. If you don't, you won't be able to retrieve txns.

[cairesantos]

I have that on my bitcoin config file, but apparently it did not process it?

I also certified myself that the Bitcoin core loaded this command via debug file

I did, however, note the following in the debug log of my core (bitcoin core version V26.0.0). Not sure exactly what an obfuscation key is, but maybe it reset txindex back to zero?

Thanks for you help!

[cculianu]

Don't worry about obfuscation key. That's some old option to get virus scanners to leave bitcoin alone.

Not sure what is going on with your setup and why it can't retrieve certain txns. Maybe Sparrow cached them from a previous mempool.. but since your node just came up.. they aren't in your node's mempool? Are these txns all unconfirmed?

[cairesantos]

I figured it out. Actually, it fixed by itself!

After fuclrum indexed the whole database, I set txindex=1 on bitcoin core and brought it online again. I thought I hat txindex was just an instruction to allow the usage of indexation within bitcoin core. However, when I opened debug file i saw core actually indexing the whole blockchain. After it finished, the wallets started to load the transactions just fine.

If i may ask another quick question. How to i shut down fulcrum safely? I did not set the admin port and now I couldn’t do it via terminal. When I open terminal and run the command, it actually tries to start fulcrum again and fails, of course. Is there a why to make fulcrum just reload de conf file, or is there a way to shut it down safely without the admin CLI?

[cculianu]

How's it running? You can hit CTRL-C or send it: SIGINT or SIGTERM and it will shut down gracefully.

[cairesantos]

It’s running on MacOS BigSur via CLI.

I hit ./Fulcrum Fulcrum.conf on Terminal.

On the same terminal window running Fulcrum, can I type SIGTERM + Enter?

[cculianu]

Just hit Ctrl-C