Metamask-extension: URI QR ABI ETH functionality

[amirisbrown]

This is no longer 2017, add support for Ethereum contracts with existing ETH wallets by allowing EIP-67 compliant URIs for payment requests (e.g. via scanned QR code) with a data payload that includes the ABI encoded function name and encoded function arguments.

[breebeck]

It seems that this issue was closed in 2017 by MetaMask (https://github.com/MetaMask/metamask-extension/issues/1060) without any promised updates with this fix. An "advanced Section" in a separate Advanced User space with a warning to inexperienced users that "This includes more data" seems to be the way to go here. Very useful option for future ETH projects. I can't see the Opera team not being the first ETH wallet to add this eip-67 function .

[PaulHughes01]

+1
A warning when signing a transaction with data is how Ledger Nano S handles it ("has data"). Protects users while not closing off functionality that Ethereum smart contracts use.

Would love this to happen. :-)

[breebeck]

I find it most important that this is fixed for the mobile versions.

[Mc-Br1an]

hi there Metamask!

please support such wallets that can function well and be of used by many in the hopes to bring mass adoption in the Millions if not Billions of user into the ecosystem...

[Anamnesia]

Dear Metamask,

I’m part of an international team working on an Ethereum App project that needs to be able to communicate with existing Ethereum wallets _using an ABI encoded function name utilizing EIP-67._ We, as users and developers, would like support for an EIP-67 URI with a data perimeter that includes an encoded function name and the functions’ arguments. Thus, we ask if generic support for the ability to invoke functions on ETH contracts — that’s not a payable function yet still paying the GAS — can be added to already existing Ethereum wallets on the market?

We understand most wallets don’t want to enable arbitrary functions, yet are fully capable of doing such in a manner that will release them from legal liability by including it within an advanced settings area for user customization and providing a warning to the user(s) — and even preventing payable functions but allowing GAS payments to go through when interfacing with an ETH contract. May the wallet(s) choose to support implementing this with a blatant warning to the user(s) so to release the wallet providers from legal liability?

All that is being asked is if Ethereum wallets, could further support users, and developers, by supporting EIP-67 compliant URIs (e.g. via scanned QR code) with a data payload that includes the ABI encoded function name and encoded function arguments. Our team is confident that by enabling, EIP-67 compliant URIs with a data payload that includes the ABI encoded function name and encoded function arguments, will further expand the Ethereum ecosystem and aid in increased adoption via mobile users. Thus, allowing EIP-67 URIs with a data perimeter that includes an encoded function name and the functions’ arguments would be a net positive overall when implemented within mobile ETH wallets.

We're 100% completed with v1.0 of our app and have passed reviews by both iOS and Android.

Sincerely, we await your response. Thank you for your patience and energy.

Kind regards

[cryptrox]

fix this function.

[The-WRITTEN-SIGN]

please fix the epi-67 issue

[breebeck]

How to get someone assigned to this issue?

[breebeck]

Frank C. (Metamask)

Dec 12, 14:45 AST
Hi Bambi,

Thank you for reaching out to us with your feedback. It looks like a similar feature was considered in the past but later removed from our developers' backlog: https://github.com/MetaMask/metamask-extension/issues/1060.

I would recommend submitting this feature request again on our repository so our developers can share their comments directly. Also, if there are enough traction and feedback from the community for a feature request like this, then the developers can give it higher priority.

Kind regards,
Frank C.

[kmphua]

Please make this happen!

[thelandoftheliving]

Fix this issue

[KingOfCrypto]

I am also highly interested in this. Let get it done in a very secure
manner!

Love Ethereum Network

Yours,

KingOfCrypto
https://t.me/TheKingsCoiNofficial

On Fri, Dec 13, 2019, 5:42 AM Amiris [e-mail] wrote:

This is no longer 2017, add support for Ethereum contracts with existing
ETH wallets by allowing EIP-67 compliant URIs for payment requests (e.g.
via scanned QR code) with a data payload that includes the ABI encoded
function name and encoded function arguments.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/MetaMask/metamask-extension/issues/7706?email_source=notifications&email_token=ALBJ67JIWAPYWVTRP5NXZE3QYMHB7A5CNFSM4J2H3PPKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IAHHS3Q,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALBJ67NZXUEBM34UGZGGJ3DQYMHB7ANCNFSM4J2H3PPA
.

[pr0toshi]

Why has this not been done. Would a Gitcoin bounty get merged a bountys put up