[ANN] DERO: DAG + Cryptonote + Bulletproofs + SSL + POW + Smart Contracts - page 142.

--Serena--

member

Activity: 224

Merit: 11

Quote from: cpmcgrat on March 01, 2018, 02:04:24 PM

Quote from: miner.rocks on March 01, 2018, 02:00:28 PM

We would suggest everyone to stop mining DERO, until fork issues will be solved. Angry

Yesterday our pool appeared on a forked chain for 3 times, the last one for 3 hours, we fully cover loses of our loyal miners.
Today our pool appeared on a forked chain, and we learned about it only after 2 hours, we will not cover loses anymore.

We suggest dev team to cover all miners loses, caused by these everyday forks, until issue will be solved.

I think at this point we need a full RCA from the devs as to why forks are happening constantly. I’d like to know the technical reason behind these issues. I’m going to keep supporting this coin, but some transparency here would go a long way. Then maybe I, or another community member could help fix it.

We will provide a root cause analysis when we've been able to analyze the problem a little further

--Serena--

member

Activity: 224

Merit: 11

Quote from: bineva17 on March 01, 2018, 12:22:30 PM

@Serena: I adore your talents. Normally community managers can only do the typing work, but not only you are a clever and devoted one, but also clearly understands how blockchain technology works and restlessly supports the Slack mining community of Dero. Not to mention you are female, a rare specie in crypto space and technical world. So good luck and keep doing the great job!

Hi bin!

I'm just trying to contribute where I can

The team is super talented and I'm incredibly fortunate to be able to learn from them everyday.

We will continue to work as hard as we have been, thank you for your positive comments they definitely help inspire me.

MagicSmoker

full member

Activity: 420

Merit: 184

Quote from: cotinco on March 01, 2018, 01:54:10 PM

dero.miner.rocks is on a longer chain. stocks.exchange seems to be also there. It's very like the same that was happened yesterday - pool.dero.live is building its own blockchain regardless of others. May be it's because of its heavy load?

Yikes... I just transferred 37 DERO from stocks.exchange to my local wallet. Hope it didn't end up on a fork and shunted off into the abyss.

cpmcgrat

member

Activity: 223

Merit: 21

DCAB

Quote from: miner.rocks on March 01, 2018, 02:00:28 PM

We would suggest everyone to stop mining DERO, until fork issues will be solved. Angry

Yesterday our pool appeared on a forked chain for 3 times, the last one for 3 hours, we fully cover loses of our loyal miners.
Today our pool appeared on a forked chain, and we learned about it only after 2 hours, we will not cover loses anymore.

We suggest dev team to cover all miners loses, caused by these everyday forks, until issue will be solved.

I think at this point we need a full RCA from the devs as to why forks are happening constantly. I’d like to know the technical reason behind these issues. I’m going to keep supporting this coin, but some transparency here would go a long way. Then maybe I, or another community member could help fix it.

miner.rocks

jr. member

Activity: 181

Merit: 2

We would suggest everyone to stop mining DERO, until fork issues will be solved. Angry

Yesterday our pool appeared on a forked chain for 3 times, the last one for 3 hours, we fully cover loses of our loyal miners.
Today our pool appeared on a forked chain, and we learned about it only after 2 hours, we will not cover loses anymore.

We suggest dev team to cover all miners loses, caused by these everyday forks, until issue will be solved.

cotinco

newbie

Activity: 24

Merit: 0

Quote from: Speedie on March 01, 2018, 01:27:54 PM

Quote from: cotinco on March 01, 2018, 01:19:47 PM

Quote from: Speedie on March 01, 2018, 01:11:50 PM

Quote from: cotinco on March 01, 2018, 01:01:21 PM

Quote from: Speedie on March 01, 2018, 09:39:52 AM

Quote from: cryptoRX on March 01, 2018, 09:30:59 AM

I'm stuck on block 40286. Doesn't sync and when I try to add priority nodes as advised in an earlier post, it just hangs. I'm not using the GUI wallet and I can't decide if my wallet is on a fork.

If your local DB already "forked" so to speak then adding the new nodes won't help with that. You'll need to delete the DB and start with a fresh sync.

I made a full DB download available that's current as of about 12 hours ago: Download Link

If you're using Windows, the data.mdb file is in ProgramData\dero\lmdb. Simply close your wallet and daemon, delete the data.mdb file in that folder, replace it with the data.mdb file from the download, and start the daemon again with the 6 priority nodes. Once it has synced you can start the wallet again.

Sorry to say that, but again seems that the network is quite synchronized except the priority nodes - all of them stuck on 40785 (official blockchain is 40793). May be they can't handle the large number of connections? The same happened with pool.dero.live.

They have around 40 - 50 connections each, total, in and out. Loads are averaging 0.05 across the 6 nodes, so it isn't a load problem.

cryptopool.space and the block explorer are off on a higher block than pool.dero.live, dero.tech, dero.miner.rocks, and the 6 nodes. The question being why.

Seems that they forked due to an alternative at 40770.
Unfortunately, the dero daemon handles alternatives very strangely, sometimes it enters in a loop with exception cryptonote::BLOCK_DNE instead of choosing the correct block chain.

Yes, I noticed that when all 6 nodes simultaneously went beserk and I had to replicate a good DB across them all. At the moment it's a case of holding things together as much as possible until the devs can get a fix in place.

dero.miner.rocks is on a longer chain. stocks.exchange seems to be also there. It's very like the same that was happened yesterday - pool.dero.live is building its own blockchain regardless of others. May be it's because of its heavy load?

Speedie

sr. member

Activity: 504

Merit: 254

Quote from: cotinco on March 01, 2018, 01:19:47 PM

Quote from: Speedie on March 01, 2018, 01:11:50 PM

Quote from: cotinco on March 01, 2018, 01:01:21 PM

Quote from: Speedie on March 01, 2018, 09:39:52 AM

Quote from: cryptoRX on March 01, 2018, 09:30:59 AM

I'm stuck on block 40286. Doesn't sync and when I try to add priority nodes as advised in an earlier post, it just hangs. I'm not using the GUI wallet and I can't decide if my wallet is on a fork.

If your local DB already "forked" so to speak then adding the new nodes won't help with that. You'll need to delete the DB and start with a fresh sync.

I made a full DB download available that's current as of about 12 hours ago: Download Link

If you're using Windows, the data.mdb file is in ProgramData\dero\lmdb. Simply close your wallet and daemon, delete the data.mdb file in that folder, replace it with the data.mdb file from the download, and start the daemon again with the 6 priority nodes. Once it has synced you can start the wallet again.

Sorry to say that, but again seems that the network is quite synchronized except the priority nodes - all of them stuck on 40785 (official blockchain is 40793). May be they can't handle the large number of connections? The same happened with pool.dero.live.

They have around 40 - 50 connections each, total, in and out. Loads are averaging 0.05 across the 6 nodes, so it isn't a load problem.

cryptopool.space and the block explorer are off on a higher block than pool.dero.live, dero.tech, dero.miner.rocks, and the 6 nodes. The question being why.

Seems that they forked due to an alternative at 40770.
Unfortunately, the dero daemon handles alternatives very strangely, sometimes it enters in a loop with exception cryptonote::BLOCK_DNE instead of choosing the correct block chain.

Yes, I noticed that when all 6 nodes simultaneously went beserk and I had to replicate a good DB across them all. At the moment it's a case of holding things together as much as possible until the devs can get a fix in place.

air133

newbie

Activity: 210

Merit: 0

Today and now i have problem with pool http://pool.dero.io/ I do not see my stats, write Connection error.

cotinco

newbie

Activity: 24

Merit: 0

Quote from: Speedie on March 01, 2018, 01:11:50 PM

Quote from: cotinco on March 01, 2018, 01:01:21 PM

