🟢 4 • 🔴 3 • ⚪️ 0
5-member quorum not met.
Vote #1: NAY
8 available members.
No CoI reported. DV delegation exercised.
https://kusama.subscan.io/extrinsic/30221409-2
https://kusama.subsquare.io/referenda/590#3
8 available members.
🟢 5 • 🔴 3 • ⚪️ 0
5 ayes greater than the 60.0% majority threshold (4.8 votes) for the Root track.
**Vote #2: 🟢 AYE
8 available members.
No CoI reported. DV delegation exercised.
https://kusama.subscan.io/extrinsic/30337187-3
https://kusama.subsquare.io/referenda/590#10
Votes·8
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.
I believe this is to help everyone move on
Discussions·1
Hi everyone, Chris Li here, founder of Turing Network.
I want to thank you all for taking the time to review and vote on our proposal. We recognize and respect the group’s decision to vote Nay.
Just to reiterate the context: the Turing chain was shut down before we could execute the de-registration command. After that, code dependency issues and the loss of the original developers meant we couldn’t restart the chain to handle it ourselves. That’s why governance was our last resort.
Even though the result wasn’t what we hoped for, I appreciate the feedback and the chance to present our case. If anyone has thoughts on alternative paths forward, or lessons we can carry into the future, I’d be very open to hearing them.
Thanks again for your time and consideration!
By the way, if any of 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