Bitcoin Core Can't Get Information from Nodes

9 days ago, I launched Bitcoin core version 27.1. The blockchain has been upgraded until December 10, 2024. The wallet is active but there is no incoming traffic. I closed the wallet normally and restarted it. Here's what I have:

The wallet was opened on the same date, and header synchronization began. And no progress. Nodes appear, there is no loading, they disappear, new ones appear, and so on without end. Incoming traffic is zero. There are periodic spikes in outbound traffic. I'm attaching the log:

2025-02-23T13:33:22Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884981, peer=1162

2025-02-23T13:33:33Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884981, peer=1164 2025-02-23T13:33:44Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884981, peer=1165 2025-02-23T13:33:48Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884981, peer=1166 2025-02-23T13:34:19Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884981, peer=1167 2025-02-23T13:34:20Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884981, peer=1169 2025-02-23T13:34:25Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884981, peer=1170 2025-02-23T13:35:02Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884982, peer=1173 2025-02-23T13:35:20Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884982, peer=1174 2025-02-23T13:35:21Z New outbound-full-relay v2 peer connected: version: 70016, blocks=26136, peer=1175 2025-02-23T13:35:21Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884982, peer=1176 2025-02-23T13:35:35Z New outbound-full-relay v1 peer connected: version: 70015, blocks=884982, peer=1178 2025-02-23T13:35:35Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884982, peer=1179 2025-02-23T13:35:37Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884982, peer=1180 2025-02-23T13:35:55Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884982, peer=1181 2025-02-23T13:35:58Z New manual v1 peer connected: version: 70016, blocks=884982, peer=1183 2025-02-23T13:36:17Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884982, peer=1184 2025-02-23T13:36:18Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884982, peer=1185 2025-02-23T13:36:19Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884982, peer=1186 2025-02-23T13:36:55Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884982, peer=1187 2025-02-23T13:36:57Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884982, peer=1188 2025-02-23T13:38:39Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884984, peer=1189 2025-02-23T13:38:47Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884984, peer=1190 2025-02-23T13:38:51Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1191 2025-02-23T13:38:58Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884984, peer=1192 2025-02-23T13:38:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 13237 seconds ago) 2025-02-23T13:39:16Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1194 2025-02-23T13:39:47Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1196 2025-02-23T13:39:48Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884981, peer=1197 2025-02-23T13:39:53Z New outbound-full-relay v1 peer connected: version: 70015, blocks=884984, peer=1198 2025-02-23T13:39:53Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1199 2025-02-23T13:40:12Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1200 2025-02-23T13:40:48Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884984, peer=1202 2025-02-23T13:41:01Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884984, peer=1203 2025-02-23T13:41:02Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1204 2025-02-23T13:41:26Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1205 2025-02-23T13:41:35Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1206 2025-02-23T13:41:55Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884984, peer=1207 2025-02-23T13:42:19Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1209 2025-02-23T13:42:26Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884984, peer=1210 2025-02-23T13:42:35Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884984, peer=1211 2025-02-23T13:42:37Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1212 2025-02-23T13:42:39Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1213 2025-02-23T13:42:56Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1214 2025-02-23T13:42:58Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884984, peer=1215 2025-02-23T13:43:23Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884984, peer=1216 2025-02-23T13:43:31Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884984, peer=1217 2025-02-23T13:44:01Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1218 2025-02-23T13:44:26Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1220 2025-02-23T13:44:44Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884984, peer=1221 2025-02-23T13:44:44Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1222 2025-02-23T13:45:11Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1223 2025-02-23T13:45:18Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1224 2025-02-23T13:45:19Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884984, peer=1225 2025-02-23T13:45:19Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1226 2025-02-23T13:45:39Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884984, peer=1227 2025-02-23T13:45:44Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1228 2025-02-23T13:45:56Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884984, peer=1229 2025-02-23T13:46:33Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1230 2025-02-23T13:46:44Z New manual v2 peer connected: version: 70016, blocks=884984, peer=1231 2025-02-23T13:46:47Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1232 2025-02-23T13:46:49Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1233 2025-02-23T13:47:21Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884984, peer=1234 2025-02-23T13:47:34Z Warning: not punishing manually connected peer 1231! 2025-02-23T13:47:37Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1236 2025-02-23T13:47:37Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884984, peer=1237

