Commit Graph

163 Commits (8c676c4e4e6565519e667eb8bb2bf9432af2fe80)

Author SHA1 Message Date
mcronin 6c4fcdbffd Edited 03_how_ln_works.asciidoc with Atlas code editor 3 years ago
Andreas M. Antonopoulos 635a3f28b7 Merge branch 'develop' 3 years ago
Andreas M. Antonopoulos b84990da34 fix broken refs 3 3 years ago
Andreas M. Antonopoulos b5e380132d fix broken refs 2 3 years ago
Andreas M. Antonopoulos d44cd74156 fix broken refs 1 3 years ago
Andreas M. Antonopoulos f8a816eef3
Merge branch 'develop' into typo-fix 3 years ago
Olaoluwa Osuntokun 22245a3b5b
ch-03: mention vbytes is the main accounting unit for fees 3 years ago
Olaoluwa Osuntokun b3fa3611ca
ch-03: mention new 26-ish hop limit post TLV 3 years ago
Olaoluwa Osuntokun 11417697fc
ch-03: don't use probe for route attempts
Usually probing is a sort of pre-processing step to see if the payment
is even possible.
3 years ago
Olaoluwa Osuntokun 5c5ecb5601
ch-03: mention transaction ordering, re-work funding_created mention
They don't need to exchange any information as they've already agreed
upon the cannonical ordering. Item 7 was confusing, so we've just merged
that in with where `funding_created` is first mentioned.
3 years ago
Olaoluwa Osuntokun 7009bda534
ch-03: mention advertised + non-advertised channels
It's obvious if the channel is advertised, but not necessarily if its
non-advertised.
3 years ago
Olaoluwa Osuntokun 1b13d7b9a7
ch-03: qualify payment channel discovery w/ bi-di+infinite
Channels were around before that, but had several limitations which were
eventually over come with newer ideas.
3 years ago
Olaoluwa Osuntokun 7d9ece330a
ch-03: soften language re instant payments
Possible that a payment needs to retry main times (hidden from the user)
or fails all together (no paths, etc).
3 years ago
bosch 93daa31985
Small edit on who funds the channel. (#767)
Small edit on who funds the channel as well as expanded the footnote to mention experimental dual-funded channels currently in c-lightning.
3 years ago
Andreas M. Antonopoulos 7e3943ba41 Merge branch 'develop' 3 years ago
Paisal Kiattananan 6c5d8b10ba
Update 03_how_ln_works.asciidoc (#760) 3 years ago
Andreas M. Antonopoulos da3b97758f Merge branch 'develop' 3 years ago
Andreas M. Antonopoulos 5bd2d1673f Added link to eltoo paper 3 years ago
Andreas M. Antonopoulos 96dbbde753 Merge branch 'develop' 3 years ago
Franky 5486ff24b5
Update 03_how_ln_works.asciidoc (#695)
Typo

Co-authored-by: Rene Pickhardt <rene@rene-pickhardt.de>
3 years ago
Lawrence Webber ab2f47b7ba
Update 03_how_ln_works.asciidoc (#691)
The word 'payment' should be pluralised to 'payments' on Line 66.
3 years ago
Franky c9c9883b21
Update 03_how_ln_works.asciidoc (#684)
Typo.

Co-authored-by: Rene Pickhardt <rene@rene-pickhardt.de>
3 years ago
Zendo102 afd2bfcc62
Update 03_how_ln_works.asciidoc (#674)
Changes to capitalization and commas mostly.  I've tidied up one or two sentences that were unclear, awkward or ambiguous.
3 years ago
voelker85 d5bc07928b
Typo (#744) 3 years ago
Andreas M. Antonopoulos 1918ebbe6e Merge remote-tracking branch 'atlas/master' 3 years ago
Andreas M. Antonopoulos 391b79e5d4 Merge branch 'develop' 3 years ago
Andreas M. Antonopoulos a2fbcefb5e Message, connection, node ID 3 years ago
benskee afbc791281 typo 3 years ago
kristen@oreilly.com 99cf432091 Edited 03_how_ln_works.asciidoc with Atlas code editor 3 years ago
Andreas M. Antonopoulos a15ab0271f Merge branch 'develop' 3 years ago
kristen@oreilly.com 446e63b92f Edited 03_how_ln_works.asciidoc with Atlas code editor 3 years ago
kristen@oreilly.com 973d8b5853 Edited 03_how_ln_works.asciidoc with Atlas code editor 3 years ago
Franky 29708730b5
Update 03_how_ln_works.asciidoc (#657)
Typo.
3 years ago
Andreas M. Antonopoulos 897c91ceea Added reference to Bitcoin Fundamentals review appendix 3 years ago
Andreas M. Antonopoulos fcdd62e308
Merge pull request #601 from aantonop/bitcoin-fundamentals
WIP: Bitcoin Fundamentals Review
3 years ago
Geremia ce8396b8f0
fixed typos (e.g., "vs" → "vs.") and wording (#643) 3 years ago
Andreas M. Antonopoulos b4e98f5cc8 Removed multisig details and replaced w reference 3 years ago
Andreas M. Antonopoulos 9ff862c037
Merge pull request #600 from HannahMR/stacked-headings
Adding a section intro sentence to avoid stacked headings.
3 years ago
Andreas M. Antonopoulos d5e830343f
Merge pull request #595 from HannahMR/whitepaper-link
Adding Lightning Network whitepaper link.
3 years ago
Hannah 958c6ed7b0 Adding a section intro sentence to avoid stacked headings. 3 years ago
Hannah ccbdd7696b Adding Lightning Network whitepaper link. 4 years ago
Andreas M. Antonopoulos bcb155eb85
Merge pull request #569 from batmanscode/develop
Minor wording and punctuation
4 years ago
Andreas M. Antonopoulos a13efbc3a6
Merge pull request #575 from jerzybrzoska/patch-2
Consistency in spelling out the numbers that are < 10 (ch. 3)
4 years ago
Andreas M. Antonopoulos eb7aff823d
Merge branch 'develop' into patch-5 4 years ago
Andreas M. Antonopoulos e8e46646a8
Merge pull request #581 from jerzybrzoska/patch-6
Minor modification that removes ambiguity (ch. 3)
4 years ago
jerzybrzoska 9cac112c96
Minor modification that removes ambiguity (ch. 3)
I removed "You have". Now it's all in one sentence -- less ambiguous and more concise I believe. The more verbose alternative would be: 
>You have *time* until ...
4 years ago
jerzybrzoska 41b06b0d7f
Consistent spelling of timelock (ch. 3)
Both "timelock" and "time lock" are correct but let us be consistent and stick to the one form.
4 years ago
jerzybrzoska 28f1552be8
Update 03_how_ln_works.asciidoc
You are right [Umar](@bolatovumar) , I have not found a single source on the web with _two-of-two_, _2-of-2_ seems to be the standard. I edited my pull request, so now the changes do not include 2-of-2 modification. I find the issue of '2-of-2' vs 'two-of-two' interesting and may soon create a question on [English Stack Exchange](https://english.stackexchange.com/) in order to get their opinion.
4 years ago
jerzybrzoska 68ebd75d5b
Consistency in spelling out the numbers that are < 10
It would be well to maintain consistency in spelling out the numbers (provided that they are not code/math/ BTC amounts) that are < 10. I left out "chapter 6" and the like unchanged. 
[A post about style][1] for the reference.
>In scientific and technical writing, the prevailing style is to write out numbers under ten. While there are exceptions to these rules, your predominant concern should be expressing numbers consistently.

[1]: https://www.grammarly.com/blog/when-to-spell-out-numbers/
4 years ago
Scott-Driscoll b0e3d9f5cd
We will not review these advanced... in depth 4 years ago