Didn't understand your idea about "staking split size". Explain better and maybe we can discuss more about this.
Thank you for your reply!
Split size: now coin pile splits in 2 halves after staking. For example: 875 will add 25 and will split into 450 and 450 piles; later those piles will split again. In case I want to keep the min pile size 500, for example, I would like to specify in conf file something like "stakesplit=500", for example to prevent coin piles to split in piles smaller than 500 coins.
I got it, but I think this is not good, mainly for the new users because - as default - I need set a standard value to split.
I mean, every occurrence of this split, the coin age will reset (like "new transaction") and wallet in Proof-of-Staking mode will be affected directly needing waiting 72 hours again to be mature.
For advanced user, maybe this is good only to organize the income.
For example:
>> stakesplit=10000
if an input of 20k coins gets a PoS block and it's coin age is 5 days, it will be split in 2 halves of to 2x5k and of course coinage resets to 0
+ Examples:
>> scenario 01 - activating stakingsplit
balance: 35,000
new inputs:
TX1: 3,000 // TX2: 5,000 // TX3: 20,000 // TX4: 7,000
::: after split you will see
::: tree list mode of inputs
> 10,000
> 10,000
> 10,000
> 7,000 (intact and will be change on the next transaction)
> *** 25 (when next income via PoS to split again)
>> current scenario:
::: balance: 35,000
::: tree list mode of inputs
> 2,000
> 5,000
> 20,000
> 7,000
> *** 25 (when next income via PoS)
> *** 25 (when next income via PoS)
Pros:
Better organization on tree list view mode
Against:
The coinage is reseted to 0 every split, so, this input has to wait 72 hours again to stake