Will the recent developments in XMR be transferred to aeon, like the GUI and RCT update? Is there a roadmap for 2017?
RCT is evil, we don't need it...
Why? Because transactions can be larger? I don't think this is a big issue for Monero, but less of an issue for Aeon where mixin 0 txs are still allowed, as it makes things pruneable, right?
Why not use transaction prefix only to calculate transaction ID hash like BBR, just do away with old ring signatures (when becomes a bloat problem)?
That can be done anyway for storage purposes, the same way Bitcoin does pruning, and is already implemented in AEON. The BBR approach has minimal benefit. You can sync faster but with a lower level of security (trusting other nodes instead of verifying everything yourself).
Will the recent developments in XMR be transferred to aeon, like the GUI and RCT update? Is there a roadmap for 2017?
RCT is evil, we don't need it...
Why? Because transactions can be larger? I don't think this is a big issue for Monero, but less of an issue for Aeon where mixin 0 txs are still allowed, as it makes things pruneable, right?
Right. Also, the AEON approach of allowing limited use of 0 mix and non-RingCT transactions would allow things like pool payouts where both tracing and hiding amounts is largely pointless (the blocks mined by the pool is generally public anyway, as are the payout transactions) to be done with lower cost. Or at least, they would bid for access to the quota of 0-mix transactions. My
guess is that those slots would be most valuable to pools for cheap payouts, but I don't know. The market will sort it out.
I don't see RingCT or required mixing being a problem here at all. People who don't need it can opt out, as long as is kept under control and doesn't compromise the privacy of the chain as a whole. (I also agree it isn't likely to be a real problem for Monero either, but we will see. If usage explodes and blocks become too large that could be a concern, possibly.)