VerusIDX Sub-Identity Creation Error

[constitutionalmoney]

OS & Version:
Windows 10 (latest VerusIDX release, ~3 days old)

Steps to Reproduce:

1. Bought 6 vUSDT.vETH prior to using Verus CLI.
2. Opened VerusIDX and selected Available Chains → Vrsc.
3. Attempted to create sub-ID via Get VerusIDX SubIdentity.

What Happened:

• Error message appeared:

  Failed to check funding status: RPC call failed: HTTP 500 Internal Server Error: {"result":null,"error":{"code":-8,"message":"Invalid "convertto" currency VerusIDX specified"},"id":"verusidx_16"}
  

• Bottom of the page also displayed:

  Insufficient Funds
  You need either 0.00000000 VerusIDX, 5.01 vUSDT.vETH, or 0.00000000 VRSC to create a sub-identity.
  Please acquire the necessary funds and return to this page to continue.
  

• I already had sufficient balance (6 vUSDT.vETH), but it was not recognized.

What I Expected:

• Sub-identity creation to succeed with 6 vUSDT.vETH available.
• Clear guidance on which currencies are actually required (VRSC, VerusIDX, or vUSDT.vETH).

Screenshot:

---

Suggestions & Improvements

• Functionality: Sub-identity creation using vUSDT.vETH balance is not functioning. Needs fix.

• Instructions: Clarify which token(s) are valid for funding sub-ID creation. Current message lists “0.00000000 VerusIDX” which may not be a real or usable token.

• Success/Error Messages:

  • Success message should confirm when balance is detected correctly.
  • Error message should distinguish between RPC failure vs. insufficient funds. Currently, both appear, which is confusing.

• User Education: Add tooltip or info note beside “funding requirements” explaining:

  • Which token is most reliable for sub-ID creation.

• UI/UX Improvements:

  • Remove or correct the “0.00000000 Verus” placeholder currency if it’s invalid.
  • Display detected balances directly (e.g., “Balance: 6 vUSDT.vETH available”).
  • Add explicit indicator if RPC connection failed vs. insufficient funds.