@ixo/did-provider-x v0.0.2

Veramo SDK plugin for x/ixo DID method

ℹ️ Overview

The purpose of this @ixo/did-provider-x NPM package is to enable developers to interact with the ixo ledger using Veramo SDK, a modular and pluggable client app SDK for decentralised identity and SSI applications.

This package includes Veramo SDK Agent methods for use with the Veramo CLI NPM package. It can also be consumed as an NPM package outside Veramo CLI for building your own applications with NPM.

The package's core functionality is borrowed from Veramo Core NPM package and extends this to include ixo ledger functionality, such as creating and managing DIDs.

🧑‍💻🛠 Quick Start

These quick start steps provide the minimal configuration that you need to set Veramo CLI for use with ixo.

1. Install Veramo CLI and clone this repo

This step is exactly as described in Veramo CLI docs:

npm install -g @veramo/cli@latest
git clone https://github.com/ixofoundation/did-provider-x.git
npm install

2. Generate a new local database encryption key

By default, the did-provider-x package has a default SQLite database password, but it's a good idea to modify and change this to a new key unique to your install.

$ veramo config gen-key

X25519 raw private key (hex encoded):

4a5aeb56c7956dd6f3312e7094130a03afc060b95621fa3a86577aaf2b67cc1d

You can use this key with @veramo/kms-local#SecretBox
# or replace the default agent.yml 'dbEncryptionKey' constant

3. Configure your ixo/Cosmos account keys and RPC endpoints

Configure the following properties under the didManager section:

1. cosmosPayerMnemonic: Mnemonic associated with your ixo/Comsos SDK account. This is only stored locally, and the mnemonic is used to reconstitute the account address and keys used to pay for the transaction.
2. rpcUrl: You can specify a Cosmos SDK RPC endpoint. This endpoint is where transactions are sent to. By default, this is populated with juno-rpc.polkachu.com (for mainnet) and testnet.ixo.earth/rpc (for testnet) and devnet.ixo.earth/rpc (for devnet), but you can can modify this to a different hosted RPC endpoint for ixo or even your own local/private RPC endpoint.
3. defaultProvider (optional): The default ixo network is set to testnet to allow developers to test out network functionality. However, if you prefer, you can switch this out to mainnet or devnet instead.

4. Verify your configuration file is correct

IMPORTANT: Not possible at the moment as the package only has functionality for resolver and base provider implementation without creating own agent.

Once you've completed the steps above, verify that your Veramo configuration is accurate using the following command. If your configuration is correct, you should get a success message like the one below.

$ veramo config check -f <path/to/>agent.yml

Your Veramo configuration seems fine. An agent can be created and the 'agent.execute()' method can be called on it.

🙋 Find us here