Notice: Polkadot has migrated to AssetHub. Balances, data, referenda, and other on-chain activity has moved to AssetHub.Learn more
Deregister paraID 2114: Turing Network
Deregister paraID 2114: Turing Network
The following proposal is to request Kusama Governance to deregister paraID 2114, corresponding to Turing Network.
Why Governance?
There are technical ways of being able to deregister a paraID, however none of these are currently available for paraID 2114.
First of, the paraID status is locked: true. This means that the only way deregister the paraID is by sending a message from the parachain itself. However, the team can't currently run the parachain, and thus it can't send a message to the parachain to perform the needed actions.
Encoded Key Storage: 0x3fba98689ebed1138735e0e7a5a790abcd710b30bd2eab0352ddcc26417aa1946e9b797315c3ac3942080000
Therefore, the only way to currently deregister the paraID is by governance approval on the Root track.
ParaID Ownership
The paraID is owned by account CmxJEdEniSV6hGWoKfHWLR6h4A1dh5gD1vgzmD12osJvGsk (same storage item as before), which is the account sending this de-registration request.
https://kusama.subscan.io/account/CmxJEdEniSV6hGWoKfHWLR6h4A1dh5gD1vgzmD12osJvGsk
Comments (5)
Two questions:
@BILL
Hi Bill, thank you for your questions.
Chris Li, founder of Turing Network here.
The reason we can’t deregister the paraID ourselves is due to timing and miscommunication: the chain was shut down before we had the chance to run the de-registration command. After that, code dependency issues and the loss of the original developers meant we couldn’t restart the chain to send the command.
So unfortunately, governance is really our last resort to clean this up, which is why we’ve brought it here. I hope this clarifies things, and I’m happy to answer any further questions.
Hi,
It's not clear to me why the root track should be occupied to save the deposit for a para team, seemingly remaining locked due to neglect. And para id is not a scarce resource that needs to be saved. Can the proposer provide some explanation? Nay in the mean time.
Thanks,
kukabi | Helikon
@🏔 HELIKON 🏔
Hi Helikon, thank you for raising this.
Chris Li, founder of Turing Network here.
The chain was unfortunately shut down before we were able to run the de-registration command. After that point, code dependency issues and the loss of the original developers made it impossible for us to restart the chain to handle it ourselves.
That’s why we’ve had to bring this to governance. It’s really the last resort to unlock the deposit and properly close things out. I completely understand the concern about using the Root track, and I appreciate you asking for clarification. Please let me know if I can provide more detail.