Blocklist removal request for qave.cc (false positive)

[lvbu1984]

Legitimate domains, IPs, IPFS hashes, or IPNS names

https://qave.cc

Please explain why this content is legitimate

qave.cc is a legitimate production website for Qave, a private file vault product.

Users sign in with their wallet, upload files through the web app, and use Qave for private storage and recovery. The wallet signature flow is used strictly for authentication.

Why we believe this is a false positive:

• MetaMask shows a “Suspicious site” warning for qave.cc during the signature request flow in production

• The same login logic does not trigger the same warning in our local environment

• Our login flow uses personal_sign, not eth_sign

• Our sign-in message has already been updated to a more complete SIWE-style format and includes:

  • domain
  • wallet address
  • statement
  • URI
  • Version
  • Chain ID
  • Nonce
  • Issued At
  • Expiration Time

• The signature is used for login only

• We do not ask for a Secret Recovery Phrase

• We do not ask for a private key

• We do not request token approval during login

• We do not trigger a blockchain transaction during login

Additional investigation we have already completed:

• We checked the production request chain and page resources and did not find unusual third-party login-time requests or suspicious external resource loading that would explain the warning
• We contacted ChainPatrol, and they confirmed that qave.cc is not currently blocked or flagged in their system
• We also removed an unused CSP allowlist entry during investigation, but the warning still remains

This issue has already delayed us for several days. Qave is very close to launch, and because users understandably interpret the MetaMask warning as a serious security risk, our launch work, communications, and promotional activities are effectively blocked until this is resolved.

We respectfully request a review of qave.cc and removal of any incorrect suspicious-site / blocklist classification if applicable.

We can provide screenshots, the exact sign-in message shown in MetaMask, network inspection results, and additional technical details immediately.

Is this a duplicate request?

• I have checked the issues page and confirmed this is not a duplicate request

[AlexHerman1]

this should be fixed now, please allow an hour or two for the change to propagate.