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

Integrate cosmwasm module into laconicd #25

Closed
1 of 3 tasks
i-norden opened this issue Aug 31, 2022 · 6 comments
Closed
1 of 3 tasks

Integrate cosmwasm module into laconicd #25

i-norden opened this issue Aug 31, 2022 · 6 comments
Assignees

Comments

@i-norden
Copy link
Contributor

i-norden commented Aug 31, 2022

From Ashwin: Integrate the latest cosmwasm module into chiba-clonk, enabling us to run cosmwasm contracts on chain.

  • Refactor cosmwasm stack onto SDK+SMT
  • Update laconicd to load the cosmwasm module into the BaseApp
  • Deploy a CosmWASM contract and run it in the testnet
@i-norden i-norden changed the title Integrate cosmwasm module into chiba-clonk Integrate cosmwasm module into laconicd Sep 1, 2022
@i-norden
Copy link
Contributor Author

To be able to run small pieces of warm to run.

Off chain someone runs watcher, claims state root of watcher at certain height.

If someone wants to contest, they send a tx to laconic claiming an operation produced the wrong result.

On chain, we execute a small portion of the watcher execution graph (within the cosmwasm execution environment) to see that the state root produced is not as expected.

For fraud proofs in the responder group, at the L3.

@i-norden
Copy link
Contributor Author

i-norden commented Nov 29, 2022

TODO:

  • Port wasmd x/ module here, fix any dependency related breaks feat: Port x/wasm module #92
  • Set so that no accounts are authorized to create
  • Create new eval keeper method that accepts WASM bytes, executes them, returns result without storing code or result in state
  • Provided to this method is not the WASM itself, but a reference to registry record containing the registered WASM (must register before evaluating)
  • If we can cleanly cut out the unused code paths we should, but if it disrupts the remaining code such that rebasing on future releases is complicated we may want to leave them as vestigial pieces

Notes:
Figure out how we manage/guarantee access to the state necessary for the execution (parameters, but much more data than possibly can be provided as call parameters)

  • Provide content IDs (e.g. set of state roots) for the state necessary, which can be fetched from IPFS as needed.
  • Each member has some subset of the various chain's IPFS blockstores, we need some aggregated view on top of all of the blockstores so that we can perform any of the state transitions necessary for watcher evaluation.
  • Members could form a private IPFS swarm

@AFDudley
Copy link
Contributor

Should this issue be closed?

@i-norden
Copy link
Contributor Author

i-norden commented Feb 3, 2023

@AFDudley this work has not been completed yet.

@AFDudley
Copy link
Contributor

AFDudley commented Feb 3, 2023

I think your edits addressed my concerns, thank you.

@telackey
Copy link
Contributor

prathamesh0 pushed a commit to deep-stack/laconicd-deprecated that referenced this issue Jul 29, 2024
otherwise this error presents itself silently:

```
updated config is invalid: client config invalid: chain-id is empty
```

Co-authored-by: zramsay <[email protected]>
Reviewed-on: https://git.vdb.to/cerc-io/laconic2d/pulls/25
Co-authored-by: zramsay <[email protected]>
Co-committed-by: zramsay <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants