We understand that there have been a few reports of synchronization and fork issues on some pools. The team is aware of how to fix the problem and are working diligently to resolve the issue.
At this time we recommend everyone use the original daemon for now.
PLEASE NOTE There is a new Windows and Linux daemon. We STRONGLY recommend everyone updates their daemon as soon as possible.
Please delete your p2pstate.bin file and your imbd folder in your programdata folder followed by a restart of your computer. From there, please choose the appropriate download, extract the files, and add admin permissions if applicable. From there please start derod and wait for the daemon to fully synchronize.
Regarding any missing transactions prior to March.5, there have been some fork issues that may have resulted in some blocks being orphaned or transactions disappearing for various technical reasons. We sincerely regret as a team that this happened and are applying all of our available time to rectify this without delay.
As always, Iâm usually available on Slack and check forums regularly.
INFO[0000] Mempool started com=POOL
INFO[0000] Chain Top Block 4733e6c193921074d5d6e83ca5f7a51a4297fcf099e53a910b34646e411c1258 Height 39304 com=BLKCHAIN
INFO[0000] P2P started com=P2P
INFO[0000] RPC server started com=RPC
WARN[0002] We are still NOT using Peer information com=P2P
WARN[0044] We are still NOT using Peer information com=P2P
WARN[0063] We are still NOT using Peer information com=P2P
WARN[0093] We are still NOT using Peer information com=P2P
WARN[0130] We are still NOT using Peer information com=P2P
WARN[0159] We are still NOT using Peer information com=P2P
WARN[0189] We are still NOT using Peer information com=P2P
WARN[0214] We are still NOT using Peer information com=P2P
WARN[0244] We are still NOT using Peer information com=P2P
WARN[0462] Prev_Hash no where in the chain, skipping it till we get a parent blid=8e26944887b20a067ab9648bc5417b3a68ab1d2e4c8d10c8ca54b058443433df com=BLKCHAIN
WARN[0462] err while unmarshallin output index data index = 336872 data_len 0 err EOF com=BLKCHAIN
WARN[0462] err while unmarshallin output index data index = 337830 data_len 0 err EOF com=BLKCHAIN
WARN[0462] err while unmarshallin output index data index = 340271 data_len 0 err EOF com=BLKCHAIN
WARN[0462] err while unmarshallin output index data index = 335209 data_len 0 err EOF com=BLKCHAIN
WARN[0462] err while unmarshallin output index data index = 336147 data_len 0 err EOF com=BLKCHAIN
WARN[0462] err while unmarshallin output index data index = 338416 data_len 0 err EOF com=BLKCHAIN
WARN[0462] TX RCT Signature failed com=BLKCHAIN txid=8f4fa5692b11e69bcbeace460bd90ac9420400947d22753d79f0a22f443350bb
WARN[0462] Incoming TX could not be verified com=BLKCHAIN
WARN[0473] Prev_Hash no where in the chain, skipping it till we get a parent blid=ec120950b1581063edbd5e213c7b466481a03499d8e34b39d8377b2f85553eed com=BLKCHAIN
Not able to sync the blockchain Was good two days back and now tried to sync but not working.
Getting these errors and my wallet hasnât got any DERO that were mined in last two days!
|2018-03-02 07:17:18.483|[RPC0]|ERROR|blockchain|src/cryptonote_core/blockchain.cpp:2098|internal error, transaction from block not found|
|â|---|â|---|â|---|
|2018-03-02 07:17:18.483|[RPC0]|ERROR|net.http|src/rpc/core_rpc_server.h:76|Failed to on_get_blocks()|
|2018-03-02 07:17:18.763|[RPC1]|ERROR|blockchain|src/cryptonote_core/blockchain.cpp:2098|internal error, transaction from block not found|
|2018-03-02 07:17:18.763|[RPC1]|ERROR|net.http|src/rpc/core_rpc_server.h:76|Failed to on_get_blocks()|
Although the derod says [P2P1] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:1521 SYNCHRONIZED OK
when I open the wallet, it says - Error: refresh failed: no connection to daemon. Please make sure daemon is running.. Blocks received: 0 Background refresh thread started [wallet dERom6 (out of sync)]:
There are major problems with network+wallet and somebody needs to address them.
Thank you for the response! Iâm on GNU/Linux, wonât use windows. Daemon is running in different terminal session and I can open my wallet but get following errors when I run daemon-
|2018-03-02 14:19:25.595|[RPC0]|ERROR|blockchain|src/cryptonote_core/blockchain.cpp:2098|internal error, transaction from block not found| |---|---|---|---|---|---| |2018-03-02 14:19:25.595|[RPC0]|ERROR|net.http|src/rpc/core_rpc_server.h:76|Failed to on_get_blocks()| |2018-03-02 14:20:55.675|[RPC0]|ERROR|blockchain|src/cryptonote_core/blockchain.cpp:2098|internal error, transaction from block not found| |2018-03-02 14:20:55.675|[RPC0]|ERROR|net.http|src/rpc/core_rpc_server.h:76|Failed to on_get_blocks()|
And get following errors when I run refresh on dero-wallet-cli prompt - refresh Starting refresh... Error: refresh failed: no connection to daemon. Please make sure daemon is running.. Blocks received: 0
Also status gives me this message - status Refreshed 40283/41063, syncing, daemon RPC v1.13
WARN[0368] transaction using immature inputs from block 39317 chain height 39325 com=BLKCHAIN
WARN[0368] TX inputs could not be expanded or inputs are NOT mature com=BLKCHAIN txid=db7bca2396548c1422db3b6f1608e392f7528e97e6ddd935e0bfef8f14602f16
WARN[0369] Block verification failed rejecting blid=58ddf2c1938aa88f0f38e834c3c829375e9201aa8204a0fd1ac293f5ba51d0f8 com=BLKCHAIN
WARN[0380] We are still NOT using Peer information com=P2P
WARN[0405] We are still NOT using Peer information com=P2P
WARN[0417] err while unmarshallin output index data index = 339940 data_len 0 err EOF com=BLKCHAIN
WARN[0417] err while unmarshallin output index data index = 347329 data_len 0 err EOF com=BLKCHAIN
WARN[0417] TX RCT Signature failed com=BLKCHAIN txid=2ddc15cb9bf6ce12358f2e72ef443ae40499d46e71f5ad24d563fec78d6236d2
WARN[0417] Incoming TX could not be verified com=BLKCHAIN
I delete all, reboot the pc, they stuck again on 40286, save blockchain and try again, same thingâŚ
derod.exe --add-priority-node 89.38.97.110:18090 --add-priority-node 212.8.242.60:18090 --add-priority-node 85.217.170.245:18090 --add-priority-node 89.38.96.169:18090 --add-priority-node 45.63.6.91:18090 --add-priority-node 108.61.220.229:18090 --add-priority-node 207.148.5.250:18090 --add-priority-node 45.77.89.64:18090 --add-priority-node 45.76.42.165:18090 --add-priority-node 45.77.242.137:18090
2018-03-03 06:54:00.727 7076 INFO global src/daemon/main.cpp:279 Dero âHelium Hydraâ (v0.11.1.0-release)
2018-03-03 06:54:00.728 7076 INFO global src/daemon/protocol.h:55 Initializing cryptonote protocolâŚ
2018-03-03 06:54:00.729 7076 INFO global src/daemon/protocol.h:60 Cryptonote protocol initialized OK
2018-03-03 06:54:00.730 7076 INFO global src/daemon/p2p.h:63 Initializing p2p serverâŚ
2018-03-03 06:54:02.331 7076 INFO global src/daemon/p2p.h:68 P2p server initialized OK
2018-03-03 06:54:02.331 7076 INFO global src/daemon/rpc.h:58 Initializing core rpc serverâŚ
2018-03-03 06:54:02.332 7076 INFO global contrib/epee/include/net/http_server_impl_base.h:70 Binding on 127.0.0.1:18091
2018-03-03 06:54:02.332 7076 INFO global src/daemon/rpc.h:63 Core rpc server initialized OK on port: 18091
2018-03-03 06:54:02.332 7076 INFO global src/daemon/core.h:73 Initializing coreâŚ
2018-03-03 06:54:02.333 7076 INFO global src/cryptonote_core/cryptonote_core.cpp:323 Loading blockchain from folder C:\ProgramData\dero\lmdb âŚ
2018-03-03 06:54:02.451 7076 INFO global src/cryptonote_core/cryptonote_core.cpp:421 Loading checkpoints
2018-03-03 06:54:02.452 7076 INFO global src/daemon/core.h:78 Core initialized OK
2018-03-03 06:54:02.453 7076 INFO global src/daemon/rpc.h:68 Starting core rpc serverâŚ
2018-03-03 06:54:02.454 [SRV_MAIN] INFO global src/daemon/rpc.h:73 Core rpc server started ok
2018-03-03 06:54:02.454 [SRV_MAIN] INFO global src/daemon/p2p.h:78 Starting p2p net loopâŚ
2018-03-03 06:54:03.455 [P2P7] INFO global src/cryptonote_core/cryptonote_core.cpp:1258 e[1;33m
The daemon will start synchronizing with the network. This may take a long time to complete.
You can set the level of process detailization* through âset_log <level|categories>â command*,
where is between 0 (no details) and 4 (very verbose), or custom category based levels (eg, *:WARNING)
Use the âhelpâ command to see the list of available commands.
e[0m
2018-03-03 06:54:03.456 [P2P7] WARN global src/cryptonote_core/cryptonote_core.cpp:1282 e[1;31me[0m
2018-03-03 06:54:03.457 [P2P7] WARN global src/cryptonote_core/cryptonote_core.cpp:1283 e[1;31mLast scheduled hard fork time shows a daemon update is needed now.e[0m
2018-03-03 06:54:03.458 [P2P7] WARN global src/cryptonote_core/cryptonote_core.cpp:1284 e[1;31me[0m
2018-03-03 06:54:03.510 [P2P7] WARN net.dns src/common/dns_utils.cpp:487 WARNING: no two valid DeroPulse DNS checkpoint records were received
2018-03-03 06:54:03.715 [P2P5] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [89.38.97.110:18090 OUT] Sync data returned a new top block candidate: 40286 -> 41495 [Your node is 1209 blocks (0 days) behind]
SYNCHRONIZATION started
2018-03-03 06:55:41.107 [P2P4] INFO global src/cryptonote_core/blockchain.cpp:1436 e[1;34m----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 40214
id: <5e9f554e5444e7f0db780400e78c683bd74c8c17123b70c481a4319a012aee2a>
PoW: <57ad04aec30df71c92b466686f80426527fd65e1cab86de77b61b85f00000000>
difficulty: 668817750e[0m
2018-03-03 06:57:28.185 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [45.77.89.64:18090 OUT] Sync data returned a new top block candidate: 40286 -> 41495 [Your node is 1209 blocks (0 days) behind]
SYNCHRONIZATION started
2018-03-03 07:03:10.474 [P2P2] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [89.38.96.169:18090 OUT] Sync data returned a new top block candidate: 40286 -> 41496 [Your node is 1210 blocks (0 days) behind]
SYNCHRONIZATION started
2018-03-03 07:04:19.363 [P2P6] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [45.63.6.91:18090 OUT] Sync data returned a new top block candidate: 40286 -> 41497 [Your node is 1211 blocks (0 days) behind]
SYNCHRONIZATION started
2018-03-03 07:04:45.558 [P2P2] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [94.130.219.86:40514 INC] Sync data returned a new top block candidate: 40286 -> 41498 [Your node is 1212 blocks (0 days) behind]
SYNCHRONIZATION started
2018-03-03 07:07:04.016 [P2P1] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [45.76.42.165:18090 OUT] Sync data returned a new top block candidate: 40286 -> 41500 [Your node is 1214 blocks (0 days) behind]
SYNCHRONIZATION started
2018-03-03 07:10:05.763 [P2P1] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [45.63.6.91:18090 OUT] Sync data returned a new top block candidate: 40286 -> 41501 [Your node is 1215 blocks (0 days) behind]
SYNCHRONIZATION started
2018-03-03 07:10:46.018 [P2P9] INFO global src/cryptonote_core/blockchain.cpp:1436 e[1;34m----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 40167
id: <3f8f64c72460003871ea98d50f2a5232acda001e206c4ab3d600c21a2e0ca823>
PoW: <644253f2314c88e3f64cef9b0f73069dfab3f5fc1aecb0c566535ddf03000000>
difficulty: 493803105e[0m
2018-03-03 07:11:51.388 [P2P4] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [212.8.242.60:18090 OUT] Sync data returned a new top block candidate: 40286 -> 41502 [Your node is 1216 blocks (0 days) behind]
SYNCHRONIZATION started
2018-03-03 12:13:01.765 [P2P7] WARN global src/cryptonote_core/cryptonote_core.cpp:1283 e[1;31mLast scheduled hard fork time shows a daemon update is needed now.e[0m
Hello everyone, Iâve had an opportunity to review supportâs posts and talk to him briefly. The fork issue will be resolved within the next 24 hours for anyone who may have missed it.
There are only two nodes that weâre recommending at this time if youâre having synchronization issues. --add-exclusive-node 89.38.96.169:18090 --add-exclusive-node 89.38.97.110:18090
Hi i just had to reply to let you know the wallet is working fine on windows. " dero_v6_windows_amd64 "
This wallet will sync on its own but freezes at 35700 - 38800.
after that you Have to run the derod from the cmd with the ( derod.exe --add-exclusive-node 89.38.96.169:18090 --add-exclusive-node 89.38.97.110:18090 ) or it will never finish syncing.
Câmon DERO guys, this needs to end! We (miners) have already lost a lots of coins and hashpower which could have been used somewhere else. I know that Serena here has been helpful a lot but I think you should either give out a message to tell all miners to stop until all issues are fixed or find a way credit all our lost coins.
When I try to sync my linux wallet with command in first post, this is what Iâm getting -
[P2P2] INFO global src/p2p/net_node.inl:258 Host 89.38.96.169 blocked [P2P8] INFO global src/p2p/net_node.inl:258 Host 89.38.97.110 blocked
If youâre mining on the official pool you will still receive the Dero youâve mined since v5 and v6 were released. Support will reply to you when they have a bit more time Iâm reasonably sure. I just wanted to take a moment to alleviate any concerns you had about any recently mined Dero potentially going missing.
I also mine so I follow up with Capt regularly and we exchange information. I know that the Dero development team is putting in incredibly long hours to sort this out.
For a lot of teams they only have to code one fix into their codebase. For Dero, theyâre coding the golang version in such a way that we will likely transition without most people initially noticing. This means that any fix that goes into the C++ code also needs to be properly accounted for in the golang code.
The Q1 roadmap is still on schedule even with the recent fork issue which should give you an indication of how much progress has been made in a very brief window of time (Q1).
There are two cases with you:
1] If you are mining on official pool you donât loose anything, simple.
2] Update daemon to the latest releases, dl and replace data.mdb from http://seeds.dero.io/data.mdb see for more details DERO blockchain sync problem
Thank you very much for the responses @Serena and @DEVELOPER. Now I could sync my cli wallet with the above blockchain file and those two exclusive nodes. No issues with the wallet now and I can see the balance minus the amount of DERO (6.9) I have lost while mining on the official pool as it was out of chain which I had reported earlier. Is there any plan to refund/credit our lost DERO because of poolâs fault?
Thank you once again for all your responses and being pro-active to issues raised.
It is regrettable that the network had some fork issues that cost many of us some Dero and we are genuinely sorry for any stress or problems this may have caused.
I know this will not be the answer youâre looking for, but the Dero team is unable to cover any losses incurred because the blockchain is still highly experimental and prone to unexpected errors while the transition is happening.
What the Dero team is doing by rewriting the entirety of the CryptoNote protocol in golang is entirely uncharted territory so some hiccups should be expected.
The Dero team is aiming for a seamless transition that many users wonât initially notice because the transition is intended to be as smooth as possible. This means that the fix needs to be accounted for in both codebases and then properly tested. While it sounds like 2 codebases = 2x the workload, it can actually be more than that making sure they function correctly together.
Was good two days back and now tried to sync but not working.