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
Wire up fast-runtime feature flag for short timeouts (#210)
* Wire up fast-runtime feature flag for short timeouts
When built with --features fast-runtime, ChallengeTimeout,
SettlementTimeout, RequestTimeout, and DeregisterAnnouncementPeriod
use short block counts (3–10) instead of hours-long production values,
making provider deregistration and challenge flows practical on
previewnet.
* Enable fast-runtime by default in justfile build recipes
just start-chain and just start-paseo-chain now build with
--features fast-runtime so local testing uses short timeouts.
* Set short challenge/settlement timeouts directly; drop fast-runtime flag
Replace the fast-runtime feature gate on the timeout constants with the short
values baked directly into both the local (testnet) and paseo runtimes:
ChallengeTimeout=10, SettlementTimeout=5, RequestTimeout=3,
DeregisterAnnouncementPeriod=10 (still >= ChallengeTimeout). This makes
challenge and provider-deregistration flows practical on previewnet without a
separate feature build.
With the constants no longer feature-dependent, remove the now-dead
fast-runtime machinery: the second build.rs WASM binary, the
fast_runtime_binary module in lib.rs, the fast-runtime Cargo feature, and the
--features fast-runtime flags in the justfile build recipes. Drop the unused
time::HOURS import.
The released paseo wasm now carries the short timeouts by default; an existing
previewnet chain still needs a runtime upgrade (setCode) to pick them up.
Verified on remote: both runtimes build; cargo +nightly fmt --check, clippy -D warnings (both runtimes), taplo, and zepter all pass.
* paseo: make storage-provider parameters runtime-settable via setStorage
Convert the parameter_types! block in the paseo runtime from compile-time
`pub const` to storage-backed `pub storage`. Each value remains the default but
can now be overridden at runtime with `system.setStorage` (under sudo/governance)
without a runtime upgrade — so previewnet timings (challenge/settlement/request
timeouts, checkpoint cadence, stakes, deregister period) can be tuned live.
Each `pub storage X` reads from unhashed storage falling back to the default and
exposes X::key()/X::set(). Local (testnet) runtime is left as const.
Verified on remote: paseo runtime builds; cargo +nightly fmt --check passes.
* chore(release): v0.4.0-paseo
- storage-provider-node crate 0.3.0 -> 0.4.0 (release tag validation)
- storage-paseo-runtime crate 0.3.0 -> 0.4.0
- RuntimeVersion: spec_version 3_000 -> 4_000
Ships the paseo timeout changes (short challenge/settlement/request timeouts and
deregister period) and the storage-backed parameter_types (runtime-settable via
system.setStorage). No extrinsic encoding changes, so transaction_version stays
at 2; the spec_version bump triggers any on-chain migrations on upgrade.
---------
Co-authored-by: Branislav Kontur <bkontur@gmail.com>
0 commit comments