The object talked about in T34 kind of wants to be called an "account", but there's a collision here between senses 5 and 9 of "account" here. Sense 9 is currently being used in the specification, so it would need to be renamed something like "member(ship)" (which might clash with the JSON sense of the word "member") or "user(name)".
Description
Description
Revisions and Commits
Revisions and Commits
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T1 Cheap, private payments via a decentralized network | ||
| Open | tim | T2 Finalize a first draft of a specification for a decentralized payments protocol | ||
| Open | tim | T12 Revise introduction to the specification | ||
| Resolved | tim | T5 Finish Messages section of the specification | ||
| Resolved | tim | T28 Define a message to request missing messages | ||
| Resolved | tim | T34 Object to specify users and a currency | ||
| Resolved | tim | T35 Don't call membership of a host an "account" |