v1.0 Architecture Overview

Version 1.0 of Connext is composed of three core components. At the core of the platform is our ChannelManager, where users deposit/withdraw funds and which acts as the arbitrator for dispute resolution.

The Connext client is a Typescript interface that lets users connect to any Connext hub over HTTP.

Our Hub can be thought of as an automated implementation of the Connext client: its logic automatically manages responding to state updates, routing payments from senders to receivers, and collateralizing channels.

Architecturealt text


Indra is the core implementation repository for Connext. Indra contains ready-for-deployment code for our core contracts, client, Hub, as well as scripts needed to deploy and operate a hub in production. When deploying a hub to production, the most recent docker images will be used.

For detailed instructions on how to run the code contained within the repository see the Running your own Hub guide.

There are several modules contained within the indra repository:


The Connext Client package is a Typescript interface which is used to connect to a hub and communicate over the Connext Network. The client package is available through NPM.

Clients are ideally integrated directly at the wallet layer. This is because they contain validator code which determines, on behalf of the user, whether a given state is safe to sign. Clients can also be used via a connextProvider in a frontend environment to make calls to a hooked client that is hosted in a more trusted environment such as a wallet.

Clients contain the following functionality:

  • Depositing to a channel

  • Opening a thread to any counterparty

  • Closing a thread and automatically submitting the latest available mutually agreed update.

  • Withdrawing from a channel and automatically submitting the latest available mutually agreed update.

  • Handling a dispute.

  • Generating/signing/sending and validating/receiving state updates over HTTP. The Client takes in the address of the server that is being used to pass messages in the constructor.

Payment channel implementations need a communication layer where users can pass signed state updates to each other. The initial implementation of Connext does this through traditional server-client HTTPS requests. While this is the simplest and most effective mechanism for now, we plan to move to a synchronous message passing layer that doesn’t depend on a centralized server as soon as possible.

Further documentation on the client can be found here.


Hubs can be thought of as an automated implementation of the client. Hubs have the same functionality outlined above, and forward payments between clients.


Our payment channel contracts. Our implementation relies on a combination of the research done by a variety of organizations, including Spankchain, Finality, Althea, Magmo and CounterFactual. Comprehensive documentation are fully open source and are available here.

The contracts repository should only be used for development purposes. The latest stable version of the contracts which works with Hub and Client will always be kept in Indra. Do not modify the contracts themselves before deploying - this could break the security model of the entire protocol


This is a simple admin UI for easily analyzing recent payment and user information as a hub operator. The dashboard server is accessible at localhost:3000/api/dashboard and the UI is served from localhost:3000/dashboard/ (if running on docker).


Contains all the database migration information to be used by the docker images. Make sure that the migrations in the database module, and in the hub/migrations folder are consistent if you are making changes here.


Routing proxy and related configurations.


The card is a sample implementation of the client designed to help you bootstrap an application that integrates Connext. It contains a simple inpage wallet and payment interface, as well as a custom Web3 injection that automatically signs transactions using the inpage wallet. For developers just beginning to build their application, the card is a great way to get started; for developers looking to integrate with existing an existing app, it’s a good instructive resource for implementation and includes some components that you can easily copy over.