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

[Arux]

just built cpuminer binaries for windows (my cross compilation was a bit messy  ) i used mooo's code source (github.com/moneromooo/cpuminer-multi)

https://github.com/Arux-BTT/CPUMiner-Multi-cryptonight-light/releases/tag/04072015
[EDIT] https://github.com/Arux-BTT/CPUMiner-Multi-cryptonight-light/releases/tag/04082015


at the hard fork, this cpuminer will be able to send shares to a compatible pool with -a cryptonight-lite cryptonight-light arg. [edit]typo
example:

Code:

minerd -a cryptonight-light -o stratum+tcp://52.8.47.33:3333 -u WmsFoKjNnCvXkTtVx8zMR8B76rhh8aUs96NkQNVo4TFiBB15ftw2YCCar9utqavY49EbZzuKink5b2NexqgrhJEx2PzbGpU8M -p x -t 2

use non-AES-NI on old cpu (else you will get a message 'cpu not supported")
don't use it before #592000, you will get banned for invalid share.

i will switch my pool manually just before block ~592000 to be compatible with cryptonight-light. you must use stratum+tcp://52.8.47.33:3333 (stratum+tcp://aeonpool.arux.ma.gy:3333 don't work)

[1713923657]

1713923657

[1713923657]

1713923657

[1713923657]

1713923657

[MoneroMooo]

..
I think most pools will ban you if you send bad shares (which the cryptonite-lite shares would be at this point). I don't know what the policy is for how long that lasts.

Looking at the default config file for the pool's code, it's (I think) 10 minutes.  I gave it 20 and still no luck.  So I imagine Moo changed his.

But it's no biggie - Arux's pool needed a little love anyway. 

It's 15 minutes on my pool. Maybe something else was wrong. Usually it's a bad address passed to -u.
You don't get banned at first bad share by the way. It can happen normally for overheating GPUs. But I regularly see bursts of bad shares in the log and it's hard to say if it's a transient problem or some jerk trying to cheat their way into more aeon.

[smooth]

Donations

Received a nice 19000 donation from someone. Thank you!

That plus the seed nodes mining has brought the total to:

balance: 433909.660548863377, unlocked balance: 433899.852813272031

[cryptrol]

WARNING: Just saw this at Minergate



Do not mine at Minergate until they update their pool, otherwise you will be mining on an invalid chain.

Only mine on pools that you know will support the fork. Or solo mine with the latest AEON release.

[Arux]

update: https://github.com/Arux-BTT/CPUMiner-Multi-cryptonight-light/releases/tag/04082015

typo in the date 04072015 04082015
file name changed according to the correct date
added an other cpuminer (lucasjones) with cryptonight-lite support (from smooth's code github.com/iamsmooth/cpuminer-multi.git branch devel)

be aware of:
wolf-cpuminer need "-a cryptonight-light" argument to work after #592000
but lucasjones-cpuminer need "-a cryptonight-lite" !

[btcluka]

One simple question: my coins on Bittrex will be safe during next upgrade or I must send them to my desktop wallet now??

[smooth]

One simple question: my coins on Bittrex will be safe during next upgrade or I must send them to my desktop wallet now??

Bittrex is fine they are fully upgraded.

[nioc]

just built cpuminer binaries for windows (my cross compilation was a bit messy  ) i used mooo's code source (github.com/moneromooo/cpuminer-multi)

https://github.com/Arux-BTT/CPUMiner-Multi-cryptonight-light/releases/tag/04072015
[EDIT] https://github.com/Arux-BTT/CPUMiner-Multi-cryptonight-light/releases/tag/04082015


at the hard fork, this cpuminer will be able to send shares to a compatible pool with -a cryptonight-lite cryptonight-light arg. [edit]typo
example:

Code:

minerd -a cryptonight-light -o stratum+tcp://52.8.47.33:3333 -u WmsFoKjNnCvXkTtVx8zMR8B76rhh8aUs96NkQNVo4TFiBB15ftw2YCCar9utqavY49EbZzuKink5b2NexqgrhJEx2PzbGpU8M -p x -t 2

use non-AES-NI on old cpu (else you will get a message 'cpu not supported")
don't use it before #592000, you will get banned for invalid share.

i will switch my pool manually just before block ~592000 to be compatible with cryptonight-light. you must use stratum+tcp://52.8.47.33:3333 (stratum+tcp://aeonpool.arux.ma.gy:3333 don't work)

I downloaded the non_AES-NI Lucas Jones miner and see you included the batch file.  I checked it out and inadvertently started the miner.  How long am I banned for?

Also what is "pause" at the end of the batch file?

[Arux]

just built cpuminer binaries for windows (my cross compilation was a bit messy  ) i used mooo's code source (github.com/moneromooo/cpuminer-multi)

https://github.com/Arux-BTT/CPUMiner-Multi-cryptonight-light/releases/tag/04072015
[EDIT] https://github.com/Arux-BTT/CPUMiner-Multi-cryptonight-light/releases/tag/04082015


at the hard fork, this cpuminer will be able to send shares to a compatible pool with -a cryptonight-lite cryptonight-light arg. [edit]typo
example:

Code:

minerd -a cryptonight-light -o stratum+tcp://52.8.47.33:3333 -u WmsFoKjNnCvXkTtVx8zMR8B76rhh8aUs96NkQNVo4TFiBB15ftw2YCCar9utqavY49EbZzuKink5b2NexqgrhJEx2PzbGpU8M -p x -t 2

use non-AES-NI on old cpu (else you will get a message 'cpu not supported")
don't use it before #592000, you will get banned for invalid share.

i will switch my pool manually just before block ~592000 to be compatible with cryptonight-light. you must use stratum+tcp://52.8.47.33:3333 (stratum+tcp://aeonpool.arux.ma.gy:3333 don't work)

I downloaded the non_AES-NI Lucas Jones miner and see you included the batch file.  I checked it out and inadvertently started the miner.  How long am I banned for?

Also what is "pause" at the end of the batch file?

you aren't banned instantly, you can sent some invalid shares to test during several seconds easily.
a ban is 10 minutes.

pause is used to let open the windows. you can remove it, no matter

[MoneroMooo]

I just disabled banning on my pool, and will reenable it some time after the fork. This should let people switch a bit before or after without issues caused by temporary bad hashes.

Additionally, the difficulty will go up, so the pool settings will have to adapt too as it does (mostly starting diff I guess).

[smooth]

Additionally, the difficulty will go up, so the pool settings will have to adapt too as it does (mostly starting diff I guess).

Yes the difficulty on the coin will instantly go up by a factor of 8 IIRC. I have no idea how long the pool software will take to adapt to that.

[Arux]

http://52.8.47.33:8080 switched on on POW algo.

warning: miner Wm..............................................................D2w2qy, you must switch you miner! your shares are not counted

[smooth]

Hard fork

Everything is working properly. There are a significant number of nodes that are not updated and get repeatedly dropped, which generates logs messages in aeond.log. Take care that this file does not grow too large and fill up your disk.

Since these are error messages, there is currently no log-level setting to turn them off.  If the number of bad nodes doesn't decrease soon I will put out a patch to suppress these messages.

[Arux]

my pool seems not OK for now.
i'm investigating

[edit] false alarm, shares are counted

[pa]

Hard fork

Everything is working properly. There are a significant number of nodes that are not updated and get repeatedly dropped, which generates logs messages in aeond.log. Take care that this file does not grow too large and fill up your disk.

Since these are error messages, there is currently no log-level setting to turn them off.  If the number of bad nodes doesn't decrease soon I will put out a patch to suppress these messages.

Are the people running the bad nodes also seeing error messages? If they aren't reading this thread, do they know that the hard fork occurred?

[smooth]

Hard fork

Everything is working properly. There are a significant number of nodes that are not updated and get repeatedly dropped, which generates logs messages in aeond.log. Take care that this file does not grow too large and fill up your disk.

Since these are error messages, there is currently no log-level setting to turn them off.  If the number of bad nodes doesn't decrease soon I will put out a patch to suppress these messages.

Are the people running the bad nodes also seeing error messages? If they aren't reading this thread, do they know that the hard fork occurred?

Yes they will get big red error messages.

[smooth]

Reminder that if you are either CPU or GPU mining with the new algorithm you will probably want to retune the settings to maximize your performance.

The new algorithm uses 1 MB per thread instead of 2 MB so if your CPU has 3 MB of cache (a common number for mainstream i5 CPUs) you can switch from 1 thread to 3 threads! Of course hardware and performance varies, so try your own and see.

[dnaleor]

I totally forgot to answer your message, was too busy yesterday 
I've send you a PM now

Yes you do need 64-bit Windows for now, so if you only have 32 bit or have <4-6 GB of RAM you better just get someone to help you move the coins.
Download the Windows wallet (.ZIP file) using the link in the first post on this thread where it says "current release windows". Extract it. Download the blockchain bootstrap using the link in the first post of this thread. I don't remember where it goes on your computer, but you can find that on the last few pages.
Open a terminal window. Launch the node (anond.exe).  Wait for it to finish syncing  (shouldn't take too long -- but if it starts from block 0 and takes forever then you put the bootstrap in the wrong place). Launch simplewallet.exe --generate-new-wallet. It will give you a bunch of seed words, those are your backup, so write those down on a piece of paper (keep in a safe place). It will also give you an address. That's the address you give to Poloniex.

If you have any more questions, please post them. There are many helpful people on this thread.

Thanks again, I might have to download later from Polo with someones help. I'm glad that this will probably be possible after the fork. But I'll keep trying. My girlfriend is coming over and I'm sure if I tell he rwhat i'm trying to do she will say...crypto..what? huh? What is it?...come to dinner

I'll pop back later
Great community here too. thanks

[smooth]

I was able to identify a half dozen bad nodes which when blocked cause virtually all of the errors to stop. I don't want to post IP addresses, but if you are having trouble with your log file getting too big and you are able to block IPs in a firewall, PM me and I'll send you the list.

[btcluka]

i5 cpu @3800Mhz on Wolf miner (-t 4) give ~480h/s.
Lucasjones miner don't work...