Craig

:wave: @abonander Do you still intend to revisit this PR when you have time or would you be open to someone taking over? I see this is quite a long-standing...

Well, it took longer than expected but I continued the branch in my fork. It's cleaned up and pretty much finished apart from documentation. If there's any interest, you can...

This is still relevant for the Stardust UTXO DID method, perhaps more so. The DID specification on the wiki needs to detail the byte layout exactly for other implementers.

Upgrade when https://github.com/rustwasm/wasm-pack/issues/1097 is resolved.

This can be closed, we are following the new examples layout after the Stardust refactor and this contains conflicting changes.

Users are already able to sign data without relying on our code. E.g. using TweetNaCl ```ts const key = new KeyPair(KeyType.Ed25519); const seed = bs58.decode(key.private); let naclKeyPair = nacl.sign.keyPair.fromSeed(seed); let...

This comment on #660 may have been missed regarding the Stronghold bindings package namespace: https://github.com/iotaledger/identity.rs/pull/660/files#r816770207 Edit: resolved.

As per internal discussions, the following tasks were marked as either important or easy to do prior to 0.5.0. - Prefer to use `UInt8Array` rather than Base58-BTC encoded strings for...

~The comment https://github.com/iotaledger/identity.rs/pull/968#discussion_r940741266 was specifically on adding the `DID` trait methods to the `WasmCoreDID` struct (`scheme()`, `authority()`, `method()`, etc.) to match the methods of `WasmIotaDID` and `WasmStardustDID`. It's still unclear...

Changing this issue away from implementing `JcsJoseSignature2021` in favour of the existing `JsonWebSignature2020`, which is similar apart from the canonicalisation algorithm being RDF rather than JCS. This is to better...