myagui
Legendary
Offline
Activity: 1154
Merit: 1001
|
|
August 06, 2015, 09:07:16 AM |
|
@smooth, I'm running these now to see how the IP banning is working on Windows. After a couple of minutes running the daemon, I've seen the offending peers getting dropped a couple of times, but so far, they look to be coming back. Could you briefly describe what to expect when this version encounters a bad peer? Such as: - Bad peer connects and sends invalid blocks, get's dropped. - After X connect/drop cycles for a given bad peer, the IP is banned for Y amount of time. EDIT: Patience pays off Just seen the following message: 2015-Aug-06 10:08:00.568484 [P2P7]Ip xxx.xxx.xxx.xxx blocked.
|
|
|
|
|
|
|
"Governments are good at cutting off the heads of a centrally
controlled
networks like Napster, but pure P2P networks like Gnutella and Tor seem
to be holding their own." -- Satoshi
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
August 06, 2015, 09:29:27 AM |
|
EDIT: Patience pays off Just seen the following message: 2015-Aug-06 10:08:00.568484 [P2P7]Ip xxx.xxx.xxx.xxx blocked. Yes that is exactly what is supposed to happen. Multiple offenses are required to get banned. (In the future I may modify this to depend on the severity of the offense; some DoS attack patterns may justify immediate banning.) The peers vary in how rapidly they reconnect. I think this is a function of the size of each node's peer candidate list (since the p2p code only tries to connect to one candidate at a time, if their list is large it will take them a while to cycle back around to your node). So they will get banned after a somewhat different delay. After about 20-30 minutes it seems all of the bad peers are banned.
|
|
|
|
myagui
Legendary
Offline
Activity: 1154
Merit: 1001
|
|
August 06, 2015, 09:37:38 AM |
|
Thanks smooth (and Arux for the win bins!)
What about unbanning the offending peers? Will the bans have some automatic expiration time, or is there some manual process by which one can clear the active bans? I'm thinking that some expiration time would be reasonable, as the ideal situation is that all those peers eventually get upgraded, though I'm assuming these are not malicious nodes.
|
|
|
|
smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
August 06, 2015, 09:39:12 AM |
|
Thanks smooth (and Arux for the win bins!)
What about unbanning the offending peers? Will the bans have some automatic expiration time, or is there some manual process by which one can clear the active bans? I'm thinking that some expiration time would be reasonable, as the ideal situation is that all those peers eventually get upgraded, though I'm assuming these are not malicious nodes.
Yes the bans automatically expire after 24 hours (but if the peer continues to misbehave it will just get banned again quickly). Again that could vary based on the severity of the offense but for now the simple approach should be good enough. EDIT: one of my test nodes has been running the ip banning version for 24 hours and I see that the unbanning does work.
|
|
|
|
eeX
|
|
August 06, 2015, 02:32:02 PM |
|
Hello,
does anybody know, is it possible to find bootstrap for Windows-x64 at any respectable place, not @ Mega?
|
Soldo [SLD] @ Soldo.IN
|
|
|
|
WCIR
|
|
August 06, 2015, 08:39:49 PM |
|
|
|
|
|
smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
August 06, 2015, 08:46:37 PM |
|
Claymore has not been updated. He said he will probably do it, but has not given a schedule. Probably yes, but not right now because I don't have any free time currently Minergate has said they are in the process of updating. For now you will need to use either NVIDIA GPUs or CPU at http://aeonpool.mooo.com/ and http://52.8.47.33:8080
|
|
|
|
MoneroMooo
Legendary
Offline
Activity: 1276
Merit: 1001
|
|
August 06, 2015, 11:06:47 PM |
|
To whoever holds these addresses:
Wmt2443c7[...] You've been using an old miner since the fork. Please update. You're hashing for nothing.
WmsM331a[...] At least one of your rigs is hashing with an old miner and is hashing for nothing.
|
|
|
|
broadsword
|
|
August 07, 2015, 02:53:18 AM |
|
nice volume on trex
|
|
|
|
smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
August 07, 2015, 03:08:56 AM |
|
nice volume on trex
Indeed it is. Seems to be some interest building on this coin. Incremental tagged release with IP banning will go up soon. I'm still at work on pruning.
|
|
|
|
broadsword
|
|
August 07, 2015, 03:17:25 AM |
|
nice volume on trex
Indeed it is. Seems to be some interest building on this coin. Incremental tagged release with IP banning will go up soon. I'm still at work on pruning. have full faith in you, great plans. best to use donations when the price is much higher.
|
|
|
|
smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
August 07, 2015, 04:45:09 AM Last edit: August 07, 2015, 05:38:10 AM by smooth |
|
New minor release (0.9.1.1)Fix diff command showing incorrect hash rate after hard fork 1 Small improvement to performance of daemon miner (1-2%) Added backup seed node Lower mining priority for anon-impairing (<2 mixins) tx Various portability fixes (mostly from Monero) Small reduction to memory usage (tens of MB) Add IP blocking for misbehaving nodes (adapted from Boolberry) Update checkpoint table Download (binaries will be added once Arux creates them): https://github.com/aeonix/aeon/releases/tag/v0.9.1.1Most of these are self-explanatory, except for the reduced mining priority for <2 mixin (< mix 3) transactions. These transactions impair the anonymity of other transactions on the network by chain reaction effects as discussed in Monero Research Lab's report MRL-0001. As such they are dangerous, but sometimes useful (for example to spend unmixable outputs, or to combine a large number of small outputs) Instead of banning them entirely, as Monero proposes to do, I have modified the mining code to include at most one such transaction per block, which means approximately 360 per day. As a result, once usage on the network increases, these transactions will only represent a small percentage of the total, and uncontrolled chain reaction effects can not occur. As a consequence, if you send a transactions with mixin less than 2, and the network is busy, your transaction may take longer to confirm. Once we have variable transaction fees, you may need to pay a higher fee. To ensure your transaction confirms as quickly as possible, use mixin 2 or higher. This restriction is not fully enforced currently. My plan is to see whether any issues arise, and then fully enforce it later. aka "AEON Solves Cryptonote Flaws" (inside joke for the Cryptonote old timers here).
|
|
|
|
smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
August 07, 2015, 06:59:43 AM |
|
nice volume on trex
Indeed it is. Seems to be some interest building on this coin. Incremental tagged release with IP banning will go up soon. I'm still at work on pruning. have full faith in you, great plans. best to use donations when the price is much higher. Thank you for the words of support and yes the project donations fund are being held long term (and continue to grow from mining and new donations) except a small amount that has been used for bounties.
|
|
|
|
smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
August 07, 2015, 09:03:22 AM Last edit: August 07, 2015, 09:23:50 AM by smooth |
|
New minor release (0.9.1.1)
For a brief time the git tag was pointing to the wrong version, so if you downloaded from the above links or cloned/pulled from git already, I apologize for the error, but please do get the fixed release now. The above links are correct.
|
|
|
|
macorcina
|
|
August 07, 2015, 09:38:40 AM |
|
Claymore has not been updated. He said he will probably do it, but has not given a schedule. Probably yes, but not right now because I don't have any free time currently Minergate has said they are in the process of updating. For now you will need to use either NVIDIA GPUs or CPU at http://aeonpool.mooo.com/ and http://52.8.47.33:8080After update isn't possible to mine on http://aeonpool.mooo.com/ with Claymore GPU Miner Error in server response : {"id":1,"jsonrpc":"2.0","error":{"code":-1,"message":"invalidaddressusedforlogin"}} and http://52.8.47.33:8080/Stratum - Cannot connect to aeonpool.arux.ma.gy port 3333 Stratum - Failed to connect, retry in 20 sec... Stratum - connecting to 'aeonpool.arux.ma.gy' <94.23.241.98> port 3333 Stratum - Cannot connect to aeonpool.arux.ma.gy port 3333 on minergate work fine.
|
|
|
|
smooth
Legendary
Offline
Activity: 2968
Merit: 1198
|
|
August 07, 2015, 09:45:06 AM |
|
Claymore's miner is NOT updated (see quote above) and can NOT be used to mine AEON at this time.
Minergate is NOT updated. Do not mine AEON on minergate or you are wasting your hash power.
If you must use Claymore (AMD), you are better of mining another cryptonote coin that still uses the older CryptoNight algorithm.
|
|
|
|
macorcina
|
|
August 07, 2015, 10:02:10 AM |
|
for AMD GPU is no mining AEON ?
|
|
|
|
|
|
|