Author

Topic: [ANN] AEON [2019-09-27: Upgrade to version 0.13.0.0 ASAP HF@1146200 Oct 25] - page 243. (Read 625666 times)

legendary
Activity: 1624
Merit: 1008

Minimum Payment Threshold: 0.050 AEON

The technical aspects I know little about.  It just seemed to me that the threshold is rather small and dusty.

Yes I agree it would be better to set it higher especially with the value and difficulty as low as it is.

0.05 is something like 0.0000025 BTC

I will be bumping up the default transaction fees to a more realistic level and improving handling of transaction fees generally once everything is stable after the hard fork
updated
Minimum Payment Threshold: 0.050 --> 0.500
Denomination Unit: 0.001 --> 0.010
Transfer Fee : 0.0010 --> 0.000001 (0.0000 will be displayed)

On the payments page of your pool it is listed as

Minimum Payment Threshold: 0.100 AEON
Denomination Unit: 0.100 AEON
legendary
Activity: 1276
Merit: 1001
Where can i find the cryptonight lite miner source code to able to mine on linux?

Thank you

Wolf's (AES-NI): https://github.com/moneromooo/cpuminer-multi
Tsiv's (GPU, nvidia): https://github.com/moneromooo/ccminer-cryptonight
Lucas Jones' (CPUs without AES-NI): https://github.com/iamsmooth/cpuminer-multi
sr. member
Activity: 240
Merit: 250
Where can i find the cryptonight lite miner source code to able to mine on linux?

Thank you
legendary
Activity: 1624
Merit: 1008
I am useing -a cryptonight-lite

Hmm. Maybe there is a bug in it. Did you try Wolfs?


No because of Arux's posting...............

use non-AES-NI on old cpu (else you will get a message 'cpu not supported")


That be LucasJones AFAIK.  Wolf's non AES-NI never worked for me in the past.


Back to work I go,  ohhhh

my apologies, LucasJones binary don't work as expected. there is an error but i still don't know wich one.

Wolf binaries are OK.
AES-NI optimization for recent hardware and non AES-NI for older.


Thank you Arux.  I am using Wolf's non AES-NI and it is working.
legendary
Activity: 1276
Merit: 1001
exciter0: update your daemon (if you can compile it, I'm not sure if there's a binary with the latest source). I've just checked the source and the diff change was done only recently.

Arux: in pages/home.html, find the line:

updateText('networkHashrate', getReadableHashRateString(lastStats.network.difficulty / 60) + '/sec')

and replace 60 with 240 (new block target).
hero member
Activity: 500
Merit: 500
How about your pools reported hashrate?  It looks a bit weird... 
Code:
Hash Rate: 201.57 KH/sec

My daemon shows over 800Kh/s
Code:
diff
2015-Aug-04 13:28:47.565403 BH: 592102, DIFF: 49228419, HR: 820473 H/s

for me, it's the opposite
my pool shows 808kh/s and my daemon 202kh/s, there is a factor 4 between them.
member
Activity: 115
Merit: 10
How about your pools reported hashrate?  It looks a bit weird... 
Code:
Hash Rate: 201.57 KH/sec

My daemon shows over 800Kh/s
Code:
diff
2015-Aug-04 13:28:47.565403 BH: 592102, DIFF: 49228419, HR: 820473 H/s

2015-Aug-04 21:06:42.603225 [P2P9][74.91.30.186:11180 OUT]Sync data returned unknown top block: 783 -> 592063 [591280 blocks behind]
SYNCHRONIZATION started


aeon 0.9.0.0 win64

Moo's pool say now is 592062
Huh?

Shouldn't matter for just one off like that. The stats on the pool can be late by like half a minute (the stats thread gathering data and refreshing the compressed bundle every N seconds, the web page's timer downloading that bundle every N seconds, etc).

legendary
Activity: 1276
Merit: 1001
2015-Aug-04 21:06:42.603225 [P2P9][74.91.30.186:11180 OUT]Sync data returned unknown top block: 783 -> 592063 [591280 blocks behind]
SYNCHRONIZATION started


aeon 0.9.0.0 win64

Moo's pool say now is 592062
Huh?

Shouldn't matter for just one off like that. The stats on the pool can be late by like half a minute (the stats thread gathering data and refreshing the compressed bundle every N seconds, the web page's timer downloading that bundle every N seconds, etc).
member
Activity: 71
Merit: 10
2015-Aug-04 21:06:42.603225 [P2P9][74.91.30.186:11180 OUT]Sync data returned unknown top block: 783 -> 592063 [591280 blocks behind]
SYNCHRONIZATION started


