• Peter Goodspeed-Niklaus's avatar
    the `inclusion` inherent call is Operational, not Mandatory · e58858d1
    Peter Goodspeed-Niklaus authored
    This resolves a lot of the trickiness about this issue, because
    we no longer need to override or supplant any existing proposer
    logic; the existing logic should exhibit these behaviors:
    - the `inclusion` inherent is prioritized over standard transactions
    - but if it's too heavy, i.e. in case of runtime upgrade, it'll be
      dropped in favor of that.
    It is my belief that allowing the proposer to just not include
    this data won't have any adverse effects: it's equivalent to replacing
    them with empty versions of themselves, which the `ProvideInherent`
    impl already does.