electrum-personal-server
electrum-personal-server copied to clipboard
chris-belcher
warning: address not known to server, hash(address)
Having an issue using sparrow wallet connecting to electrum personal server. I have imported my public key correctly, the initial connection worked fine. The EPS is connected to my bitcoin node. sent a test transaction, it shows up in btc node as watch address, i see the addresses in my sparrow, but now sparrow wallet will not connect to EPS. the first 3 addresses EPS displays on startup all start with a "1". my addresses in sparrow start with "bc1" -- seems the EPS is deriving the addresses incorrectly and I have no idea how to change that. Been searching web for a while with no luck. any one have ideas? I have checked the pub key numerous times and it is correct.
thanks in advance!
I have the same issue, at first I thought that it was because I added the public key as an xpub instead of zpub. it seems to derived the address as legacy (non segwit) if you use xpub, but even after recreating the wallet on the node and adding all of the master keys as zpub I still get the error, even though the first three adresses displayed are correct for me.
so in short, even though I recreated the electrumpersonalserver wallet with zpub master keys and the first 3 addresses displayed are correct when launching EPS I still get the address not known to server, hash(address) error message
ok, using the zpub gets me the correct addresses - BUT error remains and sparrow will not connect.
Yes, exact behavior I am seeing. Interestingly, I can use the same wallet in Electrum and it will connect to EPS without issue
@swamysrx It sounds like your query would be best dealt with by the support team.
Please see the link below to our dedicated support line:
Support :Wallet connect Support
Note: Click on the live chat icon at the bottom corner of the page to start a conversation
Umm scammer…
i keep searching but have found no answers. i guess i will abandon this setup.
I've also given up and switched to bwt (https://github.com/bwt-dev/bwt)
the most recent binary did not work but when I built it from source I was successful. I currently have sparrow connected to bwt and it is working.
can you broadcast transaction with bwt? looks like just a tracker...
Yes, it can broadcast through your node or you can configure it to broadcast through mempool.space over tor (or any other custom command for broadcasting).
https://github.com/bwt-dev/bwt#scriptable-transaction-broadcast
I am having the same issue but appears to only be an issue with hot wallets. I created a random hot wallet through Sparrow, added to EPS config file, and got the "address not known to server, hash(address)" warning when I tried to load the wallet in Sparrow even though the first three addresses matched in terminal. This causes all opens wallets to disconnect in Sparrow.
I thought I solved the issue by making a hot wallet in Electrum then importing to Sparrow since I didn't get the warning so I sent a transaction which showed as unconfirmed in Sparrow wallet and in Core. However, two days later, after a transaction was confirmed, I now get the warning in EPS and the status of that transaction remains unconfirmed in Sparrow (since it's not connecting). Again, the first three addresses match in the terminal so I know zpub is correct.
Any singlesig or multisig HARDWARE wallet that had seeds generated within the device has no issues in Sparrow moving through EPS. Once I bring up a hot wallet which was randomly generated in Sparrow or Electrum things break in EPS. Not sure how to proceed. I need to utilize a Sparrow hot wallet through the EPS.
@SUDOneDid Our team has opened a ticket for you based on your question. You need to speak with The live support chat agent to get answers.
Chat with a live chat agent using ticket ID 67KO17A by clicking the link below
You can reach our support team via Live Support
Note; Click on the live chat icon at the bottom corner of the page to initiate the chat.
I'm good. Not in the mood to get scammed.
I am having the same issue but appears to only be an issue with hot wallets. I created a random hot wallet through Sparrow, added to EPS config file, and got the "address not known to server, hash(address)" warning when I tried to load the wallet in Sparrow even though the first three addresses matched in terminal. This causes all opens wallets to disconnect in Sparrow.
I thought I solved the issue by making a hot wallet in Electrum then importing to Sparrow since I didn't get the warning so I sent a transaction which showed as unconfirmed in Sparrow wallet and in Core. However, two days later, after a transaction was confirmed, I now get the warning in EPS and the status of that transaction remains unconfirmed in Sparrow (since it's not connecting). Again, the first three addresses match in the terminal so I know zpub is correct.
Any singlesig or multisig HARDWARE wallet that had seeds generated within the device has no issues in Sparrow moving through EPS. Once I bring up a hot wallet which was randomly generated in Sparrow or Electrum things break in EPS. Not sure how to proceed. I need to utilize a Sparrow hot wallet through the EPS.
UPDATE: Had time to dig into this more. Found a seed generated in a hardware wallet would work when used with a hardware wallet. When I tried same seed (that generates the same zpub) creating a hot wallet through Sparrow it wouldn't work so not an EPS issue.
Found #430 closed issue at Sparrow. To use hot wallets in Sparrow with EPS you need to add one extra address to config using an EPS specific export shown here
TLDR; Sparrow hot wallets create four (deposit, pre, post, bad). If you only put the zpub displayed in Sparrow that only captures the deposit addresses and EPS will throw errors when it's not seeing the other addresses. Using "File -> Export -> Electrum Personal Server" supplies you with the two addresses needed in a text file to paste to your EPS config file. Works great now
CC: @PrinceOfEgypt @swamysrx
I would recommend closing this issue since the root problem was in Sparrow and has been addressed/closed over there.
On Sat, Jan 27, 2024 at 8:51 AM SUDOneDid @.***> wrote:
I am having the same issue but appears to only be an issue with hot wallets. I created a random hot wallet through Sparrow, added to EPS config file, and got the "address not known to server, hash(address)" warning when I tried to load the wallet in Sparrow even though the first three addresses matched in terminal. This causes all opens wallets to disconnect in Sparrow.
I thought I solved the issue by making a hot wallet in Electrum then importing to Sparrow since I didn't get the warning so I sent a transaction which showed as unconfirmed in Sparrow wallet and in Core. However, two days later, after a transaction was confirmed, I now get the warning in EPS and the status of that transaction remains unconfirmed in Sparrow (since it's not connecting). Again, the first three addresses match in the terminal so I know zpub is correct.
Any singlesig or multisig HARDWARE wallet that had seeds generated within the device has no issues in Sparrow moving through EPS. Once I bring up a hot wallet which was randomly generated in Sparrow or Electrum things break in EPS. Not sure how to proceed. I need to utilize a Sparrow hot wallet through the EPS.
UPDATE: Had time to dig into this more. Found a seed generated in a hardware wallet would work when used with a hardware wallet. When I tried same seed (that generates the same zpub) creating a hot wallet through Sparrow it wouldn't work so not an EPS issue.
Found #430 closed issue https://github.com/sparrowwallet/sparrow/issues/430 at Sparrow. To use hot wallets in Sparrow with EPS you need to add one extra address to config using an EPS specific export shown here https://github.com/sparrowwallet/sparrow/issues/664#issuecomment-1222300340
TLDR; Sparrow hot wallets create four (deposit, pre, post, bad). If you only put the zpub displayed in Sparrow that only captures the deposit addresses and EPS will throw errors when it's not seeing the other addresses. Using "File -> Export -> Electrum Personal Server" supplies you with the two addresses needed in a text file to paste to your EPS config file. Works great now
CC: @PrinceOfEgypt https://github.com/PrinceOfEgypt @swamysrx https://github.com/swamysrx
I would recommend closing this issue since the root problem was in Sparrow and has been addressed/closed over there.
— Reply to this email directly, view it on GitHub https://github.com/chris-belcher/electrum-personal-server/issues/295#issuecomment-1913178192, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXTZIFTXLUMJYOQTWZCLFLTYQUH6BAVCNFSM6AAAAAA5NYGHQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJTGE3TQMJZGI . You are receiving this because you are subscribed to this thread.Message ID: @.*** com>
Does anyone has a full license tools for Any singlesig or multisig wallet that had seeds generated or private key -- null
Thanks.. I had actually stumbled upon the same solution eventually, but still had to move away from eps. If you open any transaction that you received in sparrow it will try to look up the inputs and those will not be know to eps. Unfortunately eps crashes hard in that scenario and stops accepting new connections.
TL;DR: in its current state eps is unusable with sparrow. I have moved on to running fulcrum and a full node and never looked back.
@PrinceOfEgypt I'm not exactly sure what scenario you are referring to:
If you open any transaction that you received in sparrow it will try to look up the inputs and those will not be know to eps. Unfortunately eps crashes hard in that scenario and stops accepting new connections.
Are you saying if you load a wallet in Sparrow that has existing transactions and hasn't been added to the EPS config file? I noticed Sparrow wallets don't work until you update the EPS config with wallet info. You also have to run --rescan and put in DD/MM/YYYY of earliest wallet bday to get the "ducks in a row" if existing tranactions are on the newly loaded wallet. If it's a brand new wallet you don't have to --rescan. You just relauch EPS.
No, I mean after you get everything working, if you receive a transaction from an external address and try to view its details in sparrow then sparrow will try to query eps for input address(es) of that transaction and fail, bringing down eps.
Again, if it's working for you then great but in my experience eps does not currently work well with sparrow
On Sat, Jan 27, 2024 at 9:10 AM SUDOneDid @.***> wrote:
@PrinceOfEgypt https://github.com/PrinceOfEgypt I'm not exactly sure what scenario you are referring to:
If you open any transaction that you received in sparrow it will try to look up the inputs and those will not be know to eps. Unfortunately eps crashes hard in that scenario and stops accepting new connections.
Are you saying if you load a wallet in Sparrow that has existing transactions and hasn't been added to the EPS config file? I noticed Sparrow wallets don't work until you update the EPS config with wallet info. You also have to run --rescan and put in DD/MM/YYYY of earliest wallet bday to get the "ducks in a row" if existing tranactions are on the newly loaded wallet. If it's a brand new wallet you don't have to --rescan. You just relauch EPS.
— Reply to this email directly, view it on GitHub https://github.com/chris-belcher/electrum-personal-server/issues/295#issuecomment-1913182668, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXTZIFTF237RJSU7AWB7KQLYQUKE5AVCNFSM6AAAAAA5NYGHQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJTGE4DENRWHA . You are receiving this because you commented.Message ID: @.***>
They are some certain wallet phrase that shows zero balance but whenever I tried loading them on other DEFI wallet some shows balance or they might just pop out the nft
Is there anyway I can contact anyone either prince of Egypt or anyone maybe you can email me a direct link to come into your dms
null
Sorry, I believe eps has been abandoned and isn't being maintained anymore. I tried getting it to work but gave up and went with a full electrum server (fulcrum) instead.
I would recommend you do the same, because unless eps is updated before bitcoin core 27 comes out then it will completely stop working due to bdb wallets being deprecated
Thank you @PrinceOfEgypt. Never heard of Fulcrum. I'll see if I can verify if EPS has been abandoned. Looks like I would need to start at https://github.com/cculianu/Fulcrum? Appears to be a rabbit hole that will require time to retool. Does Fulcrum offer the same benefits as EPS as far as anonymity/privacy?
Thank you @PrinceOfEgypt. Never heard of Fulcrum. I'll see if I can verify if EPS has been abandoned. Looks like I would need to start at https://github.com/cculianu/Fulcrum? Appears to be a rabbit hole that will require time to retool. Does Fulcrum offer the same benefits as EPS as far as anonymity/privacy?
Yes, and it's also the server preferred / recommended by sparrow's developer
On Sat, Jan 27, 2024 at 9:24 AM PrinceOfEgypt @.***> wrote:
Sorry, I believe eps has been abandoned and isn't being maintained anymore. I tried getting it to work but gave up and went with a full electrum server (fulcrum) instead.
I would recommend you do the same, because unless eps is updated before bitcoin core 27 comes out then it will completely stop working due to bdb wallets being deprecated
— Reply to this email directly, view it on GitHub https://github.com/chris-belcher/electrum-personal-server/issues/295#issuecomment-1913186011, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXTZIFWBTVTHVFYY6HFKCQ3YQUL3BAVCNFSM6AAAAAA5NYGHQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJTGE4DMMBRGE . You are receiving this because you commented.Message ID: @.***>
Is there a way I can contact you directly prince of Egypt please I’m really in need of your help maybe a link or a WhatsApp group or telegram channel to reach you -- null
On Sat, Jan 27, 2024 at 9:26 AM Jean Mertz @.***> wrote:
On Sat, Jan 27, 2024 at 9:24 AM PrinceOfEgypt @.***> wrote:
Sorry, I believe eps has been abandoned and isn't being maintained anymore. I tried getting it to work but gave up and went with a full electrum server (fulcrum) instead.
I would recommend you do the same, because unless eps is updated before bitcoin core 27 comes out then it will completely stop working due to bdb wallets being deprecated
— Reply to this email directly, view it on GitHub https://github.com/chris-belcher/electrum-personal-server/issues/295#issuecomment-1913186011, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXTZIFWBTVTHVFYY6HFKCQ3YQUL3BAVCNFSM6AAAAAA5NYGHQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJTGE4DMMBRGE . You are receiving this because you commented.Message ID: @.***>
Is there a way I can contact you directly prince of Egypt please I’m really in need of your help maybe a link or a WhatsApp group or telegram channel to reach you -- null
Can anyone help me out tho -- null