New EthereumProvider standard (EIP-1193) breaks this library
See original GitHub issueAs of web3 1.0.0-beta.38, this library no longer works. They’ve updated and standardized the EthereumProvider API, and it uses send() instead of sendAsync().
The result is that all web3 calls throw an error “synchronous requests not supported”.
See: https://github.com/ethereum/EIPs/blob/master/EIPS/eip-1193.md
The breaking web3 version: https://github.com/ethereum/web3.js/releases/tag/v1.0.0-beta.38
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:8 (7 by maintainers)
Top Results From Across the Web
EIP-1193: Ethereum Provider JavaScript API
This EIP formalizes an Ethereum Provider API to promote wallet interoperability. The API is designed to be minimal, event-driven, ...
Read more >EIP-5749: The 'window.evmproviders' object
Abstract A Javascript Ethereum Provider interface injection that will allow for the interoperability of multiple browser wallets at the same time.
Read more >What is Metamask's ethereum.window object? - Stack Overflow
MetaMask states in their docs that the extension implements the EIP-1193: Ethereum Provider JavaScript API. It's a standardized set of rules ...
Read more >Breaking Changes to the MetaMask Inpage Provider - Medium
This post will be updated once the new API is available. ... which new provider standards like EIP 1102 and EIP 1193 take...
Read more >What is the standart for "params" in EIP-1193 (Ethereum ...
Read the relevant docs here and here. In regards to eth_sign and eth_signTypedData , which were implemented in EIP712, these params are ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Ill add that
EIP-1193status isDraftand that I cant advocate for it unless it requires backwards compatibiliyDoes that mean this repository is obsolete? If so, it should make sense stating that in the readme.