Feat: blocked user

[lionellbriones]

Jira Link

Description

How has this been tested?

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

• My code follows the code style of this project. (run lint)
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

---

Note

Medium Risk
Introduces a new modal status and error-code-specific handling (5120) that changes the login/error UI flow and state transitions. Risk is moderate because it affects user-facing authentication error handling and modal visibility logic, though it’s scoped and largely additive.

Overview
Adds a new MODAL_STATUS.BLOCKED flow that is triggered when connector errors surface error.code === 5120, storing a blockedUserConfig in modal state and rendering a dedicated blocked screen in Loader.

Plumbs blockedUserConfig from UIConfig → LoginModal state → Root → Loader, updates widget close/visibility behavior to account for BLOCKED, and extends @web3auth/no-modal errors with code 5120 plus a WalletLoginError.userBlocked() helper.

^{Reviewed by Cursor Bugbot for commit 2583007. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
web3auth-web	Ready	Preview, Comment	May 21, 2026 7:09am

[cursor]

Blocked user button has no functional action

High Severity

The handleChangeWallet callback in BlockedStatus only calls log.info("change wallet") and performs no actual action. This button is rendered prominently to blocked users (with default text "Change wallet") but clicking it does nothing. Combined with the fact that onCloseLoader for BLOCKED status hides the modal without resetting status to INITIALIZED, the user is left in a dead-end state with no functional escape path other than a full page reload.

 

^{Reviewed by Cursor Bugbot for commit e27d7d9. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 2583007. Configure here.}

[cursor]

Wrong CSS class prefix breaks BlockedStatus styling

High Severity

The BlockedStatus component uses the w3a-- prefix for all utility CSS classes (e.g., w3a--flex, w3a--text-center, w3a--bg-app-primary-600) and dark:w3a-- for dark mode. Every other component in this file and across the UI layer uses the wta: prefix for utility classes (e.g., wta:flex, wta:text-center) and wta:dark: for dark mode. The w3a-- prefix is only used in this codebase for specific named component classes like w3a--error-logo and w3a--btn, not for utility classes. This means the entire blocked user screen will render without layout, spacing, text styling, or button styling applied.

 

^{Reviewed by Cursor Bugbot for commit 2583007. Configure here.}