Merge pull request #139 from dimitris-t/patch-1

Fixed typos in 02_getting_started.asciidoc
pull/141/head
Andreas M. Antonopoulos 4 years ago committed by GitHub
commit b26c5279ca
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

@ -9,7 +9,7 @@ The Lightning Network is accessed via software applications that can speak the L
Users have the highest degree of control by running their own Bitcoin node and LN node. However, LN nodes can also use a lightweight Bitcoin client (commonly referred to as Simplified Payment Verification (SPV)) to partially validate the correctness of their blockchain.
While Bitcoin nodes need quite some hardware to be able to operate smoothly LN nodes can run with tiny hardware requirements on cellphones or on a Rhaspberry pi.
While Bitcoin nodes need quite some hardware to be able to operate smoothly LN nodes can run with tiny hardware requirements on cellphones or on a Raspberry Pi.
////
but there is no "SPV" functionality in the LN peer to peer communication right? they have to have full funcionality?
@ -36,8 +36,8 @@ Blockchains, especially open blockchains like Bitcoin, attempt to minimize or el
Every other component of a lightning wallet brings similar considerations of trust. If all the components are under the control of the user, then the amount of trust in third parties is minimized, bringing maximum power to the user. Of course, this is a direct trade-off, as with that power comes the responsibility to manage complex software.
Every user must consider their own technical skills before deciding what type of lightning wallet to use. Those with strong technical skills should use a lightning wallet that puts all of the components under the direct control of the user. Those with less technical skill but a desire to control their funds, should choose a _non-custodial_ lightning wallet, even if some of the components (other than the keystore) rely on some trusted third parties.
Ofter the trust in those cases relates to privacy.
If users decides to outsource some functionality to a thrid party they usually give up some privacy as the third party will learn some information.
Often the trust in those cases relates to privacy.
If users decide to outsource some functionality to a third party they usually give up some privacy as the third party will learn some information.
Finally, those seeking simplicity and convenience, even at the expense of control and security, may choose a custodial lightning wallet. This is the least challenging option, but it _undermines the trust model of cryptocurrency_ and should, therefore, be considered only as a stepping stone towards more control and self-reliance.
@ -177,7 +177,7 @@ image:images/bitcoin-atm.png[]
To receive the bitcoin in her Eclair LN wallet, Alice will need to present a _Bitcoin Address_ from the Eclair LN wallet to the ATM. The ATM can then send Alice's newly acquired bitcoin to this bitcoin address.
To see a Bitcoin Address on the Eclair wallet, Alice must swipe to the left column titled "YOUR BITCOIN ADDRESS" (see <<eclair-receive>>), where she will see a square bardcode (called a _QR code_) and a string of letters and numbers below.
To see a Bitcoin Address on the Eclair wallet, Alice must swipe to the left column titled "YOUR BITCOIN ADDRESS" (see <<eclair-receive>>), where she will see a square barcode (called a _QR code_) and a string of letters and numbers below.
[[eclair-receive]]
.Alice's bitcoin address, shown in Eclair

Loading…
Cancel
Save