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.

Sign up for GitHub

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

Jump to bottom

feat: fetch RPC public keys from API #122

Open
erhant opened this issue Sep 27, 2024 · 0 comments · May be fixed by #173
Open

feat: fetch RPC public keys from API #122

erhant opened this issue Sep 27, 2024 · 0 comments · May be fixed by #173
Assignees
@erhant
Labels
enhancement New feature or request

Comments

@erhant
Copy link
Member

erhant commented Sep 27, 2024 •
edited
Loading

Until v0.3.x, all messages are signed by a single Admin private key at the RPC nodes, besides their actual private key they store this admin key. Instead, they should sign the messages using their own private key and the compute node should recover the public key from that, and recover the PeerId from that.

If this PeerId is trusted by the API, it is a valid message.
@erhant erhant added the enhancement New feature or request label Sep 27, 2024
@erhant erhant mentioned this issue Sep 27, 2024
Closed
@erhant erhant self-assigned this Jan 16, 2025
@erhant erhant linked a pull request Jan 23, 2025 that will close this issue
Draft
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@erhant erhant

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: v0.3 firstbatchxyz/dkn-compute-node
1 participant
@erhant