uPort Protocol Specs
Clone or download

README.md

title index category type source
Uport Specs
3
specs
reference

uPort Specs

uPort is a platform for user centric identity and communication. The platform currently consists of our mobile app, Ethereum smart contracts and number of open protocols for signed messages and message flow.

Identities

An identity in uPort is really just someone or something that can sign data or transactions and also receive signed data about itself.

An identity has:

An identity can:

Identities created using the uPort Mobile App

Currently most uPort users manage their identities through our mobile app. Identities created today consist of an instance of the Proxy smart contract deployed on a supported Ethereum-compatible blockchain.

Request Flows

A request will typically be signed by a client app and sent to mobile app using this generic request flow:

Generic uPort Request Flow

We currently support the following flows:

More about request flows

Request and Response Transports

There are various ways that requests can be sent to the uPort app and how responses can be returned.

Request/Response Transports

Off-chain Messages

Most request and responses are performed privately off-chain between the different parties to a flow.

Most off-chain messages consist of signed JWTs (JSON Web Tokens) as defined in RFC 7519. Signatures are verified using our simple uPort PKI (see later in this document).

More about Off-chain Messages

On-chain Transactions

The user can sign Ethereum transactions using the mobile app.

More about Signing Ethereum transactions

uPort PKI

uPort implements a simple yet general purpose decentralized PKI system making it easy to create and verify off-chain JWT messages.

More about the uPort PKI