Admin vs. Node DID Demo (using Recon)

This repository goes hand-in-hand with our YouTube video walk-through on the differences between your node DID (the identifier your node uses to authenticate to the anchor service) and your admin DID (used to authenticate to the Ceramic node itself for admin operations, including deploying models).

This demo uses the rust implementation of Ceramic.

The major themes we will cover are:

Guided Ceramic node setup (using Ceramic-One, i.e. our Rust implementation)
Where your admin DID vs node DID live in your server configurations
How to access mainnet

Getting Started

We will be using this repository for the demo to automate some parts of the process. To get started:

git clone https://github.com/ceramicstudio/did-demo && cd did-demo && npm install

Node Setup

This workshop will use our rust-ceramic implementation

You can find our external Rust-Ceramic instructions here.

Assuming we will all be operating on macs, open a new terminal and:

Install nvm (if not already installed)

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash

Select node v20:

nvm install v20
nvm use 20

Install js-ceramic (with nighly builds):

npm install --location=global @ceramicnetwork/cli@nightly

Download Rust-Ceramic from binary distribution:

MacOS

curl -LO https://github.com/ceramicnetwork/rust-ceramic/releases/download/v0.13.0/ceramic-one_aarch64-apple-darwin.tar.gz
tar zxvf ceramic-one_aarch64-apple-darwin.tar.gz

Open Finder, double click the ceramic-one.pkg file to start the install

After installation, copy the binary:

sudo cp /Applications/ceramic-one /usr/local/bin/

Linux

curl -LO https://github.com/ceramicnetwork/rust-ceramic/releases/download/v0.13.0/ceramic-one_x86_64-unknown-linux-gnu.tar.gz
tar zxvf ceramic-one_x86_64-unknown-linux-gnu.tar.gz
dpkg -i ceramic-one.deb

Generate your server configuration and admin/node DID credentials:

npm run generate

This uses the commands script I've created for you to set up your server configuration found at daemon.config.json, as well as two txt files containing credentials we'll use later on.

Start up a Postgres instance in Docker (needed when accessing mainnet):

npm run postgres

Start Ceramic-One (the Rust implementation) first before your js-Ceramic process:

npm run ceramic-one

Verify your email address and register your node did (found in node_did.txt) so your js-Ceramic process can access the anchor service:

# a. Verifying email address
curl --request POST \
  --url https://cas.3boxlabs.com/api/v0/auth/verification \
  --header 'Content-Type: application/json' \
  --data '{"email": "youremailaddress"}'

# b. Registering your node DID
curl --request POST \
  --url https://cas.3boxlabs.com/api/v0/auth/did \
  --header 'Content-Type: application/json' \
  --data '{
    "email": "youremailaddress",
	  "otp": "youronetimepasscode",
	  "dids": [
		  "yourdid"
	  ]
  }'

Finally, you can start your js-Ceramic process:

npm run ceramic

In a new terminal, store the value found in admin_seed.txt in an environment variable (this is the same seed that instatiated the did:key found in the admin-dids array in your server configuration).

read -s DID_PRIVATE_KEY #paste in the key from the previous command and hit enter
export DID_PRIVATE_KEY

Check to make sure your admin seed has been saved in that terminal instance as an environment variable:

printenv DID_PRIVATE_KEY

Finally, you can deploy your composites onto your node:

composedb composite:deploy composites.json

Learn More

To learn more about Ceramic please visit the following links

Ceramic Documentation - Learn more about the Ceramic Ecosystem.

You can check out the Create Ceramic App repo and provide us with your feedback or contributions!