Supporting this proposal means you agree that, Kusama implements a "Polkadot-friendly JAM upgrade" with full standard configuration, designed for Polkadot to eventually join and share security costs.
Like Polkadot did with ref#682, it's time for Kusama to take a stance towards JAM. The problem is, the costs of running a full JAM instance are too high for Kusama's small economy, so we either run a smaller instance(optimized for new use cases with 1sec finality)((Opt.A)) or hope for Polkadot to agree to share the same instance to split the cost between the 2 economies.
To avoid KSM bias and attract Polkadot participation token holders can later decide:
Requires governance approval from both ecosystems and fair economic arrangements acceptable to both communities.
Creates precedent for multi-ecosystem JAM instances, positioning both networks as pioneers of shared security models in the JAM era.
Supporting this proposal means you agree that, Kusama implements a "Polkadot-friendly JAM upgrade" with full standard configuration, designed for Polkadot to eventually join and share security costs.
Like Polkadot did with ref#682, it's time for Kusama to take a stance towards JAM. The problem is, the costs of running a full JAM instance are too high for Kusama's small economy, so we either run a smaller instance(optimized for new use cases with 1sec finality)((Opt.A)) or hope for Polkadot to agree to share the same instance to split the cost between the 2 economies.
To avoid KSM bias and attract Polkadot participation token holders can later decide:
Requires governance approval from both ecosystems and fair economic arrangements acceptable to both communities.
Creates precedent for multi-ecosystem JAM instances, positioning both networks as pioneers of shared security models in the JAM era.