How to Recover TAO from a Deregistered Subnet
Quick Overview
Section titled “Quick Overview”Use this guide to submit and track a Recover TAO request for a deregistered subnet.
- Users: follow the user checklist, submit a request, and track status.
- Admins: configure subnet visibility and review settlement requests.
Before You Start (User Checklist)
Section titled “Before You Start (User Checklist)”Complete all items before creating a request:
- Install and unlock MetaMask (for platform signing where required).
- Install and unlock Talisman (for Bittensor wallet context).
- Ensure you have enough gas balance on required networks.
- Confirm your destination Bittensor SS58 address is correct.
- Open the correct settlements environment URL.
If any prerequisite is missing, your request may fail or stay incomplete.
User Flow: Recover TAO
Section titled “User Flow: Recover TAO”Step 1: Open Recover TAO
Section titled “Step 1: Open Recover TAO”- Open the settlements portal URL in your browser.
- Connect MetaMask.
- Connect Talisman.
- Click Recover TAO in navigation.
Expected result: the deregistered subnet list appears.
Step 2: Create a Settlement Request
Section titled “Step 2: Create a Settlement Request”- Select the deregistered subnet.
- Enter settlement amount.
- Review conversion preview (fees and estimated TAO received).
- Confirm destination Bittensor SS58 address.
- Click submit/confirm and complete required wallet signature(s).
Expected result: a request is created and visible in your request history.
Request Input Reference
Section titled “Request Input Reference”| Field | Description | Required | Notes |
|---|---|---|---|
| Subnet | Selected deregistered subnet | Yes | Visible only if enabled by admin |
| Amount | Amount to settle | Yes | Numeric input |
| Conversion Preview | Fees + estimated TAO received | Auto | Display-only |
| Bittensor Address (SS58) | Destination wallet | Yes | Auto-filled or custom |
Track Your Request
Section titled “Track Your Request”Open My Request
Section titled “Open My Request”- Navigate to Recover TAO.
- Open My Request.
Expected result: current and past requests are listed with status.
Status Meanings and Next Action
Section titled “Status Meanings and Next Action”| Status | What it means | What you should do |
|---|---|---|
| Pending Approval | Request submitted and awaiting admin action | Wait and monitor status |
| TAO Settled | Request approved and settlement executed | Verify TAO in destination wallet |
| Rejected | Request was declined by admin | Review details and submit a corrected request if applicable |
If a request remains pending longer than expected, contact support with request details.
Admin Flow (Operations)
Section titled “Admin Flow (Operations)”Visibility Rule
Section titled “Visibility Rule”A subnet becomes visible to users only after admin completes all steps:
- Save subnet configuration.
- Enable Deregister On-Chain.
- Enable Claims.
If any step is not complete, the subnet does not appear in Recover TAO.
Admin Review Process
Section titled “Admin Review Process”| Step | Action | Outcome |
|---|---|---|
| 1 | Open Settlements -> Settlement Requests | Pending queue is visible |
| 2 | Click VIEW on a request | Details are reviewed |
| 3 | ACCEPT or REJECT | Status updates for user |
Admin Best-Practice Order
Section titled “Admin Best-Practice Order”| Order | Action | Why it matters |
|---|---|---|
| 1 | Save Configuration | Prevents incorrect parameters |
| 2 | Enable Deregister On-Chain | Syncs on-chain state with portal logic |
| 3 | Enable Claims | Exposes subnet only after setup is complete |
Troubleshooting
Section titled “Troubleshooting”| Issue | Likely cause | What to do now |
|---|---|---|
| Subnet not visible | Claims/Deregister toggle not enabled | Ask admin to verify all visibility steps |
| Wallet connection error | Wallet locked or wrong network context | Unlock wallets, reconnect, refresh page |
| Confirm/Submit disabled | Missing required field | Complete subnet, amount, and SS58 address |
| Transaction/signature failed | Low gas or wallet rejection | Add gas funds and retry submission |
| Request pending too long | Admin review delay | Contact support with request ID |
| TAO not visible after settlement | Wrong destination wallet or sync delay | Verify SS58 destination and refresh wallet state |
Support Escalation Checklist
Section titled “Support Escalation Checklist”Include the following when contacting support:
- Request ID
- Subnet name/ID
- Source wallet and destination SS58 address
- Current request status
- Timestamp of submission
- Screenshot (optional but helpful)
Summary
Section titled “Summary”Recover TAO is a user-initiated flow with admin approval controls:
- User submits request.
- Admin reviews and accepts/rejects.
- On approval, TAO is delivered to the destination Bittensor wallet.
- User tracks progress in My Request.