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
Obviously, the issue is not security on those chains but having the Proxy pallet allows testing on the testnets of scenarii that are in place with Proxy on the production chains.
Steps to reproduce
Try setting a proxy on the westend people chain.
The text was updated successfully, but these errors were encountered:
…s. (#5509)
Proxies are possible in the runtimes for Kusama and Polkadot but this
functionality was not previously available on testnets.
Closes#5453.
Proxies can now be used on `coretime-rococo`, `coretime-westend`,
`people-rococo` and `people-westend` in the same way as they can be on
Kusama and Polkadot chains.
The exact same proxies are configured as the production runtimes for the
respective system parachains.
…s. (#5509)
Proxies are possible in the runtimes for Kusama and Polkadot but this
functionality was not previously available on testnets.
Closes#5453.
Proxies can now be used on `coretime-rococo`, `coretime-westend`,
`people-rococo` and `people-westend` in the same way as they can be on
Kusama and Polkadot chains.
The exact same proxies are configured as the production runtimes for the
respective system parachains.
Is there an existing issue?
Experiencing problems? Have you tried our Stack Exchange first?
Description of bug
Unlike Kusama People and Polkadot People, the westend people chain does not include the
Proxy
pallet. So does also rococo people.Obviously, the issue is not security on those chains but having the Proxy pallet allows testing on the testnets of scenarii that are in place with Proxy on the production chains.
Steps to reproduce
Try setting a proxy on the
westend people
chain.The text was updated successfully, but these errors were encountered: