From the Instant(Tx) Whitepaper:
5.2 Transaction Lock Compatibility ModeTo enable backwards compatibility with all existing software (exchanges, pools, etc), clients will
default to showing 24 hours of confirmations of transactions that have been successfully locked.
This will provide all services using Darkcoin to benefit from instant transactions without having to
implement anything specific.
If a client needs the daemon to function in the old way, there will be a flag to disable this mode.Good thinking
This section might need some work too.
Current raw blockchain (no other transactions)
(60m / 2.5m confirmation time) * 156KB per block * days in a year) / mb /gb
((60/2.5)*158*365)/1024/1024
1.31GB per year
Even without anything... the blockchain grows pretty fast. In 5 years we're looking at 5-15GB depending on the transaction volume.
((60/20)*158*365)/1024/1024
0.16GB per year
That means that we can save over a gig a year by increasing the confirmation time. The idea is we want less bloat and faster transactions, so we should be able to get both without sacrificing anything.
Am I missing something? Why aren't hours/day included in the calculations? Shouldn't it be like:
(60m / 2.5m confirmation time) * 156(158?)KB per block * hours in a day * days in a year) / MB / GB
((60/2.5)*158*24*365)/1024/1024 = ~31.68 GB?
And second calculation:
((60/20)*158*24*365)/1024/1024 = ~3.96 GB?
Thus, the move would save 31.68 - 3.96 = 27.72 GB / year?
Edit: but that's not right, DRK's blockchain isn't nearly that big now...
Edit2: As pointed out below, each block uses space measured in mere bytes, not KB.
