user5906: Can someone please explain the difference between the two sets of constraints supplied to submitTxConstraintsWith?
1st question:
The function takes two parameters, referred to as "lookups" and "tx" in the examples, which are both a set of constraints. So what differentiates the "lookup" constraints from the "tx"?  Another way to frame this is, what constraints go into "lookups" and what constraints go into "tx"?
2nd question:
Conceptually, what does the term "lookup" refer to?  What is being looked up?  The term is used throughout the documentation without any definition I can find.

user6292: "tx" constraints determine what goes into the transaction. "lookup" constraints determine which information is needed to validate the transaction, i.e. information from the blockchain or from the wallet.

5906: <p>Can someone please explain the difference between the two sets of constraints supplied to submitTxConstraintsWith?</p>
<p>1st question:
The function takes two parameters, referred to as &quot;lookups&quot; and &quot;tx&quot; in the examples, which are both a set of constraints. So what differentiates the &quot;lookup&quot; constraints from the &quot;tx&quot;?  Another way to frame this is, what constraints go into &quot;lookups&quot; and what constraints go into &quot;tx&quot;?</p>
<p>2nd question:
Conceptually, what does the term &quot;lookup&quot; refer to?  What is being looked up?  The term is used throughout the documentation without any definition I can find.</p>
 6292: <p>&quot;tx&quot; constraints determine what goes into the transaction. &quot;lookup&quot; constraints determine which information is needed to validate the transaction, i.e. information from the blockchain or from the wallet.</p>
