Brooklyn Zelenka

I think I had convinced myself when I did my rubber ducking session earlier in the thread. Shall we just mark this for inclusion in 0.10 and see what others...

☝️

Porting back here from https://github.com/ucan-wg/invocation/pull/1#issuecomment-1331754122 --- @expede In UCAN v0.10, we're going to drop the prf field so that you can construct a graph out of whatever proofs you happen...

> I would really prefer to keep them inside UCAN, even if omitted from the signature. No rush to write this at midnight PST, but can you expand on why?...

Okay, so for my own understanding: should I be able to add more proofs after the fact if the proofs written into my UCAN are all revoked/expired? ``` REVOKED V...

Ah! Indeed, it _is_ a different situation for delegation and invocation — agreed!

For invocation, for at least the `run: "*"` you need to point to some specific `[&UCAN]`. This could become `run: [&UCAN]` for the "all" case. There's some JSON examples here:...

Manually ported this change. Thanks!

Thanks! This got updated in the 1.0-rc.1 :)

Responded here: https://github.com/ucan-wg/invocation/pull/21#discussion_r1360094080 As Irakli cited above, amplification has been removed from Delegation since we can now express those cases in Invocations