Two questions:

1. Why is it necessary to deregister the parachain ID?
2. Why can't the team currently run the parachain?

[@BILL](JFArxqV6rqPSwBok3zQDnj5jL6vwsZQDwYXXqb1cFygnYVt-kusama) 
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.

[@BILL](JFArxqV6rqPSwBok3zQDnj5jL6vwsZQDwYXXqb1cFygnYVt-kusama) 

By the way, if you held TUR tokens before, you can read our rationale and guides for converting them here: https://avaprotocol.org/blog/secure-your-spot-ava-protocol-legacy-token-conversion-now-open-ahead-of-tge


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 🏔](Cb3ZF5tmeTEDR44MRLAPH3agiv5ntLG6VMZ2U5x8QM3XkGY-kusama) 

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.

[@🏔 HELIKON 🏔](Cb3ZF5tmeTEDR44MRLAPH3agiv5ntLG6VMZ2U5x8QM3XkGY-kusama) 

By the way, if you held TUR tokens before, you can read our rationale and guides for converting them here: https://avaprotocol.org/blog/secure-your-spot-ava-protocol-legacy-token-conversion-now-open-ahead-of-tge


Dear Proposer,

Thank you for your proposal. Our **first** vote on this proposal is **NAY**.

The **Root** track requires **60% quorum** according to our [voting policy v0.2](https://docs.permanence.io/voting_policy/voting_policy_v0.2.html), and any referendum in which the **majority of members vote abstain receives an abstain vote**. This proposal has received **four aye and three nay** votes from **eight available members**. Below is a summary of our members' comments:

> The proposal for deregistering paraID 2114 had been reviewed by members who offered contrasting views. One participant characterized the measure as a simple act of house cleaning, implying a routine administrative update, while another raised concerns about dedicating the root track deposit to a locked parachain that was no longer active. That voter argued that occupying the root track for a para team appeared unjustified, noting that the paraID was not a scarce resource warranting such protection. Ultimately, these considerations led members to align with the governance policy that opposed the proposal.

The full discussion can be found in our [internal voting](https://voting.opensquare.io/space/permanence/proposal/QmYYJV4JoW5eVPnpe7gqgAwoxTB835QMwc5KZKJq18p77u).

Please feel free to contact us through the links below for further discussion.

Kind regards, Permanence DAO Decentralized Voices Cohort V Delegate 📅 [Book Office Hours](https://cal.com/permanencedao/office-hours) 💬 [Public Telegram](https://t.me/permanencedao) 🌐️ [Web](https://permanence.io) 🐦 [Twitter](https://twitter.com/permanencedao) 🗳️ [Delegate](https://kusama.subsquare.io/user/EicAs5s99x17qZcQzJMiBCfada9rGyEC6njfiBX3j2EPr9W/votes)

[@PERMANENCE DAO/GOV-PROXY](Fa6mLSY4Z6Uo3FakzLN6zZSdSuZYnd2zEESPikbgiSzwiBr-kusama) 

Hi PERMANENCE DAO, please see my replies in your group link: https://voting.opensquare.io/space/permanence/proposal/QmYYJV4JoW5eVPnpe7gqgAwoxTB835QMwc5KZKJq18p77u?page=last

Dear Proposer,

Thank you for your proposal. Our **second** vote on this proposal is **AYE**.

The **Root** track **requires more than 60.0% of non-abstain votes** according to our [voting policy v0.2](https://docs.permanence.io/voting_policy/voting_policy_v0.2.html), and any referendum in which the **simple majority of voters abstain, or track-specific majority of voters aye or abstain, receives an abstain vote**. This proposal has received **five aye and three nay** votes from **eight available members**. Below is a summary of our members' comments:

> The proposal sought to deregister paraID 2114 for Turing Network because the parachain, being locked and inactive, could not deregister itself. Some voters described the action as necessary housekeeping or a move to help everyone progress, while one voter expressed reservations over using the root track to hold a deposit for a neglected para team, noting that the paraID did not seem scarce enough to justify such a measure. The discussion reflected a mix of support for cleaning up unused resources and caution about misallocating core governance assets, and ultimately, the vote favored the deregistration.

The full discussion can be found in our [internal voting](https://voting.opensquare.io/space/permanence/proposal/QmYYJV4JoW5eVPnpe7gqgAwoxTB835QMwc5KZKJq18p77u).

Please feel free to contact us through the links below for further discussion.

Kind regards, Permanence DAO Decentralized Voices Cohort V Delegate 📅 [Book Office Hours](https://cal.com/permanencedao/office-hours) 💬 [Public Telegram](https://t.me/permanencedao) 🌐️ [Web](https://permanence.io) 🐦 [Twitter](https://twitter.com/permanencedao) 🗳️ [Delegate](https://kusama.subsquare.io/user/EicAs5s99x17qZcQzJMiBCfada9rGyEC6njfiBX3j2EPr9W/votes)

Technical ref. AYE.
Root Track as last resort solution seems justified.

[@🥐 Le Nexus - Office🍷](EchjXFkxkqrsuXCYLdNVT4wDrsfzenPdt5EkeiAUju4R82r-kusama) Thank you, Le Nexus! Very much appreciate it!

# 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.
![image.png](https://subsquare.infura-ipfs.io/ipfs/QmabtXUaD2KaY6HvsAJxg7uPK7CezKgmtPhEtKEhFgxR9V)

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

- Turing Network wants to deregister its parachain ID 2114.
- They can't do it themselves because the parachain is locked and not running.
- The parachain can't send the message needed to deregister itself.
- The only way to deregister it is through Kusama Governance.
- The owner of the parachain ID is asking for this change.
- The owner's account is CmxJEdEniSV6hGWoKfHWLR6h4A1dh5gD1vgzmD12osJvGsk.