If substituting web3.js for MetaMask, does it also track users' IP address?

Question

MetaMask now monitors users' IP addresses, even blocking users from US-sanctioned countries via its backbone, Infura, which is apparently an Ethereum node.

In the thread below, it was proven that web3.js coding can substitute for all MetaMask functions such as check balance, send transfer and contract interactions.

• Why would I use Metamask instead of only using Web3.js in the browser?

Question: If you substitute MetaMask with web3.js to carry out all the same functions for your wallet, does web3.js, or the UI clients for web3.js, also somehow use surveillance on its users?

From what I understand, you need to install node.js in order to use web3.js, which people often connect by default to the Infura node. As mentioned above, Infura node is the same node that MetaMask runs on, known to police user activity.

Answer 1

dev advocate at Chainstack here!

To answer this question:

Question: If you substitute MetaMask with web3.js to carry out all the same functions for your wallet, does web3.js, or the UI clients for web3.js, also somehow use surveillance on its users?

You could use web3.js to create your 'personal' wallet app and control the information sent to the node provider, but this would surely be highly impractical!

If you are worried about privacy, the best option would be to use an alternative to MetaMask. There are several, and I think that the frame wallet will be a great alternative for your use case.

These are some features:

• frame allows you to add multiple RPC endpoints to your network list; you can have primary and secondary RPC endpoints.
• It allows you to set up 'read-only' accounts to interact with any DApp without risking losing funds if you authorize a malicious smart contract.
• You can choose to inject the frame wallet in your browser as MetaMask, so you can also interact with DApps that only support MetaMask

Note that it uses Infura by default, but there is a fix for that :)

You can use Chainstack to power your wallet and DApps. Chainstack supports multiple EVM chains and DOES NOT collect user info such as IP address, location, etc.

Also, Chainstack DOES NOT block connections based on location or the DApp you are trying to interact with. So you will not have the problem of being blocked.

Check out this article about setting up the Helios light client with Chainstack; Helios doesn't really mitigate this privacy issue, but the article explains more about how to use Chainstack and the frame wallet!

You can also use Chainstack with MetaMask if you want to keep MM!

I hope this helps you!

Answer 2

I think there are a few concepts being mixed here:

1. You can get the same functionality metamask has with web3.js, which means you can "build your own wallet". But the question is: your users might already have a metamask wallet, and connecting your UI to metamask means users can sign and send transaction from their existing wallets, which is very convenient and users trust it.

2. If you don't want to rely on Metamask, then you can go down the route of building your own wallet inside your DApp. If that's the case, you don't actually need nodejs: most browsers can provide most functionality that the web3.js library needs (browser-crypto or something like that). The reason you need a Ethereum Node (RPC endpoint) (e.g. infura, alchemy or your own node) has nothing to do with nodeJs. A ethereum node is needed for you to get access to all the shared information on the blockchain, also when you want to broadcast transations. Without a RPC provider, you can't talk to the blockchain.

3. Most PRC Nodes are under the same compliance rule (infura and alchemy), they would refuse to help you relay your transaction if you're from a restricted IP, or if you're trying to interact with sanctioned APP like Tornado Cash. You need to find some smaller providers if you want to bypass the blocking, you can always host your own node.

Answer 3

nd, you need to install node.js in order to use web3.js, which people often connect by default to the Infura node. As mentioned above, Infura node is the same node that MetaMask runs on, known to police user activity.

If you are worried about tracking run your own node.

MetaMask internally uses Infura because both of MetaMask and Infura are Consensys companies.