EIP-1193: Remove web3 compatibility section

[alcuadrado]

This EIP had a section describing how to be compatible with a certain beta version of web3 1.0.0. This would look fairly arbitrary to the uninformed reader. Also, it would be even weirder in the near future, as some changes to web3's versioning will be announced soon.

This PR removes that section, making the EIP independent from any particular library consuming it.

[eip-automerger]

Hi! I'm a bot, and I wanted to automerge your PR, but couldn't because of the following issue(s):

• EIP 1193 requires approval from one of (@MaiaVictor, @frozeman, @marcgarreau, @ryanio)

[alcuadrado]

Can any of the original authors do a review of this change? @frozeman maybe? Thanks!

[ryanio]

This section is important for those who are trying to create a js provider that would work with older dapps. Without providing sendAsync in the provider interface, the provider wouldn't work with any previously created dapps that rely on web3.js prior to 1.0.0-beta38.

[alcuadrado]

The current situation with web3.js is complicated. v1.0.0-beta.37 will be published as v1.0.0. v1.0.0-beta.38+ will be known as v2.x, which won't be published for some time. This comment will eventually bring even more confusion.

I'm pretty sure we are going to support this EIP in v1.x. Will get back with a confirmation.

[axic]

What is the status of this?

[alcuadrado]

The versioning change in web3.js has already happened, so this comment is now outdated. This EIP was supported in web3.js from beta.38 to beta.55 but it's not supported anymore.

MetaMask will stop supporting its older interface in Jan 13th 2020, so Web3.js 1.x will have to support this EIP. In the meantime I would just remove this section. //cc @cgewecke

[pedrouid]

Outdated - this spec has been improved in this regard

[pedrouid]

can be closed @alcuadrado