# Whitelist of token contract addresses that legitimately accept ETH

**URL:** <https://community.metamask.com/t/whitelist-of-token-contract-addresses-that-legitimately-accept-eth/28963>\
**Category:** Feature Requests\
**Created:** [May 19, 2024, 11:57am UTC](https://community.metamask.com/t/whitelist-of-token-contract-addresses-that-legitimately-accept-eth/28963 "2024-05-19T11:57:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mars](https://dub1.discourse-cdn.com/metamask/user_avatar/community.metamask.com/mars/32/30339_2.png) [@Mars](https://community.metamask.com/u/Mars)\
**Post date:** [May 19, 2024, 11:57am UTC](https://community.metamask.com/t/whitelist-of-token-contract-addresses-that-legitimately-accept-eth/28963/1 "2024-05-19T11:57:07Z")

</div>

**Description:**

I created an NFT project back in 2021 _(on 4/20, more than 3 years ago)_ and the same contract has both all the NFT functionalities, as well as accepting ETH to mint a new one.

**BUT**

Now receiving the warning:

 ![image](https://europe1.discourse-cdn.com/metamask/original/3X/a/a/aa2a93c28e9d3846ac6d0e471a919a07055c0f1a.png)

Address on mainnet: 0x3ef61d25b2bf303de52efdd5e50698bed8f9eb8d

_(new user, unable to post the link to Etherscan)_

While in 99% cases sending ETH to token contract is not OK, there is 1% of legitimate use cases.

**Purpose:**

Some token contracts can legitimately receive ETH.

Removing the warning will enhance UI / UX.

**Extension/Mobile/Both:**

Chrome Extension, didn’t test on mobile.

**Images/Attachments:**

Default warning, already attached.

---

<div class="post-metadata">

**Author:** ![nakedwinnie](https://dub1.discourse-cdn.com/metamask/user_avatar/community.metamask.com/nakedwinnie/32/5551_2.png) [@nakedwinnie](https://community.metamask.com/u/nakedwinnie)\
**Post date:** [May 20, 2024, 2:18pm UTC](https://community.metamask.com/t/whitelist-of-token-contract-addresses-that-legitimately-accept-eth/28963/2 "2024-05-20T14:18:36Z")

</div>

Please reach out to MetaMask Support.

- Visit : [https://support.metamask.io/](https://support.metamask.io/)

- Click the large blue “start a conversation” bubble in the upper middle of page, looks like this:

 ![Screenshot 2024-05-07 145648](https://europe1.discourse-cdn.com/metamask/original/3X/0/2/02f4fd71bf189c37f85381e5575aeefdd8a906d2.png)

- This will connect you to a bot at first, answer some questions and it will open a ticket for you with an agent.

Remember - NOBODY, including from support, will ask for your secret recovery phrase or for you to input it onto any website for confirmation.

---

<div class="post-metadata">

**Author:** ![Mars](https://dub1.discourse-cdn.com/metamask/user_avatar/community.metamask.com/mars/32/30339_2.png) [@Mars](https://community.metamask.com/u/Mars)\
**Post date:** [May 21, 2024, 11:16pm UTC](https://community.metamask.com/t/whitelist-of-token-contract-addresses-that-legitimately-accept-eth/28963/3 "2024-05-21T23:16:02Z")

</div>

> [@nakedwinnie](#):
>
> Please reach out to MetaMask Support.

Are you sure?

There is a feature: `https://support.metamask.io/managing-my-tokens/moving-your-tokens/why-am-i-being-warned-about-sending-tokens-to-a-contract/`

I’m suggesting “feature request” to circumvent that, because there are some legitimate use cases.

---

<div class="post-metadata">

**Author:** ![nakedwinnie](https://dub1.discourse-cdn.com/metamask/user_avatar/community.metamask.com/nakedwinnie/32/5551_2.png) [@nakedwinnie](https://community.metamask.com/u/nakedwinnie)\
**Post date:** [May 22, 2024, 1:58pm UTC](https://community.metamask.com/t/whitelist-of-token-contract-addresses-that-legitimately-accept-eth/28963/4 "2024-05-22T13:58:34Z")

</div>

Not saying it’s a bug, but just so someone can investigate your individual case further and see why it is being flagged now