-
Notifications
You must be signed in to change notification settings - Fork 0
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
Research: Solo-Para-Bridge-POC #1
Comments
Which format are we using for cross-messages? How do we check computational problems written in different blocks of FB, given asynchronous block creation between FB and HB different block time? (randomization of block which issuing checked_ example_ if last "FB block batch" checked was between FB block n.12 and FB block n.24; are we in current "FB block batch" randomizing check between block 24 to 36)? |
Nice catch, @Lord-Nymphis
In each FB block, we will submit the result and hash of computational works done to the heavy blockchain. |
|
It's possible. |
So we should do it |
For the cross chain communication required in M2, we will use Parity's solo-para-bridge.
So it is mandatory to have a clear understanding of the following problems.
The text was updated successfully, but these errors were encountered: