This section is still under construction
The Connext client needs to run in a trusted execution environment because it contains functionality to automatically sign on behalf of an end user. Decentralized applications then need to be able to make hooked calls to a user’s client similarly to how existing hooked Ethereum RPC calls occur.
In other words, the Connext client behaves similar to web3: it can be instantiated both within the wallet by passing in signer functionality or instantiated within decentralized applications using a ChannelProvider.
The object used to instantiate the Connext client contains the following fields:
|rpcProviderUrl||String||the Web3 provider URL used by the client|
|nodeUrl||String||url of the node|
|mnemonic||String||(optional) Mnemonic of the signing wallet|
|store||object||Maps to set/get from CF|
|logLevel?||number||Depth of logging|