Archives
/
lnbook
mirror of https://github.com/lnbook/lnbook
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
1,379 Commits
2 Branches
1 Tag
154 MiB
develop
routing-chapter-edits
firstedition_firstprint
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '42f4f0b530'
${ noResults }
Commit Graph

129 Commits (42f4f0b530eec81b6747e85f23329bdefb5e128f)

Author SHA1 Message Date
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. 3 years ago
Andreas M. Antonopoulos bcb155eb85
Merge pull request #569 from batmanscode/develop 
Minor wording and punctuation
 3 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
Scott-Driscoll f70c014507
We will not revise these concepts --> We will not review 4 years ago
batmanscode 05b29ed36b
Minor wording and punctuation 
**Changes:**

* Added some missing full stops.
* 'meaning a pre-defined process based on cryptography, used by the channel partners to re-distribute' to 'meaning a pre-defined process based on cryptography is used by the channel partners to re-distribute'
* 'Payment channels basics' to 'Payment channel basics'
* 'Channels partners can agree to announce' to 'Channel partners can agree to announce'
* 'don’t need to trust your channel to retrieve the balance of your channel' to 'don’t need to trust your channel partner to retrieve the balance of your channel'
* 'present a Lightning invoice to Alice as a QR code, or send it via email, or any other message channel' or 'present a Lightning invoice to Alice as a QR code, send it via email, or any other message channel'
* 'who just sent her an uninvitedly email' to 'who just uninvitedly sent her an email'
* 'addresses as part of payment channel on the Lightning Network' to 'addresses as part of payment channels on the Lightning Network'
* 'We looked at how payments are routed. Finally, we compared Lightning and Bitcoin and analyzed their differences and commonalities' to 'We looked at how payments are routed and finally, we compared Lightning with Bitcoin and analyzed their differences and commonalities'
 4 years ago
Andreas M. Antonopoulos e7637ba2a1
Merge pull request #545 from bitcoincoretech/ch_03 
Chapter: 03_how_ln_works
 4 years ago
Andreas M. Antonopoulos 909c8190c9
Merge pull request #544 from justinmoon/multisig-typo 
Fix typo
 4 years ago
Vlad Stan 8437018394 ch_3: add missing verb 4 years ago
Justin Moon ae9b49b892 Fix typo 4 years ago
Vlad Stan 48430f4ed2 small typo 4 years ago
Vlad Stan 7f4f648f62 fix first bullet point 4 years ago
Vlad Stan 5535b3651b use bulletpoints for "channel limitations"; be consistent with the below "useful properties" 4 years ago
Umar Bolatov 4f91a1ea98
Update spelling in Ch. 3 
close #539
 4 years ago
Andreas M. Antonopoulos 668d59640b Fixes #448 4 years ago
Andreas M. Antonopoulos d1cc9eed23 Fixes #437 4 years ago
Andreas M. Antonopoulos e253756ced Fixes #435 4 years ago
Andreas M. Antonopoulos 9522121745 Fixes #435 4 years ago
Andreas M. Antonopoulos ea5758ae99 Fixes #432 4 years ago
Andreas M. Antonopoulos 4d9774e519 Fixes #431 4 years ago
Andreas M. Antonopoulos cc88e22889 Fixes #430 
Fixes #430
 4 years ago
Andreas M. Antonopoulos 7fef49f61e
Merge pull request #508 from dangershony/patch-2 
how ln works -typo
 4 years ago
Andreas M. Antonopoulos 0a4f1ad4cb
Merge pull request #509 from tigeryant/develop 
How ln works - typos
 4 years ago
tigeryant 35c888f18d
Update how ln works - typo 
Corrected two typos - 'put' to 'puts' and 'send' to 'sends'
 4 years ago
tigeryant 9dcbefc063
Update 03_how_ln_works.asciidoc 4 years ago
Dan Gershony 35f03e67b5
how ln works -typo 4 years ago
Alex Prut 9ca2e94f3e Chapter: How LN Works - fix typos, punctuation 4 years ago
Dan Gershony b1be808423
Update 03_how_ln_works.asciidoc 4 years ago
Dan Gershony bf23aab48b
How LN works - typo 4 years ago
Dan Gershony de3f8df8cb
Fix typo 4 years ago
René K abe9b4835f
Merge branch 'develop' into patch-1 4 years ago
Andreas M. Antonopoulos 9525765885
Merge branch 'develop' into chapter_3_edits 4 years ago
René K 7a3830cc49
Update 03_how_ln_works.asciidoc 
Some typos fixed.
 4 years ago
Sergei Tikhomirov 04719c86de minor edits in Chapter 3 4 years ago
Imran 44314b62e1
Typo 4 years ago
Imran 25de2edda1
Update 03_how_ln_works.asciidoc 4 years ago
Imran 0a47707142
How LN Works - Closing a channel (Language edits) 
Incorporated some edits from the defunct pull request below to make this section read a little more easily. Some particulars

* Instead of stating as good way, bad way, ugly way -> state as their technical name and put (the good way) bracketed after
* The first and third examples referred to "you" and the second referred to "Alice and Bob". All three now refer to "you"
* Each paragraph now describes the method with a one liner
* Some miscellaneous detail

https://github.com/lnbook/lnbook/pull/307
 4 years ago
Emilio Norrmann 97a83e2405
Update 03_how_ln_works.asciidoc (#367) 
I don't know who Mallory is.. perhaps he is talking about Bob
 4 years ago