wip(feat): make ecash signing a trait #5495
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
todo: deep dive on remote signing for clients / gateways |
dpc
reviewed
Oct 16, 2024
| pub use sm::*; | ||
|
|
||
| pub trait SchnorrSigner: Clone + MaybeSend + MaybeSync { |
There was a problem hiding this comment.
In case anyone ever picks it up: probably better to have a one "DynSigner" that is resonsible for all client crypto operations.
|
Closing as stale. Eventually we'll want to have it, but does not seem like a prio RN. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this my hack job of step 1 of doing if remote signing with fedimint. it took my awhile to figure out the all the
DynXand object safe stuff, documentation around that stuff could definitely be better