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

Resolving watcher input IPLD blocks #325

Open
ashwinphatak opened this issue Dec 22, 2021 · 0 comments
Open

Resolving watcher input IPLD blocks #325

ashwinphatak opened this issue Dec 22, 2021 · 0 comments

Comments

@ashwinphatak
Copy link
Collaborator

ashwinphatak commented Dec 22, 2021

  • Watchers are state machines which take IPLD blocks as input and generate IPLD blocks and "watcher blocks" (which are identical to a Blockchain's) as output. There is a "mapper" which does arbitrary transformations on the input and are written in typescript.
  • Watcher code is turing complete, so it's difficult to determine what subset of an input Ethereum block it's using in computing the derived state.
  • Watchers can also perform eth_calls to compute derived state, resulting in usage of Ethereum state/storage created over an arbitrary no. of previous Ethereum blocks.
  • Watchers are composable, so one watcher can use the data created by another.
@AFDudley AFDudley assigned AFDudley and unassigned AFDudley Dec 22, 2021
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

2 participants