1. Switch database to LevelDB - faster startup and shutdown, less chance for data corruption.
2. Increase number of full nodes that accept incoming connections - currently my node can't find even 8 of them after few hours online.
3. Use different wallet look and feel - check Silkcoin or N5coin, integrated blockchain explorer and statistics are just awesome addition.
4. Aliases - user creates an alias and assigns YAC address to it via special transaction, later to send coins to user one could just use alias instead of normal YAC address.
1. - I think that was done a long time ago
3. - Great ideas, just need someone to volunteer to write them
4. - Seems problematic and memory intensive - everyone with an open wallet would need to be scanning all aliases on the off chance they're sending it to one. Plus, nothing like having alias squatters! Has any coin implemented this?
Even if one knew intimately what the Bitcoin ...chainstate/nnnnnnn.sst files were, the .../blocks/index/00nnnn.sst files were, etc. And even if one could "convert" the old data to a new levelDB rendition, coordinating the change-over would seem to be "tricky", without testing, etc. etc.
Doesn't mean one shouldn't though.
subSTRATA, I'm not seeing any appreciable shutdown delay in YACoin 0.4.3 or 0.4.4 And the start up is quite fast (the 2nd time, when "stuff" is in the OS caches ) Even the "first-time" LoadBlockIndexGuts() isn't too shabby since at ~1 minute per block, there are more blocks than a ~10 minute per block coin. YACoin has almost twice as many blocks as Bitcoin. There are other start up checks too, and I don't know if levelDB would affect them that much. For example the checking stake checksums and the Verifying the last xxx blocks.
Ron