I have the 2020 .dat backed up in multipe locations so not to worried about anything happening this copy of a backup. 

I am now wondering can i just make a new backup of the wallet from core 27.1.0 and that will be it sorted.

Thanks

Just loaded an old Core backup from 2020 and was informed about migration in version 27.1.0, is this something i need to do soon?  it talked about legacy wallets, but all the addresses in the backup are bc1q, native segwit addressess.  Anything i should be concerned about or is it pretty straight forward?

Thanks

Thanks for all the replies, particularly from nc50lc.  As always a cool came reply.  Thanks

I am about to do an IBD and i have assumevalid=(Latest block). i understand some of the risks involved with this, regarding being feed a false history etc:  But if i don't plan to use the node to validate transactions for a long time 6 month min then i am assuming that my node will eventually check all blocks thoroughly and so its fine. 

Thanks

This is correct, I renamed the old, locked "chainstate" folder to "chain" then ran bitcoind -reindex.  Bitcoin core created a new chainstate folder,  until that point, --reindex/--reindex-chainstate wouldnt work.   

2024-02-28T11:07:52Z Initializing databases...
2024-02-28T11:07:52Z Wiping LevelDB in E:\BitcoinNode\chainstate
2024-02-28T11:07:52Z Opening LevelDB in E:\BitcoinNode\chainstate
2024-02-28T11:07:52Z Fatal LevelDB error: IO error: E:\BitcoinNode\chainstate/LOCK: The file or directory is corrupted and unreadable.\x0d

2024-02-28T11:07:52Z You can use -debug=leveldb to get more complete diagnostic messages
2024-02-28T11:07:52Z Fatal LevelDB error: IO error: E:\BitcoinNode\chainstate/LOCK: The file or directory is corrupted and unreadable.\x0d

2024-02-28T11:07:52Z Error: Error opening block database
2024-02-28T11:07:52Z Shutdown: In progress...
2024-02-28T11:07:52Z scheduler thread exit
2024-02-28T11:07:52Z Shutdown: done

PC Crashed yesterday due to a graphics error, nothing to do with Bitcoin core.  went to run core again today but getting this error below.  I had a look in the Chainstate folder and all files are locked by Microsoft Access, any ideas on how to resolve this? 

also tried running with arg -reindex but still error.

Thanks



2024-02-28T10:21:38Z Opening LevelDB in E:\BitcoinNode\chainstate
2024-02-28T10:21:38Z Fatal LevelDB error: IO error: E:\BitcoinNode\chainstate/LOCK: The file or directory is corrupted and unreadable.\x0d

2024-02-28T10:21:38Z You can use -debug=leveldb to get more complete diagnostic messages
2024-02-28T10:21:38Z Fatal LevelDB error: IO error: E:\BitcoinNode\chainstate/LOCK: The file or directory is corrupted and unreadable.\x0d

2024-02-28T10:21:38Z : Error opening block database.
Please restart with -reindex or -reindex-chainstate to recover.
: Error opening block database.
Please restart with -reindex or -reindex-chainstate to recover.
2024-02-28T10:21:38Z Aborted block database rebuild. Exiting.
2024-02-28T10:21:38Z Shutdown: In progress...
2024-02-28T10:21:38Z scheduler thread exit
2024-02-28T10:21:38Z Shutdown: done

Many thanks for the replies always great to get help here.  I ended up putting the multisig backup into Sparrow wallet and it worked first time, it found the jade and just used it to sign.  i will play around and getting it working on Electrum for the learning.   

Thanks again

So i just cut and paste the 3 Zpubs into a new electrum 2of3 and it recognized the previous transactions.  however, when i went to send it doesn't give me the option to sign.  I get it, electrum doesn't know anything about the HWs now, any ideas on how to work this out?

so in the Preview pay page, the sign button is greyed out. There must be a way to initialise the HWs?

Yes this is right.  The Ledger I originally used has shit itself and i don't want to buy another Ledger.  So when i connect my HW to Electrum it is asking for the fingerprint of the Ledger.  There is bound to be away around this, nc50lc hs given me an idea, i will let yous know how it works.  Thanks for the replies.

So i have a 2 of 3 setup using a trezor, jade and a ledger.  I recently put the seed words for the ledger onto a jade HW and tried to use it to sign a transaction as if it were from the ledger.

 Electrum is looking for the ledger bip32 root fingerprint, so even tho the seed is the same but is on a jade. is there a way to get Electrum to recognize the jade as the ledger?

So trying to verify 24.0 but using Kleopatra I keep getting a "signatures could not be verified" message.  I am guessing this is because I need at least one of the builder keys from the github key list.  But when I try to import one of them using this

gpg.exe --keyserver hkps://keys.openpgp.org --recv-keys E463A93F5F3117EEDE6C7316BD02942421F4889F

I keep on getting "keyserver receive failed: Certificate expired" message, which surely can't be right, what am I doing wrong here. 

Thanks got it..... 

When verifying the latest Bitcoin core software I get this below.  i am sure its probably fine but it just doesn't look right "Can't check signature: No public key".  what am I doing wrong?

