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

Improve the compatibility with various Web3Signer versions and configurations #3640

Merged
merged 1 commit into from
May 17, 2022

Conversation

zah
Copy link
Contributor

@zah zah commented May 17, 2022

  • Some Web3Signer versions insist on replying with text/plain messages
  • When reading blocks, the Web3Signer uses upper-case fork identifiers
    instead of lower-case identifies like the Beacon API.

…urations

* Some Web3Signer versions insist replying with text/plain messages
* When reading blocks, the Web3Signer uses upper-case fork identifiers
  instead of lower-case identifies like the Beacon API.
@zah zah merged commit 397033a into unstable May 17, 2022
@zah zah deleted the web3signer-fixes branch May 17, 2022 16:55
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.

1 participant