Update example-reference-script-usage.sh to also use inline datums #4006
Conversation
Jimbo4350
force-pushed
the
jordan/inline-datum-integration
branch
2 times, most recently
from
ff26f83
to
9d1ae5e
Compare
Jimbo4350
requested review from
dcoutts,
erikd,
newhoggy and
JaredCorduan
as code owners
Jimbo4350
force-pushed
the
jordan/inline-datum-integration
branch
2 times, most recently
from
c2cd1af
to
a2234f9
Compare
| + spending ada at the Plutus script address using the Plutus reference script | ||
|
|
||
| In this example we will use the [Required Redeemer](scripts/plutus/scripts/v2/required-redeemer.plutus) Plutus spending script. In order to execute a reference Plutus spending script, we require the following: | ||
|
|
||
| - Collateral tx input(s) - these are provided and are forfeited in the event the Plutus script fails to execute. | ||
| - A Plutus tx output with accompanying datum hash. This is the tx output that sits at the Plutus script address. It must have a datum hash, otherwise, it is unspendable. | ||
| - A Plutus tx output. This is the tx output that sits at the Plutus script address. Note because we are using an inline datum, it is not mandatory that the utxo at the plutus script address has a datum hash. |
There was a problem hiding this comment.
it is not mandatory
Actually, it strictly cannot have a datum hash because the inline datum we reference cannot witness it. It would then need the datum to be attached to the tx, which means we cannot also reference the inline datum!
There was a problem hiding this comment.
We should stress this point, how about: "Note because we are using an inline datum, the utxo at the plutus script address must not have a datum hash because datum witnessing requirements cannot be satisfied with reference inputs. Outputs with datum hashes must have datum included in transaction body as witness."
There was a problem hiding this comment.
Actually, it strictly cannot have a datum hash because the inline datum we reference cannot witness it. It would then need the datum to be attached to the tx, which means we cannot also reference the inline datum!
Yep my wording is poor. "it is not mandatory that the utxo at the plutus script address has a datum hash" what I mean to say here is you can use an inline datum instead of a datum hash.
Jimbo4350
force-pushed
the
jordan/inline-datum-integration
branch
3 times, most recently
from
4817c30
to
85439b4
Compare
Jimbo4350
force-pushed
the
jordan/inline-datum-integration
branch
from
85439b4
to
96b6144
Compare
Bit scary. It would only fail local validation so we could say that. |
Jimbo4350
force-pushed
the
jordan/inline-datum-integration
branch
from
96fa588
to
620705d
Compare
Add documentation for inline datum usage Implement inline-datum-present cli parser to indicate that an inline datum is present
Jimbo4350
force-pushed
the
jordan/inline-datum-integration
branch
from
620705d
to
be290c5
Compare
|
bors r+ |
|
Build succeeded: |
We introduce
--reference-tx-in-inline-datum-presentand--tx-in-inline-datum-presentto indicate when we are using an inline datum.