[Stacks-2.1] Can stack-aggregation-commit lock smaller amounts of STX after the minimum threshold for a PoX address has been met?

[jcnelson]

This was a question raised by @friedger on his review of SIP-015. If possible, stack-aggregation-commit should be modified in .pox-2 to permit locking up additional STX for a PoX address once the minimum STX threshold has been met. If this can be done, then new pool members can be added over a sequence of stack-aggregation-commit calls even if their collective STX do not exceed the stacking minimum.

It doesn't look like a very big change in the .pox-2 code; the bulk of this task is in devising an adequate test for it.

[jcnelson]

To speak to the implementation a bit more, the code needs to ensure that the PoX address receiving the STX already has the minimum Stacking threshold, and has an entry in reward-cycle-pox-address-list whose stacker is none. If so, then it needs to add the STX to this already-present entry. It cannot just append a new PoX address with append-reward-cycle-pox-addr, since that would open a DDoS vector -- someone could just stack 1 uSTX a bunch of times in order to grow the reward-cycle-pox-address-list map to contain so many entries that creating a new reward set takes more than the block time.

[jcnelson]

Merged!

[blockstack-devops]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.