search

paritytech / txwrapper-core

Tools for FRAME chain builders to publish chain specific offline transaction generation libraries.
https://paritytech.github.io/txwrapper-core/
Apache License 2.0
77 stars 28 forks source link

Trying to understand the flow when there is a Runtime Upgrade #385

Closed HmFlashy closed 4 months ago

HmFlashy commented 4 months ago

Hello, I am here to clarify some concepts with substrate.

I wonder about runtime upgrades and what it implies.

Imagine there is a runtime upgrade for a specific chain, like KSM. I didn't upgraded the substrate library in my project. But I hardcoded the metadata because I need full offline solution.

My question is, is it retrocompatible ? If I use a new metadata but using an old version of the library. Do we agree that since the library is based on new metadata it could fail if I am using a method for which its arguments changed ? Or will it work because I passed the correct metadata and specVersion ?

Thanks

bee344 commented 4 months ago

Two things: First, this isn't the appropriate place to ask this, since it isn't related to Txwrapper. You should try https://substrate.stackexchange.com/ and you will get a better and more complete answer. Second, I don't know what you referring to as substrate library, but to know if it will work or not you should really check the changes that the runtime upgrade brings. It's always better to update, but I cannot tell without more details.

Closing this now since it's not relevant, but I suggest you ask on stackexchange to clear your doubts.