ah, interesting.  what user:password does one use for the daemon URL?

Are you looking for this?- https://github.com/kyuupichan/electrumx/blob/master/contrib/systemd/electrumx.conf

try:

You'll probably find that it's picking up the bitcoind from /usr/local/bin instead of running the "bitcoind" in the local directory. If you want to override the "path"... use ./ notation to indicate you wish to run from the local dir (or provide the full path to the executable)...

For instance, from your "~/Downloads/bitcoin-sv-1.0.0.beta/src" directory

or, from anywhere

Assuming there is actually a "bitcoind" in your "~/Downloads/bitcoin-sv-1.0.0.beta/src/" directory

Not as far as I'm aware... BTC, BCH and BSV should all be using different datadirs...

It's possible that the ABC node is still being stupid and attempting to hijack existing BTC datadirs, like it did when the fork first happened... But as far as I'm aware, they stopped doing that.

I've successfully run BTC, BCH, BTG and other full nodes on the same machine at the same time.

I know you can run "Electrum", "Electron Cash" and "Electrum SV" at the same time... they all use different data directories and wallets. In addition, you can run Bitcoin Core alongside all of these without issue.

The problem you'll have is trying to use "Electron Cash" and "Electrum SV" with your own local "EPS", as I believe that "EPS" is only designed to work with Bitcoin Core and BTC... it will not work properly with forks like BCH and BSV.

"ElectrumX" however does support forks... and quite a lot of them... so you could theoretically run ElectrumX against a BCH or BSV full node client and then connect to it with "Electron Cash" or "Electrum SV". You would need a separate instance of "ElectrumX" for each coin/fork that you wanted to access.

So, something like this:

ElectrumX #1 -> Bitcoin Core
ElectrumX #2 -> Bitcoin ABC (or whatever the bch full node is called these days)
ElectrumX #3 -> BitcoinSV Core

You could then use:

Electrum -> ElectrumX #1
ElectronCash -> ElectrumX #2
ElectrumSV -> ElectrumX #3

You should read https://github.com/chris-belcher/electrum-personal-server#how-to
It means you have to use Bitcoin Blockchain. So it doesn't work for BCH and BSV.

https://github.com/chris-belcher/electrum-personal-server/releases/tag/eps-v0.2.0

Released notes:

https://github.com/chris-belcher/electrum-personal-server/blob/master/release-notes

That's a wrong command. Assuming you have installed python, run python3 setup.py install . You might need to use sudo if it refuses to install due to no permissions.

I may be wrong, but I always though you only connected to a single server at once? Like, you can use multiple servers in a short period of time (e.g every time you restart Electrum it can choose a different server), but since in the server list window it only shows a single connected server and there isn't even space for a multi listing, I believe you don't connect to multiple servers at once.

Correct... generally the best course of action would be to leave it on "Auto"... and simply use a VPN to hide your IP if that is your sole concern (and you're not wanting to run a personal server etc).

If you're just trying to obscure your IP... your options are TOR (or some other VPN). Although, running via VPNs has been the cause of issues for folks in the past. Mostly the inability to connect to servers and/or sync.

More info here: https://electrum.readthedocs.io/en/latest/tor.html

AFAIK your wallet sends the addresses it wants to know the balance/transaction to the node (server), the node figures out this info and sends the balance and transactions data back to you. Your wallet (client) is the one that initially knows the addresses, which are originated from the wallet seed.

Was that your question? (I may have misinterpreted it).

Yes, but only your IP. The server stills gets a list of your addresses (which could be bad for privacy).

Electrum is a convenience that obviously costs a bit of privacy. If you want full privacy, then running a full node is probably the answer.

If the privacy is your major concern then  you  have an option to run an Electrum personal server and benefit from its use. The only cons of such approach, as I see it, is the necessity to run in background a fully synced  bitcoind. That demon  is naturally going to  consume a lot of  space for blockchain storage which means  you need the disk (preferably SSD) with big capacity, .

This is a local thing, your own node is rejecting the tx. Fee logic is quite complicated actually, the age the utxo and the spent value in relation to the tx size as well as a min flat fee per tx all come into play. Lowering the minimum broadcast requirements below default for your node will allow you to push that tx to your node's mempool, but chances are it won't broadcast at all to the network.

These are the 2 settings you can mess with for Core: