FAQ / Troubleshooting

#### 1. “I missed the 3‑minute window and got kicked. What now?”

Answer: Wait the full 15‑minute cooldown, then re‑join the group and finish the verification steps in one attempt. The timer restarts each time you successfully re‑enter the group.

---

#### 2. “I entered the wrong date of birth or chose the wrong wallet.”

Answer: Leave the group, wait 15 minutes, and re‑join. You’ll receive a new verification link where you can submit the correct DOB or connect the right wallet. VeriX always checks your latest submission—previous data is discarded.

---

#### 3. “I don’t hold enough tokens and was removed. How do I qualify?”

Answer:

1. Add the required amount of the specified token (check the pinned message for the exact minimum).

2. Wait until the 15‑minute cooldown passes.

3. Re‑join the group and complete verification again. VeriX will read your updated balance automatically.

---

#### 4. “I verified successfully, but I still can’t send messages.”

Possible causes & fixes

Cause	How to Check	Fix
Telegram flood‑control muted you	Telegram shows “slow mode”/“you can’t send messages for …”	Wait out the Telegram mute (VeriX cannot override).
Bot lost admin “Ban Users” right	Ask an admin to open Group Settings → Administrators and confirm VeriX has Ban Users permission	Admin re‑grants the permission, then manually unmutes you or asks you to re‑join after 15 min.
Verification success message was for someone else	Look for your own handle in the success announcement	Re‑click the portal link to ensure you completed the flow; if still blocked, re‑join after 15 min.

---

#### 5. “Do rule changes kick existing members?”

Answer: No. When admins update /setage, /settoken, or /setamount, only future joins must meet the new requirements. Existing verified members stay unless they leave and come back later.

---

#### 6. “Can admins bypass or manually approve a user?”

Answer: VeriX is designed for automated, equal enforcement. If you must add someone manually:

1. Temporarily disable VeriX’s Ban Users right.

2. Add the user and confirm.

3. Re‑enable Ban Users so gating resumes.

4. (Optional) Force the user to verify later by removing them and having them re‑join.

---

#### 7. “How is my personal data stored?”

Answer:

• DOB – hashed and salted; no raw birth date is stored in plaintext.

• Wallet address – kept only long enough to prove token balance, then deleted under the bot’s data‑retention policy.

• VeriX never asks for private keys or seed phrases—only a standard Sign Message.

---

#### 8. “The verification portal won’t connect to my wallet.”

Quick checks:

1. Browser extensions – ensure your CKB/xUDT wallet extension is enabled on the portal page.

2. Mobile wallet – if on mobile, use a wallet → browser deep‑link or scan the QR code if presented.

3. Network latency – slow RPC nodes can stall balance checks; retry after a minute.

4. If it still fails, capture console logs (F12) and share them with support.

---

#### 9. “What happens if VeriX goes offline?”

• New joins won't be gated until the bot is back online.

• When service is restored, only new joins will trigger verification (no mass retro‑checks).

Quick checks:

• Admin can send /mygroups command directly to VeriX. If the bot is online, it will reply with the list of groups it currently manages; if there’s no response, the service is still down.

  

---

#### 10. “Where can I get further help?”

• Pinned message – quick rules, required token amount, and official verification link from group admin.

• UTXO Global Support Telegram – live help from moderators and engineers.