Skip to content

Latest commit

 

History

History
36 lines (23 loc) · 4.73 KB

traction-overview.md

File metadata and controls

36 lines (23 loc) · 4.73 KB

Traction

What is Traction

Traction is an application built on top of ACA-Py to facilitate the provisioning and management of tenant agents. With Traction, the DITP team does not need to prepare and deploy new agent instances for each adopter: users submit a request for a tenant and are able to self check-in and manage their settings when approved.

Tenants

A tenant is a "resident" of Traction: similar to occupants of a condominium, different entities/organizations access the same resources, but remain isolated and independent.

There are several instances of Traction that can be used for different purposes:

  • Sandbox: this instance is completely self-serve and can be used for prototyping and discovery of short-lived projects. The sandbox is reset automatically, on the 1st and 15th day of the month.
  • Development: this instance would be the first step after prototyping in the sandbox and requires a request to be created in-app and reviewed by the DITP team.
  • Test and Production access can be requested the same way as for development, once the integration is ready to move further.

A Traction tenant provides full access to an Aries agent connected to pre-approved ledgers, however the functionality to become issuers is not enabled by default: a request outlining the business case/requirement to become an issuer should be submitted to DITP when the tenant request is initially created, or any time after that when integrating with credential issuance processes becomes necessary.

More information about becoming an issuer can be found here.

Ledgers

The following table describes the ledgers supported for both read and write operations, for each environment.

Environment BCovrin Test CANdy Dev CANdy Test CANdy Prod Sovrin TestNet Sovrin MainNet
Sandbox Write Read Read Read Read Read
Development Write Write Read Read Write Read
Test Write N.A. Write Read Write Read
Production N.A. N./A. N./A. Write N./A. Write

!!! info "Note" An issuer can only connect to ONE ledger in write mode at any given time. Moving to another ledger is generally not recommended and it is not supported at this time.

!!! warning "Limitations" Sovrin TestNet and MainNet ledgers are connected in write mode only for special scenarios, like temporary support of legacy issuers moving to a Traction tenant.