Skip to content

[Dijkstra] Phase-1 transaction-wise validation checks #1017

@carlostome

Description

@carlostome

Description

In Dijkstra, in addition to pre-Dijkstra phase-1 validation of subtransactions and top-level transaction, several phase-1 validation checks depend on the transaction as a whole:

  1. Sub and top-level transaction(s) don't spend outputs of previous subtransactions CIP. (See [Dijkstra] resolve ambiguity: visibility of reference inputs #1014)
  2. (Top/sub) transactions reference scripts which are provided anywhere in the transaction CIP
  3. The size of the transaction, that is the sum of the sizes of all subtransactions plus the size of the top-level transaction, must be less than maxTxSize CIP

Tasks

  • Define auxiliary predicates corresponding to the checks described above.

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions