Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: use w3 key create instead of ucan-key ed #70

Merged
merged 1 commit into from
Jan 19, 2024

Conversation

alanshaw
Copy link
Member

Updates the docs to use the new w3 key create command instead of ucan-key ed.

Also updates docs for generating a key and delegation and using it to point to relevant docs on the docs site.

Copy link
Contributor

Copy link
Contributor

@vasco-santos vasco-santos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM ✨

Comment on lines +33 to +45
Currently the best way to generate a DID is to use the w3up JS CLI:

<Steps>
### Install w3 CLI

```sh
npm install -g @web3-storage/w3cli
```

### Generate a DID

```sh
npx ucan-key ed
w3 key create
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe leave this as ucan-key as it has fewer dependencies?

Or for the sake of go devs patience, they will still be able to use npx like npx @web3-storage/w3cli key create, as key create doesn't need any existing client state.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can confirm... npx still works

$ npx @web3-storage/w3cli key create
# did:key:z6Mkuu8gnJEe5uWPtExfwPcC8xvJQr23AmXArmqKXwBYGCEV
MgCZa59TQQ+xTk2ko+Sn+oZZ3ir9bmD6gZ5s09ubqk9I3bO0B5YAVloPr3OhRk9qSEMgV1sHaQFz6mCTeJeYrJkWxL6I=

@alanshaw alanshaw merged commit a831b39 into main Jan 19, 2024
3 checks passed
@alanshaw alanshaw deleted the feat/use-w3-key-create branch January 19, 2024 17:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants