-
Notifications
You must be signed in to change notification settings - Fork 30
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
Key version numbers #149
Comments
By key version numbers you mean sth. like having counters in the leafs for different key versions, right? |
Thanks! Hmm, interesting. So basically, yes, this is a counter. The second idea is storing all different versions of the key in the leaf-node. Do you know if there is a more complete write-up/spec/rfc of this ideas published somewhere? Neither google's end2end project nor the trillian related white-paper seem to mention it. |
@jcb82 would be the one to ask. |
I had already asked Joe about this before: #13 (comment) My main concern remains the idea of maintaining a full history tree in each leaf node. |
Explore key version numbers as an alternative to promises (temporary bindings, in the terminology here).
The text was updated successfully, but these errors were encountered: