An agent is a software program that controls wallets, keys, credentials, and other information on your behalf. In order to use Trinsic in any capacity, whether as an organization issuing credentials or a person storing credentials, you'll need an agent.
You can read more about the Sovrin Foundation's definition of agent here.
In Trinsic, your agency is the set of agents that you control. Your Trinsic account enables you to create as many agents as you'd like. We call institutional/enterprise agents (capable of issuing and verifying credentials) organizations.
A connection is a peer-to-peer relationship using a pairwise key exchange. It is the most secure way to offer, issue, and verify credentials.
The process of establishing connections is described in Aries RFC 0023: DID Exchange Protocol 1.0
From the Sovrin Glossary:
A digital assertion containing a set of Claims made by an Entity about itself or another Entity. Credentials are a subset of Identity Data. A Credential is based on a Credential Definition. The Entity described by the Claims is called the Subject of the Credential. The Entity creating the Credential is called the Issuer. The Entity holding the issued Credential is called the Holder. If the Credential supports Zero Knowledge Proofs, the Holder is also called the Prover. The Entity to whom a Credential is presented is generally called the Relying Party, and specifically called the Verifier if the Credential is a Verifiable Credential. Once issued, a Credential is typically stored by an Agent. (In Sovrin Infrastructure, Credentials are not stored on the Sovrin Ledger.) Examples of Credentials include college transcripts, driver licenses, health insurance cards, and building permits. See also Verifiable Credential.
Decentralized Identifiers (DIDs)
Decentralized identifiers (DIDs) are a new type of identifier that enables verifiable, decentralized digital identity. A DID identifies any subject (e.g., a person, organization, thing, data model, abstract entity, etc.) that the controller of the DID decides that it identifies. These new identifiers are designed to enable the controller of a DID to prove control over it and to be implemented independently of any centralized registry, identity provider, or certificate authority.
Trinsic charges a low, usage-based fee for the services we provide. We measure your usage based on incoming and outgoing DIDComm, which is the protocol by which two or more SSI agents communicate. Every action our tools enable, whether it be creating secure connections or verifying a proof presentation, uses some number of DIDComm. You can read more about DIDComm and our pricing model, as well as available plans, here.
An organization is an institutional/enterprise agent with the capability to issue and verify credentials.
Self-sovereign Identity (SSI)
From the Sovrin Glossary:
"An identity system architecture based on the core principle that Identity Owners have the right to permanently control one or more Identifiers together with the usage of the associated Identity Data. The Sovrin Governance Framework specifies two types of Identity Owners: Independents, who do not need to rely on any external administrative authority; and Dependents, who need to rely on a Guardian."
Tenant is synonymous with organization. It is an issuing or verifying entity that you control.
Verifiable Credentials (VCs)
A verifiable credential is a digital document that holds instantly verifiable information about something.
From the W3C Verifiable Credentials Data Model:
Credentials are a part of our daily lives; driver's licenses are used to assert that we are capable of operating a motor vehicle, university degrees can be used to assert our level of education, and government-issued passports enable us to travel between countries. This specification provides a mechanism to express these sorts of credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable.
As part of daily life, we need to prove things about ourselves regularly. Whether that is proof we can operate a vehicle, get into a bar, or do brain surgery, we use credentials to document the verifiable information about ourselves. As similar activities move to the internet, there still exists a serious need to instantly verify information about individuals (e.g. about their location, accomplishments, experience, etc). From educational records to payment account access, the next generation of web applications will need to verify this information in an easy way.
Read more about the Verifiable Credentials Data Model here.
The data structure that is sent from the verifier to the holder which describes requested information and conditions about a credential. Also know as a Proof Request, the structure of verifications can be understand with the Present Proof Aries RFC