| commit | 3babbcb48786372d4b22171674c4cc5a6220c294 | |
| author | Gregory Maxwell <greg@xiph.org> | |
| Sat, 17 Jun 2017 00:18:42 +0000 (17 00:18 +0000) | ||
| committer | Gregory Maxwell <greg@xiph.org> | |
| Fri, 14 Jul 2017 19:24:17 +0000 (14 19:24 +0000) | ||
| tree | 099fab1403b69a6da62d222fbf8b2d45f0c12fa7 | treesnapshot (tar.gz zip) |
| parent | e4fcbf797ed3b472d352ac3794ec82f581209c50 | commitdiff |
Remove confusing MAX_BLOCK_BASE_SIZE.
Some people keep thinking that MAX_BLOCK_BASE_SIZE is a separate
size limit from the weight limit when it fact it is superfluous,
and used in early tests before the witness data has been
validated or just to compute worst case sizes. The size checks
that use it would not behave any differently consensus wise
if they were eliminated completely.
Its correct value is not independently settable but is a function
of the weight limit and weight formula.
This patch just eliminates it and uses the scale factor as
required to compute the worse case constants.
It also moves the weight factor out of primitives into consensus,
which is a more logical place for it.
Some people keep thinking that MAX_BLOCK_BASE_SIZE is a separate
size limit from the weight limit when it fact it is superfluous,
and used in early tests before the witness data has been
validated or just to compute worst case sizes. The size checks
that use it would not behave any differently consensus wise
if they were eliminated completely.
Its correct value is not independently settable but is a function
of the weight limit and weight formula.
This patch just eliminates it and uses the scale factor as
required to compute the worse case constants.
It also moves the weight factor out of primitives into consensus,
which is a more logical place for it.
17 files changed: