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   

Thanks for the replies.  will try adding bind=127.0.0.1 and see, i know it can take awhile to be found. 

Cheers

No matter what everytime you are making a change backup your wallet.dat to a safe location

Like if i am onlynet=onion how can i have an incoming connection to my real ip?

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

I am currently running a Tor node on a linux Laptop and want to connect my Node on my Windows machine to it and it only.  How do i get my windows node to only connect to it.  when i looked for my Tor node Ip it was an ipv4 not a .onion

So how do i connect to my Tor node is really the question i am asking and the answer i want? 

i am not really familiar with the coinbase platform.  but if you are looking to secure your bitcoin into your own custody and store them on the ledger then you just set up the ledger and generate a new bitcoin address.  you then send the bitcoin at the coinbase pro account to the ledger address you generate.

So the address in getnetworkinfo and addlocaladdress in debug is just an Ipv4 address i was expecting it to be a something like jbsdfkasjdbfkdbf.onion (example) is that just how others see it?

Is that address a tor guard node that i am using?

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)

If Only

No such file or directory.