-
Notifications
You must be signed in to change notification settings - Fork 90
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
nimbus author inherent mock #648
Conversation
@girazoki Does your system require |
Yes I can definitely! Yes we need that to be set in all the blocks for now. BTW I spoke to parity about being able to proof all keys that you want inside set-validation-data. This way we can just take in chopsticks whatever comes from validation-data in the previous block and modify only the keys corresponding to XCM,etc (so similar to what you are doing right now) We need a bit of time for this, but hopefully we can propose the PR to parity in the next weeks. What can I help you with? Do you want me to try a specific version? |
@girazoki test latest beta |
@ermalkaleci we have not been able to use directly the version you point at:
However after hacking a bit in the version branch we have been able to make it work and we confirm that is able to fork correctly our networks. We might need to propose one additional inherent to make it fully compatible but we can do this, as right now it seems much easier. Thanks! |
@girazoki I've pushed a new beta with the fix |
I confirm it works with our container-chains, thank you so much! As I said for the tanssi chain we need an additional inherent, but we should be able to do a PR for it. Will let you know when we have it! Once again, thank you! |
Yes, with the refactored inherent it should be straightforward |
#665 CC: @ermalkaleci |
No description provided.