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

Key version numbers #149

Open
arlolra opened this issue Dec 3, 2016 · 5 comments
Open

Key version numbers #149

arlolra opened this issue Dec 3, 2016 · 5 comments

Comments

@arlolra
Copy link
Member

arlolra commented Dec 3, 2016

Explore key version numbers as an alternative to promises (temporary bindings, in the terminology here).

@liamsi
Copy link
Member

liamsi commented Dec 4, 2016

By key version numbers you mean sth. like having counters in the leafs for different key versions, right?

@arlolra
Copy link
Member Author

arlolra commented Dec 4, 2016

https://www.youtube.com/watch?v=Ca0BHUNoTF0&t=56m25s

@liamsi
Copy link
Member

liamsi commented Dec 4, 2016

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.

@arlolra
Copy link
Member Author

arlolra commented Dec 4, 2016

Do you know if there is a more complete write-up/spec/rfc of this ideas published somewhere?

@jcb82 would be the one to ask.

@masomel
Copy link
Member

masomel commented Dec 5, 2016

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.

@vqhuy vqhuy modified the milestone: Backlog Apr 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants