[ANN] DERO: DAG + Cryptonote + Bulletproofs + SSL + POW + Smart Contracts

[Jarod1231]

My wallet appears stuck on block #40283 ... how can I fix this?

[--Serena--]

My wallet appears stuck on block #40283 ... how can I fix this?

Can you try a resync using the new priority nodes added by Speedie today? They're officially supported by the Dero team. The following is Speedie's post with the relevant info and a link to a tutorial for adding priority nodes

https://forum.dero.io/t/dero-blockchain-sync-problem/21



****** IMPORTANT ******

I have been working with support and DeroBoy this morning to try and help with the network problems that we've been seeing. To that end, I have created a network of 6 geo-diverse nodes dedicated purely to running Dero daemons. The nodes have each other as priority nodes, and it is requested that all pools add them as priority nodes too.

They are located in: New Jersey US, Los Angeles US, Dallas US, London UK, Amsterdam NL, and Singapore.

IP addresses:

45.63.6.91
108.61.220.229
207.148.5.250
45.77.89.64
45.76.42.165
45.77.242.137

To add them to your pool's derod startup command line:

--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

I will be watching them carefully to ensure that they stay in sync and running fast. So far no problems noted, and they're under very low load. Any problems please let me know.

[MagicSmoker]

My wallet appears stuck on block #40283 ... how can I fix this?

Can you try a resync using the new priority nodes added by Speedie today? They're officially supported by the Dero team. The following is Speedie's post with the relevant info and a link to a tutorial for adding priority nodes

Just to emphasize, you must also delete (or, ideally, replace) data.mdb from the c:\programdata\dero\lmdb directory otherwise the daemon will remain stuck on the forked chain, even with the new priority nodes (ask me how I know this...  )

[--Serena--]

DERO: Privacy + Smart Contracts

Dero at present is a code fork of Monero (Helium Hydra) with the Bytecoin CryptoNote protocol.
Dero will be a completely new blockchain technology integrating the CryptoNote protocol with new smart contract controls.
Dero is being rewritten from C++ to Golang (Google Language) to bring together CryptoNote and smart contracts on the Dero blockchain.
No ICO just hard POW mining

CryptoNote protocol implementation in Golang is almost completed.

Website: https://dero.io/
Forum : https://forum.dero.io/
Explorer : https://explorer.dero.io
Explorer : http://dero.live:8080/

Exchange: https://stocks.exchange/trade/DERO/BTC

DERO STATS: https://coincodex.com/crypto/dero/

GitHub: https://github.com/deroproject

How to mine: https://forum.dero.io/t/how-to-be-part-of-dero-network-start-mining-dero/22

Dero has a very welcoming community and we would enjoy the opportunity to have you join us in Slack or on Reddit!

https://join.slack.com/t/deroproject/shared_invite/enQtMzAwMDc5MDY4NDUzLTAzOWNjYWZmNDgxZTk1YjNiNWFiYjg1OWNiMmQ2MmUxOWRmNjNjOWM3ODAzMzE3M2RhNzBhZjUyZGQxYjQxY2U

https://www.reddit.com/r/DeroProject/

If you have any questions or require assistance, please don't hesitate to reach out for any reason. Slack tends to elicit the fastest response times from the community but all listed links are checked several times a day

[Jarod1231]

My wallet appears stuck on block #40283 ... how can I fix this?

Can you try a resync using the new priority nodes added by Speedie today? They're officially supported by the Dero team. The following is Speedie's post with the relevant info and a link to a tutorial for adding priority nodes

Just to emphasize, you must also delete (or, ideally, replace) data.mdb from the c:\programdata\dero\lmdb directory otherwise the daemon will remain stuck on the forked chain, even with the new priority nodes (ask me how I know this...  )

Deleting and resyncing with those nodes finally worked, now I just have to do a bunch of smalls withdrawals from this terrible exchange lol

[itslukebenz]

My wallet appears stuck on block #40283 ... how can I fix this?

Can you try a resync using the new priority nodes added by Speedie today? They're officially supported by the Dero team. The following is Speedie's post with the relevant info and a link to a tutorial for adding priority nodes

Just to emphasize, you must also delete (or, ideally, replace) data.mdb from the c:\programdata\dero\lmdb directory otherwise the daemon will remain stuck on the forked chain, even with the new priority nodes (ask me how I know this...  )

Deleting and resyncing with those nodes finally worked, now I just have to do a bunch of smalls withdrawals from this terrible exchange lol

I feel your pain  It's gonna take a while with 30 coins/tx 

[Jarod1231]

My wallet appears stuck on block #40283 ... how can I fix this?

Can you try a resync using the new priority nodes added by Speedie today? They're officially supported by the Dero team. The following is Speedie's post with the relevant info and a link to a tutorial for adding priority nodes

Just to emphasize, you must also delete (or, ideally, replace) data.mdb from the c:\programdata\dero\lmdb directory otherwise the daemon will remain stuck on the forked chain, even with the new priority nodes (ask me how I know this...  )

Deleting and resyncing with those nodes finally worked, now I just have to do a bunch of smalls withdrawals from this terrible exchange lol

I feel your pain  It's gonna take a while with 30 coins/tx 

I just finished withdrawing them all, now to forget I have them for a couple years.... 

[TRON_NZ]

Just a warning, don't withdrawal DERO from Stock Exchange. I have a reasonable amount lock under "withdrawal error" (balance is now zero). Placed a ticket and support says the dev will look into it (about 24 hours ago, no change).

Will let you know of any update....Hopefully I haven't lost my coins :/

Follow up, Stock Exchange returned all my coins (took about 48 hours)....

On another note, is it still safe to use the GUI wallet or should I switch to the latest command line wallet due to the issue with block change syncing? Thanks.

[--Serena--]

Just a warning, don't withdrawal DERO from Stock Exchange. I have a reasonable amount lock under "withdrawal error" (balance is now zero). Placed a ticket and support says the dev will look into it (about 24 hours ago, no change).

Will let you know of any update....Hopefully I haven't lost my coins :/

Follow up, Stock Exchange returned all my coins (took about 48 hours)....

On another note, is it still safe to use the GUI wallet or should I switch to the latest command line wallet due to the issue with block change syncing? Thanks.

Hi Tron, I'm relieved to hear that Stocks.Exchange is starting to respond to the tickets from the community. The GUI wallet was cloned by a community member and is not the official GUI wallet due to be released further into the roadmap. To date I have not had anyone report any issues with the current GUI wallet and the community member who made it remains a respected member.

If you're having any sync issues let me know and we can resolve them by clearing the existing data and starting fresh with several new priority nodes which has resolved the issue for all reported cases so far.

[microran]

Announcing RUS DERO no official pool http://www.cryptorus.space
DERO: A secure, private cryptocurrency with Smart Contracts.
Total Pool Fee: 0.01%

[cotinco]

Sorry but seems that did not help. sync_info command in daemon shows now most of these nodes (except two - 108.61.220.229 and 207.148.5.250) are simultaneously out of the blockchain. Seems that alternative at 40646 did the damage Regardless of that, the rest of network is probably synchronized.

****** IMPORTANT ******

I have been working with support and DeroBoy this morning to try and help with the network problems that we've been seeing. To that end, I have created a network of 6 geo-diverse nodes dedicated purely to running Dero daemons. The nodes have each other as priority nodes, and it is requested that all pools add them as priority nodes too. End users may also add them as priority nodes to your local daemon which will help everything to stay in sync.

They are located in: New Jersey US, Los Angeles US, Dallas US, London UK, Amsterdam NL, and Singapore.

IP addresses:

45.63.6.91
108.61.220.229
207.148.5.250
45.77.89.64
45.76.42.165
45.77.242.137

