mirror of
https://github.com/sonr-io/sonr.git
synced 2026-08-02 17:31:39 +00:00
* feat: Add Enclave Usage Examples * feat(es/ucan): Add comprehensive integration tests - Create integration.test.ts with full UCAN token lifecycle testing - Cover end-to-end token creation, parsing, and validation - Test capability attenuation and delegation chains - Validate multi-algorithm support and timestamp scenarios - Implement error recovery and performance test scenarios 🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com> * No commit suggestions generated * No commit suggestions generated * chore: Remove migrated components and add migration documentation Removed all code and references for components that have been moved to separate repositories: **Moved to sonr-io/hway:** - bridge/ - HTTP service with OAuth2/OIDC/WebAuthn handlers - cmd/hway/ - Highway service binary - internal/migrations/ - PostgreSQL schema migrations **Moved to sonr-io/motr:** - cmd/motr/ - Motor worker service (WASM vault operations) - cmd/vault/ - Vault CLI tool - crypto/ - Comprehensive cryptographic library - packages/ - TypeScript SDK packages (es, sdk, ui, com, pkl) - web/auth/ - Authentication web application - web/dash/ - Dashboard web application **Updated Configuration:** - Makefile: Removed build/test/release targets for moved components - CLAUDE.md: Simplified to focus on core blockchain components - devbox.json: Removed scripts for moved services - docker-compose.yml: Removed hway, postgres, redis, auth, dash services - .github/scopes.yml: Removed CI scopes for migrated components - .goreleaser.yml: Updated release configuration **Added Migration Documentation:** - MIGRATE_HWAY.md: Comprehensive Highway service architecture and migration guide - MIGRATE_MOTR.md: Comprehensive Motor/Worker/Vault architecture and migration guide These migration documents provide complete context for setting up the new repositories including architecture diagrams, component breakdowns, API documentation, and migration checklists. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * No commit suggestions generated * chore: Remove contracts references and documentation Removed all references to the contracts directory that was migrated to a separate repository. **Changes:** - .gitignore: Removed contract-specific ignore patterns for DAO and wSNR contracts - .gitignore: Removed hway and motr binary references (already migrated) - .rgignore: Removed contracts, chains, and crypto directory references - docs/reference/contracts/: Removed DAO.mdx and wSNR.mdx documentation files This completes the cleanup of migrated components from the repository. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * docs: add crypto library migration documentation Added comprehensive migration documentation for the crypto library that was moved to sonr-io/crypto repository. This documentation provides complete context for understanding the cryptographic primitives and protocols used throughout the Sonr ecosystem. ## Key Documentation Added ### MIGRATE_CRYPTO.md Complete documentation of the crypto library covering: **Core Cryptographic Primitives** - Elliptic curve implementations (Ed25519, Secp256k1, P-256, BLS12-381, Pallas/Vesta) - Native curve arithmetic with optimized field operations - Pairing-friendly curves for BLS signatures **Multi-Party Computation (MPC)** - MPC enclave for vault key generation and management - Threshold cryptography (TECDSA, TED25519 with FROST protocol) - Distributed Key Generation (DKG) via Gennaro and FROST protocols - Secret sharing schemes (Shamir, Feldman VSS, Pedersen VSS) **Digital Signature Schemes** - BLS signatures with aggregation support - BBS+ signatures for selective disclosure - Schnorr signatures (standard and Mina/NEM variants) - ECDSA with deterministic nonce generation **Zero-Knowledge Proofs** - Bulletproofs for range proofs - Inner Product Arguments (IPA) - Batch verification support **Advanced Cryptographic Protocols** - Cryptographic accumulators for set membership proofs - Paillier homomorphic encryption - Oblivious Transfer (OT) protocols - Verifiable Random Functions (VRF) **Key Management & Identity** - DID key management with multi-chain support - Multi-algorithm public key handling - Wallet address derivation (Bitcoin, Ethereum, Cosmos, Solana, etc.) **UCAN Integration** - User-Controlled Authorization Networks - Capability delegation and attenuation - JWT-based capability tokens - MPC-enabled UCAN signing **Security Utilities** - AEAD encryption (AES-GCM, AES-SIV) - Argon2 key derivation - ECIES encryption - Secure memory handling ### MIGRATE_MOTR.md Updates Updated Motor migration documentation to clarify that the crypto library is now a separate external dependency at github.com/sonr-io/crypto v1.0.1 ## Repository Context The crypto library has been successfully migrated to its own repository and is published as a Go module. It serves as the foundational cryptographic layer for: - Sonr blockchain (snrd) - DID signatures, vault operations - Highway service (hway) - UCAN token signing, WebAuthn - Motor/Worker (motr) - MPC vault operations, threshold signatures ## Integration Impact All Sonr ecosystem components now depend on the external crypto library: ```go require github.com/sonr-io/crypto v1.0.1 ``` The migration enables independent versioning and maintenance of cryptographic primitives while maintaining security and compatibility across the ecosystem. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * No commit suggestions generated * No commit suggestions generated * No commit suggestions generated --------- Co-authored-by: Claude <noreply@anthropic.com>
130 lines
2.8 KiB
Plaintext
130 lines
2.8 KiB
Plaintext
---
|
|
title: "DID Generation and Management"
|
|
description: "Learn how to generate and manage Decentralized Identifiers (DIDs) using advanced crypto interfaces"
|
|
sidebarTitle: "Identity Generation"
|
|
icon: "signature"
|
|
---
|
|
|
|
# DID Generation Patterns
|
|
|
|
The Sonr project provides a robust and flexible DID (Decentralized Identifier) generation system supporting multiple key types and cryptographic methods.
|
|
|
|
## Supported Key Types
|
|
|
|
The `didkey.go` interface supports the following key types:
|
|
|
|
- RSA Public Keys
|
|
- Ed25519 Public Keys
|
|
- Secp256k1 Public Keys
|
|
|
|
## Basic DID Generation
|
|
|
|
### Creating a DID from a Public Key
|
|
|
|
```go
|
|
import (
|
|
"github.com/libp2p/go-libp2p/core/crypto"
|
|
"github.com/sonr-io/crypto/keys"
|
|
)
|
|
|
|
// Generate a new key pair
|
|
privateKey, publicKey, err := crypto.GenerateKeyPair(crypto.Ed25519, -1)
|
|
|
|
// Create a DID
|
|
did, err := keys.NewDID(publicKey)
|
|
```
|
|
|
|
### Parsing an Existing DID
|
|
|
|
```go
|
|
// Parse a DID string
|
|
did, err := keys.Parse("did:key:z6MkhaXgBZDvotDkL5257faiztiGiC2QtKLGTsyDFWYviJr4")
|
|
```
|
|
|
|
## Advanced DID Operations
|
|
|
|
### Address Derivation
|
|
|
|
```go
|
|
// Get a blockchain-compatible address from a DID
|
|
address, err := did.Address()
|
|
```
|
|
|
|
### Compressed Public Key Retrieval
|
|
|
|
```go
|
|
// Get a compressed public key (for Secp256k1)
|
|
compressedPubKey, err := did.CompressedPubKey()
|
|
```
|
|
|
|
## MPC Enclave DID Generation
|
|
|
|
For MPC (Multi-Party Computation) enclaves, use a specialized method:
|
|
|
|
```go
|
|
// Create a DID from MPC enclave public key bytes
|
|
did, err := keys.NewFromMPCPubKey(enclavePublicKeyBytes)
|
|
```
|
|
|
|
## DID Validation
|
|
|
|
```go
|
|
// Validate a DID format
|
|
err := keys.ValidateFormat("did:key:example123")
|
|
```
|
|
|
|
## Multicodec Support
|
|
|
|
The library supports various multicodec prefixes for different key types:
|
|
|
|
- RSA: `0x1205`
|
|
- Ed25519: `0xed`
|
|
- Secp256k1: `0xe7`
|
|
|
|
## Security Considerations
|
|
|
|
- Always generate keys using cryptographically secure methods
|
|
- Validate DIDs before using them in critical operations
|
|
- Use the appropriate key type for your security requirements
|
|
|
|
## Example: Complete DID Workflow
|
|
|
|
```go
|
|
package main
|
|
|
|
import (
|
|
"fmt"
|
|
"github.com/libp2p/go-libp2p/core/crypto"
|
|
"github.com/sonr-io/crypto/keys"
|
|
)
|
|
|
|
func main() {
|
|
// Generate a new key pair
|
|
privateKey, publicKey, err := crypto.GenerateKeyPair(crypto.Ed25519, -1)
|
|
if err != nil {
|
|
panic(err)
|
|
}
|
|
|
|
// Create a DID
|
|
did, err := keys.NewDID(publicKey)
|
|
if err != nil {
|
|
panic(err)
|
|
}
|
|
|
|
// Get the DID string
|
|
didString := did.String()
|
|
fmt.Println("Generated DID:", didString)
|
|
|
|
// Derive blockchain address
|
|
address, err := did.Address()
|
|
if err != nil {
|
|
panic(err)
|
|
}
|
|
fmt.Println("Blockchain Address:", address)
|
|
}
|
|
```
|
|
|
|
## Compatibility and Interoperability
|
|
|
|
The Sonr DID implementation follows the W3C DID specification, ensuring broad compatibility with other decentralized identity systems.
|