aeon 0.9.0.0 win64

Moo's pool say now is 592062
Huh?
sr. member
Activity: 450
Merit: 250
Is http://aeonpool.mooo.com/ on the correct chain? My miner says it's detecting new blocks and finding shares, but the front page says no block found for an hour.

This pool has what looks like the correct info on the front page: http://52.8.47.33:8080/

You probably just need to do a proper browser refresh. I've seen pool stats not getting updated often (browser fault?).
Mooo's pool is definitely on the correct chain, and it has found a few blocks since the fork (current round is an unlucky one though, at ~40 minutes at the moment).

Indeed, hard refresh did the job. Rookie mistake..
sr. member
Activity: 450
Merit: 250
AMD FX-8320 with 8 threads using wolf's updated miner is giving ~700H/s. Thanks for compiling this for us losers still using windies!

I'd love an AMD GPU miner for windies. I'll go give the Claymore thread another nudge...
AMD FX-8320 with 8 threads @4GHz is at 850 h/s. Claymore's can easily beat 1 Kh/s.

Mine is @3.5GHz. I'm trying to keep the heat and noise down Smiley
sr. member
Activity: 283
Merit: 250
AMD FX-8320 with 8 threads using wolf's updated miner is giving ~700H/s. Thanks for compiling this for us losers still using windies!

I'd love an AMD GPU miner for windies. I'll go give the Claymore thread another nudge...
AMD FX-8320 with 8 threads @4GHz is at 850 h/s. Claymore's can easily beat 1 Kh/s.
legendary
Activity: 1276
Merit: 1001
Yes, it's as Myagui said. Last block 40 minutes ago. Blocks are now targetted a 4 minutes, and I've lost about half of the miner hash from people who haven't updated yet, so block finding rate on the pool has gone down a lot. On the plus side, we get 40 AEON per block instead of 10 Smiley

I've seen the not-refreshing-problem, no idea what it is about as I'm not super clued in to Javascript/browser tech.



legendary
Activity: 1154
Merit: 1001
Is http://aeonpool.mooo.com/ on the correct chain? My miner says it's detecting new blocks and finding shares, but the front page says no block found for an hour.

This pool has what looks like the correct info on the front page: http://52.8.47.33:8080/

You probably just need to do a proper browser refresh. I've seen pool stats not getting updated often (browser fault?).
Mooo's pool is definitely on the correct chain, and it has found a few blocks since the fork (current round is an unlucky one though, at ~40 minutes at the moment).
sr. member
Activity: 450
Merit: 250
Is http://aeonpool.mooo.com/ on the correct chain? My miner says it's detecting new blocks and finding shares, but the front page says no block found for an hour.

This pool has what looks like the correct info on the front page: http://52.8.47.33:8080/
sr. member
Activity: 450
Merit: 250
AMD FX-8320 with 8 threads using wolf's updated miner is giving ~700H/s. Thanks for compiling this for us losers still using windies!

I'd love an AMD GPU miner for windies. I'll go give the Claymore thread another nudge...
legendary
Activity: 2968
Merit: 1198
Did you guys notify chainradar? It seems they are on the wrong fork.

Height 592037

Edit: I have dropped them a line.

Yes they've been notified, yes they are on the wrong fork.
hero member
Activity: 649
Merit: 500
Did you guys notify chainradar? It seems they are on the wrong fork.

Height 592037

Edit: I have dropped them a line.
hero member
Activity: 500
Merit: 500
Thanks to MoneroMooo who identified the bug in cpuminer-multi. I pushed the fix to my repo



ok, no time to build a new w64 binary now, i will see later.

meanwhile, cpumine is ok on windows with wolf's binaries.
hero member
Activity: 500
Merit: 500
I am useing -a cryptonight-lite

Hmm. Maybe there is a bug in it. Did you try Wolfs?


No because of Arux's posting...............

use non-AES-NI on old cpu (else you will get a message 'cpu not supported")


That be LucasJones AFAIK.  Wolf's non AES-NI never worked for me in the past.


Back to work I go,  ohhhh

my apologies, LucasJones binary don't work as expected. there is an error but i still don't know wich one.

Wolf binaries are OK.
AES-NI optimization for recent hardware and non AES-NI for older.
Jump to: