Failed Login with embedde wallets

[William_G_Wydler]

• Subject: URGENT — BitHouse Production Authentication Failure and Developer Dashboard Login Loop

  We are BitHouse, Inc., operator of https://bithouse.ai, using Web3Auth / MetaMask Embedded Wallets for investor authentication.

  Our production website is stuck on “Preparing” after email verification.

  Additionally, our administrator cannot log into either the original Web3Auth dashboard or the new MetaMask Developer Dashboard. After receiving and entering a verification code, the system returns to the sign-in screen.

  We have tested:

  • Google Chrome

  • Microsoft Edge

  • Mobile phone over cellular data

  • Both developer dashboards

  All tests failed.

  Please urgently investigate whether our account has authentication restrictions, subscription issues, migration problems, or backend service errors.

  This is affecting access to our production investment platform.

  Please advise how we can restore access without affecting existing investor

  William G. Wydler
  CEO, BitHouse, Inc.Which Web3Auth/ Embedded Wallet SDK (SDK Name and

Additional diagnostic findings — BitHouse production login failure

We have isolated repeated failed JSON-RPC requests in Chrome Developer Tools on https://bithouse.ai.

Failing endpoint:
https://node-1.node.web3auth.io/sss/jrpc

Observed symptoms:

• Five failed jrpc requests with CORS errors.

• Earlier network requests returned HTTP 503.

• The Web3Auth API also returned HTTP 403 for feature-access requests.

• Email verification completes, but BitHouse remains stuck on “Preparing.”

• Login to both the original Web3Auth dashboard and MetaMask Developer Dashboard returns to the sign-in screen, including when tested on another browser and mobile cellular connection.

Please investigate the Sapphire/SSS node responses, account permissions, and authentication-session failures.

Please advise whether this requires an infrastructure fix or a BitHouse SDK configuration change.

MetaMask Support Team:

BitHouse’s investors remain unable to access their embedded wallets following the service suspension. We understand that resolving a security incident requires care, but the limited communication leaves us unable to assess our exposure or provide meaningful guidance to investors.

Please provide an update addressing:

1. Whether BitHouse’s embedded wallets, private keys, or assets are affected or potentially at risk.

2. Whether BitHouse or its investors should take any protective action now.

3. The current recovery status and estimated restoration time, if available.

4. When we can expect the next update, even if the investigation remains ongoing.

The statement that no evidence of impact to “MetaMask users” has been found does not clearly tell us whether it includes investors using MetaMask Embedded Wallets through BitHouse. Please clarify this distinction.

Please also identify a direct support contact or escalation channel for BitHouse during this incident. We need timely, actionable communication to fulfill our responsibilities to investors.

William G. Wydler
Founder & CEO
BitHouse, Inc.

[yashovardhan]

We have temporarily paused the Embedded Wallet service due to an ongoing security issue. We’ll get back to you as soon as possible with an update.

A security incident with Web3Auth Embedded Wallets

We’re aware of a security issue affecting our Embedded Wallet - Web3Auth’s services used by some third parties. We have temporarily paused the Embedded Wallet service. After an initial investigation, we’ve found no evidence that MetaMask users are impacted. We’ll share confirmed details and any steps that users of affected services need to take as soon as we have them.