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

1285 Commits (4723491456edce139cdba814a946a629f3926fd8)
 

Author SHA1 Message Date
Andreas M. Antonopoulos 1c139865e5
Merge pull request #563 from ImranLorgat/patch-47 
Glossary - Feature Bits
 4 years ago
Andreas M. Antonopoulos 629d6ecb76
Merge pull request #571 from Scott-Driscoll/minor-grammar-and-text-suggestions 
Minor grammar and text suggestion
 4 years ago
Andreas M. Antonopoulos 55a0e90db0
Merge pull request #580 from Roasbeef/gossip-chapter 
ggch-channel-graph: initial draft of channel graph chapter
 4 years ago
jerzybrzoska f35b50dfd4
Made one sentence out of these two. 
Someone better versed in the noise protocol may consider including 'authentication' and 'identity privacy', so that the glossary information on the noise protocol is parallel to [the one in ch.3](https://github.com/lnbook/lnbook/blob/develop/03_how_ln_works.asciidoc):
>The Noise Protocol Framework allows the construction of cryptographic communication protocols that offer authentication, encryption, forward secrecy and identity privacy.
 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
Olaoluwa Osuntokun aff95b8b10 ch-channel-graph: initial draft of channel graph chapter 
In this commit, we present an initial version of the chapter on the
channel graph itself, how to bootstrap a new peer to the network, how to
sync it, how to validate it, and how to maintain it once bootstrapped.

The current version of this chapter covers the following BOLTs: 07, 10.
BOLTs 09, 08, and 01 are alluded to along the way.

This is marked as a draft commit, as I still need to fill out the final
portion that covers how the current gossip network works, and the
protocol used to sync the channel graph based on block heights of
channels.

Due to the current length, we may want to consider eventually breaking
this chapter up, however I'm focusing on content first.
 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
Gustavo Silva e460a145fb [fix] minor misspells 4 years ago
jerzybrzoska d430b70149
Corrected a typo "2-of-2" instead of "2-2" 4 years ago
jerzybrzoska 0feaabb365
Consistency in spelling out the numbers that are < 10 (introduction) 
It would be fine to maintain consistency in spelling out the numbers (provided that they are not code/math/ BTC amounts) that are < 10. I left out "8 GB" unchanged, though. "eight Gigabyte" would perhaps be more consistent, but at the same time would seem very
unusual, whereas "eight GB" just make no sense to me.  
[A post about style](https://www.grammarly.com/blog/when-to-spell-out-numbers/) 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.
 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
jerzybrzoska 6158b78123
Update e2e-presentation-layer.asciidoc 
Added a period after the last sentence of a paragraph. After spotting it I could not help correcting it.
 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
Johns Beharry d3eae93bbe
refactor(glossary): differentiate bitcoin and lightning specs 4 years ago
Andreas M. Antonopoulos adbd2efbad Routing chapter edits 4 years ago
Andreas M. Antonopoulos eac6f28f77 node operations chapter status fix 4 years ago
Andreas M. Antonopoulos a720529872 Updated README with publication date, chapter progress, and wordcount, 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
Johns Beharry eec41ae02c
fix(glossary): resolve typo 4 years ago
Johns Beharry 4f2917d7d3
fix(glossary): lowercase protocol and of 4 years ago
Johns Beharry ca79710601
refactor(glossary): simplify BOLT definition 4 years ago
Janus Troelsen 7231f5f102 Update Eclair manual building instructions 
- Explain something that looks like a version number ("2.13").
- Explain how to skip tests, which are fragile on master and not run for the other clients.
 4 years ago
Andreas M. Antonopoulos 2da8c72599 Merge branch 'fairness_protocol' into develop 4 years ago
Andreas M. Antonopoulos b83245852c Finished fairness protocol section 4 years ago
Andreas M. Antonopoulos 6427d048f3
Merge pull request #565 from batmanscode/develop 
minor wording fixes
 4 years ago
Andreas M. Antonopoulos 7f9206a0aa
Merge pull request #566 from bitcoincoretech/issue_549b 
Issue 549b
 4 years ago
Vlad Stan ebf409e0e0 #549 always restart containers 4 years ago
Vlad Stan 37e068de4a #5 update lnd version 4 years ago
Vlad Stan 52cb91bd44 #549 replace deprecated property 
see https://github.com/ACINQ/eclair/issues/1505
 4 years ago
Vlad Stan 060be23df1 #549 update eclair to latest version & commit 4 years ago
Vlad Stan 0c27defb00 #549 update lightningd to use a specific version 4 years ago
Imran a1d30a7503
Update glossary.asciidoc 4 years ago
batmanscode 57eb42cb03
minor wording fixes 
**changed:**

* 'mined since (and inclusive) the block' to 'mined since (and inclusive of) the block'
* 'Six confirmation is a best practice' to 'Six confirmations is best practice'
* 'without "on-chain" transaction' to 'without an "on-chain" transaction'
 4 years ago
Imran e6e30e27fc
Glossary - Feature Bits 4 years ago
Rene Pickhardt c85af67476 Merge branch 'develop' of https://github.com/lnbook/lnbook into develop 4 years ago
Rene Pickhardt 8ccc05adf4 fixed MPP an AMP definition in glossary 4 years ago
Andreas M. Antonopoulos 6958723248
Merge pull request #536 from dipunm/patch-1 
Update routing.asciidoc
 4 years ago
Andreas M. Antonopoulos f913d8dc81
Merge pull request #560 from bitcoincoretech/ch_channel_operation 
Chapter: channel operation
 4 years ago
Andreas M. Antonopoulos b6d8ddda43
Merge pull request #559 from quantumcthulhu/patch-6 
node_client.asciidoc typo
 4 years ago
Andreas M. Antonopoulos 86bbaf4315
Merge pull request #558 from quantumcthulhu/patch-5 
node_client.asciidoc typo
 4 years ago
Andreas M. Antonopoulos 69a73d26c5
Merge pull request #557 from quantumcthulhu/patch-4 
node_client.asciidoc typo
 4 years ago
Andreas M. Antonopoulos b9a85b7878
Merge pull request #556 from quantumcthulhu/patch-3 
node_client.asciidoc typo
 4 years ago
Andreas M. Antonopoulos 4400f44596
Merge pull request #555 from ImranLorgat/patch-45 
P2P - Feature Bits
 4 years ago
8go 74078b4df3
path-finding: multipath 2: improvements (#522) 
- commas
- rephrasing
- speciefied -> specified
- multipath is one word, see https://en.wiktionary.org/wiki/multipath
- multipart is one word, see https://en.wiktionary.org/wiki/multipart
- etc
 4 years ago
Andreas M. Antonopoulos 15e733b6f4
Merge pull request #554 from tomichec/fixWei 
adds touch to /eclair/eclair.log so Wei doesn't fail
 4 years ago
Andreas M. Antonopoulos f5c307901f
Merge pull request #553 from justinmoon/loop 
Renting channel liquidity is reason to operate node
 4 years ago
Andreas M. Antonopoulos 0cb116a0bf
Merge pull request #552 from bitcoincoretech/ch_channel_construction 
Chapter: channel construction
 4 years ago
Andreas M. Antonopoulos 7df01f2ce1
Merge pull request #551 from quantumcthulhu/patch-2 
node_client typo
 4 years ago