This adds a flag to `BundleType` that, when set, requires a dummy-only
bundle to be produced even if no spends or outputs are added to the
builder, and when unset results in standard padding.
The term `recipient` is commonly used to refer to the address to which a
note is sent; however, a bundle may include multiple outputs to the same
recipient. This change is intended to clarify this usage.
Co-authored-by: Daira Emma Hopwood <daira@jacaranda.org>
to 10240. This improves the accuracy by ensuring a more even distribution
of more expensive decryptions.
Signed-off-by: Daira Hopwood <daira@jacaranda.org>
The benchmark assumed that the first action in the bundle was for the
recipient it had added, but we've started shuffling recipients within
actions, and the builder pads to a minimum of two actions. This meant
that 50% of benchmark runs would fail to start, but would proceed fine
if they did start (as the bundle is cached for the entire test).
We now add two recipients, to cancel out the effect of the padding and
shuffle.
Kris Nuttycombe
Daira Hopwood
Jack Grigg
therealyingtong