Skip to content
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

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
Open

gochain web3 service WIP1 #1

wants to merge 5 commits into from

Conversation

bergauz
Copy link

@bergauz bergauz commented Sep 23, 2019

No description provided.

ready$: BehaviorSubject<boolean> = new BehaviorSubject<boolean>(null);
accountBalance: string;
gochainWeb3: Web3;
pluginWeb3: Web3;
Copy link

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?

Copy link
Author

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

Copy link

@jmank88 jmank88 Sep 26, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants