If an instance misses a tally from its relay, or a statement from its peer, for example, the relay or peer may not realize that it needs to resend the message. It would be useful to have a type of message that can be used to request the resending of a message that was expected but not received.
Description
Description
Details
Details
- Commits
- R1:f58d61273b29: Requests for tallies
R1:04c6fd96d706: Requests for missing receipts
R1:eddab21b78cf: Requests for complete agreements
R1:3ce7f36b224f: Requests for partial agreements
R1:c26aa355a60d: Requests for hints
R1:5174af0c19f8: Requests for statements
R1:5bc6920e09eb: Better missing information request name and introduction
R1:379064a25aa6: How to request a missing invitation
R1:92ac13a3cc92: Introduction to missing message requests
| 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" | ||
| Resolved | tim | T36 Tallys must report how many receipts were sent |