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

[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

[1714018670]

1714018670

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

[acru]

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

Can we use the same databse or is a new one

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

Can we use the same databse or is a new one

No new database required - testnet chain height at the time of this post is 13895

[MagicSmoker]

No new database required - testnet chain height at the time of this post is 13895

I left the daemon running all night and this morning it was once again complaining about system time deviation and it never did get the blockchain fully synced (yellow numbers). So I manually resynced the time, updated to 0.1.1 and this new version definitely runs slower and is falling more and more behind trying to sync; i.e. - it started off around 500 blocks behind and after 15 minutes of running it is now 650 blocks behind.

As of now it looks like I won't be able to mine DERO at all with Atlantis because I either can't get the blockchain to sync or else my system time gets too far out of whack way before Windows bothers to check a timeserver again (which is every 12 hours by default). I can (presumably) fix the latter issue by running a 3rd party timeserver, but there isn't anything I can do about the daemon syncing slower than new blocks are generated.

[Mojo_LB]

I left the daemon running all night and this morning it was once again complaining about system time deviation and it never did get the blockchain fully synced (yellow numbers). So I manually resynced the time, updated to 0.1.1 and this new version definitely runs slower and is falling more and more behind trying to sync; i.e. - it started off around 500 blocks behind and after 15 minutes of running it is now 650 blocks behind.

As of now it looks like I won't be able to mine DERO at all with Atlantis because I either can't get the blockchain to sync or else my system time gets too far out of whack way before Windows bothers to check a timeserver again (which is every 12 hours by default). I can (presumably) fix the latter issue by running a 3rd party timeserver, but there isn't anything I can do about the daemon syncing slower than new blocks are generated.

Hi,

Apparently from your various reports that there is an issue with your computer's clock?

We were able to successfully sync the Atlantis testnet update very low-end hardware with no issues at all. Could you please try to run it on a different system? (I previously understood you have several ones)

If you are still facing issues, please reach out in Slack or Discord, we are active there and would love to assist 

[MagicSmoker]

I left the daemon running all night and this morning it was once again complaining about system time deviation and it never did get the blockchain fully synced (yellow numbers). So I manually resynced the time, updated to 0.1.1 and this new version definitely runs slower and is falling more and more behind trying to sync; i.e. - it started off around 500 blocks behind and after 15 minutes of running it is now 650 blocks behind.

As of now it looks like I won't be able to mine DERO at all with Atlantis because I either can't get the blockchain to sync or else my system time gets too far out of whack way before Windows bothers to check a timeserver again (which is every 12 hours by default). I can (presumably) fix the latter issue by running a 3rd party timeserver, but there isn't anything I can do about the daemon syncing slower than new blocks are generated.

Hi,

Apparently from your various reports that there is an issue with your computer's clock?

We were able to successfully sync the Atlantis testnet update very low-end hardware with no issues at all. Could you please try to run it on a different system? (I previously understood you have several ones)

If you are still facing issues, please reach out in Slack or Discord, we are active there and would love to assist  

That is precisely what I am doing now - running a fresh install of 0.1.1 on a different system. So far it is complaining about system time deviation despite 3 manual resyncs.

I know that Slack is active but the stream of consciousness format gives me a headache and I wanted to make sure that people who are only here (which included me up until a few days ago) are in the loop.


UPDATE -well, I also copied over the blockchain db file to speed up the syncing then after taking the dog for a walk (~30m) I came back to find it was all caught up... Go figure.

[acru]

Hi guys, can someone please help me with this question. Which version of the daemon I should download from http://seeds.dero.io/testnet/ to run it on UBUNTU LINUX. I have some old PC and I want to use to mine DERO, but I am not used to linux.

Thanks for answering
 

[valgandar]

Hi guys, can someone please help me with this question. Which version of the daemon I should download from http://seeds.dero.io/testnet/ to run it on UBUNTU LINUX. I have some old PC and I want to use to mine DERO, but I am not used to linux.

Thanks for answering
 

It will depend of your CPU (x86 or x64 architecture).

dero_linux_386.tar.gz       -> for x86 architecture
dero_linux_amd64.tar.gz  -> for x64 architecture

[acru]

Hi guys, can someone please help me with this question. Which version of the daemon I should download from http://seeds.dero.io/testnet/ to run it on UBUNTU LINUX. I have some old PC and I want to use to mine DERO, but I am not used to linux.

Thanks for answering
 

It will depend of your CPU (x86 or x64 architecture).

dero_linux_386.tar.gz       -> for x86 architecture
dero_linux_amd64.tar.gz  -> for x64 architecture

thanks a lot

[acru]

Hello, can someone please create a "Quick Testnet How-To For Ubuntu Linux" like the one for windows

[acru]

Quick Testnet How-To For Ubuntu Linux
[/quote]

Thanks bro, I am going to try it. Please someone give merit to him.

[sexontoast]

These 2 questions may have already been answered so sorry in advance

What happens to the old Dero ? separate block chain ? coins swapped to new coins ?

Is this still a Cryptonote based algorithm for GPU mining or ?

[Dr_Voidberg]

These 2 questions may have already been answered so sorry in advance

What happens to the old Dero ? separate block chain ? coins swapped to new coins ?

Is this still a Cryptonote based algorithm for GPU mining or ?

1. Old chain will be converted to new DAG, you do not have to do anything
2. No info about GPU mining algo released

[sexontoast]

If its converted, does that mean there is 2 dero chains then, rather than the single. SO in essence, 2 Dero coins ?

[MagicSmoker]

If its converted, does that mean there is 2 dero chains then, rather than the single. SO in essence, 2 Dero coins ?

No, it means the old PoW algo will stop working. The coins from the old chain can be converted to the new chain, but once the algo changes no new blocks will be added to the old chain.

In other words, existing mining software and ASICs will stop working.

My understanding - though this has not been confirmed or denied by the DERO team - is that only the wallet daemon will be usable to mine on the new algo at first.

[Miguelgreen]

Hello people good night. From my understading,
It seems that the mining Will ONLY be from
Cpu now. I AM correct or some rx570 Will work?
I love This project, but unfortenely i am really bad in
Computer stuuf. Really really bad.
Sorry for all caps and my bad English

[MagicSmoker]

Hello people good night. From my understading,
It seems that the mining Will ONLY be from
Cpu now. I AM correct or some rx570 Will work?
I love This project, but unfortenely i am really bad in
Computer stuuf. Really really bad.
Sorry for all caps and my bad English

You need to have some knowledge of "computer stuff" to mine crypto; no way around it, I'm afraid.

At least in the very beginning DERO Atlantis will only be mineable with a CPU using the official wallet daemon. I wrote a post a couple pages back that people have been brazenly plagiarizing on how to mine with the daemon in Windows so go read that... several times if you have to. It's really not that difficult.

[acru]

No, it means the old PoW algo will stop working. The coins from the old chain can be converted to the new chain, but once the algo changes no new blocks will be added to the old chain.

In other words, existing mining software and ASICs will stop working.

My understanding - though this has not been confirmed or denied by the DERO team - is that only the wallet daemon will be usable to mine on the new algo at first.


[/quote]

Lets hope this is correct, for this was the original idea of sathosy and this is real desentralization. On the other hand, as DERO is written in GO, DERO will have no problem to manage the load in only CPU.

Lets hope this came true

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

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

Actually I think it is better to keep the filenames static with these alpha builds that are updated often.

It makes it easier to update, when you know a new release is out, you just run the same command again

wget http://seeds.dero.io/testnet/dero_linux_amd64.tar.gz

(or whatever works for your version)  without needing to check the new filename and change the command possibly across multiple systems or in a script etc