[ANN] AEON: Scalable, private, mobile-friendly cryptocurrency

[stoffu]

Call for participation: Testing difficulty reset on stagenet (fork scheduled TOMORROW)
https://www.reddit.com/r/Aeon/comments/8lenj0/call_for_participation_testing_difficulty_reset/

[bbc.reporter]

@stoffu. I will do if I have some time. I am doing some renovations in my apartment kitchen hehehe.

In any case, has Bittrex already replied if they will support the hardfork? I reckon that they have no choice but to support it right?

[stoffu]

@stoffu. I will do if I have some time. I am doing some renovations in my apartment kitchen hehehe.

In any case, has Bittrex already replied if they will support the hardfork? I reckon that they have no choice but to support it right?

I've never contacted Bittrex. I remember smooth or katiecharm told them that there'll be an update soon although the official release is yet to be announced.

[Elder III]

Call for participation: Testing difficulty reset on stagenet (fork scheduled TOMORROW)
https://www.reddit.com/r/Aeon/comments/8lenj0/call_for_participation_testing_difficulty_reset/

I'd love to help, but I don't have the knowledge or experience to do so .

[mattcode]

Call for participation: Testing difficulty reset on stagenet (fork scheduled TOMORROW)
https://www.reddit.com/r/Aeon/comments/8lenj0/call_for_participation_testing_difficulty_reset/

Will it work (/not work) like the Bitcoin Cash EDA? Or is it just a one-off thing straight after the fork.

[stoffu]

Call for participation: Testing difficulty reset on stagenet (fork scheduled TOMORROW)
https://www.reddit.com/r/Aeon/comments/8lenj0/call_for_participation_testing_difficulty_reset/

Will it work (/not work) like the Bitcoin Cash EDA? Or is it just a one-off thing straight after the fork.

Though I don’t know much about Bitcoin Cash’s EDA, most likely ours is different as it is simple resetting of difficulty to some predefined 'reasonable' value and ignoring all the difficulties prior to the fork. It’s like as if a new coin is launched with some predefined difficulty greater than 1.

[smooth]

Call for participation: Testing difficulty reset on stagenet (fork scheduled TOMORROW)
https://www.reddit.com/r/Aeon/comments/8lenj0/call_for_participation_testing_difficulty_reset/

Will it work (/not work) like the Bitcoin Cash EDA? Or is it just a one-off thing straight after the fork.

EDA (or any algorithm based on the consensus difficulty model) still requires at least finding some blocks. That only really makes sense if you don't expect a BIG drop, or if you have a significant mining infrastructure that isn't motivated by mining profits. Otherwise, if the difficulty is too high, most/all miners will leave and you will never get blocks (or not for an unacceptably long time).

In this case the reset is based on the recognition that carrying over difficulty from a different algorithm doesn't make sense at all. For example, imagine switching from SHA256 to cryptonight. The difficulty would have to drop by orders of magnitude to even find any blocks.

This case isn't quite as extreme, but switching from an ASIC algorithm to a non-ASIC variant is still quite extreme. In any case it is conceptually the same that 'difficulty' only makes sense relative to a particular algorithm and carrying over does not make sense. We will simply reset the difficulty to a reasonable value slightly below where it seems like it should be based on profitability, but not so low as to allow mining a large number of blocks at low difficulty. My current thinking is around 1 billion. If that is wrong, it will still adjust pretty fast.

[mattcode]

Thanks, that's what I wanted to know . I was just worried because the Bitcoin Cash EDA implementation allowed it to be gamed by miners which made the block times fly all over the place.

[smooth]

New release 0.12.0.0 (Sophia)

This is a mandatory software upgrade due to the rebase of the Aeon codebase to the latest master branch of Monero. More info in the release notes at the link below.

*** The mainnet fork date is scheduled on June 3rd, 2018 (height 963500) ***

