Commit Graph

840 Commits (routing-chapter-edits)
 

Author SHA1 Message Date
Olaoluwa Osuntokun 430bcbe104
routing: small typo fix 4 years ago
Olaoluwa Osuntokun 9c63c0cb32
routing: begin to modernize onion format payload description
The existing examples and diagrams towards the end of the chapter are
actually out of date now, as the network as mostly moved over to using
the TLV format everywhere within the onion payload.
4 years ago
Olaoluwa Osuntokun 56c293403a
routing: further chapter edits 4 years ago
Olaoluwa Osuntokun cefd65a0ce routing: flesh out bridge section on abstract HTLC construct 4 years ago
Olaoluwa Osuntokun 862d0404ac routing: revise chapter outlook end of first section 4 years ago
Olaoluwa Osuntokun d8b3526bd3 routing: further chapter edits up to onion routing section 4 years ago
Olaoluwa Osuntokun 9ab3494a17 (temp)routing: set up outline for revised chapter. 4 years ago
Olaoluwa Osuntokun b3e9f79b15 routing: move basic state machine example to channel construction
This doesn't belong here as we're only concerned with routing. The exact details of channels are described in another chapter.
4 years ago
Olaoluwa Osuntokun 2fb0fe00a4 routing: further golden coin example edits 4 years ago
Olaoluwa Osuntokun 95fc5da2b9 routing: frame ecrow as an "ideal functionality" 4 years ago
Olaoluwa Osuntokun ce4fd1d27b routing: edits to golden coin example 4 years ago
Olaoluwa Osuntokun 8d32b39a60 routing: re-work intor paragraph of golden coin example 4 years ago
Olaoluwa Osuntokun 86cc56de47 routing: specify traits of onion routing, into HTLC breakdown 4 years ago
Olaoluwa Osuntokun 130c529c6b routing: add caveat re funds loss assuming proper time-lock usage 4 years ago
Olaoluwa Osuntokun 89ad27db62 routing: stress distinction between routing and path finding in intro paragraph 4 years ago
Olaoluwa Osuntokun b24c8562a3 routing: secrete -> secret 4 years ago
Rene Pickhardt 99536b9ad9 counted words 4 years ago
Rene Pickhardt 1698c2d9d7 Merge branch 'develop' of https://github.com/lnbook/lnbook into develop 4 years ago
Rene Pickhardt e5c3caa287 added some text about multipart / multipath payments 4 years ago
Andreas M. Antonopoulos 16d93761bf Merge branch 'node_operations_chapter' into develop 4 years ago
Andreas M. Antonopoulos ee460e6347 node_operations: installing and running a service 4 years ago
Andreas M. Antonopoulos 89559bfb8f
Merge pull request #346 from 8go/patch-80
Eclair: English touch ups, commas
4 years ago
Andreas M. Antonopoulos a3bacdc724
Merge pull request #345 from 8go/patch-79
Eclair: English touch ups
4 years ago
Andreas M. Antonopoulos 915ebc195a
Merge pull request #343 from 8go/patch-78
LND: more English fixes, 1 error
4 years ago
Andreas M. Antonopoulos bc54811d12
Merge pull request #341 from 8go/patch-77
LND: typos, touch ups, English, etc.
4 years ago
Andreas M. Antonopoulos af5f45d73e
Merge pull request #347 from 8go/patch-81
Complete Network, part 1: English touch ups
4 years ago
8go 8c853ee92c
Complete Network, part 1: English touch ups
- Oxford comma for consistency (see PR #340)
- sentence restructuring (one does not compose by routing a payment)
- no comma in list of 2
- only the top of the config is listed, we should say so. --> The top looks like ...
- in most cases, no comma before "because" or "since", exceptions apply
- it's (wrong) --> its (possessive)
4 years ago
8go a77e4161c4
Eclair: English touch ups, commas
- commas
- reorg of sentences
- "Check to..." sentence is copy-paste from above, changed it slightly to avoid repetition
- OK, Eclair is uppercase, but here we refer to a directory which is lowercase, so "eclair" (just because it is the lowercase name of the dir)
- etc
4 years ago
Andreas M. Antonopoulos 8a460b2547 Merge branch 'node_operations_chapter' into develop 4 years ago
Rene Pickhardt 078ae93a50 wrote a little bit about stuckless payments but not happy with it 4 years ago
Andreas M. Antonopoulos f3d5f8ef94 node_operations: choosing node type 4 years ago
Andreas M. Antonopoulos 3f7838e84c Merge branch 'node_operations_chapter' into develop 4 years ago
8go 90836468d0
Eclair: English touch ups
- commas
- "by this point" --> "at this point" or "by this time". Maybe best "by now"
- "... you have seen previously to build the Eclair container" is ambiguous. Rephrased
- "directly" .... word order
- it's: incorrect,  --> its
- "unlike the LND or c-lightning containers": did not read well, reordered sub-phrases
- eclair vs Eclair: ok, the logo is lower cased. But when you read their https://github.com/ACINQ/eclair page ALL occurrences of Eclair are UPPERCASED.
- Based on their own use of "Eclair" in English text I have upper-cased all "Eclair" occurrences 
- up to line 779 it was already upper-case, then suddenly it was lower-case
- rephrasing
- etc
4 years ago
Rene Pickhardt 7ec3ca3686 added more to the path finding chapter 4 years ago
Andreas M. Antonopoulos dde1228235 node_operations: choosing bitcoin node and OS 4 years ago
8go ac2ec76dd4
LND: more English fixes, 1 error
- again commas
- sentence simplifications
- typo
- "at minimum" : that's wrong, "at a minimum", "at least" but I rephrased anyway to avoid it altogether because it does not read well in any case due to the following "or later"
- "distributed" repetitive, changed to "available"
- "It doesn't matter where the GOPATH points" ... this is misleading or could be misunderstood. I rephrased.
- ERROR: "git clone" should be "go get"
4 years ago
Andreas M. Antonopoulos 3c680bec24 node_operations - added BTCPay 4 years ago
8go 06b8a2f38e
more touch ups, English, commas (#340)
- replaced ", as is often the case," with "common"
- "prerequisite" has no hyphen
- in most cases no comma in front of "which"
- replaced "that we can do" with "available"
- if there is a list of 3 choices, one can place (optional) a comma before the "and". This is called the Oxford comma. It is optional, but it should be used consistently, always in the book or never. Since above it was used, I set it below as well.
- replaced "aggressively" with "heavily", we are not aggressive :)
- etc.
4 years ago
8go fd9635d345
minor touch up, English corrections (#338)
- usually there is no comma in front of because, as, etc. (exceptions exist)
- other commas
- "Let's" sounds very colloquial. It shows up a lot. In a couple of locations I replaced it with "let us" to make it a bit more formal, but I did not want to replace all. Maybe colloquialisms create some closeness to the reader.
- "also" seemed out of place
- local area network  has no hyphen
- "not important, but has ...": either no comma   or   a subject (it) has to be added after "but"
- "like this" was also a bit repetitive, I replaced it once with "as follows"
4 years ago
Zachery Glass 1454b0e50e
Fix minor spelling, capitalization and grammar mistakes in channel-construction.asciidoc (#339) 4 years ago
Francisco Calderon 99ded49570
Enumerate using asciidoc for better readability (#336) 4 years ago
Rene Pickhardt 53b06e8f0e added information sources for path finding 4 years ago
Andreas M. Antonopoulos d8eeb4ba03
Merge pull request #147 from HAOYUatHZ/explorer
add LN explorer section
4 years ago
8go cee0dfe142
LND: typos, touch ups, English, etc.
- no comma in front of "and" in a list of 2
- same for "or" in list of 2
- list of 3: yes, we want a comma there to be consistent (Oxford comma, see PR #340 
- many many --> many
4 years ago
Andreas M. Antonopoulos 9008219681 Merge branch 'node_operations_chapter' into develop 4 years ago
Andreas M. Antonopoulos 56e5ee430a Merge remote-tracking branch 'aantonop_fork/node_operations_chapter' into node_operations_chapter 4 years ago
Andreas M. Antonopoulos dc85ccc532 Node operations: merged and rewrote hardware requirements 4 years ago
Andreas M. Antonopoulos 00d55ed729 Small changes to outline 4 years ago
Andreas M. Antonopoulos aad9e62f8f README status updates and word count 4 years ago
Rene Pickhardt 905031554b editing path finding, adding path construction, discussing fundamental observatins about path finding 4 years ago