Page MenuHomecode.freespoken.nz
Create Task
Maniphest T6

Write transaction life-cycle section
Closed, ResolvedPublic
Actions

Description

The specification would benefit from a section running through the life-cycle of a transaction, in roughly chronological order.

Revisions and Commits

R1 circulex-specification
R1:8349a36d3ea9 Typical use of missing information requests and responses
R1:77191a37c4d9 Typical computer interactions around transaction execution
R1:8795a01c6763 Typical human interactions around a transaction's execution
R1:1b3ba31cf510 Typical paywise partial agreements
R1:de78eca5009f Typical use of relay requests and latency reports
R1:83c78ffabdc9 Minor corrections
R1:667c4ef186c9 Discuss finality deadlines in typical usage section
R1:fd176c9eb28a Reorganize typical computer pathfinding section
R1:e089c03fe8f1 Typical partial agreements
R1:fde0f589de6c Typical creation of a transaction identifier
R1:86067fd3d4f4 Explanation of typical use of hints
R1:c00d1c183739 Human interactions prior to pathfinding
R1:c53d03e684d9 More computer interaction when establishing relationships
R1:67e32feeee33 Extending credit, and Bob's interactions with Carlos
R1:d41ea037c11f Separate sections for establishing human and computer relationships
R1:91a8a2e0fc5a Started subsection on establishing relationships
R1:1259e4a0f2eb Began "Typical operation" section

Related Objects
Search...

Event Timeline

tim created this task.Apr 6 2017, 11:58 AM
tim added a subtask: T4: Fixed-size payment paths.Apr 6 2017, 12:29 PM
tim added a parent task: T12: Revise introduction to the specification.Apr 7 2017, 12:34 PM
tim closed subtask T4: Fixed-size payment paths as Wontfix.Jun 6 2017, 11:23 AM
tim added a commit: R1:1259e4a0f2eb: Began "Typical operation" section.Sep 6 2018, 4:57 PM
tim closed subtask T47: Define payment requests as Resolved.Nov 2 2018, 5:36 PM
tim closed subtask T44: "Tell X where I am" messages as Resolved.Nov 8 2018, 4:59 PM
tim added a commit: R1:91a8a2e0fc5a: Started subsection on establishing relationships.Dec 21 2018, 4:56 PM
tim added a commit: R1:d41ea037c11f: Separate sections for establishing human and computer relationships.Jan 2 2019, 4:12 PM
tim added a commit: R1:67e32feeee33: Extending credit, and Bob's interactions with Carlos.Jan 3 2019, 5:04 PM
tim added a commit: R1:c53d03e684d9: More computer interaction when establishing relationships.Jan 4 2019, 4:30 PM
tim added a commit: R1:c00d1c183739: Human interactions prior to pathfinding.Jan 10 2019, 5:23 PM
tim added a commit: R1:86067fd3d4f4: Explanation of typical use of hints.Jan 11 2019, 4:34 PM
tim added a commit: R1:fde0f589de6c: Typical creation of a transaction identifier.Jan 18 2019, 5:52 PM
tim added a commit: R1:e089c03fe8f1: Typical partial agreements.
tim added a commit: R1:fd176c9eb28a: Reorganize typical computer pathfinding section.
tim added a commit: R1:667c4ef186c9: Discuss finality deadlines in typical usage section.Jan 24 2019, 5:46 PM
tim added a commit: R1:83c78ffabdc9: Minor corrections.
tim added a commit: R1:de78eca5009f: Typical use of relay requests and latency reports.Jan 25 2019, 5:34 PM
tim added a commit: R1:1b3ba31cf510: Typical paywise partial agreements.Jan 30 2019, 4:24 PM
tim added a commit: R1:8795a01c6763: Typical human interactions around a transaction's execution.Jan 31 2019, 5:47 PM
tim closed this task as Resolved by committing R1:77191a37c4d9: Typical computer interactions around transaction execution.Feb 1 2019, 5:54 PM
tim added a commit: R1:77191a37c4d9: Typical computer interactions around transaction execution.
tim added a commit: R1:8349a36d3ea9: Typical use of missing information requests and responses.Feb 5 2019, 3:45 PM