Bitcoin Forum
May 26, 2024, 05:54:15 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Sparrow Wallet + Pruned Node  (Read 79 times)
BGK045 (OP)
Newbie
*
Offline Offline

Activity: 14
Merit: 6


View Profile
August 14, 2023, 11:56:54 AM
 #1

Hey everyone - I set up a pruned node (20 GB max). When I connected it to my Sparrow wallet, I got an error that says "Error: Wallet birthday earlier than Bitcoin Core prune date". I understand why I'm getting this error, but curious if this affects transactions going forward? If I'm just using the Sparrow + Core setup for privacy vs. a public server (i.e., I don't need to search the blockchain for txns), is this set up ok?
DaveF
Legendary
*
Offline Offline

Activity: 3486
Merit: 6309


Crypto Swap Exchange


View Profile WWW
August 14, 2023, 01:18:40 PM
 #2

It should be fine, but unless you are really tight on drive space it's better to run a full node.
There are just some things you will not be able to to do with a pruned node.

IF all you are doing is sending and receiving from addresses that are new it does not matter.

-Dave

█▀▀▀











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











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

Activity: 14
Merit: 6


View Profile
August 14, 2023, 01:19:38 PM
 #3

Got it - thank you!
nc50lc
Legendary
*
Offline Offline

Activity: 2422
Merit: 5640


Self-proclaimed Genius


View Profile
August 14, 2023, 01:36:28 PM
 #4

When I connected it to my Sparrow wallet, I got an error that says "Error: Wallet birthday earlier than Bitcoin Core prune date". I understand why I'm getting this error, but curious if this affects transactions going forward? If I'm just using the Sparrow + Core setup for privacy vs. a public server (i.e., I don't need to search the blockchain for txns), is this set up ok?
It's fine as long as Bitcoin Core has the blocks where your new (not-yet scanned) transactions are included.

If your earliest transactions are already scanned (by other server?), verified and saved to your Sparrow wallet, you can disregard that error message.
Scanning new transactions within the unpruned blocks wont be an issue.

Read this for more info: https://sparrowwallet.com/docs/connect-node.html#pruned-nodes

█▀▀▀











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











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
o_e_l_e_o
In memoriam
Legendary
*
Offline Offline

Activity: 2268
Merit: 18565


View Profile
August 14, 2023, 03:13:11 PM
 #5

Your node will continually prune blocks as time goes on, so the earliest you will be able to scan for transactions will also advance in time. Therefore any other wallets you create or import in to Sparrow will need to have later and later birthdays, or you will be unable to view their transactions and balances.

As long as Bitcoin Core has the Sparrow "cormorant" wallet, then it will continue to scan incoming blocks for transactions relevant to your addresses. If for any reason the cormorant wallet is moved, removed, doesn't load, etc., then you could miss transactions in blocks that are later pruned.
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!