It seems that all of our data submissions so far consist of only payment sequences. Given that we currently don't have any organic payment data in which the feerate was recorded along side the payments, it may be nice to be able to separately specify a payment operation sequence with a feerate sequence.
Instead of creating a scenario by combining a sequence of payment operations with a sequence of feerates and storing that as a distinct file, we could then create new scenarios on the fly by combining a sequence of payment operations with a sequence of feerates.
Since they might differ in length, the simulation should run as long as there are payment operations and repeat the sequence of feerates as necessary.
murchandamus
commented
2 years ago
It seems that all of our data submissions so far consist of only payment sequences. Given that we currently don't have any organic payment data in which the feerate was recorded along side the payments, it may be nice to be able to separately specify a payment operation sequence with a feerate sequence.
Instead of creating a scenario by combining a sequence of payment operations with a sequence of feerates and storing that as a distinct file, we could then create new scenarios on the fly by combining a sequence of payment operations with a sequence of feerates.
Since they might differ in length, the simulation should run as long as there are payment operations and repeat the sequence of feerates as necessary.