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

Verify that the one of the public keys set in accept_pk_set is actually the nodes public key #409

Open
DavidM-D opened this issue Jan 10, 2024 · 1 comment
Open

Verify that the one of the public keys set in accept_pk_set is actually the nodes public key #409

DavidM-D opened this issue Jan 10, 2024 · 1 comment
Assignees
@volovyks @DavidM-D
Labels
Emerging Tech Emerging Tech flying formation at Pagoda Near BOS NEAR BOS team at Pagoda

Comments

@DavidM-D
Copy link
Contributor

Description

We don't currently do this and it would make us fail faster and probably help with security
@DavidM-D DavidM-D added Near BOS NEAR BOS team at Pagoda Emerging Tech Emerging Tech flying formation at Pagoda labels Jan 10, 2024
@volovyks
Copy link
Collaborator

@DavidM-D accept_pk_set is used only in the old design (signing node). And we are checking our key there: accept_pk_set

In ksith design we have 4 types of keys (and 3 actual keys).

  • NEAR AccountId key (used to sign transactions for a contract)
  • Encryption key (used to encrypt messages between nodes)
  • Signing key (used to send signed messages between nodes)
  • Node key share

Can you please clarify what you mean?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@volovyks volovyks

@DavidM-D DavidM-D

Labels
Emerging Tech Emerging Tech flying formation at Pagoda Near BOS NEAR BOS team at Pagoda
Projects
Emerging Technologies
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@volovyks @DavidM-D