You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 14, 2021. It is now read-only.
Web3 defaults a tx with no from field to be the current selectedAddress, and this makes for some pretty obvious and clean web3.eth.sendTransaction calls.
I'd vote to loosen the enforcement of the from parameter to allow this to follow to the provider level.
The text was updated successfully, but these errors were encountered:
There are other features we might to add in the future, too, so finding a nice nimble way to revise validations could be nice.
Example:
Currently considering accepting ENS names as recipients of transactions to metamask's provider. To add this now, we would have to add this feature at the provider level, and change the validations at the library level.
- Dan
On Feb 19, 2017, at 3:27 PM, Nick Dodson ***@***.***> wrote:
I'll look into this design pattern, i think we can accommodate this fairly easily.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Web3 defaults a tx with no
from
field to be the currentselectedAddress
, and this makes for some pretty obvious and cleanweb3.eth.sendTransaction
calls.I'd vote to loosen the enforcement of the
from
parameter to allow this to follow to the provider level.The text was updated successfully, but these errors were encountered: