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

Provide a tool for doing offline validation #81

Open
bkchr opened this issue Feb 17, 2021 · 0 comments
Open

Provide a tool for doing offline validation #81

bkchr opened this issue Feb 17, 2021 · 0 comments

Comments

@bkchr
Copy link
Member

bkchr commented Feb 17, 2021

When working with blockchains it can happen that sometimes there is some non-determinism or similar problems that you don't see when building the block. In traditional blockchains you will see other nodes fail to import the block and it will be "relative" easy to debug this. When it comes to parachains, this can not be that easy. Importing the block maybe works, but it fails while being validated on the relay chain. If you encounter such a problem in a local test network, it is also relative easy to debug as you control all the nodes. However, in a fully decentralized network this gets impossible. You will not have access to the logs of the relay chain validators to check why your candidate failed to validate.

For this use case I think it would be nice to have some sort of offline validation tool. This tool takes a PoV blob, a parachain validation blob, the encoded validation params and tries to execute the PoV.

Later we also should provide a way to get a PoV from a parachain in some "easy" way.

@the-right-joyce the-right-joyce transferred this issue from paritytech/cumulus Aug 24, 2023
helin6 pushed a commit to boolnetwork/polkadot-sdk that referenced this issue Feb 5, 2024
* Document EthereumRuntimeApi

* Update readme

* Styling fixes
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Mar 26, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Mar 27, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 8, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 8, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 8, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 9, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 10, 2024
serban300 pushed a commit to serban300/polkadot-sdk that referenced this issue Apr 10, 2024
jonathanudd pushed a commit to jonathanudd/polkadot-sdk that referenced this issue Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: backlog
Development

No branches or pull requests

1 participant