2025-02-23T13:51:24Z New manual v2 peer connected: version: 70016, blocks=884984, peer=1261 2025-02-23T13:51:29Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884984, peer=1262 2025-02-23T13:51:47Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1264 2025-02-23T13:52:01Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884984, peer=1266 2025-02-23T13:52:02Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1267 2025-02-23T13:52:15Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1269 2025-02-23T13:52:21Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1270 2025-02-23T13:52:27Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1271 2025-02-23T13:52:36Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884984, peer=1273 2025-02-23T13:53:01Z Flushed fee estimates to fee_estimates.dat. 2025-02-23T13:53:03Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1277 2025-02-23T13:53:18Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1278 2025-02-23T13:53:25Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1279 2025-02-23T13:53:50Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1280 2025-02-23T13:53:50Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884984, peer=1281 2025-02-23T13:54:30Z New outbound-full-relay v2 peer connected: version: 70016, blocks=26141, peer=1282 2025-02-23T13:54:30Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1283 2025-02-23T13:54:44Z New manual v2 peer connected: version: 70016, blocks=884984, peer=1284 2025-02-23T13:54:44Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1285 2025-02-23T13:54:50Z New outbound-full-relay v2 peer connected: version: 70016, blocks=884984, peer=1286 2025-02-23T13:54:50Z Warning: not punishing manually connected peer 1284! 2025-02-23T13:55:08Z New outbound-full-relay v1 peer connected: version: 70016, blocks=884984, peer=1287

I tried to add nodes manually. Nothing changes.

I have launched a bitcoin core, but the wallet.dat itself, on which my assets are located, has not yet been uploaded.

I have launched a bitcoin core, but the wallet.dat itself, on which my assets are located, has not yet been uploaded.

I was just trying to paste screenshots here. But I still haven't figured out how to do it. I just wanted to paste from the buffer. BUT it doesn't work.



from Recent Questions - Bitcoin Stack Exchange https://ift.tt/D0X4LmT
via IFTTT

Popular posts from this blog

Do Kwon’s Detention Prolonged Until 2024 As Montenegro Responds To Extradition Requests

Image
According to an International Business Times report , Montenegro’s Supreme Court decided to extend the detention of TerraForm Labs founder and CEO Do Kwon until February 2024, following extradition requests from the United States and South Korea. Closed-Door Discussions Reveal Montenegro’s Plan For Do Kwon Initially set to be extradited to the US on December 15, Do Kwon’s fate turned when the Montenegrin High Court ruled to prolong his stay until February 15, 2024. The decision stems from charges related to the collapse of the TerraUSD stablecoin, which led to significant financial losses. The High Court had previously ordered Kwon’s extradition by Friday, but his defense team appealed the decision in the appellate court in Podgorica, the capital of Montenegro. The Montenegrin Court of Appeal confirmed that Kwon contested the High Court’s ruling, vehemently stating, “I do not submit to the court’s decision.” Recent reports indicate that Montenegro’s Justice Minister, Andrej Mil...
Read more

Sam Bankman-Fried Trial Begins Tomorrow: 3 Reasons Ex-SEC Official Foresees Conviction

Image
The trial of Sam Bankman-Fried, the founder of cryptocurrency exchange FTX and hedge fund Alameda Research, is set to commence in New York on Tuesday, October 3.  This comes almost a year after the collapse of both FTX and Alameda Research. The events leading up to the trial paint a picture of alleged fraudulent activities and money laundering that caused significant damage to the businesses involved. Ex-SEC Official’s Bleak Prediction As Sam Bankman-Fried Trial Commences In a nutshell, Alameda Research purportedly took customer deposits from FTX and invested them in fictitious crypto tokens, which derived their value from the confidence in FTX’s operations.  When this confidence waned, FTX and Alameda Research suffered substantial losses, which many argue contributed to a broader disillusionment in the cryptocurrency industry.  Following an investigation, federal authorities uncovered numerous alleged crimes, leading to seven federal fraud and money-laundering cha...
Read more

Future of Bitcoin encryption and security in a QC era

How will the advancement of quantum computing impact the security of Bitcoin, and what steps are necessary to protect the network from this emerging threat? What role could lattice-based encryption play in safeguarding Bitcoin, and which of the current algorithms are best suited for this purpose? How would the implementation of such encryption technology be integrated into the existing Bitcoin infrastructure, and what challenges might arise during this process? What happens to existing addresses that rely on elliptic curve cryptography? Is there a way to seamlessly transition old addresses to the new system, or would users need to actively transfer their funds to new, more secure addresses? How could such a transition be designed to ensure user security while maintaining trust in the network? from Recent Questions - Bitcoin Stack Exchange https://ift.tt/aZeY2fo via IFTTT
Read more