-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Aeon CryptonightR-light / What about? #72
Comments
Most likely the same Monero tweaks will be adopted, unless there's a strong objection: |
I believe that this could be implemented with integration of Bulletproofs and RingCT as part of a network upgrade. Edit-
I would be more for a small tweak if asic issues occur but deem it unnecessary right now. |
And another direct quote from aeon.cash
In this case why don't be updated with main? Anyway in case of age "trash coin's" and current price of AEON per USD i think - no good to be "not updated"! And it show "really support" of this coin! *Anyway it all by my mind |
New PoW + Bulletproof + RingCT will be an awesome update for Aeon indeed |
Network hashrate doubled! In one day from 8MH to 18MH) I believe "investors" come )))) |
Topic for discussion 12_4_2018 community meet up |
Any updates after 12_4_2018 meet up? |
Did you see the hash rate drop on xmr? More plausible that miners are looking at other alternatives when profitability drops. |
going to have to agree; there's been quite a lot of hashrate drop off XMR since October and remember the impact of 1 MH on XMR is ~2-3x on AEON. |
I see that. ASIC's for CN version 7 exists.
after fork (for example today):
ASIC's for CNv7 exists. |
Do you have any links to cnv7 asic miners? They must not be publicly available right now because nobody can seem to provide any purchasing information. |
No I do not have links) The current situation is completely similar to the beginning of this year. The future progress of Aeon is gonna be sad/upsetting. It is the reason why PoW needs to start changing right NOW. |
China (Bitmain, Bailkan, Innosilicon ...) brings scares to the whole crypto world. I love China, it makes things keep moving. |
Maybe you seemed to miss even after the Monero V8 Fork hashrate still made it past 500+ MH/s in late october/early Nov. 1MH on XMR = ~2-3.5 MH/s on CN-Lite. Currently XMR is only at ~360 MH/s leaves ~140+ MH/s on the table to be spread out to other alts or turned off. Here you can click this link below and wait a little while for it to load. So going to continue with original statement while there is a possibility of ASIC(s), the investment required 10 mil + to begin manufacturing the ASICs and the currently bear market it didnt make sense to make any CN-Lite units as no CN-Lite coin would have made ROI in under 3 years. Thus this is just a shift of miners moving from what become unprofitable to mine in some places pending on your kWh cost, to speculative mining on alts. |
I do believe that the next fork will include a slog change to match monero. Remember, Aeon needs to be brought up to date for other, more pressing software bug patches, than forking an algo change. |
We should test the current Aeon PRs ASAP so they can be merged and @stoffu can bring new code from monero :) |
Looks like there's a proposal over in #95 |
For CN-Turtle yes, not for CNv8. |
If you take a look at the code it implements variation 2 (which many like to call v8 because of Monero’s major block version when implemented) as well as a few other changes. |
If Monero (using CNv8) is experiencing a difficulty increase due to ASIC/FPGA devices, then that renders CNv8 useless in the fight against ASIC/FPGA's. This cat<->mouse game cryptonight coins are playing by changing one byte is clearly not working. A better solution is needed. |
Sounds funny )))) But how about CryptoNightR ? |
As community moves forward - i mean Monero as main source tree! What should we do in this situation? to remind direct quote from aeon.cash
|
So it looks like CN-r may be the way to go right now. We need someone to make a PR for these changes and schedule a fork. It has been confirmed that ASICS are on the network (although they are spreading the hash rate mostly evenly as if someone contacted baikal to ask them to play nicely this way). |
I think main problem of many "shit coins" in no following of they beginnings! I mean under that one main mistake - loud statements of developers in Communist slogans like we should make own currency, we should do lightweight, we should do decentralization, we should take the best of monero ) and other bla bla bla - what we have in fact. In fact we have - main rule of whole IT developers in the world: "DO NOT TOUCH WORKING MECHANISM" When year ago i come in world of different crypto currencies - i start search information about, start try many of them - it was hype at that moment in whole world. It was something new and whole markets grew up seventy mile steps ahead! I installed my own pool and start dig aeon because it was like lightweight monero. After two hardforks i adopted twice for myself xmrig classic to support new monero, but after second - when i start this topic one of developer say: Currently it seems unnecessary to do this (minimal if any fpga or ASICS on aeon network)! Do you really believe in 45MH/s of network - network grew up 300% per 3 month! May be people see in this coin future? May be! But most of them use simple money calculation and it easiest! Ok let we have new many coin adepts in 35MH it equivalent around 1900 AEON per day if we use simplest calculator in any most of pools so: 35MH -> 1900AEON -> 570$ per day! Not included any other losts! I know it simplest calculation, but it reflect main problem of our coin - IF NOTHING CHANGED COIN DIE UNDER ASIC'S THAT WAS DEVELOPMENT FOR MONERO! Because Monero protect main princip of coin - DECENTRALIZATION OF NETWORK! It whole by my mind and i know my voice is nothing - but if nothing changed - i will move to Monero! FUTURE ALREADY NOW! 300% NETWORK GROW IT ONLY BECAUSE SOME RETARGET ALREADY THEIR ASICS |
label:enhancement
What about this encasement in future? Any movements?
The text was updated successfully, but these errors were encountered: