Matthias Benkort
Matthias Benkort
Not yet; I voluntarily postponed the discussion to beginning of April, where we have a wider workshop regarding node diversity and ensuring conformance between node implementations. Seems like a right...
Yup. Although I still see values in scenarios that are spreading over multiple blocks too; and especially, across epochs. There are sufficiently many things happening at epoch boundaries!
@rrruko perhaps we should consider CBOR as an encoding here? Given that I assume test vectors are mostly a mix of ledger-state and transactions?
> reworking watch to be a full blown tui kind of thing `aiken ide`
> Is it annoying? Yes but that is extremely temporary. This has been coming up a few times already though. So it seems like a sufficiently simple thing to allow...
@jmagan i don't think it is related. But the above error suggests that you are somewhere storing the MillerLoopResult in a list or a tuple? Or somehow casting it to...
Could you try annotating the pairing function with a return type of Ë‹MillerLoopResult` (it's a type available in the Prelude, imported by default). I am guessing that the type checker...
Syntax and beginning of semantic suggestion for V3: ``` // V2 / Current Situation validator(arg1: Whatever) { fn my_spend_function(datum: Datum, redeemer: Redeemer, ctx: ScriptContext) { expect Spend(utxo_ref) = ctx.purpose ......
Not in this task I believe. This is something we need to think a bit more about IMO.
Sure thing!