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

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

What about GPU miner for Atlantis ?

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

2million premine is very high. Is there any bounty\airdrop planned from this ?

No qt wallets ? Whats the block reward ?

You're welcome, but you might want to put a quote link back to my post so some overzealous plagiarism hunter like me doesn't report it to the mods.  

Now, my comments on the testnet after about a day of messing around with it (posting here since the Slack channel is an unending stream of consciousness which I find incredibly aggravating; hence why I have avoided using it up until yesterday).

1. The daemon could be a bit more explicit about when it has synced with the network, especially since the numbers it displays otherwise suggest it is perpetually behind. Also, be more explicit with what numbers go green, and what the other colors mean (red and yellow, from what I've noticed).

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). Might I suggest that block times be lengthened back to 20 or even 30 seconds so that a couple seconds of mismatch in system clocks doesn't cause such major problems.

3. As for mining, I only managed to get up to around 140H/s with 8 threads on a Ryzen 5 1600 (16MB L3 cache, 16GB system RAM, no overclock). In contrast, this same system does 450-475H/s on CryptoNight-v7 (ie - Monero). So, don't be alarmed if your hashrate seems pathetic. It is, but that seems to be par for the course.

Anyone can come try the testnet and we will let the stat site software out soon for others to add nodes

Good news. Anyone can start testing a product or just a project team? It would be interesting.

DERO Atlantis Testnet live stats in action.
  With CryptoNote Privacy protocol and more than 50 TPS in action.
http://stats.atlantis.dero.live/

It's really nice to know that Dero's goal is to create a unique state of the art blockchain technology with enhanced reliability, privacy, security, usability, and portability by bringing together some of the best proven technologies. With this alone, I think it could be very big help to us.

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

Testnet downloads: http://seeds.dero.io/testnet/
Testnet stat site: http://stats.atlantis.dero.live/
Testnet explorer: 212.8.242.60:8081


Quick Testnet How-To For Windows

1.Download the new wallet/daemon from: http://seeds.dero.io/testnet/ - choose the windows_amd64 binary - and unzip the newly downloaded files to a new folder.

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

3. Right click on the derod executable and set to "Run as Administrator" in the compatibility options.

4. Open a command prompt terminal

5. Find the folder where you extracted your testnet files to and get the location (ex: C:\Users\robot\Desktop\dero_windows_amd64\dero_windows_amd64\)

6.To begin syncing with the testnet, use the terminal and run the command: derod-windows-amd64.exe --testnet (ex: C:\Users\robot\Desktop\dero_windows_amd64\dero_windows_amd64\./derod-windows-amd64 --testnet)

7. Find your testnet folder, delete the database file you see there, and extract your database file you downloaded earlier to this folder. After your testnet daemon opens it will create a new testnet folder for you that is (on Windows) usually contained in your user data.

8. While the daemon is syncing you next need to generate a NEW wallet address specifically for the testnet - any coins mined on the testnet will not be valid once the mainnet goes live (ie - they don't exist on the mainnet). Later on when the official Atlantis wallet comes out you'll want to use the "restore from seed" option to import the balance from your existing DERO wallet address to the new Atlantis wallet.

9. Open a new and separate command prompt terminal

10. To open the wallet in testnet mode use the following command in the cmd prompt terminal:  dero-wallet-cli-windows-amd64.exe --testnet (ex:C:\Users\robot\Desktop\dero_windows_amd64\dero_windows_amd64\./derod-wallet-cli-windows-amd64 --testnet)

11.a)Then select option 2 from the menu - create new wallet
b) Enter a name for the testnet wallet
c) Enter a password for the wallet twice
d) Save the recovery seed (this is a testnet seed and won't work on the mainnet)
e) Display the wallet address - save address

12.Once the daemon has finished syncing enter the following command string at the daemon prompt to begin mining on the testnet:
start_mining <# of threads>  (Do not include < >)
Replace with your address and <# of threads> to a maximum of the amount of L3 cache divided by 2; e.g. - a Ryzen 5 1600 has 16MB L3 cache so max number of threads is 8 (but to preserve desktop interactivity set to 1 or 2 less threads than maximum).


(Beginner tip: You can tell if your daemon is in sync when the numbers go green)

I added/edited MagicSmoker's reply (thank you very much for that Magic!)

Hi guys, sorry to ask this perhaps is so simple for you, but I can not undestand Serena and MagicSmoker instructions to mine in testenet. I alredy download the daemon, sync and create the wallet, but I do not know how to mine.

Please could you be more specific for begginers, step by step and more simple perhaps with more details and examples.

And by the way, I know I am  brand new here, but I have been watching this coin since the begining, and as an external member I totaly support Serena´s work and Capdero´s work, despite some commets of misplaced members of the community, continue with your good work.

Not only that, I made a mistake.  It is a dual processor system, the L3 cache is per processor, not total, so it is 55 x 2 = 110 MB, i.e. 55 threads by the 2MB rule which is larger than the total number of threads available so 44.

I know it isn't much, but sometimes our glorious Captain forgets about the skill level of us mere mortals when it comes to this sort of thing... 


I've lost sync twice in less than 12 hours so I already resorted to changing the timeserver to pool.ntp.org as suggested on the Slack channel, but I really don't think this an acceptable solution for the general public. Yes, it is fairly easy to make this change, but it also the kind of thing that M$ could change back at any time in one of their infamous forced updates (you know, the kind you can't block no matter what services you stop). For example, the 1803 update now makes Bing on the Edge browser the all-but-unchangeable means of searching via the desktop; I was none too pleased about that, as I despise both Bing and Edge.



Yeah, I fully expect to have to tweak this, but until we get an actual explanation of how the new PoW algo works I fell back on the usual recommendation for straight CryptoNight, as that seems to be working for /most/ of the people on Slack.

That said, your CPU is distinctly unusual and so what works/doesn't work for you might not apply to those of us with rather more pedestrian processors.

I'm not sure this is good advice for all cases.  I have a 44 core machine with 55 MB of L3 cache.  Mining with 27 threads (55 / 2) I get about 62% of the hashrate I get by mining with 44 threads.  (I have turned hyperthreading off, so have not tried with 88 threads, but I doubt that would see better performance, and it could well be worse.)

Thanks MagicSmoker for the guide, I think people will find that very useful.

Note that the Windows way of syncing to a timeserver could cause problems.  If you find that even after checking to make sure that Windows is set to update the clock, and has (it claims) updated the clock, you still get complaints about the clock being out of sync from the daemon, come back here and we will try to solve that problem.

I am really exited about dero atlantis, had to register to say that

Testnet is working fine and even found a block!

DERO: 97140/97526 [97140/97526] P 11 TXp 0 NW 3.2 KH/s > TESTNET>> start_mining dEToixWwr2iR76Muf2rR3eAjmC65L6Bb25vvgGQqhEtfZtnDBugtJmEdYGcCUbXLa4B4r1gSTRYMTf2 GYqU8kPna4QpeV8ZrPm 1
DERO: 97140/97526 [97140/97526] P 11 TXp 0 NW 3.2 KH/s > TESTNET>>
INFO[0428] Block 9ffe6626a8e9c91529a8e7ce0687adbaafd3f90fcc25559ed6b6876c9cbcdabe successfully accepted
INFO[0733] Chain Height 97201                            blid=9f87b212c408543b39116533bd832b68c6f013e52be6ac3d05f112b7f524c94e com=BLKCHAIN
INFO[2632] Chain Height 97401                            blid=75d57c3ce430a9349074e64009aae5d39090ca4e222bbf6930cdcb6d7f3d1b33 com=BLKCHAIN

Quick Testnet How-To For Windows

Download the new wallet/daemon from: http://seeds.dero.io/testnet/ - choose the windows_amd64 binary - and unzip to a new folder.

Next create a new subfolder called "testnet" in the above folder.

Download the database.db snapshot from http://seeds.dero.io/testnet/blockchain/derod_database.db.zip - and unzip it to the testnet folder.

Right click on the derod executable and set to "Run as Administrator" in the compatibility options.

Run the command:
derod-windows-amd64.exe --testnet
to begin syncing with the testnet.

While the daemon is syncing you next need to generate a NEW wallet address specifically for the testnet - any coins mined on the testnet will not be valid once the mainnet goes live (ie - they aren't worth a damn thing). Later on when the official Atlantis wallet comes out [I think!] you'll want to use the "restore from seed" option to import the balance from your existing DERO wallet address to the new Atlantis wallet.

Run the command:
dero-wallet-cli-windows-amd64.exe --testnet
Then select option 2 from the menu - create new wallet
Enter a name for the testnet wallet
Enter a password for the wallet twice
Save the recovery seed
Display the wallet address - save address

Once the daemon has finished syncing enter the following command string at the daemon prompt to begin mining on the testnet:
start_mining <# of threads>
Replace with your address and <# of threads> to a maximum of the amount of L3 cache divided by 2; e.g. - a Ryzen 5 1600 has 16MB L3 cache so max number of threads is 8 (but to preserve desktop interactivity set to 1 or 2 less threads than maximum).

Et voilla, you are now mining completely worthless coins for the good of the DERO network!

EDIT - forgot to mention that Atlantis is exceptionally sensitive to time-sync errors; the easiest way to fix that should the daemon complain your clock is out of whack is to open up the time and date settings, uncheck "set time automatically" then re-check it. That will force an update with the M$ timeserver. Or you can be a masochist and attempt to change the timeserver to pool.ntp.org; good luck with that.

Is this classic cryptonight that is ASIC mineable?