Quote from: Speedie on March 01, 2018, 09:39:52 AM

Quote from: cryptoRX on March 01, 2018, 09:30:59 AM

I'm stuck on block 40286. Doesn't sync and when I try to add priority nodes as advised in an earlier post, it just hangs. I'm not using the GUI wallet and I can't decide if my wallet is on a fork.

If your local DB already "forked" so to speak then adding the new nodes won't help with that. You'll need to delete the DB and start with a fresh sync.

I made a full DB download available that's current as of about 12 hours ago: Download Link

If you're using Windows, the data.mdb file is in ProgramData\dero\lmdb. Simply close your wallet and daemon, delete the data.mdb file in that folder, replace it with the data.mdb file from the download, and start the daemon again with the 6 priority nodes. Once it has synced you can start the wallet again.

Sorry to say that, but again seems that the network is quite synchronized except the priority nodes - all of them stuck on 40785 (official blockchain is 40793). May be they can't handle the large number of connections? The same happened with pool.dero.live.

They have around 40 - 50 connections each, total, in and out. Loads are averaging 0.05 across the 6 nodes, so it isn't a load problem.

cryptopool.space and the block explorer are off on a higher block than pool.dero.live, dero.tech, dero.miner.rocks, and the 6 nodes. The question being why.

Seems that they forked due to an alternative at 40770.
Unfortunately, the dero daemon handles alternatives very strangely, sometimes it enters in a loop with exception cryptonote::BLOCK_DNE instead of choosing the correct block chain.

Speedie

sr. member

Activity: 504

Merit: 254

Quote from: cotinco on March 01, 2018, 01:01:21 PM

Quote from: Speedie on March 01, 2018, 09:39:52 AM

Quote from: cryptoRX on March 01, 2018, 09:30:59 AM

I'm stuck on block 40286. Doesn't sync and when I try to add priority nodes as advised in an earlier post, it just hangs. I'm not using the GUI wallet and I can't decide if my wallet is on a fork.

If your local DB already "forked" so to speak then adding the new nodes won't help with that. You'll need to delete the DB and start with a fresh sync.

I made a full DB download available that's current as of about 12 hours ago: Download Link

If you're using Windows, the data.mdb file is in ProgramData\dero\lmdb. Simply close your wallet and daemon, delete the data.mdb file in that folder, replace it with the data.mdb file from the download, and start the daemon again with the 6 priority nodes. Once it has synced you can start the wallet again.

Sorry to say that, but again seems that the network is quite synchronized except the priority nodes - all of them stuck on 40785 (official blockchain is 40793). May be they can't handle the large number of connections? The same happened with pool.dero.live.

They have around 40 - 50 connections each, total, in and out. Loads are averaging 0.05 across the 6 nodes, so it isn't a load problem.

cryptopool.space and the block explorer are off on a higher block than pool.dero.live, dero.tech, dero.miner.rocks, and the 6 nodes. The question being why.

cotinco

newbie

Activity: 24

Merit: 0

Quote from: Speedie on March 01, 2018, 09:39:52 AM

Quote from: cryptoRX on March 01, 2018, 09:30:59 AM

I'm stuck on block 40286. Doesn't sync and when I try to add priority nodes as advised in an earlier post, it just hangs. I'm not using the GUI wallet and I can't decide if my wallet is on a fork.

If your local DB already "forked" so to speak then adding the new nodes won't help with that. You'll need to delete the DB and start with a fresh sync.

I made a full DB download available that's current as of about 12 hours ago: Download Link

If you're using Windows, the data.mdb file is in ProgramData\dero\lmdb. Simply close your wallet and daemon, delete the data.mdb file in that folder, replace it with the data.mdb file from the download, and start the daemon again with the 6 priority nodes. Once it has synced you can start the wallet again.

Sorry to say that, but again seems that the network is quite synchronized except the priority nodes - all of them stuck on 40785 (official blockchain is 40793). May be they can't handle the large number of connections? The same happened with pool.dero.live.

