acolytec3
acolytec3
I'm starting to dig into an interface based approach to the session/keys/crypto stuff and this is kind of what I'm thinking. I'd like to remove the `v4` file and `enrKeyPair`...
@wemeetagain and I met today and talked through this PR and at this point, there doesn't seem like a viable path forward for implementing a crypto interface for the `secp256k1`...
One more note on this. I was finally able to get webpack to find the correct `bcrypto` bindings in the browser by adding a new environmental variable to explicitly tell...
I still vote to drop bcrypto at the earliest opportunity but that may be tricky with secp256k1 until you allow for an interface to be passed in.
If there is, I can explore implementing it following the spec outlined by Piper for `discv5`.
What's your use case with this library? We no longer maintain this library and this same functionality should be available in `ethers` via the `ethers.wallet.fromEncryptedJson` method call. If that's not...
> I've got a keystore file from when I staked 2 years ago. I have the password and the keystore tests as valid, but I'm trying to get the privatekey/mnemonic...
Would it make more sense to update this package to use a different WASM toolchain perhaps? I'm not super knowledgeable on rust but it looks like the `emscripten` target is...
Note to self, finish this up.
Hmm, ok, we'll have to look and see if this is feasible. "Should be" but we haven't touched the radius stuff in a while.