Skip to content

Commit

Permalink
note about checking vrf pk thru auditor
Browse files Browse the repository at this point in the history
  • Loading branch information
sanjit-bhat committed Nov 19, 2024
1 parent f91732d commit 8a601f0
Showing 1 changed file with 14 additions and 0 deletions.
14 changes: 14 additions & 0 deletions kt/auditor.go
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,20 @@ import (
"sync"
)

/*
TODO: consider adding a simple static vrf pk check to the auditor.
i think it might be hard to justify the current vrf agreement assumption.
can't just get it from the server.
could get it from the binary, but then someone else needs to monitor
the binary versions to check that it's the same across binaries.
that's additional to monitoring for good code.
it's more straightforward if clients to audit, learn that their vrf
pk is good, and then move forward.
shouldn't be that bad to implement either, ish.
add another sigpred msg type to the auditor, which is just
a ghost var that contains the vrf pk.
*/

type Auditor struct {
mu *sync.Mutex
sk *cryptoffi.SigPrivateKey
Expand Down

0 comments on commit 8a601f0

Please sign in to comment.