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.

Sign up for GitHub

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

Jump to bottom

Use current chainId for signTypedData instead of 3 #5

Merged
merged 1 commit into from
Jan 17, 2020
Merged

Use current chainId for signTypedData instead of 3 #5

merged 1 commit into from
Jan 17, 2020

Commits on Jan 17, 2020

  1. Use current chainId for signTypedData instead of 3 

    Instead of using the `chainId` "3" for the `signTypedData` button
(i.e. Ropsten), the test dapp will now use the `chainId` of whichever
network is currently selected (falling back to the `networkId` if there
is no `chainId`).
    @Gudahtt
    Gudahtt committed Jan 17, 2020
    Configuration menu
    Copy the full SHA
    4aa3934 View commit details
    Browse the repository at this point in the history