Orie Steele

Yep, this is a bug. https://github.com/transmute-industries/did-key.js/blob/main/packages/did-key.js/src/index.ts#L26 This file is missing the prefixes for G1 and G2 by themselves.

thanks! PRs welcome, I know these helper methods are useful, you can convert base58 to hex and then use: https://github.com/transmute-industries/did-key.js/blob/master/packages/secp256k1/src/keyUtils.ts#L93 ``` const publicKeyJwkFromPublicKeyBase58 = (base58Encoded: string) => { const publicKeyHex...

pending https://github.com/transmute-industries/did-key.js/pull/30

The convention for these is loosely modeled off of: - https://github.com/digitalbazaar/secp256k1-key-pair - https://github.com/digitalbazaar/crypto-ld/blob/master/lib/Ed25519KeyPair.js The modules might be better named `JWS` not `ES256K` and `EdDSA`... since secp256k1 both support Schnorr and...

Observed this: ``` error - unhandledRejection: { code: -32603, message: 'Unknown Error: user project is inactive\n', data: { originalError: {} } } ``` Fixed by updating the infura ethereum rpc...

Observed this, reproduced consistently when trying to resolve a DID locally. This is caused by this awkward bit: ``` useEffect(() => { async function loadPageData() { if (did !== undefined)...

After some analysis, it seems the create operation is either: 1. never anchored correctly. 2. anchored correctly but not handled correctly during resolution.

Current hypothesis is that the anchor transaction is never written... so there is never anything downloaded, so the did is never resolveable... in other words... a ledger interface issue.

``` insufficient funds for gas * price + value ``` yep.

https://ropsten.etherscan.io/address/0x0B646Bf48D4D3dAFDA28AE239480adB9Fc383A17 funding secured.