Downloads$ gpg --verify SHA256SUMS.asc
gpg: assuming signed data in 'SHA256SUMS'
gpg: Signature made Fri 22 Apr 2022 17:03:04 BST
gpg:                using RSA key 152812300785C96444D3334D17565732E08E5E41
gpg:                issuer "achow101@gmail.com"
gpg: Can't check signature: No public key
gpg: Signature made Fri 22 Apr 2022 17:17:06 BST
gpg:                using RSA key 0AD83877C1F0CD1EE9BD660AD7CC770B81FD22A8
gpg:                issuer "benthecarman@live.com"
gpg: Can't check signature: No public key
gpg: Signature made Fri 22 Apr 2022 12:54:30 BST
gpg:                using RSA key 590B7292695AFFA5B672CBB2E13FC145CD3F4304
gpg:                issuer "darosior@protonmail.com"
gpg: Can't check signature: No public key
gpg: Signature made Fri 22 Apr 2022 09:25:24 BST
gpg:                using RSA key 28F5900B1BB5D1A4B6B6D1A9ED357015286A333D
gpg: Can't check signature: No public key
gpg: Signature made Fri 22 Apr 2022 19:39:41 BST
gpg:                using RSA key 637DB1E23370F84AFF88CCE03152347D07DA627C
gpg: Can't check signature: No public key
gpg: Signature made Fri 22 Apr 2022 09:22:55 BST
gpg:                using RSA key CFB16E21C950F67FA95E558F2EEB9F5CC09526C1
gpg:                issuer "fanquake@gmail.com"
gpg: Can't check signature: No public key
gpg: Signature made Fri 22 Apr 2022 09:36:47 BST
gpg:                using RSA key F4FC70F07310028424EFC20A8E4256593F177720
gpg:                issuer "gugger@gmail.com"
gpg: Can't check signature: No public key
gpg: Signature made Fri 22 Apr 2022 09:22:08 BST
gpg:                using RSA key D1DBF2C4B96F2DEBF4C16654410108112E7EA81F
gpg:                issuer "hebasto@gmail.com"
gpg: Can't check signature: No public key
gpg: Signature made Sat 23 Apr 2022 09:39:06 BST
gpg:                using RSA key 287AE4CA1187C68C08B49CB2D11BD4F33F1DB499
gpg: Can't check signature: No public key
gpg: Signature made Sun 24 Apr 2022 09:31:28 BST
gpg:                using RSA key F9A8737BF4FF5C89C903DF31DD78544CF91B1514
gpg: Can't check signature: No public key
gpg: Signature made Sat 23 Apr 2022 13:39:56 BST
gpg:                using ECDSA key C388F6961FB972A95678E327F62711DBDCA8AE56
gpg:                issuer "kvaciral@protonmail.com"
gpg: Can't check signature: No public key
gpg: Signature made Fri 22 Apr 2022 17:18:09 BST
gpg:                using RSA key 9DEAE0DC7063249FB05474681E4AED62986CD25D
gpg: Can't check signature: No public key
gpg: Signature made Sat 23 Apr 2022 05:43:29 BST
gpg:                using RSA key E463A93F5F3117EEDE6C7316BD02942421F4889F
gpg: Can't check signature: No public key
gpg: Signature made Fri 22 Apr 2022 09:56:54 BST
gpg:                using RSA key 9D3CC86A72F8494342EA5FD10A41BDC3F4FAFF1C
gpg:                issuer "aaron@sipsorcery.com"
gpg: Can't check signature: No public key
gpg: Signature made Fri 22 Apr 2022 13:32:27 BST
gpg:                using RSA key 4DAF18FE948E7A965B30F9457E296D555E7F63A7
gpg: Can't check signature: No public key
gpg: Signature made Sat 23 Apr 2022 18:21:37 BST
gpg:                using RSA key 28E72909F1717FE9607754F8A7BEB2621678D37D
gpg:                issuer "vertion@protonmail.com"
gpg: Can't check signature: No public key
gpg: Signature made Fri 22 Apr 2022 09:50:58 BST
gpg:                using RSA key 74E2DEF5D77260B98BC19438099BAD163C70FBFA
gpg:                issuer "will8clark@gmail.com"
gpg: Can't check signature: No public key

Thanks for the replies guys.  I think I'm getting the vibe that this isn't a great idea.  it is at a physical meetup and there is prob a lot that could go wrong over time.  Appreciate the replies as always. 

Hi all, me and a couple of bitcoiners have been considering running a coinjoin thing at our local meetup, but are wondering if it is even worth doing?  i haven't really gamed it out in my head yet, just thought I would come on here and have you guys blow holes in it quickly if it's stupid.  fire away.

roughly 10- 20 participants with 0.01 btc

NO others, (including clearnet nodes) can connect to a Tor node.

The best why to support the Bitcoin network is to buy and hold bitcoin.  self custody it and use your own Node to verify you received it. 

Anything replacing Bitcoin would destroy the store of value thesis which is a fundamental of money, this would be game over.  I dont believe it will ever happen as the market is not that stupid. 

Most people who ask or believe it are basically hoping their bags will be the one to do it.  If your altcoin could do it then what would stop your alt being replaced in 10 years by another.....? ie: Store of value would be dead.

Doh, im an idiot sorry ........ 

I currently have Core 0.20.1 , but i just checked both the post by AChow on this site and the bitcoincore.org and they say the latest is 0.20.0