POW change discussion about aeon-legacy HOT 7 OPEN

Keeping aeon lightweight is key. Min ringsize5 may keep some users from doing transactions on a daily basis.

Aeon should give the user whatever size they want and option for fees. Obviously fees must match rigsize so people don’t under/over pay for simple transactions.

I believe many users currently use 1 for transactions to exchanges while other transactions use 3+. Possibly a note in gui/cli stating implications of lower ring size when used.

from aeon-legacy.

I agree on ringsize- Min 5 will make it hard to make frequent tx's

from aeon-legacy.

Ring size 1 is a keeper for me as well.

from aeon-legacy.

The asic solution feels like whack a mole. But I could go either way at this point.

from aeon-legacy.

Mostly agree with whack-a-mole @guzzijones, but it seems okay to follow along with Monero's experiment at this point.

from aeon-legacy.

I’d avoid hard fork if it can be avoided. Lot’s to be said for stability, IMHO leave POW as-is. From what I see, it os working well. Maybe focus on pool diversity instead.

from aeon-legacy.

@tomaszwojewoda We're going to have a hard fork anyway. General consensus in the community seems to be to include the anti-ASIC PoW change in the hard fork for now but probably not continue with whack-a-mole indefinitely.

Ring size rules will remain essentially the same as they are now from an end user perspective but be implemented differently.

from aeon-legacy.