Need help to get everything to work on Windows 10 machine

[o_e_l_e_o]

I've hit a dead end and am out of ideas

I'm afraid I am too. If it were me, I would be trying Linux instead, or even Windows Subsystem for Linux (WSL) or a virtual machine.

Paging @NeuroticFish @DaveF @HCP - not sure if any of these good folks might be able to figure this out.

[1714103926]

1714103926

[1714103926]

1714103926

[1714103926]

1714103926

[1714103926]

1714103926

[NeuroticFish]

Woah, I've "scanned" shortly the posts, from what I understand OP couldn't make even EPS work (and he's still keen to use EPS)?
If so, I recommend this post of mine where I managed to run EPS with Electrum. Maybe it hives hints of what is missing.
I remember that I did also hit a dead end .. until I've tried with Sparrow wallet which kinda hinted me that I should create a wallet file. Then all started working. But I didn't like it at all (I find Electrs a much better server).

[doggoboi]

I've had a break through just messing around with various check boxes but still no working EPS

I just created a new Bitcoin Core wallet with Descriptor wallet un-checked.  (IDK what descriptor does)  It was checked by default this whole time.
https://i.imgur.com/5uHbr4e.png

Can one of you advise really which of those settings should be checked when creating a new wallet with Bitcoin Core ?  - I think I've been selecting Make Blank Wallet and Descriptor Wallet.  Until now

Now this is what my command line looks like

https://i.imgur.com/58IWmNv.jpg


At least it looks a little different?!?!?!

[NotATether]

I just created a new Bitcoin Core wallet with Descriptor wallet un-checked.  (IDK what descriptor does)  It was checked by default this whole time.

The descriptor wallet just changes the export format of (bitcoin core) wallets from regular public keys to a data structure which includes derivation paths and unlocking scripts (eliminating problems such as "wrong derivation path used and now I can't see my addresses"). It's unlikely to be of any use to EPS [particularly if it doesn't support the descriptor wallet export format].

[o_e_l_e_o]

Can one of you advise really which of those settings should be checked when creating a new wallet with Bitcoin Core ?

When I've set up EPS in the past, I've always just left all the boxes unchecked. Wasn't aware that made a difference though.

https://i.imgur.com/58IWmNv.jpg

What happens next? Have you tried relaunching it after it's synchronized? Go back in to the console on Core and use the listaddressgroupings command again and see if your addresses have imported properly this time?

[doggoboi]

What happens next? Have you tried relaunching it after it's synchronized? Go back in to the console on Core and use the listaddressgroupings command again and see if your addresses have imported properly this time?

First thing I tried is listaddressgroupings but unfortunately it is still blank.  If I relaunch the exact same messages display.

[o_e_l_e_o]

Are you running Core Version 23.0? Here is an issue of several people experiencing hanging at the same point of "Synchronizing mempool": https://github.com/chris-belcher/electrum-personal-server/issues/266

Essentially, just add deprecatedrpc=fees to your bitcoin.conf file and then restart everything. Might be worth a try?

[doggoboi]

Are you running Core Version 23.0? Here is an issue of several people experiencing hanging at the same point of "Synchronizing mempool": https://github.com/chris-belcher/electrum-personal-server/issues/266

Essentially, just add deprecatedrpc=fees to your bitcoin.conf file and then restart everything. Might be worth a try?

I COULD KISS YOU!

Finally got a "Listening for Electrum Wallet"

https://i.imgur.com/qZhTVr2.jpg



At this point I just feel dumb

I am still getting a big red button when I start up Electrum - but at least I know that EPS can work!!!

On the electrum side - I have the command

"C:\Program Files (x86)\Electrum\electrum-4.2.2.exe" --oneserver --server 127.0.0.1:50002

to run as per one of the guides - but it is still showing red

[NeuroticFish]

"C:\Program Files (x86)\Electrum\electrum-4.2.2.exe" --oneserver --server 127.0.0.1:50002

I think that what you need there is (note the :s at the end) :

Code:

"C:\Program Files (x86)\Electrum\electrum-4.2.2.exe" --oneserver --server 127.0.0.1:50002:s

[o_e_l_e_o]

I COULD KISS YOU!

Finally got a "Listening for Electrum Wallet"

https://i.imgur.com/qZhTVr2.jpg

Amazing! God, took us long enough, haha. So in the end it seemed to be a combination of the Bitcoin Care wallet not being quite right, plus a bug with Bitcoin Core version 23.0.

I think that what you need there is (note the :s at the end) :

Yeah, I think this is right. If I run my Electrum without the s, then in Tools -> Network inside Electrum it just tries to connect to "localhost". If I include the s, then it correctly tries to connect to "127.0.0.1:50002".

[doggoboi]

I think that what you need there is (note the :s at the end) :

Code:

"C:\Program Files (x86)\Electrum\electrum-4.2.2.exe" --oneserver --server 127.0.0.1:50002:s

Thank you so much this fixed it.

What do you call these letter identifiers after the port number?  I saw the :s and another guide had a :t

Am I supposed to use :t to run it through Tor or something?

Yeah, I think this is right. If I run my Electrum without the s, then in Tools -> Network inside Electrum it just tries to connect to "localhost". If I include the s, then it correctly tries to connect to "127.0.0.1:50002".

That is exactly what happened

https://i.imgur.com/HRlWs6e.png

Oh glory green button how you have pained me.

Thank you guys for helping me solve this puzzle, can finally get my stuff off of the websites in peace

Just a last few questions

I read that Bitcoin Core stores your wallet data (xpub etc) unencrypted on the desktop.  Is there a setting to prevent that so only Electrum is handling the wallet data?

Also, is there a way to close the command line window of EPS once it's running? X-ing it out closes the server currently.

[NeuroticFish]

What do you call these letter identifiers after the port number?  I saw the :s and another guide had a :t

Am I supposed to use :t to run it through Tor or something?

The letter is basically the protocol identifier, though for each protocol there's a default port. It's not something related to Tor.

supported protocols (“t” = tcp@50001, “h” = http@8081, “s” = tcp/tls@50002, “g” = https@8082; non-standard port would be announced this way: “t3300” for tcp on port 3300)

I read that Bitcoin Core stores your wallet data (xpub etc) unencrypted on the desktop.  Is there a setting to prevent that so only Electrum is handling the wallet data?

1. xpub is not a security concern.
2. I guess that it cannot work without that info in Bitcoin Core (that was my missing bit and one of the reasons I've dropped EPS), but, as we said in the past, maybe you consider switching to Electrs server which doesn't care/works as good no matter how many wallets you use in Electrum (and doesn't need any wallet info in Bitcoin core)

Also, is there a way to close the command line window of EPS once it's running? X-ing it out closes the server currently.

Did you try Ctrl-C?

[o_e_l_e_o]

I read that Bitcoin Core stores your wallet data (xpub etc) unencrypted on the desktop.  Is there a setting to prevent that so only Electrum is handling the wallet data?

Not really. Public keys are not encrypted in Bitcoin Core wallets, only the private keys are (which your Bitcoin Core wallet shouldn't contain anyway). Whenever Core is running, then it must have access to your public keys to be able to watch the relevant addresses for transactions. You could encrypt your wallet file manually (using something like VeraCrypt, for example) so it cannot be accessed by anyone else, but you would need to decrypt it every time you wanted to run Core or your EPS.

Also, is there a way to close the command line window of EPS once it's running? X-ing it out closes the server currently.

Don't think so. You could use a virtual desktop to hide it where you can't see it, though.