As I understand and reverse engineered, this extension injects two objects into the window scope: web3 and ethereumProvider.
Both provide some functionality to use them later with:
import Api from '@parity/api';
const api = new Api(ethereumProvider);
But since we need some parity specific features, I would like to know if these injected objects are actually from parity and not from MetaMask.
Inside parity dapps (http://127.0.0.1:8180/) the injected objects are: web3 and ethereum (note this time without the "Provider"-suffix), whereas the ethereum object has a isParity method.
Furthermore it would be nice if both injecting mechanisms inject the same stuff.
As I understand and reverse engineered, this extension injects two objects into the window scope:
web3andethereumProvider.Both provide some functionality to use them later with:
But since we need some parity specific features, I would like to know if these injected objects are actually from parity and not from MetaMask.
Inside parity dapps (http://127.0.0.1:8180/) the injected objects are:
web3andethereum(note this time without the "Provider"-suffix), whereas theethereumobject has aisParitymethod.Furthermore it would be nice if both injecting mechanisms inject the same stuff.