Creating an Organization

After creating an account with WalliD and defining a name fot the organization on the CertiShop dashboard, our backend begins the process of establishing the organization as a Certificate Authority (CA) on a DID protocol. This involves interacting with Walt.ID's API to generate a Decentralized Identifier (DID) for the organization.

1. Call to Walt.ID's API:

   • Once the organization’s name is set in the dashboard, WalliD’s backend makes a call to Walt.ID's Onboard Issuer API. This API handles the creation of a DID (public identifier) and associated DID key using Walt.ID's cryptographic algorithms. You can refer to Walt.ID documentation for more details on their cryptography processes.

2. DID Generation:

   • Walt.ID returns a unique public DID (Decentralized Identifier) and a private DIDKey specific to the newly created CA. These elements are essential for ensuring that any certificates issued by this organization can be verified cryptographically across decentralized networks.

---

Wallet Generation Transactions

In addition to generating the DID, the backend performs the following operations:

1. Wallet Creation:

   • For each issuer (i.e., organization acting as a CA), the WalliD backend generates unique wallets. These wallets are used to manage the cryptographic keys and transactions associated with certificate issuance and verification.

2. Server-Side Wallet Management:

   • The wallets are managed server-side by WalliD. However, control remains with the issuer: only the credentials used to create the organization’s account can authorize the use of the wallet. This ensures that while WalliD abstracts the complexity, the organization retains control over the issuance and use of their credentials.

3. Transaction Management:

   • WalliD takes responsibility for managing all the transactions related to certificate issuance and verification. This includes signing certificates, verifying the chain of trust, and ensuring the integrity of the certificate.

4. Transparent to the User:

   • All backend interactions with the DID protocol, cryptographic operations, and wallet transactions are handled transparently. The organization does not need to interact directly with the blockchain or understand the underlying protocol mechanics. Everything happens behind the scenes, allowing the organization to focus on issuing and managing their certificates without friction.