Pages:
Author

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

jr. member
Activity: 111
Merit: 5
--nemo me impune lacessit--
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  Smiley

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


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.  Smiley Smiley
newbie
Activity: 45
Merit: 0
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  Smiley

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

jr. member
Activity: 111
Merit: 5
--nemo me impune lacessit--
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.
 Huh

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  Smiley
newbie
Activity: 45
Merit: 0
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.
 Huh

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

member
Activity: 92
Merit: 12
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)
member
Activity: 308
Merit: 33
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.
newbie
Activity: 45
Merit: 0
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!

newbie
Activity: 21
Merit: 0
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
full member
Activity: 420
Merit: 184
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.

newbie
Activity: 21
Merit: 0
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
member
Activity: 224
Merit: 11

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
newbie
Activity: 21
Merit: 0

[/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?
newbie
Activity: 45
Merit: 0

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.

jr. member
Activity: 111
Merit: 1
Hi, DEV team, i have an issue in testnet.

Eventhought I alredy sync, and also sync time of windows correctly, this message appear in tesnet while mining

Your system time deviation is more than 2 secs (1.261497317s).
You may experience chain sync issues and/or other side-effects.
If you are mining, your blocks may get rejected.
Please sync your system using NTP software (default availble in all OS).
 eg. ntpdate pool.ntp.org  (for linux/unix)
INFO[3565] Block 808b511c7245daa938e127b825b1fef72f0cfb7b6f55ad941e27b37338c2b288 successfully accepted


Is it normal?



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.
newbie
Activity: 21
Merit: 0
Hi, DEV team, i have an issue in testnet.

Eventhought I alredy sync, and also sync time of windows correctly, this message appear in tesnet while mining

Your system time deviation is more than 2 secs (1.261497317s).
You may experience chain sync issues and/or other side-effects.
If you are mining, your blocks may get rejected.
Please sync your system using NTP software (default availble in all OS).
 eg. ntpdate pool.ntp.org  (for linux/unix)
INFO[3565] Block 808b511c7245daa938e127b825b1fef72f0cfb7b6f55ad941e27b37338c2b288 successfully accepted


Is it normal?

member
Activity: 308
Merit: 33
 
Work in progress http://stats.atlantis.dero.live/
Learn more about blockchain and DERODAG live.

Thanks Serena, Mojo, Dank, Zoz and many more for their efforts and support.



member
Activity: 224
Merit: 11
Hello everyone!

We've added a graph showing the DERODAG on http://stats.atlantis.dero.live/ (thanks ZoZ and Capt!) If you check the site out you can watch the DAG live in action!
full member
Activity: 420
Merit: 184
2. The short block time of ~10 seconds has one major downside: very little tolerance of variation in the system time. Currently Atlantis refuses to sync if the system time is off by +/-1 second, which is understandable given the block time of 10 seconds, but it is not terribly practical or robust in the real world, particularly with Windows computers, which the vast majority of people use. The suggested solution is to change the timeserver to pool.ntp.org but this isn't really the source of the problem, rather, it is that Windows only updates the time via the internet every 12 hours by default, and my daemon starts complaining about the time being off after 3-6 hours... I'm definitely not getting up in the middle of the night to manually update my clock and so the only other alternative is to use a paid-for 3rd party timeserver app (as suggested by @fellestreum).
Try Ridiculously Simple NTP Client, rsNTP download, it syncs every 30 min.
There is a bunch of other third party clients. Or you can potentially change the [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time\Config\UpdateInterval] value in clock ticks on Windows 7 or [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient\SpecialPollInterval] value in seconds on Windows 10. I have not tried the registry keys, you can read up on these if you want.
Windows 10 NTP
Windows 7 NTP

Hmm, yes, a poor choice of words on my part to say the "only other alternative" is a paid-for 3rd party timeserver app. Even though I wasn't aware of the other solutions at the time I wrote that post, I should know by now there is always more than one way to skin the proverbial cat when it comes to Windows.

However, I haven't changed my opinion that the current iteration of Atlantis is simply too sensitive to system time mismatches. Unfortunately, with a block time of 9-11 seconds I don't see any way around that without opening up the PoW algo to the sort of timestamp spoofing attacks perpetrated against the Verge network.

newbie
Activity: 129
Merit: 0
I see for its very nice features for this project. With the extraordinary security of making this an extraordinary going forward. Any plans for the future? Promotion, roadmap? 2 million pre-mine is a bitcoins too much, do not you think?
full member
Activity: 224
Merit: 100
2million premine is very high. Is there any bounty\airdrop planned from this ?


Quote
 
The first 1 million Dero is block height locked for 4 years straight.
The second 0.5 million Dero is reserved for various activities such as marketing, exchange listings, and other project related costs. This Dero gets unlocked in the follow amounts: 10%, 20%, 30%, 40% each year consecutively.
The third 0.5 million Dero is reserved for research & development. This Dero gets unlocked in the follow amounts: 20%, 20%, 30%, 30% each year consecutively.


big rewards for Dev team, if they do  hard work to make Dero success

Maybe they will do an airdrop, I dont know.. but its really for dev work, as getting funding these days is either scammy via ico or through hard work after growing their coin
Its better through this way when the team is able to work and show results constantly...
Pages:
Jump to: