Closed dgpv closed 9 months ago
I decided that it is better to just report information about the usage of the witnesses as signatures, hash preimages, etc, and their participation in enforcements. plugins/model_value_usage_track_bsst_plugin.py
is doing just that. Closing this issue.
Can help with analyzing malleability
Problem is that if model values for signatures will be reported with
=
instead of:
, it might add confusion, because the values will still not be 'real', it would just show that there's only one value possible (with the constraint under discussion, only one sig per pub/data pair). Usually when there's=
, we can expect that this is the 'real' value (but no guarantees actually, did not research this). Maybe add some special symbol in addition to=
and:
to denote this situation ?