You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Potential size savings: 20 bytes * number_of_out_of_consensus_and_errors per tally transaction.
Alternatives: since the reveals have a well known ordering, we could just store the reveal_index instead of PublicKeyHash. This would reduce the overhead from 20 bytes to ~1 byte, but not sure if we can easily implement that in the node.
The text was updated successfully, but these errors were encountered:
As of PR witnet/witnet-rust#1267 there are two fields in
TallyTransaction
that look redundant, we should be able to implicitly calculate them:out_of_consensus
anderror_committers
Potential size savings:
20 bytes * number_of_out_of_consensus_and_errors
per tally transaction.Alternatives: since the reveals have a well known ordering, we could just store the
reveal_index
instead ofPublicKeyHash
. This would reduce the overhead from 20 bytes to ~1 byte, but not sure if we can easily implement that in the node.The text was updated successfully, but these errors were encountered: