Skip to content
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

Define public key cryptography RPCs #15

Closed
3 tasks done
nchashch opened this issue Oct 24, 2024 · 2 comments · Fixed by #22
Closed
3 tasks done

Define public key cryptography RPCs #15

nchashch opened this issue Oct 24, 2024 · 2 comments · Fixed by #22
Assignees
Labels
enhancement New feature or request

Comments

@nchashch
Copy link
Collaborator

nchashch commented Oct 24, 2024

  • Ecdsa(private key) ---> public key
  • Sign( r , m ) --> s
  • Verify( P, m , s) ---> True/False

Is it secure to serve this over RPC?

@nchashch nchashch added enhancement New feature or request question Further information is requested labels Oct 24, 2024
@Ash-L2L
Copy link
Collaborator

Ash-L2L commented Oct 24, 2024

We can encrypt the connection with TLS, but that requires setting up a certificate for the server...
any custom encryption would require clients to already have the crypto facilities that this service provides. I think it is a bad idea to do this via gRPC

@nchashch
Copy link
Collaborator Author

I will just implement this for now. It is definitely good enough for regtest/testchain.

We should iron this out before going to production though.

I opened a separate issue, so we won't forget about this in the bip300301_enforcer repo:

LayerTwo-Labs/bip300301_enforcer#64

@nchashch nchashch removed the question Further information is requested label Oct 26, 2024
@nchashch nchashch self-assigned this Oct 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants