You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BlockHashCount is defined by the runtime and thus we cannot know for sure what an ok mortal_period is. Ideally we could fetch the BlockHashCount from the runtime and do something like find the next greatest power of two and use that as the default mortal_period
The text was updated successfully, but these errors were encountered:
emostov
changed the title
Dynamically derive default mortality from Cystem::Constants::BlockHashCounts
Dynamically derive default mortality from System::Constants::BlockHashCount
Dec 16, 2020
We can now specify the mortality. transactions default to immortal if you don't provide any params.
I could see an argument for transacitons defaulting to being mortal though, since it's a much safer default, so I guess this is still worth looking into!
Since not all extrinsics have a mortality (it's an additional property that can vary by chain (and users can configure Subxt to have whatever additional things they want), I'm thinking to close this at this point. Users can specify Mortality at least using a slightly nice API when talking to Polkadot nodes :)
BlockHashCount
is defined by the runtime and thus we cannot know for sure what an okmortal_period
is. Ideally we could fetch theBlockHashCount
from the runtime and do something like find the next greatest power of two and use that as the defaultmortal_period
Originally posted by @niklasad1 in #204 (comment)
The text was updated successfully, but these errors were encountered: