Topic: [ANN] DERO: DAG + Cryptonote + Bulletproofs + SSL + POW + Smart Contracts - page 57. (Read 123199 times)
June 11, 2018, 09:16:24 AM
If its converted, does that mean there is 2 dero chains then, rather than the single. SO in essence, 2 Dero coins ?
June 11, 2018, 09:12:31 AM
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 ?
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
June 11, 2018, 08:39:01 AM
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 ?
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 ?
June 10, 2018, 05:48:45 PM
Quick Testnet How-To For Ubuntu Linux
[/quote]
Thanks bro, I am going to try it. Please someone give merit to him.
June 10, 2018, 12:32:40 PM
Hello, can someone please create a "Quick Testnet How-To For Ubuntu Linux" like the one for windows
June 09, 2018, 04:13:04 PM
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
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
June 09, 2018, 03:40:54 PM
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
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
June 09, 2018, 02:32:15 PM
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
Thanks for answering
June 09, 2018, 05:25:45 AM
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.
June 09, 2018, 05:19:02 AM
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
June 09, 2018, 05:07:22 AM
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.
June 08, 2018, 09:55:23 PM
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
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
June 08, 2018, 09:07:11 PM
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
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
June 08, 2018, 08:57:11 PM
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
We are asking everyone to please update to this version as soon as is reasonably possible
June 08, 2018, 11:00:52 AM
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
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
June 08, 2018, 10:24:11 AM
Hey guys! Very interesting project based on cryptonote. Smart contracts and fast transactions speed are definitely a must ! Can't wait to see more.
June 08, 2018, 10:20:04 AM
@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!)
June 08, 2018, 10:00:09 AM
Well kudos to Capt - a nicer chap than me 
June 08, 2018, 09:56:24 AM
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.
June 08, 2018, 09:56:02 AM
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...
Jump to: