Manifold triggers new version of Temple wallet instead of MetaMask, unless their extension is disabled.
I contacted the Temple development team (MadFish) on Telegram, asking them to offer a switch to turn off Ethereum features from their new version. They refused, claiming this is Manifold’s fault, asking me to bring up the issue to you, because they won’t, even though I said that no matter whose fault it was, the issue should be fixed for their users, as Manifold is much used in the Ethereum world, and many of their users are exposed to the issue (as many have told me).
This is what Temple dev team says:
“It seems there is some issue on manifold dapp side. It seems like the connect method have some “confusion” in which wallet is “Metamask” exactly.
After the 2.0.6 update the solution for such issue was implemented and on similar dapps Temple got proper UX to avoid miss-connection.”
To show the extent of the issue, consider that the website of Robness’ new project (https://auroma.online/) mentions it as a big warning on the main page.
Yeah, getting the same issue but for Metamask. Always triggered the metamask wallet instead of others.. Cant connect my account if not using metamask.
For the studio. there are no issue, but for manifold.xyz still bothering… Could you please use the same connection for manifold.xyz as for the studio?
I’ve run more tests. About 50% of all random Ethereum websites I’ve tried trigger the same hijacking behaviour: proof.xyz, marketplace.forgottenrunes (.com), venus.pboy-art (.com), dokidoki (.com), samsy.ninja/nocompute/, getpixls (.com), and many more
Worse of all, when using niftygateway.com, Temple offers to choose the wallet between Temple and Metamask—so Temple still hijacks—but when Metamask is chosen, connection fails, and the setting is not remembered. Since this selection screen is the fix that was supposed to be implemented, I believe it is absolutely an attempt to hijack the connection and force us to uninstall Metamask. So I’m posting here to give a chance to Manifold devs to answer to the claims of Temple’s dev team that it’s their fault of implementing connection with an old buggy framework. And they’ve worked so much on ignoring the issue, we can all safely assume it’s time to switch to Kukai or any alternative you can find.
For the record, I warned MadFish more than a month ago. They answered “We are not hijacking. If you click on MetaMask and Temple opens, it means the website that you are using did NOT update the wallet connection framework to the latest version.” which blames Manifold and other websites. I asked that it’s possible to disable Ethereum since they should not expect 50% of websites to update their code for their v2. they answered “it is a known caveat, and of course, we will fix this in the next update”. It was not fixed, and the actual wallet-selection pseudo-fix confirms their intention to front-run Metamask connections.