Transaction

be903a8fde92df70a32c4fcdcf5d09d4b137ddb9ba6845eae64c52f3f9111fdd
2024-03-23 06:45:12
0.00000015 BSV
(
0.03392309 BSV
-
0.03392294 BSV
)
10.33 sat/KB
1
75,028
1,451 B

2 Outputs

Total Output:
0.03392294 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM®<div class="post">That is what happens if you copy wallet files around.&nbsp; If you copy your wallet file to a second computer, then they both think the money in the wallet is theirs.&nbsp; If one spends any of it, the other doesn't know those coins are already spent and would try to spend them again, and that's the error you would hit.<br/><br/>Now that it's clear this is a key error message, it ought to be something more like "the money appears to be already spent...&nbsp; this could happen if you used a copy of your wallet file on another computer." <br/><br/>You can move or backup your wallet file, but it needs to have only one "lineage" and only used in one place at a time.&nbsp; Any time you transfer money out of it, then you must no longer use any previous copies.<br/><br/>This brings up a good point.&nbsp; In the case of restoring a backup that may be from before you spent some coins, we need to add functionality to resync it to discover which coins have already been spent.&nbsp; This would not be hard to do, it just hasn't been implemented yet.&nbsp; I'll add it to the list.&nbsp; This would make it mostly repair the situation instead of giving that error message.</div> text/html
    https://whatsonchain.com/tx/be903a8fde92df70a32c4fcdcf5d09d4b137ddb9ba6845eae64c52f3f9111fdd