What is this about?
Dear MetaMask Support Team,
We are reaching out regarding a critical issue affecting our users globally, where the BDAG token is currently being flagged as “Potential Scam” within MetaMask wallets.
This warning is appearing across a wide range of user accounts and is causing significant disruption, confusion, and reputational damage to our project and community.
🔍 Important Clarification on Address Submitted
As part of our investigation and communication with Blockaid, we previously submitted the following address:
0xd8A5D6Df7F3A1d57CDC9661f4a8132E9206B00D5
We would like to clearly state:
This is one of our internal reference/presale-related addresses, provided solely to help identify and report the issue
It is not the root cause of the warning
The issue is not isolated to this address
The “Potential Scam” warning is currently being shown across multiple wallets globally, including users who are simply holding or interacting with BDAG.
This strongly indicates that the flag is being applied at a token-level, domain-level, or system-wide risk classification, rather than being tied to a single address.
🔍 Project Overview
BDAG is the native asset of the BlockDAG Network — a Layer-1 blockchain with:
A global user base across 140+ countries
Active ecosystem usage and presale participation
Public infrastructure including website, explorer, and developer tools
Multiple completed security audits (including CertiK and Halborn)
⚠️ Current Situation
Blockaid has confirmed that no malicious flags remain on their end
Despite this, MetaMask continues to display a “Potential Scam” warning across user wallets
This suggests the issue may be due to:
Cached or outdated data within MetaMask
Residual or secondary risk signals
Incomplete propagation of updated security status
🔴 Immediate Requests
We urgently request:
Removal of the “Potential Scam” Warning across all MetaMask environments
A full refresh of risk/caching layers to ensure updated Blockaid signals are applied
Investigation into any remaining triggers (token-level, domain-level, or heuristic flags)
Confirmation once fully resolved across both extension and mobile versions
📎 Additional Support
We can provide:
Screenshots from affected users
Wallet addresses showing the warning
Transaction hashes and connection flows
Direct confirmation from Blockaid
⚠️ Urgency
This issue is actively:
Affecting user trust and onboarding
Disrupting transactions and participation
Creating unnecessary concern within our community
We kindly request this be treated with highest priority and resolved as soon as possible.
We appreciate your support and look forward to your prompt response.
Best regards,
BlockDAG Network Team




Scenario
Users attempting to connect their wallets or view their balances in MetaMask are shown a “Potential Scam” warning when interacting with or holding BDAG.
This warning appears across multiple wallets and environments (browser extension and mobile), even for users who are only holding the asset and not interacting with any suspicious contracts.
The issue persists despite confirmation from Blockaid that no malicious flags remain on the submitted address or associated signals.
Scenario
A user opens MetaMask and:
Views their wallet holding BDAG
Or attempts to connect their wallet to the official platform
MetaMask displays a “Potential Scam” warning
This creates:
Immediate loss of user trust
Hesitation or abandonment of transactions
Increased support requests and confusion
The issue is not isolated to a single wallet or address, indicating a broader classification (token-level, domain-level, or cached risk signal).
Design
No response
Technical Details
Blockaid Confirmation & Resolution Status
We have been in direct communication with the Blockaid Security Team regarding this issue.
Blockaid has confirmed the following:
The submitted address has been fully reviewed
No malicious or risk flags remain on their system
Any previously associated warnings have been successfully removed
Their official response states:
“We can confirm that it no longer has any malicious flagging on our end.”
This confirms that the issue has already been resolved at the security provider level.
Given that Blockaid powers transaction security for MetaMask, the continued display of a “Potential Scam” warning strongly suggests:
A propagation delay between Blockaid and MetaMask
Cached or outdated risk data still being shown to users
Or a residual UI-level classification within MetaMask
Threat Modeling Framework
No response
Acceptance Criteria
No response
Stakeholder review needed before the work gets merged
References





What is this about?
Dear MetaMask Support Team,
We are reaching out regarding a critical issue affecting our users globally, where the BDAG token is currently being flagged as “Potential Scam” within MetaMask wallets.
This warning is appearing across a wide range of user accounts and is causing significant disruption, confusion, and reputational damage to our project and community.
🔍 Important Clarification on Address Submitted
As part of our investigation and communication with Blockaid, we previously submitted the following address:
0xd8A5D6Df7F3A1d57CDC9661f4a8132E9206B00D5
We would like to clearly state:
This is one of our internal reference/presale-related addresses, provided solely to help identify and report the issue
It is not the root cause of the warning
The issue is not isolated to this address
The “Potential Scam” warning is currently being shown across multiple wallets globally, including users who are simply holding or interacting with BDAG.
This strongly indicates that the flag is being applied at a token-level, domain-level, or system-wide risk classification, rather than being tied to a single address.
🔍 Project Overview
BDAG is the native asset of the BlockDAG Network — a Layer-1 blockchain with:
A global user base across 140+ countries
⚠️ Current Situation
Active ecosystem usage and presale participation
Public infrastructure including website, explorer, and developer tools
Multiple completed security audits (including CertiK and Halborn)
Blockaid has confirmed that no malicious flags remain on their end
Despite this, MetaMask continues to display a “Potential Scam” warning across user wallets
This suggests the issue may be due to:
Cached or outdated data within MetaMask
Residual or secondary risk signals
Incomplete propagation of updated security status
🔴 Immediate Requests
We urgently request:
Removal of the “Potential Scam” Warning across all MetaMask environments
A full refresh of risk/caching layers to ensure updated Blockaid signals are applied
Investigation into any remaining triggers (token-level, domain-level, or heuristic flags)
Confirmation once fully resolved across both extension and mobile versions
📎 Additional Support
We can provide:
Screenshots from affected users
⚠️ Urgency
Wallet addresses showing the warning
Transaction hashes and connection flows
Direct confirmation from Blockaid
This issue is actively:
Affecting user trust and onboarding
Disrupting transactions and participation
Creating unnecessary concern within our community
We kindly request this be treated with highest priority and resolved as soon as possible.
We appreciate your support and look forward to your prompt response.
Best regards,
BlockDAG Network Team
Scenario
Users attempting to connect their wallets or view their balances in MetaMask are shown a “Potential Scam” warning when interacting with or holding BDAG.
This warning appears across multiple wallets and environments (browser extension and mobile), even for users who are only holding the asset and not interacting with any suspicious contracts.
The issue persists despite confirmation from Blockaid that no malicious flags remain on the submitted address or associated signals.
Scenario
A user opens MetaMask and:
Views their wallet holding BDAG
Or attempts to connect their wallet to the official platform
MetaMask displays a “Potential Scam” warning
This creates:
Immediate loss of user trust
Hesitation or abandonment of transactions
Increased support requests and confusion
The issue is not isolated to a single wallet or address, indicating a broader classification (token-level, domain-level, or cached risk signal).
Design
No response
Technical Details
Blockaid Confirmation & Resolution Status
We have been in direct communication with the Blockaid Security Team regarding this issue.
Blockaid has confirmed the following:
The submitted address has been fully reviewed
No malicious or risk flags remain on their system
Any previously associated warnings have been successfully removed
Their official response states:
“We can confirm that it no longer has any malicious flagging on our end.”
This confirms that the issue has already been resolved at the security provider level.
Given that Blockaid powers transaction security for MetaMask, the continued display of a “Potential Scam” warning strongly suggests:
A propagation delay between Blockaid and MetaMask
Cached or outdated risk data still being shown to users
Or a residual UI-level classification within MetaMask
Threat Modeling Framework
No response
Acceptance Criteria
No response
Stakeholder review needed before the work gets merged
References