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

That is odd.

The first miner seems to be Wolf's. It works on Arux' pool but not mine, can you confirm ?

The second miner seems to be LJ's. There was a bug in that miner which caused the hashes to be wrong. This was fixed two days ago or so, so make sure you have the most recent version.

If I try your first command:

minerd -a cryptonight-light -o stratum+tcp://52.8.47.33:3333 -u
WmtVTeq17d57y1gHwB6LwNNR41GwvgdKSBNd272WF7D931cXZRsHtFzTm9JkFHsZbuWV5Pr8Te2dwVV B
MZMeo8Pn2Ebx6dZaw -p x

Then I can connect to Arux' pool, and changing the IP to my pool also works (there was a space in the address, but I think it's just BCT adding it).

I don't see connections for this address apart from my tests, nor bans, so it looks like your connection is stopped before it reaches the server.

yes,I had updated miner and replace -a cryptonight-light, But the error still exists

The strange thing is I'm in the mine pool with this command , it is normal
http://52.8.47.33:8080

D:\新建文件夹\2>minerd -a cryptonight-light -o stratum+tcp://52.8.47.33:3333 -u
WmtVTeq17d57y1gHwB6LwNNR41GwvgdKSBNd272WF7D931cXZRsHtFzTm9JkFHsZbuWV5Pr8Te2dwVV B
MZMeo8Pn2Ebx6dZaw -p x
[2015-08-10 02:13:27] Using JSON-RPC 2.0
[2015-08-10 02:13:27] Starting Stratum on stratum+tcp://52.8.47.33:3333
[2015-08-10 02:13:27] 3 miner threads started, using 'cryptonight-light' algorit
hm.
[2015-08-10 02:13:27] Pool set diff to 100
[2015-08-10 02:13:27] Stratum detected new block
[2015-08-10 02:13:29] accepted: 1/1 (100.00%), 69.81 H/s at diff 100 (yay!!!)

==================================
another mind,Has been circulating , can not properly connected to the mine pool

C:\Users\cyz\Downloads\新建文件夹\1>minerd -a cryptonight-lite -o stratum+tcp://
aeonpool.mooo.com:5577 -u WmsFoKjNnCvXkTtVx8zMR8B76rhh8aUs96NkQNVo4TFiBB15ftw2YC
Car9utqavY49EbZzuKink5b2NexqgrhJEx2PzbGpU8M -p x -t 2
[2015-08-10 02:57:28] Using JSON-RPC 2.0
[2015-08-10 02:57:28] CPU Supports AES-NI: NO
[2015-08-10 02:57:28] Starting Stratum on stratum+tcp://aeonpool.mooo.com:5577
[2015-08-10 02:57:28] 2 miner threads started, using 'cryptonight-lite' algorith
m.
[2015-08-10 02:57:28] thread 0: 1 hashes, 32.05 H/s
[2015-08-10 02:57:30] thread 1: 66 hashes, 28.56 H/s
[2015-08-10 02:57:49] Stratum connection failed: Failed to connect to aeonpool.m
ooo.com port 5577: Timed out
[2015-08-10 02:57:49] ...retry after 10 seconds

There was a recent hardfork. The mining algorithm has changed.You need to do two things:
- get an updated miner (https://github.com/moneromooo/cpuminer-multi or https://github.com/iamsmooth/cpuminer-multi)
- replace -a cryptonight with -a cryptonight-light (first miner URL) or -a cryptonight-lite (for second miner URL)

If you need windows binaries, they don't seem to be on the first page, but look for posts by Arux (don't download them from any quoted post, just from an original Arux post).

Why I can not link to the mine pool:
http://aeonpool.mooo.com/

This is my mining parameters：
minerd -a cryptonight -o stratum+tcp://aeonpool.mooo.com:5577 -u WmtVTeq17d57y1gHwB6LwNNR41GwvgdKSBNd272WF7D931cXZRsHtFzTm9JkFHsZbuWV5Pr8Te2dwVV BMZMeo8Pn2Ebx6dZaw -p x

[2015-08-10 01:27:31] Using JSON-RPC 2.0
[2015-08-10 01:27:31] Starting Stratum on stratum+tcp://aeonpool.mooo.com:5577
[2015-08-10 01:27:31] 3 miner threads started, using 'cryptonight' algorithm.
[2015-08-10 01:27:52] Stratum connection failed: Failed to connect to aeonpool.m
ooo.com port 5577: Timed out
[2015-08-10 01:27:52] ...retry after 10 seconds

Thanks, I've just consolidated coins again. Payouts will restart as soon as they unlock.

MoneroMooo
Pool Pending Balance raising without payouts.

There is no such thing as embedded disfunctional nodes. There are nodes out there which have not updated, but still try to connect to the network. If your node is up to date, it will reject/disconnect/ban these other nodes. You will see the disconnects as red text in your own node, but this is not a bad thing. Just ignore it.

This is getting frustrating, i'm starting to think there is some sort of bad information going on here.

Why are there tons of disfunctional nodes embedded in the exe file since its been updated yesterday ?

Hmm, one thing you can also try:

git checkout 1780acd08b5bbcf0760bbd78bc09653d0705c0b9

Then rebuild all.

I pushed a patch to bump a requirement for the CUDA SDK, and I have no idea what it implies, as it was just suggested to me. I guess it might cause this size issue, though I'd kinda expect things to be self consistent.

I'm not sure how they will do their internal accounting, but...
Minergate will lose all coins they received on block 592000 and later until they update.
Similarly, any coins they already sent on these blocks will vanish too, as the network does not know about these transactions.

Most likely seems to be you are using an include file (or compilation options) with a sizeof(cudaDeviceProp) that is smaller than twhat cudaGetDeviceProperties thinks.
If you already had it working, I'd make clean, or whatever is the equivalent there. If it's a fresh clone... Can you run any other CUDA program that you compiled in the same way and which uses cudaGetDeviceProperties ?

Does this mean we will lose minergate coins? It makes no sense

Minergate have not updated, so they are not mining the correct chain. Because there are so few mining this incorrect chain, you will get a very high proportion of the incorrect chain hashrate and it will look like you are getting lots of coins. But these coins will NOT be usable with the correct chain.

Don't hash there, as you'll receive NOTHING in return, so it's not profitable at all

Mining is strangely profitable (in terms of Aeon) right now on Minergate. A lot of people asked the support what's up with these mined Aeons and he said it's all good. How?...

Current chain height as I write this is 593690, so I guess you are synced?

593600 > 593688 after running 5 hour block sync go up very very slow 

I've been bugging them via trollbox. Eventually they will cave.

If you check the options on polo there is an option for suggesting a coin. I have submitted the suggestion and the reasoning. With Monero so popular there, and the great dev here, Aeon is an obvious choice now. (with future potential based on new development)

Can you be more specific as to the problems you are having?

Please update the bootstrap, i've tried everything.