-
Notifications
You must be signed in to change notification settings - Fork 57
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
Docs for currency #2042
Docs for currency #2042
Conversation
70e6a84
to
86941c7
Compare
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.
A very nice write up.
However, note it is based one the new spend struct, hence may have to be merged of the refactor PR got merged.
|
||
Without the `DerivationIndex`, there is no way to link a `MainPubkey` to a `UniquePubkey`. Since `UniquePubkey`s are spendable only once, this means every transaction involves new and unique keys which are all unrelated and unlinkable to their original owner's `MainPubkey`. | ||
|
||
Under the hood, those types are simply: |
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.
simply -> simple ?
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.
Depends on the PR #1989
pub struct Spend { | ||
pub unique_pubkey: UniquePubkey, | ||
pub ancestors: BTreeSet<UniquePubkey>, | ||
pub descendants: BTreeMap<UniquePubkey, NanoTokens>, |
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.
still need to keep the royalties
member field
also, shall the doc cover the reason
member field as well?
if this doc is just about currency & spend DAG, which these two fields (especially the reason field) are not that related,
at least put a ...
below the line of descendants
, to avoid give a mis-impression to the readers that Spend
struct only has that three member fields ?
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.
Yes I didn't document that as those fields are more likely to evolve thus the ...
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.
We could add those once stabilized?
86941c7
to
aaaff31
Compare
Docs for the currency