To add them to your pool's derod startup command line:

--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

I will be watching them carefully to ensure that they stay in sync and running fast. So far no problems noted, and they're under very low load. Any problems please let me know.

[MagicSmoker]

Sorry but seems that did not help. sync_info command in daemon shows now most of these nodes (except two - 108.61.220.229 and 207.148.5.250) are simultaneously out of the blockchain. Seems that alternative at 40646 did the damage Regardless of that, the rest of network is probably synchronized.

Did you delete or replace data.mdb as I emphasized a page back?

Either works, but downloading it from http://seeds.dero.io/data.mdb will make the re-sync go a lot faster.

File is located in c:\programdata\dero\lmdb\

[cotinco]

Sorry but seems that did not help. sync_info command in daemon shows now most of these nodes (except two - 108.61.220.229 and 207.148.5.250) are simultaneously out of the blockchain. Seems that alternative at 40646 did the damage Regardless of that, the rest of network is probably synchronized.

Did you delete or replace data.mdb as I emphasized a page back?

It's not my local problem, there is no need to delete my base.
It's remote problem on these nodes.
The rest of network including my daemon are ok.
Now 45.77.89.64 seems also ok, so there are 3 stuck nodes of those 6.

[MagicSmoker]

Sorry but seems that did not help. sync_info command in daemon shows now most of these nodes (except two - 108.61.220.229 and 207.148.5.250) are simultaneously out of the blockchain. Seems that alternative at 40646 did the damage Regardless of that, the rest of network is probably synchronized.

Did you delete or replace data.mdb as I emphasized a page back?

It's not my local problem, there is no need to delete my base.
It's remote problem on these nodes.
The rest of network including my daemon are ok.
Now 45.77.89.64 seems also ok, so there are 3 stuck nodes of those 6.

Oh, it seems I am the one that should have read more carefully! 

You are referring to external nodes - including some in Speedie's priority network - as still being out of sync. Hmm, we have now reached my level of incompetency so I'll defer to the experts but my suspicion is that this is a non-issue for now, though the only evidence I have for that is my daemon/wallet is still sync'ed up and working fine.

[--Serena--]

Sorry but seems that did not help. sync_info command in daemon shows now most of these nodes (except two - 108.61.220.229 and 207.148.5.250) are simultaneously out of the blockchain. Seems that alternative at 40646 did the damage Regardless of that, the rest of network is probably synchronized.

Did you delete or replace data.mdb as I emphasized a page back?

It's not my local problem, there is no need to delete my base.
It's remote problem on these nodes.
The rest of network including my daemon are ok.
Now 45.77.89.64 seems also ok, so there are 3 stuck nodes of those 6.

Hi Cotinco,

It's a little bit early here so I'm sorry if I missed anything. I've been looking into the priority nodes and they appear to be in sync at the moment.

I ran into the blockchain sync issue myself yesterday and found that deleting the p2pstate.bin and the imbd file did it for me. However, YMMV and I'm willing to do what it takes to help you get up and running to your satisfaction. It's still about 3am here so when I'm online in 4 - 5 hours I will be available again for the day on Slack at your convenience.

It sounds like your file may be corrupted. I just resynced my blockchain before I started this post to confirm that it's updating correctly with the new nodes. Perhaps try running the following in your command interface when you're ready to start fresh.

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

[Speedie]

Sorry but seems that did not help. sync_info command in daemon shows now most of these nodes (except two - 108.61.220.229 and 207.148.5.250) are simultaneously out of the blockchain. Seems that alternative at 40646 did the damage Regardless of that, the rest of network is probably synchronized.

Did you delete or replace data.mdb as I emphasized a page back?

It's not my local problem, there is no need to delete my base.
It's remote problem on these nodes.
The rest of network including my daemon are ok.
Now 45.77.89.64 seems also ok, so there are 3 stuck nodes of those 6.

Good morning! Just checked all 6 nodes and they're at the same height as the official pool. Are you still seeing something different?

