did-peer

Crates.iodid-peer
lib.rsdid-peer
version
sourcesrc
created_at2024-09-09 10:47:54.980181
updated_at2024-12-08 15:28:59.570579
descriptionImplementation of the did:peer method in Rust, uses the ssi crate
homepagehttps://affinidi.com/
repositoryhttps://github.com/affinidi/affinidi-did-resolver
max_upload_size
id1369135
Cargo.toml error:TOML parse error at line 19, column 1 | 19 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include`
size0
(affinidibot)

documentation

README

did-peer Rust implementation

Only supports did:peer numalgo 0,2 (did:peer:0, did:peer:2)

NOTE: serviceEndpoint.id should be an IRI (e.g. #service). Due to a limitation of the SSI Crate Document type, we must use a URI. Instead of #service we resolve to did:peer:#service

Build a WebAssembly package

Prerequisite: wasm-pack

wasm-pack build --target web --out-dir www/pkg

this places compiled wasm files into the ./www/pkg/ directory.

Serve the website locally, run from the ./www/ directory of the project python3 -m http.server

Website available here

Examples

To run examples cargo run --example <command>

Generate a random did:peer and corresponding DID document cargo run --example generate

Resolve a did:peer to a DID Document cargo run --example resolve <did:peer:2.*>

Commit count: 32

cargo fmt