Uh oh!
There was an error while loading. Please reload this page.
Added ⚡️ content to Payments > Transactions - #593
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Bosch-0
left a comment
There was a problem hiding this comment.
Few minor changes but LGTM!
| Let's lay out the entire payment process. | ||
| | Bitcoin | Lightning | | ||
| |-------------|------------------| | ||
| | Users send *[transactions]({{'/guide/glossary/#transaction' | relative_url}})*. | Users send *[payments]({{'/guide/glossary/#payment' | relative_url}})*. | |
There was a problem hiding this comment.
I find it super unintuitive to distinguish transactions and payments by which layer they are on. To me, those words mean 95% the same thing. A distinction I could see being made is that a transaction is the technical thing that happens, while a payment is the thing users make.
There was a problem hiding this comment.
Especially weird since the section is called Payments. The tech primer also uses the term transactions when referring to Lightning.
There was a problem hiding this comment.
Yeah I agree, could just remove the first line and change this section name to Comparing Bitcoin and Lightning payments.
Could distinguish how Bitcoin is more a settlement layer where as Lightning is more for P2P payments.
There was a problem hiding this comment.
We had a Slack discussion about this point.
Let me summarize briefly what I was trying to convey in that thread. Consider this: "Alice pays Bob". We could provide two different descriptions of what is happening in that sentence. One is the user experience description. The other is the technical description. For the UX description, I feel comfortable using the terms payment and transaction interchangeably. However, for the tech description, the 2 terms should not be used interchangeably. They are very different concepts.
In this Figma file, I have tried to lay out the differences visually.
Since this page is providing more of a technical overview, I think it might be a good idea to use tech descriptions and not UX descriptions.
I tried to update and make this idea a little more clear in 513973c.
Thoughts?
GBKS
left a comment
There was a problem hiding this comment.
Looking good. Had some minor capitalization feedback. The reason why I requested changes is that I think the differentiation between transactions and payments is really fuzzy and not consistent with how we've used those terms elsewhere. Would be sweet to clear that up.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: bosch <55287964+Bosch-0@users.noreply.github.com>
Co-authored-by: bosch <55287964+Bosch-0@users.noreply.github.com>
Co-authored-by: bosch <55287964+Bosch-0@users.noreply.github.com>
Co-authored-by: Christoph Ono <chri@sto.ph>
Co-authored-by: Christoph Ono <chri@sto.ph>
Co-authored-by: Christoph Ono <chri@sto.ph>
Uh oh!
There was an error while loading. Please reload this page.
| This is radically different from the traditional financial system, where it is often possible for others to pull and withdraw money from your account (utility companies, financial institutions, merchants, etc.). When you make a payment, it will pass through systems that might delay, control or block the payment. | ||
| ## Transaction lifecycle | ||
| {% include tip/open.html color="blue" icon="info" label="A note about terminology" %} |
GBKS
left a comment
There was a problem hiding this comment.
ACK. Looks great. It's really easy to read and follow along. Thanks for accommodating my request around the terminology.
I added LN content to the Payments > Transactions page.
See Deploy Preview
Fix for #571