#run-time #parachain #relay #westend #chain #instance #glutton

no-std glutton-westend-runtime

Glutton parachain runtime. (polkadot v1.10.0)

8 releases (major breaking)

7.0.0 Apr 9, 2024
6.0.0 Mar 19, 2024
5.0.0 Feb 27, 2024
4.0.0 Feb 13, 2024
0.0.0 Nov 15, 2023

#2792 in Magic Beans

Download history 2/week @ 2024-01-19 24/week @ 2024-02-09 13/week @ 2024-02-16 150/week @ 2024-02-23 23/week @ 2024-03-01 7/week @ 2024-03-08 130/week @ 2024-03-15 18/week @ 2024-03-22 9/week @ 2024-03-29 117/week @ 2024-04-05

274 downloads per month
Used in polkadot-parachain-bin

Apache-2.0 and GPL-3.0-only

68KB
676 lines

Glutton Westend Runtime

The purpose of the Glutton parachain is to do stress testing on the Kusama network. This runtime targets the Westend runtime to allow development separate to the Kusama runtime.

There may be multiple instances of the Glutton parachain deployed and connected to its parent relay chain.

These parachains are not holding any real value. Their purpose is to stress test the network.

Governance

Glutton defers its governance (namely, its Root origin), to its Relay Chain parent, Kusama (or Westend for development purposes).

XCM

Since the main goal of Glutton is solely stress testing, the parachain will only be able receive XCM messages from the Relay Chain via DMP. This way the Glutton parachains will be able to listen for upgrades that are coming from the Relay chain.

Dependencies

~33–50MB
~855K SLoC