In3 Client integration

[chirag-parmar]

Pretext:

Slock.it just released the first stable version of its blockchain client, INCUBED (IN3). INCUBED unlike Infura connects to the Ethereum Blockchain via an INcentivized Node Network which incentivises and distributes the trust on remote nodes while still keeping the bandwidth and storage requirements low. Such a client fits the requirements of wallets like portis.

New Functionality:

Normal usage(Current)

import Portis from '@portis/web3';
import Web3 from 'web3';

const portis = new Portis('YOUR_DAPP_ID', 'mainnet');
const web3 = new Web3(portis.provider);

Using IN3

const in3Config = {
  chainId: 'kovan',
  requestCount: 5,
  minDeposit: 0.01
}

const portis = new Portis('dapp-id', in3Config, {useIn3: true});
const web3 = new Web3(portis.provider);

Code Changes:

1. Addition of extra flag to options parameter of the constructor. This flag is used to switch on/off in3.

interface IOptions {
  scope?: Scope[];
  gasRelay?: boolean;
  registerPageByDefault?: boolean;
  pocketDevId?: string;
  useIn3?: boolean;
}

2. Function signature change for networkAdapter to include extra boolean parameter to handle in3 networks.

New Signature: networkAdapter(network: string | INetwork, gasRelay?: boolean, useIn3?: boolean)

3. Function signature change for changeNetwork to include extra boolean parameter to handle in3 networks.

New Signature: changeNetwork(network: string | INetwork, gasRelay?: boolean, useIn3?: boolean)

4. Functionality Change: In3 is provided as an alternative to pocket and infura(iframe). So developer cannot turn on in3 and pocket/infura at the same time.

NOTE: None of the changes are breaking.

Dependency Changes:

1. Added In3Subprovider to the portis web3 provider engine library. See pull request 4

Config Changes:

1. Added source map plugin to webpack config for better debugging.

Possible Improvements: (with the help of Portis Team).

1. The property of nodeUrl is internally used in the iframe for infura communication. If we can remove this dependency of infura in the iframe and somehow relay the requests from inside of iframe to the in3 client it would make the flow much more smoother and code much more cleaner.
2. The SDK requires tests.

Links:

• Read the Docs
• Release Blog
• How IN3 Works

[chirag-parmar]

Well it's been two months since I posted this pull request. Since I see no interest from your side I'll take the liberty in assuming that you don't see IN3 client as a game changer for your wallet. Let me know if I should close this pull request already.