Dev, can you clarify what the target block time is? My pool (which is the only place producing any significant amount of block currently) has had a fairly constant hashrate for about 8 hours and mined about 120 blocks during that time, which indicates an approximately 4 minute block time, yet in the OP you say the target block spacing time is 1 minute. What's going on here?
EDIT: also a few other questions:
* you removed the "copyright bitcoin core developers" from the top of each file in the source code, i know it's released under MIT but I'm not completely sure if that's legal.
* Any plans to get on exchange soon? Have you applied to YoBit or Nova?
* Why is the source code based on Bitcoin 0.8 rather than a more recent version? 0.8 was originally released over 4 years ago.
can't speak to the legality question and mithril is being courted by Tristan D' agosta of the Poloniex Exchange http://imgur.com/a/vNfWy i think we are going to pass though. EDIT: also a few other questions:
* you removed the "copyright bitcoin core developers" from the top of each file in the source code, i know it's released under MIT but I'm not completely sure if that's legal.
* Any plans to get on exchange soon? Have you applied to YoBit or Nova?
* Why is the source code based on Bitcoin 0.8 rather than a more recent version? 0.8 was originally released over 4 years ago.
![Roll Eyes](https://bitcointalk.org/Smileys/default/rolleyes.gif)
we like both YoBit and Nova and have plans to reach out when we hit some internal commitment goals.
understand your frustration with the ambiguous block times here is the main.cpp values for target time span:
static const int64 nTargetTimespan = 2 * 60; //look at the last 2 minutes
static const int64 nTargetSpacing = 1 * 60; // 60 seconds per block
static const int64 nInterval = nTargetTimespan / nTargetSpacing; //change every 120/60 2 blocks
we experience the same thing 2 - 7 minute block time on average with 10 - 40 second successive blocks and then the difficulty spikes. So technically the code is working as designed an unexpected result is lower:
nTargetTimespan = 120 nActualTimespan = 30
or
nTargetTimespan = 120 nActualTimespan = 306
a lot higher.
a possible remedy would be to increase the target spacing and target timespan to allow for a more consistent target and we'll be reviewing transaction data prior to making any changes.