Drop script sizes
kderme opened this issue · comments
Fields tx.script_size and script.serialised_size are redundant, since their values can be derived by the length of the script.bytes. If there is no significant reason to keep them, they should be dropped.
This requires users input
Only advantage I can think of is they can have is when analysing scripts by sizes on DB, but that can easily be achieved by point-in-time views. Agree they should be dropped