Bitcoin Forum
June 20, 2024, 12:57:58 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Bitcoin core showing 0 balance after transferring bw sparrow wallets  (Read 107 times)
Cronus1234 (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
May 18, 2024, 03:41:49 PM
 #1

Hi everyone,

I have core v25 connected to my fulcrum server with sparrow wallet. I recently transferred from one hardware wallet to another within sparrow using my node.

Core shows all the sending transactions but none of the receiving, even though sparrow shows all of the receiving.

How do I get core to view the receiving transactions as a positive balance? I feel like because all the transactions were done within sparrow this should be automatic but I can't seem to get core to see this receiving wallet

Any tips would be appreciated!

Thanks
achow101
Moderator
Legendary
*
Offline Offline

Activity: 3430
Merit: 6720


Just writing some code


View Profile WWW
May 19, 2024, 03:25:50 AM
 #2

Probably Sparrow uses different wallet files for different devices, so there should be a dropdown at the top right of Bitcoin Core that lets you choose a different wallet. Bitcoin Core does not show information for all wallets loaded, you need to choose specifically which wallet you want to view information for, and spend from.

nc50lc
Legendary
*
Offline Offline

Activity: 2450
Merit: 5723


Self-proclaimed Genius


View Profile
May 19, 2024, 05:06:32 AM
 #3

I have core v25 connected to my fulcrum server with sparrow wallet.
Hmm, If it's Fulcrum, then there shouldn't be a "mirrored" watch-only wallet in Bitcoin Core since it doesn't work like EPS or Sparrow's direct connection to Bitcoin Core.

What I'm thinking is you might have previously connected Sparrow to Core using either options (not Fulcrum) which created a watching-only wallet.
Thus the wallet where you're seeing the sending transactions.
But now that you're using Fulcrum, your new descriptors from the other (new?) hardware wallet aren't imported to that existing watch-only wallet.

Any tips would be appreciated!
If the above scenario is correct, you can manually import your new wallet's public descriptors to that watching-only wallet.
You can get it from Sparrow Wallet: "Settings Tab->Export>Output Descriptors"
Then import the Bitcoin Core-compatible descriptors to Bitcoin Core using importdescriptors command.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
Cronus1234 (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
May 22, 2024, 08:30:15 PM
 #4

I have core v25 connected to my fulcrum server with sparrow wallet.
Hmm, If it's Fulcrum, then there shouldn't be a "mirrored" watch-only wallet in Bitcoin Core since it doesn't work like EPS or Sparrow's direct connection to Bitcoin Core.

What I'm thinking is you might have previously connected Sparrow to Core using either options (not Fulcrum) which created a watching-only wallet.
Thus the wallet where you're seeing the sending transactions.
But now that you're using Fulcrum, your new descriptors from the other (new?) hardware wallet aren't imported to that existing watch-only wallet.

Any tips would be appreciated!
If the above scenario is correct, you can manually import your new wallet's public descriptors to that watching-only wallet.
You can get it from Sparrow Wallet: "Settings Tab->Export>Output Descriptors"
Then import the Bitcoin Core-compatible descriptors to Bitcoin Core using importdescriptors command.

Thank you! I managed to fix it with a Core reinstall before I saw your reply, but the logic of *how* to fix it was bugging the heck out of me. Your reply makes a lot of sense so I think it would have fixed it, but unfortunately I won't be able to find out for sure Sad Nonetheless you've finally put my mind at ease trying to figure out what the problem was haha.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!