jackg (OP)
Copper Member
Legendary
Offline
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
|
|
August 30, 2017, 09:10:50 PM Last edit: August 31, 2017, 04:19:20 PM by jackg |
|
I was running Bitcoin Core and it got up to about 5% through the blockchain and then said "connecting to peers" instead of what it normally says at the bottom (I was reindexing at the time so it was saying "reindexing files on disk"). I downloaded the blockchain a while ago and then realised that it would take a very long time to syncronise and would take up a lot of space. I then decided to give up but kept my old version of the blockchain. With about 20GB (as a total of the blocks and chainstate folders) I have blocks up to about 2 or 3 years ago - I think. 1. I've tried to reindex twice and got the same errors. 2. I then went to the command line and found a peer on bitnodes.21.co and attempted to use the addnode command to add the peer and nothing happend (there was a print out below from the console that said something like "null") - I did this after going to the debug window and noticing there were 0 connection (0 in, 0 out). debug.log 2017-08-30 16:34:39 Bitcoin version v0.14.2 2017-08-30 16:34:39 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2017-08-30 16:34:44 Assuming ancestors of block 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90 have valid signatures. 2017-08-30 16:34:44 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..." 2017-08-30 16:35:06 Default data directory C:\Users\Laptop\AppData\Roaming\Bitcoin 2017-08-30 16:35:06 Using data directory F:\Bitcoin\Bitcoin\Data 2017-08-30 16:35:06 Using config file F:\Bitcoin\Bitcoin\Data\bitcoin.conf 2017-08-30 16:35:06 Using at most 125 automatic connections (2048 file descriptors available) 2017-08-30 16:35:06 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements 2017-08-30 16:35:06 Using 2 threads for script verification 2017-08-30 16:35:06 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2017-08-30 16:35:06 Using wallet wallet.dat 2017-08-30 16:35:06 scheduler thread start 2017-08-30 16:35:06 init message: Verifying wallet... 2017-08-30 16:35:06 CDBEnv::Open: LogDir=F:\Bitcoin\Bitcoin\Data\database ErrorFile=F:\Bitcoin\Bitcoin\Data\db.log 2017-08-30 16:35:08 Bound to [::]:8333 2017-08-30 16:35:08 Bound to 0.0.0.0:8333 2017-08-30 16:35:08 Cache configuration: 2017-08-30 16:35:08 * Using 2.0MiB for block index database 2017-08-30 16:35:08 * Using 8.0MiB for chain state database 2017-08-30 16:35:08 * Using 1014.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space) 2017-08-30 16:35:08 init message: Loading block index... 2017-08-30 16:35:08 Opening LevelDB in F:\Bitcoin\Bitcoin\Data\blocks\index 2017-08-30 16:35:08 Opened LevelDB successfully 2017-08-30 16:35:08 Using obfuscation key for F:\Bitcoin\Bitcoin\Data\blocks\index: 0000000000000000 2017-08-30 16:35:08 Opening LevelDB in F:\Bitcoin\Bitcoin\Data\chainstate 2017-08-30 16:35:40 Opened LevelDB successfully 2017-08-30 16:35:40 Using obfuscation key for F:\Bitcoin\Bitcoin\Data\chainstate: c7c959be4dd03e37 2017-08-30 16:35:52 LoadBlockIndexDB: last block file = 44 2017-08-30 16:35:52 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=681, size=132845295, heights=222565...223521, time=2013-02-22...2013-02-28) 2017-08-30 16:35:52 Checking all blk files are present... 2017-08-30 16:35:52 LoadBlockIndexDB: transaction index disabled 2017-08-30 16:35:53 LoadBlockIndexDB: hashBestChain=00000000000002901b7e9e60bf00b9321edb43dab58ae9df9254109b9b216f41 height=223521 date=2013-02-28 03:28:11 progress=0.054055 2017-08-30 16:35:53 init message: Rewinding blocks... 2017-08-30 16:35:55 init message: Verifying blocks... 2017-08-30 16:35:55 Verifying last 6 blocks at level 3 2017-08-30 16:35:55 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE]. 2017-08-30 16:35:56 No coin database inconsistencies in last 7 blocks (1811 transactions) 2017-08-30 16:35:56 block index 47810ms 2017-08-30 16:35:56 init message: Loading wallet... 2017-08-30 16:35:56 nFileVersion = 140200 2017-08-30 16:35:56 Keys: 102 plaintext, 0 encrypted, 102 w/ metadata, 102 total 2017-08-30 16:35:56 wallet 207ms 2017-08-30 16:35:56 setKeyPool.size() = 100 2017-08-30 16:35:56 mapWallet.size() = 0 2017-08-30 16:35:56 mapAddressBook.size() = 1 2017-08-30 16:35:56 mapBlockIndex.size() = 223522 2017-08-30 16:35:56 nBestHeight = 223521 2017-08-30 16:35:56 Imported mempool transactions from disk: 0 successes, 0 failed, 0 expired 2017-08-30 16:35:56 torcontrol thread start 2017-08-30 16:36:00 init message: Loading addresses... 2017-08-30 16:36:00 upnp thread start 2017-08-30 16:36:00 Loaded 398 addresses from peers.dat 91ms 2017-08-30 16:36:00 init message: Loading banlist... 2017-08-30 16:36:00 init message: Starting network threads... 2017-08-30 16:36:00 net thread start 2017-08-30 16:36:00 dnsseed thread start 2017-08-30 16:36:00 addcon thread start 2017-08-30 16:36:00 msghand thread start 2017-08-30 16:36:00 opencon thread start 2017-08-30 16:36:00 init message: Done loading 2017-08-30 16:36:00 GUI: Platform customization: "windows" 2017-08-30 16:36:00 GUI: PaymentServer::LoadRootCAs: Loaded 49 root certificates 2017-08-30 16:36:08 No valid UPnP IGDs found 2017-08-30 16:36:08 upnp thread exit 2017-08-30 16:36:11 Loading addresses from DNS seeds (could take a while) 2017-08-30 16:36:12 93 addresses found from DNS seeds 2017-08-30 16:36:12 dnsseed thread exit 2017-08-30 17:47:53 tor: Thread interrupt 2017-08-30 17:47:53 net thread exit 2017-08-30 17:47:53 opencon thread exit 2017-08-30 17:47:53 addcon thread exit 2017-08-30 17:47:53 torcontrol thread exit 2017-08-30 17:47:53 msghand thread exit 2017-08-30 17:47:53 scheduler thread interrupt 2017-08-30 17:47:54 Shutdown: In progress... 2017-08-30 17:47:56 Dumped mempool: 0.002s to copy, 0.090005s to dump 2017-08-30 17:48:06 Shutdown: done
Any ideas?
|
|
|
|
achow101
Moderator
Legendary
Offline
Activity: 3444
Merit: 6748
Just writing some code
|
|
August 30, 2017, 10:54:07 PM |
|
Start with the -debug option and post the full debug.log from that (it may be very large).
|
|
|
|
jackg (OP)
Copper Member
Legendary
Offline
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
|
|
August 30, 2017, 11:07:34 PM |
|
2017-08-30 23:03:52 Bitcoin version v0.14.2 2017-08-30 23:03:52 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2017-08-30 23:03:53 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..." 2017-08-30 23:03:53 Assuming ancestors of block 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90 have valid signatures. 2017-08-30 23:03:55 RandAddSeedPerfmon: 228448 bytes 2017-08-30 23:03:55 Default data directory C:\Users\Laptop\AppData\Roaming\Bitcoin 2017-08-30 23:03:55 Using data directory F:\bitcoin\bitcoin\data 2017-08-30 23:03:55 Using config file F:\bitcoin\bitcoin\data\bitcoin.conf 2017-08-30 23:03:55 Using at most 125 automatic connections (2048 file descriptors available) 2017-08-30 23:03:55 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements 2017-08-30 23:03:55 Using 2 threads for script verification 2017-08-30 23:03:55 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2017-08-30 23:03:55 scheduler thread start 2017-08-30 23:03:55 Using wallet wallet.dat 2017-08-30 23:03:55 init message: Verifying wallet... 2017-08-30 23:03:55 CDBEnv::Open: LogDir=F:\bitcoin\bitcoin\data\database ErrorFile=F:\bitcoin\bitcoin\data\db.log 2017-08-30 23:03:56 Bound to [::]:8333 2017-08-30 23:03:56 Bound to 0.0.0.0:8333 2017-08-30 23:03:56 Cache configuration: 2017-08-30 23:03:56 * Using 2.0MiB for block index database 2017-08-30 23:03:56 * Using 8.0MiB for chain state database 2017-08-30 23:03:56 * Using 1014.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space) 2017-08-30 23:03:56 init message: Loading block index... 2017-08-30 23:03:56 Opening LevelDB in F:\bitcoin\bitcoin\data\blocks\index 2017-08-30 23:03:56 Opened LevelDB successfully 2017-08-30 23:03:56 Using obfuscation key for F:\bitcoin\bitcoin\data\blocks\index: 0000000000000000 2017-08-30 23:03:56 Opening LevelDB in F:\bitcoin\bitcoin\data\chainstate 2017-08-30 23:03:56 Opened LevelDB successfully 2017-08-30 23:03:56 Using obfuscation key for F:\bitcoin\bitcoin\data\chainstate: c7c959be4dd03e37 2017-08-30 23:04:00 LoadBlockIndexDB: last block file = 44 2017-08-30 23:04:00 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=681, size=132845295, heights=222565...223521, time=2013-02-22...2013-02-28) 2017-08-30 23:04:00 Checking all blk files are present... 2017-08-30 23:04:00 LoadBlockIndexDB: transaction index disabled 2017-08-30 23:04:00 LoadBlockIndexDB: hashBestChain=00000000000002901b7e9e60bf00b9321edb43dab58ae9df9254109b9b216f41 height=223521 date=2013-02-28 03:28:11 progress=0.054039 2017-08-30 23:04:00 init message: Rewinding blocks... 2017-08-30 23:04:02 Committing 0 changed transactions (out of 0) to coin database... 2017-08-30 23:04:02 init message: Verifying blocks... 2017-08-30 23:04:02 Verifying last 6 blocks at level 3 2017-08-30 23:04:02 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE]. 2017-08-30 23:04:08 No coin database inconsistencies in last 7 blocks (1811 transactions) 2017-08-30 23:04:08 block index 12706ms 2017-08-30 23:04:08 Reading estimates: 98 buckets counting confirms up to 25 blocks 2017-08-30 23:04:08 init message: Loading wallet... 2017-08-30 23:04:08 nFileVersion = 140200 2017-08-30 23:04:08 Keys: 102 plaintext, 0 encrypted, 102 w/ metadata, 102 total 2017-08-30 23:04:08 wallet 59ms 2017-08-30 23:04:08 setKeyPool.size() = 100 2017-08-30 23:04:08 mapWallet.size() = 0 2017-08-30 23:04:08 mapAddressBook.size() = 1 2017-08-30 23:04:08 mapBlockIndex.size() = 223522 2017-08-30 23:04:08 nBestHeight = 223521 2017-08-30 23:04:08 Imported mempool transactions from disk: 0 successes, 0 failed, 0 expired 2017-08-30 23:04:08 torcontrol thread start 2017-08-30 23:04:08 init message: Loading addresses... 2017-08-30 23:04:08 upnp thread start 2017-08-30 23:04:08 Loaded 676 addresses from peers.dat 12ms 2017-08-30 23:04:08 init message: Loading banlist... 2017-08-30 23:04:08 Loaded 0 banned node ips/subnets from banlist.dat 3ms 2017-08-30 23:04:08 init message: Starting network threads... 2017-08-30 23:04:08 dnsseed thread start 2017-08-30 23:04:08 net thread start 2017-08-30 23:04:08 addcon thread start 2017-08-30 23:04:08 opencon thread start 2017-08-30 23:04:08 init message: Done loading 2017-08-30 23:04:08 msghand thread start 2017-08-30 23:04:08 GUI: initializeResult : Initialization result: 1 2017-08-30 23:04:08 GUI: Platform customization: "windows" 2017-08-30 23:04:08 GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "01" ("Microsoft Authenticode(tm) Root Authority") () () 2017-08-30 23:04:08 GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "01" () () ("Copyright (c) 1997 Microsoft Corp.", "Microsoft Time Stamping Service Root", "Microsoft Corporation") 2017-08-30 23:04:08 GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "4a:19:d2:38:8c:82:59:1c:a5:5d:73:5f:15:5d:dc:a3" () () ("NO LIABILITY ACCEPTED, (c)97 VeriSign, Inc.", "VeriSign Time Stamping Service Root", "VeriSign, Inc.") 2017-08-30 23:04:08 GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "03:c7:8f:37:db:92:28:df:3c:bb:1a:ad:82:fa:67:10" () () ("VeriSign Commercial Software Publishers CA") 2017-08-30 23:04:08 GUI: PaymentServer::LoadRootCAs: Loaded 49 root certificates 2017-08-30 23:04:09 GUI: TransactionTablePriv::refreshWallet 2017-08-30 23:04:09 25: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-30 23:04:09 25: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-30 23:04:09 6: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-30 23:04:09 7: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-30 23:04:09 8: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-30 23:04:09 9: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-30 23:04:09 10: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-30 23:04:09 11: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-30 23:04:09 12: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-30 23:04:09 13: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-30 23:04:09 14: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-30 23:04:09 15: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-30 23:04:09 16: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-30 23:04:09 17: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-30 23:04:09 18: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-30 23:04:09 19: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-30 23:04:09 20: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-30 23:04:09 21: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-30 23:04:09 22: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-30 23:04:09 23: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-30 23:04:09 24: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-30 23:04:09 25: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-30 23:04:09 GUI: PaymentServer::initNetManager: No active proxy server found. 2017-08-30 23:04:09 trying connection 24.240.197.18:8333 lastseen=166.0hrs 2017-08-30 23:04:09 tor: Error connecting to Tor control socket 2017-08-30 23:04:09 tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect 2017-08-30 23:04:11 tor: Error connecting to Tor control socket 2017-08-30 23:04:11 tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect 2017-08-30 23:04:14 tor: Error connecting to Tor control socket 2017-08-30 23:04:14 tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect 2017-08-30 23:04:14 connection to 24.240.197.18:8333 timeout 2017-08-30 23:04:14 trying connection 197.245.238.252:8333 lastseen=95.5hrs 2017-08-30 23:04:16 No valid UPnP IGDs found 2017-08-30 23:04:16 upnp thread exit 2017-08-30 23:04:17 tor: Error connecting to Tor control socket 2017-08-30 23:04:17 tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect 2017-08-30 23:04:19 Loading addresses from DNS seeds (could take a while) 2017-08-30 23:04:19 Added 22 addresses from 45.32.130.19: 0 tried, 696 new 2017-08-30 23:04:19 connection to 197.245.238.252:8333 timeout 2017-08-30 23:04:19 Added 20 addresses from 8.8.8.8: 0 tried, 715 new 2017-08-30 23:04:20 Added 21 addresses from 104.28.18.99: 0 tried, 733 new 2017-08-30 23:04:20 Added 18 addresses from 138.201.55.219: 0 tried, 750 new 2017-08-30 23:04:20 93 addresses found from DNS seeds 2017-08-30 23:04:20 dnsseed thread exit 2017-08-30 23:04:20 trying connection 78.47.24.42:8333 lastseen=140.9hrs 2017-08-30 23:04:22 tor: Error connecting to Tor control socket 2017-08-30 23:04:22 tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect 2017-08-30 23:04:25 connection to 78.47.24.42:8333 timeout 2017-08-30 23:04:25 trying connection 87.229.26.68:8333 lastseen=170.8hrs 2017-08-30 23:04:28 tor: Error connecting to Tor control socket 2017-08-30 23:04:28 tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect 2017-08-30 23:04:30 connection to 87.229.26.68:8333 timeout 2017-08-30 23:04:31 trying connection 188.165.252.147:8333 lastseen=115.6hrs 2017-08-30 23:04:36 connection to 188.165.252.147:8333 timeout 2017-08-30 23:04:36 tor: Error connecting to Tor control socket 2017-08-30 23:04:36 tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect 2017-08-30 23:04:36 trying connection 67.205.140.197:8333 lastseen=92.7hrs 2017-08-30 23:04:41 connection to 67.205.140.197:8333 timeout 2017-08-30 23:04:42 trying connection 35.197.59.75:8333 lastseen=99.3hrs 2017-08-30 23:04:47 connection to 35.197.59.75:8333 timeout 2017-08-30 23:04:47 trying connection 73.50.113.111:8333 lastseen=349.9hrs 2017-08-30 23:04:49 tor: Error connecting to Tor control socket 2017-08-30 23:04:49 tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect 2017-08-30 23:04:49 GUI: requestShutdown : Requesting shutdown 2017-08-30 23:04:49 GUI: shutdown : Running Shutdown in thread 2017-08-30 23:04:49 Interrupting HTTP server 2017-08-30 23:04:49 Interrupting HTTP RPC server 2017-08-30 23:04:49 Interrupting RPC 2017-08-30 23:04:49 tor: Thread interrupt 2017-08-30 23:04:49 net thread exit 2017-08-30 23:04:49 addcon thread exit 2017-08-30 23:04:49 torcontrol thread exit 2017-08-30 23:04:49 scheduler thread interrupt 2017-08-30 23:04:49 Shutdown: In progress... 2017-08-30 23:04:49 Stopping HTTP RPC server 2017-08-30 23:04:49 Stopping RPC 2017-08-30 23:04:49 Stopping HTTP server 2017-08-30 23:04:49 Stopped HTTP server 2017-08-30 23:04:49 CDBEnv::Flush: Flush(false) 2017-08-30 23:04:49 CDBEnv::Flush: Flushing wallet.dat (refcount = 0)... 2017-08-30 23:04:49 msghand thread exit 2017-08-30 23:04:50 CDBEnv::Flush: wallet.dat checkpoint 2017-08-30 23:04:50 CDBEnv::Flush: wallet.dat detach 2017-08-30 23:04:50 CDBEnv::Flush: wallet.dat closed 2017-08-30 23:04:50 CDBEnv::Flush: Flush(false) took 153ms 2017-08-30 23:04:52 connection to 73.50.113.111:8333 timeout 2017-08-30 23:04:52 opencon thread exit 2017-08-30 23:04:52 Flushed 750 addresses to peers.dat 11ms 2017-08-30 23:04:52 Dumped mempool: 0s to copy, 0.008s to dump 2017-08-30 23:04:52 Committing 0 changed transactions (out of 0) to coin database... 2017-08-30 23:04:53 CDBEnv::Flush: Flush(true) 2017-08-30 23:04:53 CDBEnv::Flush: Flushing wallet.dat (refcount = 0)... 2017-08-30 23:04:53 CDBEnv::Flush: wallet.dat checkpoint 2017-08-30 23:04:53 CDBEnv::Flush: wallet.dat detach 2017-08-30 23:04:53 CDBEnv::Flush: wallet.dat closed 2017-08-30 23:04:53 CDBEnv::Flush: Flush(true) took 28ms 2017-08-30 23:04:53 Shutdown: done 2017-08-30 23:04:53 GUI: shutdown : Shutdown finished 2017-08-30 23:04:53 GUI: shutdownResult : Shutdown result: 1 2017-08-30 23:04:53 GUI: ~BitcoinApplication : Stopping thread 2017-08-30 23:04:53 GUI: ~BitcoinApplication : Stopped thread
Here is the log. The TOR browser I have installed has a problem connecting to its own control port if that's useful information. I made a new tor browser that functions perfectly if there's a way to get that to override connections sent to the other tor browser? Or a way for it to not need the tor control port as I don't think it's used anyway.
|
|
|
|
achow101
Moderator
Legendary
Offline
Activity: 3444
Merit: 6748
Just writing some code
|
|
August 30, 2017, 11:25:12 PM |
|
The TOR browser I have installed has a problem connecting to its own control port if that's useful information. I made a new tor browser that functions perfectly if there's a way to get that to override connections sent to the other tor browser? Or a way for it to not need the tor control port as I don't think it's used anyway.
I don't think that matters. Is TOR running? If so, what happens if you stop it and then run Core?
|
|
|
|
jackg (OP)
Copper Member
Legendary
Offline
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
|
|
August 30, 2017, 11:28:04 PM Last edit: August 30, 2017, 11:40:15 PM by jackg |
|
The TOR browser I have installed has a problem connecting to its own control port if that's useful information. I made a new tor browser that functions perfectly if there's a way to get that to override connections sent to the other tor browser? Or a way for it to not need the tor control port as I don't think it's used anyway.
I don't think that matters. Is TOR running? If so, what happens if you stop it and then run Core? No. Tor isn't running. There are only 6 connections currently on my computer (without bitcoin core or tor running) - from the netstat command in cmd. EDIT: after loading up bitcoin core and doing a couple of google searches on some unfamiliar IPs I was previously connected to, I found that the number of connections have increased by a very large amount. It went from 6 to 4 to 56 connections.
|
|
|
|
achow101
Moderator
Legendary
Offline
Activity: 3444
Merit: 6748
Just writing some code
|
|
August 31, 2017, 12:02:14 AM |
|
EDIT: after loading up bitcoin core and doing a couple of google searches on some unfamiliar IPs I was previously connected to, I found that the number of connections have increased by a very large amount. It went from 6 to 4 to 56 connections.
That normally happens when you start a browser. It tends to connect to many things on the internet. Have you tried doing a full resync? You can see if that will do anything before actually resyncing by renaming the datadir to something else and letting it make a new one. If it is able to establish connections, this means that something is corrupted in your block files, the block index, or the chainstate that is making it unable to connect, although I don't see anything in the log that indicates that that is happening.
|
|
|
|
jackg (OP)
Copper Member
Legendary
Offline
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
|
|
August 31, 2017, 12:41:05 AM Last edit: August 31, 2017, 01:00:28 AM by jackg |
|
EDIT: after loading up bitcoin core and doing a couple of google searches on some unfamiliar IPs I was previously connected to, I found that the number of connections have increased by a very large amount. It went from 6 to 4 to 56 connections.
That normally happens when you start a browser. It tends to connect to many things on the internet. Have you tried doing a full resync? You can see if that will do anything before actually resyncing by renaming the datadir to something else and letting it make a new one. If it is able to establish connections, this means that something is corrupted in your block files, the block index, or the chainstate that is making it unable to connect, although I don't see anything in the log that indicates that that is happening. Just tried that and still get the same error. 2017-08-31 00:36:05 Bitcoin version v0.14.2 2017-08-31 00:36:05 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2017-08-31 00:36:06 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..." 2017-08-31 00:36:06 Assuming ancestors of block 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90 have valid signatures. 2017-08-31 00:36:08 RandAddSeedPerfmon: 230568 bytes 2017-08-31 00:36:08 Default data directory C:\Users\Laptop\AppData\Roaming\Bitcoin 2017-08-31 00:36:08 Using data directory F:\Bitcoin\Bitcoin\Data 2017-08-31 00:36:08 Using config file F:\Bitcoin\Bitcoin\Data\bitcoin.conf 2017-08-31 00:36:08 Using at most 125 automatic connections (2048 file descriptors available) 2017-08-31 00:36:08 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements 2017-08-31 00:36:08 Using 2 threads for script verification 2017-08-31 00:36:08 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2017-08-31 00:36:08 scheduler thread start 2017-08-31 00:36:08 Using wallet wallet.dat 2017-08-31 00:36:08 init message: Verifying wallet... 2017-08-31 00:36:08 CDBEnv::Open: LogDir=F:\Bitcoin\Bitcoin\Data\database ErrorFile=F:\Bitcoin\Bitcoin\Data\db.log 2017-08-31 00:36:08 Bound to [::]:8333 2017-08-31 00:36:08 Bound to 0.0.0.0:8333 2017-08-31 00:36:08 Cache configuration: 2017-08-31 00:36:08 * Using 2.0MiB for block index database 2017-08-31 00:36:08 * Using 8.0MiB for chain state database 2017-08-31 00:36:08 * Using 1014.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space) 2017-08-31 00:36:08 init message: Loading block index... 2017-08-31 00:36:08 Wiping LevelDB in F:\Bitcoin\Bitcoin\Data\blocks\index 2017-08-31 00:36:08 Opening LevelDB in F:\Bitcoin\Bitcoin\Data\blocks\index 2017-08-31 00:36:08 Opened LevelDB successfully 2017-08-31 00:36:08 Using obfuscation key for F:\Bitcoin\Bitcoin\Data\blocks\index: 0000000000000000 2017-08-31 00:36:08 Wiping LevelDB in F:\Bitcoin\Bitcoin\Data\chainstate 2017-08-31 00:36:08 Opening LevelDB in F:\Bitcoin\Bitcoin\Data\chainstate 2017-08-31 00:36:08 Opened LevelDB successfully 2017-08-31 00:36:08 Wrote new obfuscate key for F:\Bitcoin\Bitcoin\Data\chainstate: 11beca5e4f40da67 2017-08-31 00:36:08 Using obfuscation key for F:\Bitcoin\Bitcoin\Data\chainstate: 11beca5e4f40da67 2017-08-31 00:36:08 Initializing databases... 2017-08-31 00:36:08 init message: Verifying blocks... 2017-08-31 00:36:08 block index 67ms 2017-08-31 00:36:08 Reading estimates: 98 buckets counting confirms up to 25 blocks 2017-08-31 00:36:08 init message: Loading wallet... 2017-08-31 00:36:08 nFileVersion = 140200 2017-08-31 00:36:08 Keys: 102 plaintext, 0 encrypted, 102 w/ metadata, 102 total 2017-08-31 00:36:08 wallet 67ms 2017-08-31 00:36:08 setKeyPool.size() = 100 2017-08-31 00:36:08 mapWallet.size() = 0 2017-08-31 00:36:08 mapAddressBook.size() = 1 2017-08-31 00:36:08 Reindexing finished 2017-08-31 00:36:08 Initializing databases... 2017-08-31 00:36:08 Pre-allocating up to position 0x1000000 in blk00000.dat 2017-08-31 00:36:08 Committing 0 changed transactions (out of 0) to coin database... 2017-08-31 00:36:08 - Load block from disk: 1.00ms [0.00s] 2017-08-31 00:36:08 - Connect total: 1.00ms [0.00s] 2017-08-31 00:36:08 - Flush: 0.00ms [0.00s] 2017-08-31 00:36:08 - Writing chainstate: 0.00ms [0.00s] 2017-08-31 00:36:08 UpdateTip: new best=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 version=0x00000001 log2_work=32.000022 tx=1 date='2009-01-03 18:15:05' progress=0.000000 cache=0.0MiB(0tx) 2017-08-31 00:36:08 - Connect postprocess: 2.00ms [0.00s] 2017-08-31 00:36:08 - Connect block: 4.00ms [0.00s] 2017-08-31 00:36:08 mapBlockIndex.size() = 1 2017-08-31 00:36:08 nBestHeight = 0 2017-08-31 00:36:08 Imported mempool transactions from disk: 0 successes, 0 failed, 0 expired 2017-08-31 00:36:08 torcontrol thread start 2017-08-31 00:36:08 upnp thread start 2017-08-31 00:36:08 init message: Loading addresses... 2017-08-31 00:36:08 Loaded 828 addresses from peers.dat 15ms 2017-08-31 00:36:08 init message: Loading banlist... 2017-08-31 00:36:08 Loaded 0 banned node ips/subnets from banlist.dat 2ms 2017-08-31 00:36:08 init message: Starting network threads... 2017-08-31 00:36:08 dnsseed thread start 2017-08-31 00:36:08 net thread start 2017-08-31 00:36:08 addcon thread start 2017-08-31 00:36:08 opencon thread start 2017-08-31 00:36:08 msghand thread start 2017-08-31 00:36:08 init message: Done loading 2017-08-31 00:36:08 GUI: initializeResult : Initialization result: 1 2017-08-31 00:36:08 GUI: Platform customization: "windows" 2017-08-31 00:36:08 GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "01" ("Microsoft Authenticode(tm) Root Authority") () () 2017-08-31 00:36:08 GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "01" () () ("Copyright (c) 1997 Microsoft Corp.", "Microsoft Time Stamping Service Root", "Microsoft Corporation") 2017-08-31 00:36:08 GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "4a:19:d2:38:8c:82:59:1c:a5:5d:73:5f:15:5d:dc:a3" () () ("NO LIABILITY ACCEPTED, (c)97 VeriSign, Inc.", "VeriSign Time Stamping Service Root", "VeriSign, Inc.") 2017-08-31 00:36:08 GUI: "ReportInvalidCertificate: Payment server found an invalid certificate: " "03:c7:8f:37:db:92:28:df:3c:bb:1a:ad:82:fa:67:10" () () ("VeriSign Commercial Software Publishers CA") 2017-08-31 00:36:08 GUI: PaymentServer::LoadRootCAs: Loaded 49 root certificates 2017-08-31 00:36:08 GUI: TransactionTablePriv::refreshWallet 2017-08-31 00:36:08 25: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-31 00:36:08 25: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-31 00:36:08 6: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-31 00:36:08 7: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-31 00:36:08 8: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-31 00:36:08 9: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-31 00:36:08 10: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-31 00:36:08 11: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-31 00:36:08 12: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-31 00:36:08 13: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-31 00:36:08 14: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-31 00:36:08 15: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-31 00:36:08 16: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-31 00:36:08 17: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-31 00:36:08 18: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-31 00:36:08 19: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-31 00:36:08 20: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-31 00:36:08 21: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-31 00:36:08 22: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-31 00:36:08 23: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-31 00:36:08 24: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-31 00:36:08 25: For conf success > 0.95 need feerate >: -1 from buckets 2.1e+015 - 2.1e+015 Cur Bucket stats nan% 0.0/(0.0+0 mempool) 2017-08-31 00:36:08 GUI: PaymentServer::initNetManager: No active proxy server found. 2017-08-31 00:36:08 trying connection 2.235.201.237:8333 lastseen=132.3hrs 2017-08-31 00:36:09 tor: Error connecting to Tor control socket 2017-08-31 00:36:09 tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect 2017-08-31 00:36:11 tor: Error connecting to Tor control socket 2017-08-31 00:36:11 tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect 2017-08-31 00:36:13 tor: Error connecting to Tor control socket 2017-08-31 00:36:13 tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect 2017-08-31 00:36:13 connection to 2.235.201.237:8333 timeout 2017-08-31 00:36:14 trying connection 177.18.6.112:8333 lastseen=151.5hrs 2017-08-31 00:36:16 No valid UPnP IGDs found 2017-08-31 00:36:16 upnp thread exit 2017-08-31 00:36:17 tor: Error connecting to Tor control socket 2017-08-31 00:36:17 tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect 2017-08-31 00:36:19 Loading addresses from DNS seeds (could take a while) 2017-08-31 00:36:19 connection to 177.18.6.112:8333 timeout 2017-08-31 00:36:19 Added 20 addresses from 8.8.8.8: 0 tried, 848 new 2017-08-31 00:36:19 Added 19 addresses from 104.28.18.99: 0 tried, 865 new 2017-08-31 00:36:19 Added 1 addresses from 138.201.55.219: 0 tried, 865 new 2017-08-31 00:36:19 93 addresses found from DNS seeds 2017-08-31 00:36:19 dnsseed thread exit 2017-08-31 00:36:19 trying connection 88.99.185.121:8333 lastseen=87.5hrs 2017-08-31 00:36:21 tor: Error connecting to Tor control socket 2017-08-31 00:36:21 tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect 2017-08-31 00:36:24 connection to 88.99.185.121:8333 timeout 2017-08-31 00:36:25 trying connection 66.41.198.203:8333 lastseen=162.7hrs 2017-08-31 00:36:27 tor: Error connecting to Tor control socket 2017-08-31 00:36:27 tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect 2017-08-31 00:36:30 connection to 66.41.198.203:8333 timeout 2017-08-31 00:36:30 trying connection 46.163.74.184:8333 lastseen=167.7hrs 2017-08-31 00:36:35 connection to 46.163.74.184:8333 timeout 2017-08-31 00:36:36 tor: Error connecting to Tor control socket 2017-08-31 00:36:36 tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect 2017-08-31 00:36:36 trying connection 75.40.139.203:8333 lastseen=190.6hrs 2017-08-31 00:36:41 connection to 75.40.139.203:8333 timeout 2017-08-31 00:36:41 trying connection 88.99.36.224:8333 lastseen=168.4hrs 2017-08-31 00:36:46 connection to 88.99.36.224:8333 timeout 2017-08-31 00:36:47 trying connection 78.46.253.41:8333 lastseen=108.8hrs 2017-08-31 00:36:48 tor: Error connecting to Tor control socket 2017-08-31 00:36:48 tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect 2017-08-31 00:36:52 connection to 78.46.253.41:8333 timeout 2017-08-31 00:36:52 trying connection 2.225.185.129:8333 lastseen=151.3hrs 2017-08-31 00:36:57 connection to 2.225.185.129:8333 timeout 2017-08-31 00:36:58 trying connection 82.72.88.33:8333 lastseen=168.1hrs 2017-08-31 00:37:03 connection to 82.72.88.33:8333 timeout 2017-08-31 00:37:03 trying connection 52.26.77.177:8333 lastseen=154.6hrs 2017-08-31 00:37:06 tor: Error connecting to Tor control socket 2017-08-31 00:37:06 tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect 2017-08-31 00:37:08 connection to 52.26.77.177:8333 timeout 2017-08-31 00:37:09 trying connection 103.11.64.46:8333 lastseen=308.9hrs 2017-08-31 00:37:14 connection to 103.11.64.46:8333 timeout 2017-08-31 00:37:14 trying connection 45.56.99.96:8333 lastseen=318.1hrs 2017-08-31 00:37:19 connection to 45.56.99.96:8333 timeout 2017-08-31 00:37:20 trying connection 47.94.152.157:8333 lastseen=162.5hrs 2017-08-31 00:37:25 connection to 47.94.152.157:8333 timeout 2017-08-31 00:37:25 trying connection 199.34.127.173:8333 lastseen=151.9hrs 2017-08-31 00:37:30 connection to 199.34.127.173:8333 timeout 2017-08-31 00:37:31 trying connection 89.163.224.195:8333 lastseen=101.0hrs 2017-08-31 00:37:33 tor: Error connecting to Tor control socket 2017-08-31 00:37:33 tor: Not connected to Tor control port 127.0.0.1:9051, trying to reconnect 2017-08-31 00:37:36 connection to 89.163.224.195:8333 timeout 2017-08-31 00:37:36 trying connection 104.222.99.56:8333 lastseen=140.0hrs 2017-08-31 00:37:41 connection to 104.222.99.56:8333 timeout 2017-08-31 00:37:42 trying connection 35.195.79.250:8333 lastseen=91.2hrs 2017-08-31 00:37:47 connection to 35.195.79.250:8333 timeout 2017-08-31 00:37:47 trying connection 46.246.49.100:8333 lastseen=270.0hrs 2017-08-31 00:37:52 connection to 46.246.49.100:8333 timeout 2017-08-31 00:37:53 trying connection 188.234.245.16:8333 lastseen=291.3hrs 2017-08-31 00:37:58 connection to 188.234.245.16:8333 timeout 2017-08-31 00:37:58 trying connection 176.36.229.196:8333 lastseen=118.4hrs
This is another debug.log. The client just keeps trying to find a peer indefinitely and I'm not sure this is supposed to happen. It did produce a blk00000.dat file that is 16777216 bytes which is quite strange if there are no connections over the network? I might try tommorrow to take my own piece of advice and see if booting it in safe mode does anything to fix the problem (if it does, then it's just my user account that's faulty).
|
|
|
|
achow101
Moderator
Legendary
Offline
Activity: 3444
Merit: 6748
Just writing some code
|
|
August 31, 2017, 12:54:20 AM Merited by ABCbits (1), jackg (1) |
|
The client just keeps trying to find a peer indefinitely and I'm not sure this is supposed to happen.
That is quite strange since I am able to connect to one of the IPs in your log that had a connection timeout. Are you sure that you don't have a firewall that is blocking connections to and from Bitcoin Core? You can try disabling UPnP, but I don't think that is a problem here. It did produce a blk00000.dat file that is 16777216 bytes whihc is quite strage if there are no connections over the network?
That's from Bitcoin Core allocating space for blk00000.dat and inserting the genesis block into it.
|
|
|
|
jackg (OP)
Copper Member
Legendary
Offline
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
|
|
August 31, 2017, 03:50:10 PM |
|
UPDATE: I started running it in safe mode with networking and the core appears to establish connections fine. Yesterday I tried to load up the TOR that was previously working and it seems to not be working itself (no control port connection).
|
|
|
|
jackg (OP)
Copper Member
Legendary
Offline
Activity: 2856
Merit: 3071
https://bit.ly/387FXHi lightning theory
|
|
August 31, 2017, 03:53:26 PM Last edit: August 31, 2017, 04:18:38 PM by jackg |
|
The client just keeps trying to find a peer indefinitely and I'm not sure this is supposed to happen.
That is quite strange since I am able to connect to one of the IPs in your log that had a connection timeout. Are you sure that you don't have a firewall that is blocking connections to and from Bitcoin Core? You can try disabling UPnP, but I don't think that is a problem here. It did produce a blk00000.dat file that is 16777216 bytes whihc is quite strage if there are no connections over the network?
That's from Bitcoin Core allocating space for blk00000.dat and inserting the genesis block into it. Sorry, didn't spot this before. My firewall is fairly easy to disable and based on the post I just made, disabling it might be what I need to do (as it gets killed when booting in safe mode as well). Edit: thanks achow that worked! It seems running a program from a hard drive is automatically blacklisted by my firewall so I just had to change that.
|
|
|
|
pbies
|
|
July 04, 2022, 05:26:40 PM |
|
I have this "No valid UPnP IGDs found" problem with Bitcoin Core 23.0 and TP-Link router AX55. TP-Link support is not responding in this case, I've asked them about checking if this AX55 router is working ok about UPnP.
I had some other routers before, also TP-Link, and didn't had this problem exist with any of them.
This message can be seen in Bitcoin Core debug.log file when upnp=1 is given in configuration file. The same problem is in Litecoin Core and Raven Core.
Still I didn't resolved that.
DMZ for computer didn't helped in that case.
|
BTC: bc1qmrexlspd24kevspp42uvjg7sjwm8xcf9w86h5k
|
|
|
|