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

[pegos]

2.Download the database.db snapshot from http://seeds.dero.io/testnet/blockchain/derod_database.db.zip - and leave it for a few steps

Not Found

The requested URL /testnet/blockchain/derod_database.db.zip was not found on this server.

[acru]

[/quote]

1. Create a batch file (eg: time.bat), and put :

Code:

net stop w32time
net start w32time
w32tm /config /syncfromflags:manual /manualpeerlist:"pool.ntp.org"
w32tm /resync

2. Right-click on the file > Run as Administrator.
[/quote]

Thanks for help, but still do not work, I am using windows 10
Do i have to cancel this command in somehow or not?

[--Serena--]

2.Download the database.db snapshot from http://seeds.dero.io/testnet/blockchain/derod_database.db.zip - and leave it for a few steps

Not Found

The requested URL /testnet/blockchain/derod_database.db.zip was not found on this server.

database file no longer needed as the new test chain is very small/compact - editing post

[acru]

Hello devs, I am having problems with this mesage in daemon

Your system time deviation is more than 2 secs (1.956488151s)

I had try evething, even contact with microsoft help, and they tell me to put this lines in cmd

net stop w32time
w32tm /unregister
w32tm /register
net start w32time
w32tm /resync

and then restar the PC, but still apear the mesagge, what do you think windows users should do to sync time using NTP

[MagicSmoker]

Hello devs, I am having problems with this mesage in daemon
...

You posted more or less the same message twice; don't do that. Also, make sure you read the last couple pages of a thread to see if your issue has been discussed already (hint: it has).

The above sequence of commands are a bunch of crap and won't work.

Almost nothing really works for this issue, actually, and the one "solution" - temporary at best - is a pain:

Right click on the clock.
Select "adjust date/time".
Click on the radio button for "set time automatically" to turn it off.
Click on the "change" button to change the date/time
Now adjust the time up or down by 1 minute - it doesn't matter - and save changes
Click on the radio button for "set time automatically" again to turn it back on.

This is undoubtedly way less efficient than a theoretically ideal solution but it worked for me.

[acru]

Hello devs, I am having problems with this mesage in daemon
...

You posted more or less the same message twice; don't do that. Also, make sure you read the last couple pages of a thread to see if your issue has been discussed already (hint: it has).

The above sequence of commands are a bunch of crap and won't work.

Almost nothing really works for this issue, actually, and the one "solution" - temporary at best - is a pain:

Right click on the clock.
Select "adjust date/time".
Click on the radio button for "set time automatically" to turn it off.
Click on the "change" button to change the date/time
Now adjust the time up or down by 1 minute - it doesn't matter - and save changes
Click on the radio button for "set time automatically" again to turn it back on.

This is undoubtedly way less efficient than a theoretically ideal solution but it worked for me.

Thanks a lot

[pegos]

please update your testnet daemons to the latest version from here: http://seeds.dero.io/testnet/ this update just came out

bothers me, that versions are not numbered, there is a terrible mess ...
synchronization is really much faster than yesterday!

[CaptDero]

please update your testnet daemons to the latest version from here: http://seeds.dero.io/testnet/ this update just came out

bothers me, that versions are not numbered, there is a terrible mess ...
synchronization is really much faster than yesterday!

Everything is version-ed internally. Use version cmd/syncinfo cmd in testnet daemon to see versions.

[Dr_Voidberg]

Hello devs, I am having problems with this mesage in daemon
...

You posted more or less the same message twice; don't do that. Also, make sure you read the last couple pages of a thread to see if your issue has been discussed already (hint: it has).

The above sequence of commands are a bunch of crap and won't work.

Almost nothing really works for this issue, actually, and the one "solution" - temporary at best - is a pain:

Right click on the clock.
Select "adjust date/time".
Click on the radio button for "set time automatically" to turn it off.
Click on the "change" button to change the date/time
Now adjust the time up or down by 1 minute - it doesn't matter - and save changes
Click on the radio button for "set time automatically" again to turn it back on.

This is undoubtedly way less efficient than a theoretically ideal solution but it worked for me.

I installed an external NTP service to fix this (NTP for Windows)

[pegos]

please update your testnet daemons to the latest version from here: http://seeds.dero.io/testnet/ this update just came out

bothers me, that versions are not numbered, there is a terrible mess ...
synchronization is really much faster than yesterday!

Everything is version-ed internally. Use version cmd/syncinfo cmd in testnet daemon to see versions.

in programming has always been a good habit of numbering a version, whether it be a test or a sharp script.
 

In any case, the test-net runs without any problems, occasionally disrupts system time ...
I miss the time stamps for more accurate analyzes!

[fellestreum]

please update your testnet daemons to the latest version from here: http://seeds.dero.io/testnet/ this update just came out

