-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gochain web3 service WIP1 #1
base: master
Are you sure you want to change the base?
Conversation
ready$: BehaviorSubject<boolean> = new BehaviorSubject<boolean>(null); | ||
accountBalance: string; | ||
gochainWeb3: Web3; | ||
pluginWeb3: Web3; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about naming these callableWeb3
and payableWeb3
or something like that with more meaning?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jmank88 pluginWeb3 only available when user uses Metamask or TrustWallet, either private key
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure I understand. How does private key work?
I was thinking that 'callable' and 'payable' better express what is required at the call sites, where they don't care about implementation details. ThenpayableWeb3
would only be set when the ability to sign txs is available, whether that is via a plugin like Metamask/TrustWallet, or our own private key handling.
No description provided.