Metamask error: request may not be secure - security provider did not verify this request proceed with caution

Smart Contracts
1

Dear Zeppelins:

We have deployed smart contracts on polygon's mainnet network from our project.

But from time to time when interacting with them the following message appears in the metamask intermittently for some users:

‘Metamask error: request may not be secure - security provider did not verify this request proceed with caution’.

These messages are very scary.
My questions are as follows:

Which security provider has failed?
Do you mean the node used?

Our contracts are honest but this does not help to make them look that way.

What can we do to stop these messages from appearing?
Or at any rate,
What settings should be made in the metamask so that it does not fail its security check?

Imagen de WhatsApp 2024-11-24 a las 19.15.00_9fa8e01b
Imagen de WhatsApp 2024-11-24 a las 19.15.00_9fa8e01b432×768 61.2 KB

3

What is this support for?

Does it belong to openzeppellin?

4

Yes it does. Did you get your issue resolved?

5

No, I am looking for an explanation.

I created this post for that.

This is not a problem I have, but a problem our users have when interacting with our contracts.

We want to know the cause. If it is because of the polygon node or the metamask or if it is because of the type of contracts.

If anyone knows what the cause is I would be happy to read it here.

6

I think this is a report by Blockaid. You can look at this article for more details: https://support.metamask.io/privacy-and-security/how-to-turn-on-security-alerts/

1 Like