Something that came up with @zeeshanlakhani and earlier in the process with @Gozala is if it's possible to produce a complete Invocation from a return value. I don't think we need to ship this in the v1.0, but could easily be extended to do this in a v1.x.
A rough sketch of the idea looks roughly like this:
Pass relevant delegations to the Executor in the original Action
The Executor knows how to sign those as part of execution
e.g. either directly, or if it's running Wasm or Docker or something, they can do it inside
Add a run: [Invocation] field to the Reciept that picks these up and immedietly dispatches them
In this world, the inner Action has all of the data it needs to construct a complete Invocation down to the cryptographic signature. This is dicey if you don't have a way to keep the cryptogtraphic material off of the network (i.e. don't put it in an argument to the function, so it's inherently effectful).
Fission has plans to handle this case safely, but I don't want to ship something that can inadvertently leak cryptographic material in the meantime.
Something that came up with @zeeshanlakhani and earlier in the process with @Gozala is if it's possible to produce a complete Invocation from a return value. I don't think we need to ship this in the
v1.0, but could easily be extended to do this in av1.x.A rough sketch of the idea looks roughly like this:
run: [Invocation]field to the Reciept that picks these up and immedietly dispatches themIn this world, the inner Action has all of the data it needs to construct a complete Invocation down to the cryptographic signature. This is dicey if you don't have a way to keep the cryptogtraphic material off of the network (i.e. don't put it in an argument to the function, so it's inherently effectful).
Fission has plans to handle this case safely, but I don't want to ship something that can inadvertently leak cryptographic material in the meantime.