-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
move signing to external wallet #2
Comments
I have this change compelted here but I will wait for cryptidtech/multikey#3 and cryptidtech/multisig#2 to resolve before opening the PR, and the dependency tree is downstream from those deps. |
nudge @dhuseby |
I just merged the multisig PR. Thanks |
And poked Mike about the blsful update to crates.io |
just fixed the multikey one |
@DougAnderson444 I've been thinking for some time that there should be a standard protocol for activating external cryptographic services. Here's a proposal I made years ago for abstracting the cryptographic operations out of git: https://github.com/cryptidtech/git-cryptography-protocol/blob/main/Git%20Cryptography%20Protocol.md It would be cool to generalize the proposal, update the spec, and implement it in Multikey/Multisig |
FIDO is similar I think. |
Yeah that's interesting. I think ultimately something like this is what is needed as part of the evolution. I'll give it some thought. Implementing something like that would require an overhaul to the public API, likely having the user implement some signing trait that returns a future, instead of using a closure like it does now. |
multicid/src/vlad.rs
Line 186 in 891a9ba
This signing needs to be done from an external function.
The text was updated successfully, but these errors were encountered: