Self Custody Troubleshooting

Match the problem → try the fix. Still stuck? Contact support with username + tx hash.

Wrong network

Symptoms: MetaMask errors, balance “0”, or site says wrong network.

Fix:

1. Open MetaMask → network menu.
2. Select BNB Smart Chain (chain ID 56 mainnet).
3. Refresh TheBenefactor.Net and reconnect.
4. Retry the action.

Wallet won’t connect

Try:

1. Unlock MetaMask.
2. Refresh the page.
3. Disable conflicting wallet extensions temporarily.
4. Check you’re not in a private/blocked browser mode that blocks extensions.
5. Update MetaMask / browser.
6. Try another browser (Chrome/Brave/Firefox).

Verification failed (SIWE)

Try:

1. Ensure the account you sign with is the one you intend as primary.
2. Sign the exact message—don’t reject mid-flow.
3. Check system clock (large clock skew can break signatures).
4. Disconnect site in MetaMask → reconnect → verify again.
5. Clear site permission for the dapp and reconnect carefully.

Remember: verification is a signature, not a PIF transfer.

Already paid error

Meaning (varies):

• This tx hash was already recorded, or
• Feature is already paid/active, or
• You’re trying to pay again after success.

Fix:

1. Open the feature status page (banner, badge, subscription, etc.).
2. If unpaid but you already sent crypto → use Already paid / Record transaction.
3. Paste the correct 0x… hash from BscScan.
4. Do not create a second transfer “to be safe.”

Failed finalization

Meaning: MetaMask sent the tx, but the website didn’t finish recording (timeout, network, refresh).

Fix:

1. Copy tx hash from MetaMask Activity.
2. Confirm on BscScan: success, correct from, to, amount.
3. On the site: Retry record / Already paid.
4. Keep the same primary account connected.
5. Wait if the tx is still pending; finalize after confirmation.

Missing rewards

Check:

1. Mode is still Self-Custody.
2. Primary wallet is verified.
3. Reward was actually earned (rules, caps, anti-abuse).
4. BscScan for your primary address (incoming PIF).
5. In-app notifications/transaction list.

Rewards may be queued (job/worker delay). If long delay, contact support with approximate time and reward type.

Contact support

Include:

• Your username
• Wallet mode (self-custody)
• Primary address (public is OK)
• Tx hash(es)
• Screenshot of the error (no seed phrase in shots)
• What you clicked and when (timezone)

We can investigate records and chain data — we cannot restore a lost seed phrase.

FAQ

1. How long should I wait before contacting support?
For a stuck finalize: after the tx is confirmed on BscScan and retry failed. For rewards: allow reasonable processing time, then reach out with details.

2. Support asked for my seed — what now?
That’s not real support. Stop. See Security.

3. Can I cancel a confirmed on-chain payment?
No. Blockchain transfers are final. Only a wrong finalize can be fixed by recording the existing hash.

4. Where’s the full setup guide again?
Start at Getting Started or the index.