And why is again used a difficulty retarget of 2 weeks, which can be easy manipulated with high hashrates peaks ?
SHA256 is the next thing... It consumes enormous energy resources and feed again only the chinese mining farms.
Take a look for lyra2z and neoscrypt algo. This algos are far more energy and resource friendly.
The high blocktime has only the need for higher memory requirements to buffer all the incomming transactions, which
is not very v-server friendly.
My suggestions for real improvements are:
- Difficulty retarget at every block (following the hashrate in near realtime)
- Algo: lyra2z or neoscrypt, instead SHA256 - No ASIC-Support please - to make it real decentralized
- Alternative: Multi-Algo capability (like DGB)
- Blocktime 180-360 seconds, instead 10 Minutes
- An Option to use "Zero fee" for small amounts of coins
- Instant-Sent/Private Send Option
A good sample for an improved implementation are the actual GoByte/CrowdCoin/Innova, etc. Codebases
One of the main problems of BTC is the long waiting time for enough confirmations.
for this reason they integrated hybrid consensus both pos and pow for miners to get less control
after fork yes