Plutus Pioneer Program - Iteration #2 - Lecture #3

00:00:00 Start.
00:00:55 Script contexts.
00:07:03 Handling time.
00:22:31 A vesting example.
00:51:54 Parameterized contracts.
01:11:08 Homework.
01:20:19 Summary.

[matthiassieber]

Appreciate the work you do. Going through the program a second time helps me a lot.

[frankhampusweslien]

Thanks for updating the lectures, really helps me get up to speed with all the changes :D

[cardanodev]

Super excited to see what's the state of Plutus Application Backend on iteration #2! :D

[Drewtmulock]

Need clarification @6:08 - @7:00

"Spending Tx, Tx that spend a script output need to include the datum of that script output"
"Spending Tx always have to include the datum of the inputs they spend"

So a producing Tx that locks a UTxO at a script address needs to include the datum hash of the UTxO its locking.

A spending Tx that wants to consume a UTxO at a script address needs to include:
- The datum of the script output
- The datums of the input UTxOs its trying to consume. So the raw datum that the producing tx has a hash of but optionally the data itself.

[dominickgarey]

Great lectures! As I read up on Cabal, Nix, and Lambda Calulus, I see a lot Cardano Code snippet used as examples...Do you all know each other?!?!? In any case.. Thank you!

[JamesPratt]

At 15:53 @Lars finishes discussing TxInfoValidRange and has said that you can't specify an upper bound for time more than 36 hours from the time the transaction is submitted. Surely even if you could specify an upper bound for this range beyond 36 hours in the future it would not make any difference compared to an upper bound of 36 hours or even infinity. There is no way that a transaction would get delayed this long so that such any of these upper bounds would be reached??

[oliverrosario]

I have cloned the Plutus repo and switched to a new branch on the commit ea0ca4e9f (the one specified in lecture #1), but when I open the plutus-playground and start a simulation the default amount of lovelace for a new wallets is 10. Do I need to switch to a different commit? If so: Which one?

[FineyLeee]

Do I have to do anything else besides check out the right commit tag, run plutus-playground-server and then npm start to get the correct version running? When I do these steps locally, I get a different playground that doesn't parse the POSIXTime fields correctly (it turns them into objects).

[ew]

How can I get the information from the transaction on how much each signatory has spent in the contract? I can get all signatories, and the amount left over, but I'm finding it hard to figure out how much each spent in total.

[fuu]

Sorry not understanding what's the benefit of using the parametrised version? When we should use one or the other?