CLI: https://github.com/aeonix/aeon/releases/tag/v0.12.0.0
GUI: https://github.com/aeonix/aeon-gui/releases/tag/v0.12.0.0-aeon

Note: Since the aeon repo has been completely replaced (the old one is no archived as aeon-legacy), if you are using git, you should do a new clone, not pull.

Note 2: A preliminary testing build was accidentally uploaded instead of the Windows GUI release binary, which made the hashes mismatch. This has now been corrected, and the hashes match. The file was not corrupted or compromised, it just wasn't the final release build.

[Elder III]

Thanks for the update Smooth, that is most excellent news indeed.  I am looking forward to the fork and will try to have a few CPUs ready to mine when it the time comes around.

[sammy007]

Updated solo stuff here https://github.com/sammy007/monero-stratum/tree/aeon must work with new fork, nfi actually, somebody have to test the mining.

[JCS-CCT]

Baikal is releasing a new 480KH/s cryptonight-light miner.  Is there going to be a PoW algorithm change?
https://www.baikalminer.com/product16.php

[farfiman]

Baikal is releasing a new 480KH/s cryptonight-light miner.  Is there going to be a PoW algorithm change?
https://www.baikalminer.com/product16.php

June 3rd.

[Elder III]

Baikal is releasing a new 480KH/s cryptonight-light miner.  Is there going to be a PoW algorithm change?
https://www.baikalminer.com/product16.php

The post from higher up on this page (by Smooth) is about the upcoming fork to nullify these asics.  There are already asics on the market that are mining AEON now, so Baikal's new unit doesn't really make any difference at this point.

[bbc.reporter]

@smooth. The release notes does not mention LMDB but I assume that it is already included in this upgrade? I would like to run another node on an old computer with 2GB of RAM and locate it at home.

[jwinterm]

@smooth. The release notes does not mention LMDB but I assume that it is already included in this upgrade? I would like to run another node on an old computer with 2GB of RAM and locate it at home.

It's definitely included. You might need slightly more than 2GB of ram to compile, but swap will suffice.

[glandulaHewq]

This is a great project, the price of this coin is easily uplifted, so don't sell it cheaply, waiting for a huge leap in the price of Aeon.

[bbc.reporter]

@smooth. The release notes does not mention LMDB but I assume that it is already included in this upgrade? I would like to run another node on an old computer with 2GB of RAM and locate it at home.

It's definitely included. You might need slightly more than 2GB of ram to compile, but swap will suffice.

It was mentioned but under how to upgrade the daemon, at the bottom of the release notes hehe. In any case I can always take ram from another computer if needed.

@smooth. There are low hashrate cryptocoins that were attacked this year and it is becoming a trend among hackers. Monacoin, Verge, Electroneum and bitcoin gold all attacked. We might be next.

Are you open to the idea of merge mining with Monero for protection?

[sammy007]

Merge mining is a bullshit, second coin worth nothing, a bonus. Scammy pools like minergate will claim all shit and dump on exchanges, their customers are retards and whole business is conversion of idiotism to fortune. Learned from VTC + Monocle, second coin goes to zero.

Only price can save from 51 for now, so buy as much as you can afford to multiply by 10 to attract more GPU miners /s.

[moviebcf]

Hello,
Since block 961340, my internal blockchain is no longer updated.
I am using the current cmd-version 0.12.0.0 and have re-downloaded the blockchain with the current version

Below the status message:

2018-05-30 14:17:33.663 [P2P3]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:310     [176.9.117.76:11180 OUT] Sync data returned a new top block candidate: 961340 -> 962048 [Your node is 708 blocks (1 days) behind]
SYNCHRONIZATION started
.....
.....

2018-05-30 14:24:26.283 [P2P3]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:310     [24.179.130.232:11180 OUT] Sync data returned a new top block candidate: 961340 -> 962049 [Your node is 709 blocks (1 days) behind]
SYNCHRONIZATION started

and so on....

I have done this also with a backup and it stops syncing with block 961340. Is there a known problem?