-
Notifications
You must be signed in to change notification settings - Fork 106
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
Tree phase comments #124
Tree phase comments #124
Conversation
// The public-key | ||
PubKey abstract.Point | ||
// The private-key - mostly for ourselves | ||
PrivKey abstract.Secret |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this should be in the Peer struct, given that it seems like it's definitely only for ourselves and should probably be "known" by ourselves in some other way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's true. I just thought that it's the most convenient place to put it by putting similar things together. Else I'll have to put the private key somewhere in the Node
structure (which doesn't exist yet)
// The hash-id of this list | ||
Hash hashid.HashId | ||
// The suite used in this list | ||
Suite abstract.Suite |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Following our discussion, I think suite should not be here. Should it not be higher up, in the definition of what application we want to run(stamp,bitcosi etc) ?
Will start new |
Open for first comments of the new tree/peer structures.