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

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

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

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. 

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

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

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   

Been running a Node over Tor for weeks now (outgoing only) decided to add listen=1 to the .conf  so now i am getting incoming but some of the 1st connections were to my actual ip address.  all of the new connections recently are incoming to 127.0.0.1:9050 but there is still one currently connected to my actual ip.   this seems strange to me considering my .conf can anyone explain why this would be happening?


txindex=1
server=1
blockfilterindex=1
listen=1
proxy=127.0.0.1:9050
onlynet=onion
dnsseed=0
dns=0

Ok so i managed to work out and set up a Bitcoin node that runs over Tor but i cant seem to find my .onion address.  I have ran bitcoind and never seem to see any .onion address.  i can see that all the addresses i connect to are through different ips but if someone wanted to connect to me how do they do that?

Hi

quick question, obviously a Tor node can have incoming connections,  so how does an inbound node find my node? (ie: ip address)

[Letter Text]

i set up a Node running over Tor last week and am now receiving a message from my ISP that i am vulnerable to a potential Multicast DNS vulnerability.  I have read that this is something to do with using 127.0.0.1 but don't really get why.  Anyone understand whats going on here?

I have put the text from the ISP provider below for reference.


Letter Text

Your home devices could be at risk

We're writing to let you know that a device connected to your home network has been identified as having a potential Multicast DNS vulnerability.

Multicast DNS is commonly used to share music and video streaming services between devices on your home network. When exposed to the wider Internet, it can be misused by 3rd parties in order to commit abuse.

It is therefore important that you follow the advice in this letter.

What has happened?

We suspect the device may have been misconfigured by you, someone in your household or without your knowledge. If the settings are left unchanged they can be exploited to unwittingly participate in malicious activities, for example a Distributed Denial of Service (DDoS) attack.

Hi anyone know why Bitcoin Core 0.19.0.1 mempool info constantly shows N/A?

both Current number of transactions and memory usage just say N/A

Is there a command i can put in console that will give an address beginning with a 1?

Thanks

 i am trying to sign a message with a segwit address but when i do it says it is for a legacy address (beginning with  1)  Is this normal? i'm using Samouri wallet.

I have 2 node on the same network, one is 0.18.1 and the other is older 0.12.0.  I want to get 0.12 to stay connected to 0.18.1 permanently as its only connection for information whats the best way to go about that.

currently i can get them to connect simply by addnode in Conf but after a few minutes 0.18.1 is dropping the connection with 0.12.     also how do i stop from connecting to any other node.

Hi

i have just found an old electrum wallet with Bitcoin in it, what is the best way to brute force the password?  i sorta know what it might be but nothing i have tried is working......

Whats your opinions on storing bitcoins in the Bitcoin core wallet on a home PC with a strong password and regular malware scans?

Recently noticed that my core Node is using 100% cpu and whilst trying to fire up a eclair lightning node i noticed that the log said "Blockchain transactions are still in the process of being indexed".  how ever my node has been running for months.  any ideas?

Been getting this in my node debug log:  connection from 162.218.65.128:27555 dropped: not accepting new connections.  Its like every minute this is happening and it has been going on for weeks.     

Any ideas?