-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: mpc swift provider #15
Conversation
Isn't this a rehash of #8 ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please see the comments on #8. Many of the same comments apply here.
#if canImport(curveSecp256k1) import curveSecp256k1 #endif
add if canImport(curveSecp256k1)
|
||
|
||
public func sign(message: Data) throws -> Data { | ||
return try self.signer.sign(message: message) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I disagree with this.
You're pushing the tss-client from core kit into the dependencies here, where it is already a dependency. This is illustrated with all the extra deps in the tests.
What we should be doing instead in my opinion if you want to do it like this:
- Put
protocol EvmSigner
into it's own package, with basic mock for a test - Import that package here and extend the classes here to conform additionally to
EvmSigner
- Build the rest of the relevant signers, plus the tests specific to the signers, either here or in their own packages. Import the evm signer package here.
- Import the EVMSigner protocol package and relevant signer packages into core kit.
- Build tests that integrate core kit and the relevant signers, in core kit.
No description provided.