Release/v1.1.2 (#260)

* feat: add support for simple self-signed app profiles hosted on IPFS

* feat: add support for issc field in requests and on connect obj

* test: add coverage for issc/profiles

* feat: self-sign and upload profile claim to ipfs on construction

* fix: small typo in requestVerificationSignature, formatting changes

* fix: update credentials methods in tests, update credentials dep

also fix vc being passed in unsignedClaim rather than as an additional option.

* feat: move ipfs upload out of constructor

* test: create tests for ipfs upload, fix old tests to avoid upload

* fix: update profile property names to match spec

* chore: update package-lock and remove yarn.lock

* chore: update circle.yml to use npm

* feat: add profileImage, bannerImage and restructure profile claim

* test: fix uport-credentials dep to #develop to fix tests

* chore: update dependency on uport-credentials

* feat: use universal links on first request, deep links after (#214)

* chore: update .babelrc to use preset-env and transform-runtime

* 1.1.0-alpha-3

* feat: use universal links on first request, deep links after

* test: add tests for mobileTransport and URI schemes

* chore: bump version in uport-transports

* feat: add support for eip 712 sig request in Connect and Subprovider (#212)

* feat: add support for signTypedData request in subprovider and connect

* test: fix dependencies and add tests for eth_signTypedData

* chore: bump dependency on uport-transports

* test: add test for wrapped subprovider call in connect

* fix: destructure profile claim (#219)

* Fix profile claim

* Fix profile test

* Fix `sub` of profile jwt (#220)

* fix: use this.keypair.did for profile subject

* 1.1.0-alpha.5

* Revise Headings/ Move tutorial.md (#222)

* Revise Headings

I've made some adjustments to the headings to improve navigation through this document. I also made a few minor changes here and there.

* Create readme

This document was originally under guides as a tutorial, but it fits better here.

* Delete Tutorial.md

This file has been renamed to readme.md and moved to the example-tutorials folder.

* Update readme.md

A few minor changes:
* Heading capitalization
* Fixing a broken link
* Removing unnecessary content

* fix: remove dead link in README (#226)

point to developer site instead.  resolves #188
also change `requestDisclosure({})` to `requestDisclosure()`

* Feat/update eip712 (#227)

* chore: bump uport-transports to 0.1.0

* feat: replace aud with did, callbackUrl with callback

* Feat/update transports (#229)

* chore: bump transports

* 1.1.0-alpha.8

* chore: bump transports to 0.2.0-alpha.4, fix chasqui parsing

* 1.1.0-alpha.9

* Adding protocol to profile url (#234)

Looks good

* feat: add support for personal sign in Connect and Subprovider (#230)

* bump to 1.1.0-alpha.13 and update credentials/transports (#235)

* Remove usage guide from ToC

* Update issue templates (#248)

* Int/shim pubsub (#254)

* Shim the loading of pubsub-js, to not use define as a function (#252)

Looks good, thanks for the contribution! Moving to an integration branch on this repo, and will go to develop from there

* chore: use carrot dependencies

* do not convert message data type (#253)

ignoring warning for coverage reduction by 0.09%

* Better Private Chain support (#257)

* Better Private Chain support

* fix: add rpcUrl to tx, don't allow id override

* Support injected providers in UportSubprovider (#231)

* feat: add support for injected providers

* feat: add inject-loader and tests for using askProvider

* feat: add support for injected providers

* feat: add inject-loader and tests for using askProvider

* refac: move common utility functions out to ./util.js

* feat: don't show injected provider dialog on mobile, remember choices

* feat: bump to compatible transports

* fix: update deep link handling

* fix: resolved broken tests after merge

* 1.1.2-rc.0

README.md

@@ -162,6 +162,25 @@ To send transaction:
 ```javascript
 web3.eth.sendTransaction(txObj, (error, txHash) => {...})
 ```
+
+### Private Chain support
+
+While the primary uPort Credentials functionality does not tie you to any specific blockchain. You are able to request ethereum accounts for use with private ethereum compatible chains. You will need a network ID and a JSON-RPC endpoint accessible to both your browser app and the mobile client.
+
+To configure it, pass in a network object for configuration.
+
+```javascript
+const uport = new Connect('MyDAppName', {
+  network: {
+    id: '0xdeadbeef',
+    rpcUrl: 'https://mybankrpc.example.com/'
+  }
+})
+const provider = uport.getProvider()
+const web3 = new Web3(provider)
+web3.eth.getCoinbase((error, address) => { ... }) // request address for use on private chain
+```
+
 ### <a name="browser-quick-start"></a> Browser Window Quick Start
 
 For use directly in the browser you can reference the uport-connect distribution files from a number of places. They can be found in our npm package in the 'dist' folder or you can build them locally from this repo.

docs/guides/usage.md

@@ -305,4 +305,21 @@ The following calls will initiate a uPort request, by default, this will show a
 
 **Limitations**: It's important to note that because the web3 transaction handling is stateful, it requires that uPort requests and responses are handled on the same page. This means that for some mobile browsers, using a web3 object with a uport subprovider to send transactions may not work properly. Instead, for full mobile support we recommend using `Connect.sendTransaction`, or creating contracts via `Connect.contract`, and listening for responses from the mobile app with `Connect.onResponse`. _We are actively investigating more elegant solutions to seamless web3 integration. If you are a developer integrating uport-connect with web3, feel free to open an issue to discuss how to better support your use case._
 
+### <a name="private-chain"></a> Private Chain support
+
+While the primary uPort Credentials functionality does not tie you to any specific blockchain. You are able to request ethereum accounts for use with private ethereum compatible chains. You will need a network ID and a JSON-RPC endpoint accessible to both your browser app and the mobile client.
+
+To configure it, pass in a network object for configuration.
+
+```javascript
+const uport = new Connect('MyDAppName', {
+  network: {
+    id: '0xdeadbeef',
+    rpcUrl: 'https://mybankrpc.example.com/'
+  }
+})
+const provider = uport.getProvider()
+const web3 = new Web3(provider)
+web3.eth.getCoinbase((error, address) => { ... }) // request address for use on private chain
+
 ---------------------------------------------