bothers me, that versions are not numbered, there is a terrible mess ...
synchronization is really much faster than yesterday!

Everything is version-ed internally. Use version cmd/syncinfo cmd in testnet daemon to see versions.

in programming has always been a good habit of numbering a version, whether it be a test or a sharp script.
 

In any case, the test-net runs without any problems, occasionally disrupts system time ...
I miss the time stamps for more accurate analyzes!

I think when you are in alpha version and almost constantly producing new builds, it just slows you down keeping track of file naming versioning  

[pegos]

I think when you are in alpha version and almost constantly producing new builds, it just slows you down keeping track of file naming versioning  

I have nothing to add, I know exactly what I'm writing, 20 years a day I'm producing a code.
I do not know exactly what you are advocating.
xxx_001, xxx_002, xxx_003 ....?
it is enough to note the working name in the description in download page
I will not participate in the wacky wars!
I write these remarks because I am interested in the project being developed in the right direction, based on personal experience.
 

[fellestreum]

I think when you are in alpha version and almost constantly producing new builds, it just slows you down keeping track of file naming versioning  

I have nothing to add, I know exactly what I'm writing, 20 years a day I'm producing a code.
I do not know exactly what you are advocating.
xxx_001, xxx_002, xxx_003 ....?
it is enough to note the working name in the description in download page
I will not participate in the wacky wars!
I write these remarks because I am interested in the project being developed in the right direction, based on personal experience.
 

Ok, fine, no problem, not trying to pick a fight.  Just trying to offer a rational explanation for observed behaviour.  I imagine the dev team are working under extreme time pressure right now and are just not doing stuff they consider non-essential.  However if you have different explanation for observed behaviour feel free to offer it. 

[fellestreum]

I think when you are in alpha version and almost constantly producing new builds, it just slows you down keeping track of file naming versioning  

I have nothing to add, I know exactly what I'm writing, 20 years a day I'm producing a code.
I do not know exactly what you are advocating.
xxx_001, xxx_002, xxx_003 ....?
it is enough to note the working name in the description in download page
I will not participate in the wacky wars!
I write these remarks because I am interested in the project being developed in the right direction, based on personal experience.
 

Besides which... the whole point of the testnet is that members of the community are invited to help test the network.  If you don't like the way this is being done you are free to stay away.  No-one is forcing  you to contribute.

The dev team are dealing with some pretty major issues.  To complain that they are not naming the files correctly according to some convention you like, especially when you can easily see how old the files are - they are all datestamped so verifying whether you have the latest version is as easy as checking whether a new version has been uploaded since you last checked - and especially given that the team alerts everyone when a new version is ready to be downloaded (if you are alpha testing you should be on the slack or discord testnet channels) - is maybe getting the priorities a wee bit in the wrong order...

[CaptDero]

I think when you are in alpha version and almost constantly producing new builds, it just slows you down keeping track of file naming versioning  

I have nothing to add, I know exactly what I'm writing, 20 years a day I'm producing a code.
I do not know exactly what you are advocating.
xxx_001, xxx_002, xxx_003 ....?
it is enough to note the working name in the description in download page
I will not participate in the wacky wars!
I write these remarks because I am interested in the project being developed in the right direction, based on personal experience.
 

Ok, fine, no problem, not trying to pick a fight.  Just trying to offer a rational explanation for observed behaviour.  I imagine the dev team are working under extreme time pressure right now and are just not doing stuff they consider non-essential.  However if you have different explanation for observed behaviour feel free to offer it. 

@pegos, you are absolutely right. As @fellestreum said is right but will definitely add in coming releases.

[fellestreum]

Well kudos to Capt - a nicer chap than me 

[pegos]

@pegos, you are absolutely right. As @fellestreum said is right but will definitely add in coming releases.

thank you for your response.

(I do not know why the remarks of a technical nature,  make a passionate reaction on this forum.
I have no personal interest in it!)

[Melody Jelly]

Hey guys! Very interesting project based on cryptonote. Smart contracts and fast transactions speed are definitely a must ! Can't wait to see more.

[acru]

Hello dev, I am mining in test net to help the project and also to get used to the new way of mining, everything was ok until yesterday 9 pm. Today I started to sync and the daemon stop sync at 5180 block and I have restart it many times and also the PC, can you tell me please how do I fix it.

I also want to ask some extra questions to dev.

1.- When dero atlantis is lunch (main net) we are only going to be able to mine this way. If the answer is yes I think is awesome, for this was the initial idea of Sathosi on bitcoin

2.- Will or will not be possible to mine with GPU. I hope the answer is not

3.- When is main net going to be launch

Thanks

[--Serena--]

Hello everyone, there is a new update out - http://seeds.dero.io/testnet/
We are asking everyone to please update to this version as soon as is reasonably possible