Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feed-forward tasks #29

Open
expede opened this issue Oct 16, 2023 · 0 comments
Open

Feed-forward tasks #29

expede opened this issue Oct 16, 2023 · 0 comments

Comments

@expede
Copy link
Member

expede commented Oct 16, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant