From 5640462f9e6bb02b457421b3d4a00fc4e2a5fadd Mon Sep 17 00:00:00 2001 From: Patricio Palladino Date: Wed, 19 Jun 2019 10:24:28 -0300 Subject: [PATCH] EIP-1193: Remove web3 compatibility section 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. --- EIPS/eip-1193.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/EIPS/eip-1193.md b/EIPS/eip-1193.md index e2e51a4827d254..cd6b9629021e9b 100644 --- a/EIPS/eip-1193.md +++ b/EIPS/eip-1193.md @@ -203,10 +203,6 @@ If the network the provider is connected to changes, the provider **MUST** emit If the accounts connected to the Ethereum Provider change at any time, the Ethereum Provider **MUST** send an event with the name `accountsChanged` with args `accounts: Array` containing the accounts' addresses. -### web3.js Backwards Compatibility - -If the implementing Ethereum Provider would like to be compatible with `web3.js` prior to `1.0.0-beta38`, it **MUST** provide the method: `sendAsync(payload: Object, callback: (error: any, result: any) => void): void`. - ### Error object and codes If an Error object is returned, it **MUST** contain a human readable string message describing the error and **SHOULD** populate the `code` and `data` properties on the error object with additional error details.