Oh it seems to be the only viable option for the moment. I'd just be a little wary of anything that handles my money and doesn't offer me at least an account to connect all those wallets to.
Especially when the
So I assume in any way that it'd be better for me to initiate any deal by sending the GMEs first since we do not know how many confirmations it takes until they are there.
BTW, jayo89, you seem quite fluent with the source code - any idea of what new diff we can expect after diff change? What minute interval does the source aim for?
Would you consider yourself able to implement a more dynamic algorithm like with BitBar, or the new one about to go live with Freicoin in ~20 blocks?
The difficulty change seems to follow the standard algorithm, so the difficulty is going to drop proportionally so that the average hash power over the last bit would be enough to mine coins at the target rate. I was thinking of using a more fluid algorith that would sort of look at a "graph" of mining activity over the period, rather than an average. ie if mining power is obviously on a sharp decline, make the difficulty lower than only a slight decline, even if the averages in those two scenarios would be the same. This would hopefully make for difficulty adjustments that are more realisitc, preventing both an unsuitable difficulty for the whole network, or a ridiculously low difficulty that is taken advantage of by the opportunistic few.
Also, from the source code:
Code:
838: static const int64 nTargetTimespan = 3.5 * 24 * 60 * 60; // Gamecoin: 3.5 days
839: static const int64 nTargetSpacing = 2.5 * 60; // Gamecoin: 2.5 minutes
840: static const int64 nInterval = nTargetTimespan / nTargetSpacing;
839: static const int64 nTargetSpacing = 2.5 * 60; // Gamecoin: 2.5 minutes
840: static const int64 nInterval = nTargetTimespan / nTargetSpacing;
Difficulty shift is aimed for every 3.5 days, assuming a block is found every 2.5 minutes, that gives us a difficulty retarget every 2016 blocks.