bineva17

member

Activity: 130

Merit: 11

Quote from: --Serena-- on February 28, 2018, 10:25:35 PM

Quote from: TRON_NZ on February 28, 2018, 09:49:08 PM

Quote from: TRON_NZ on February 27, 2018, 12:47:03 PM

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.

I asked the same question and think it's safe to use Denis' beautiful Gui wallet v0.0.2. It works like a charm. Anyway, have successfully tested the withdrawal amount of 29,39,49 and 59 coins, error at 69. Our devs are working on it and hope we'll soon find a solution.

@Serena: I adore your talents. Normally community managers can only do the typing work, but not only you are a clever and devoted one, but also clearly understands how blockchain technology works and restlessly supports the Slack mining community of Dero. Not to mention you are female, a rare specie in crypto space and technical world. So good luck and keep doing the great job!

cryptoRX

member

Activity: 196

Merit: 12

Quote from: Speedie on March 01, 2018, 09:39:52 AM

Quote from: cryptoRX on March 01, 2018, 09:30:59 AM

I'm stuck on block 40286. Doesn't sync and when I try to add priority nodes as advised in an earlier post, it just hangs. I'm not using the GUI wallet and I can't decide if my wallet is on a fork.

If your local DB already "forked" so to speak then adding the new nodes won't help with that. You'll need to delete the DB and start with a fresh sync.

I made a full DB download available that's current as of about 12 hours ago: Download Link

If you're using Windows, the data.mdb file is in ProgramData\dero\lmdb. Simply close your wallet and daemon, delete the data.mdb file in that folder, replace it with the data.mdb file from the download, and start the daemon again with the 6 priority nodes. Once it has synced you can start the wallet again.

That worked like a charm. Thank you.

Speedie

sr. member

Activity: 504

Merit: 254

Quote from: cryptoRX on March 01, 2018, 09:30:59 AM

I'm stuck on block 40286. Doesn't sync and when I try to add priority nodes as advised in an earlier post, it just hangs. I'm not using the GUI wallet and I can't decide if my wallet is on a fork.

If your local DB already "forked" so to speak then adding the new nodes won't help with that. You'll need to delete the DB and start with a fresh sync.

I made a full DB download available that's current as of about 12 hours ago: Download Link

If you're using Windows, the data.mdb file is in ProgramData\dero\lmdb. Simply close your wallet and daemon, delete the data.mdb file in that folder, replace it with the data.mdb file from the download, and start the daemon again with the 6 priority nodes. Once it has synced you can start the wallet again.

cryptoRX

member

Activity: 196

Merit: 12

I'm stuck on block 40286. Doesn't sync and when I try to add priority nodes as advised in an earlier post, it just hangs. I'm not using the GUI wallet and I can't decide if my wallet is on a fork.

--Serena--

member

Activity: 224

Merit: 11

Quote from: cotinco on March 01, 2018, 07:40:21 AM

Quote from: --Serena-- on March 01, 2018, 07:07:29 AM

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.

cotinco

newbie

Activity: 24

Merit: 0

Quote from: --Serena-- on March 01, 2018, 07:07:29 AM

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

member

Activity: 224

Merit: 11

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.

MagicSmoker

full member

Activity: 420

Merit: 184

Quote from: Speedie on March 01, 2018, 06:47:53 AM

Quote from: cotinco on March 01, 2018, 05:58:05 AM

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.

Speedie

sr. member

Activity: 504

Merit: 254

Quote from: cotinco on March 01, 2018, 05:58:05 AM

Quote from: MagicSmoker on March 01, 2018, 05:55:53 AM

Quote from: cotinco on March 01, 2018, 05:50:17 AM

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 Sad

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?

Topic: [ANN] DERO: DAG + Cryptonote + Bulletproofs + SSL + POW + Smart Contracts - page 142. (Read 123199 times)