There are 2 new debug window functions, svscanblocks and svdebugblock,
to measure total in- and outflow for addresses that start with
a given vanitygen string.
testing:
block 168266, 70 Fbx sent to fXgaga4p31vZvizUP6Y6coDAe6su8JMiph
block 168271, 80 Fbx sent to fXgagaVmUAcfpptmEHhH64v5j6fbuxvXwd, change from 1st tx is one of the inputs
block 168279, 200 Fbx sent to fXgaga4p31vZvizUP6Y6coDAe6su8JMiph
block 168282, 300 Fbx sent to fXgagaVmUAcfpptmEHhH64v5j6fbuxvXwd
block 168344, 115 Fbx sent to some address, the 70 Fbx from 1st tx is one of the inputs
svscanblocks 168265 168345 Xgaga
"total balance change" : 580.00000000
}
It backtraces tx's like the Bitcoin v0.7.2 Coin Control traceback function that was kicked out in 0.8,
but only 1 deep to find the correct input(s), and without using the database. (txindex=1 is required)
Why? Currently nodes can't access real world facts in any reliable way,
thats why "Bitcoin mining difficulty contract" is used as example in
https://bitcointalksearch.org/topic/m.2926734
I want a PoS based voting system for this...