[MagicSmoker]

It's not my local problem, there is no need to delete my base.
It's remote problem on these nodes.
The rest of network including my daemon are ok.
Now 45.77.89.64 seems also ok, so there are 3 stuck nodes of those 6.

Good morning! Just checked all 6 nodes and they're at the same height as the official pool. Are you still seeing something different?

You typed too soon, methinks... I've got 7 alternate chains showing up in my daemon (alt_chain_info) and the main pool is once again not updating stats. However, mining still seems to be working there and I just received a payment a few minutes ago.

[--Serena--]

Height: 40674/40674 (100.0%) on mainnet, not mining, net hash 4.55 MH/s, v6, update needed, 8(out)+13(in) connections, uptime 0d 0h 33m 54s

The worker stats on the official pool aren't related to a daemon sync issue but I have let support know

The official priority nodes, including the ones Speedie added appear to be in sync at this time. We do understand that there may still be some hiccups and are diligently working to provide effective solutions to anyone who may still need assistance.

I'm here for as long as anyone needs me.

[cotinco]

Height: 40674/40674 (100.0%) on mainnet, not mining, net hash 4.55 MH/s, v6, update needed, 8(out)+13(in) connections, uptime 0d 0h 33m 54s

The worker stats on the official pool aren't related to a daemon sync issue but I have let support know

The official priority nodes, including the ones Speedie added appear to be in sync at this time. We do understand that there may still be some hiccups and are diligently working to provide effective solutions to anyone who may still need assistance.

I'm here for as long as anyone needs me.

Can I just throw a hypothesis? I'm not sure that it is true because I'm very new to the cryptocurrency world, but at least an idea.
Seems that using --add-priority-node decreases diversity the network and creates heavy load on these priority nodes added by a lot of participants, so they could not handle the large traffic.
Is it possible that the network is better without any priority nodes?
May the problems had been arisen (or the things got worse) when the first bunch of priority nodes appeared?
How other networks based on monero (e.g. sumo, etn) do exist without any priority nodes and with a quite number of alternatives according to daemons' logs?

P.S. Sorry for writing this early morning but seems we're in completely different time zones.

[--Serena--]

Height: 40674/40674 (100.0%) on mainnet, not mining, net hash 4.55 MH/s, v6, update needed, 8(out)+13(in) connections, uptime 0d 0h 33m 54s

The worker stats on the official pool aren't related to a daemon sync issue but I have let support know

The official priority nodes, including the ones Speedie added appear to be in sync at this time. We do understand that there may still be some hiccups and are diligently working to provide effective solutions to anyone who may still need assistance.

I'm here for as long as anyone needs me.

Can I just throw a hypothesis? I'm not sure that it is true because I'm very new to the cryptocurrency world, but at least an idea.
Seems that using --add-priority-node decreases diversity the network and creates heavy load on these priority nodes added by a lot of participants, so they could not handle the large traffic.
Is it possible that the network is better without any priority nodes?
May the problems had been arisen (or the things got worse) when the first bunch of priority nodes appeared?
How other networks based on monero (e.g. sumo, etn) do exist without any priority nodes and with a quite number of alternatives according to daemons' logs?

P.S. Sorry for writing this early morning but seems we're in completely different time zones.

No worries about the time zone thing, I actually really just enjoy helping people when I can so I don't mind at all (Plus my dogs love to hang out in the middle of the night)

We're using priority nodes for now because it's a smaller network but they shouldn't be needed in the future for the average person. They can make life easier for some people like pool operators though.

The first priority nodes didn't cause any problems but we've had a large influx of new connections lately so we (thank you -->Speedie!<--) added more priority nodes to reduce the load per node, increase geographical diversity, and generally help support the network while it's in its infancy. The nodes should help keep each other in sync for now.

Edit: I forgot to add that the load per node is very low right now and they're setup to handle a massive influx of new connections.