mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2024-12-23 15:18:11 +00:00
All: remove bit.ly link redirects
This commit is contained in:
parent
fe8c70871d
commit
dae7f90976
@ -997,7 +997,7 @@ channel network, which has now been implemented by at least five
|
|||||||
different open source teams. ((("Basics of Lightning Technology
|
different open source teams. ((("Basics of Lightning Technology
|
||||||
(BOLT)")))The independent implementations are coordinated by a set of
|
(BOLT)")))The independent implementations are coordinated by a set of
|
||||||
interoperability standards described in the
|
interoperability standards described in the
|
||||||
https://bit.ly/2rBHeoL[_Basics of Lightning Technology (BOLT)_ repository].
|
https://github.com/lightning/bolts/blob/master/00-introduction.md[_Basics of Lightning Technology (BOLT)_ repository].
|
||||||
|
|
||||||
==== Basic Lightning Network Example
|
==== Basic Lightning Network Example
|
||||||
|
|
||||||
@ -1119,8 +1119,8 @@ refund if the channel was closed or the routed payment failed.
|
|||||||
|
|
||||||
((("Lightning Network", "transport and pathfinding")))All communications
|
((("Lightning Network", "transport and pathfinding")))All communications
|
||||||
between LN nodes are encrypted point-to-point. In addition, nodes have a
|
between LN nodes are encrypted point-to-point. In addition, nodes have a
|
||||||
long-term public key that they https://bit.ly/2r5TACm[use as an
|
long-term public key that they use as an
|
||||||
identifier and to authenticate each other].
|
identifier and to authenticate each other.
|
||||||
|
|
||||||
Whenever a node wishes to send a payment to another node, it must first
|
Whenever a node wishes to send a payment to another node, it must first
|
||||||
construct a _path_ through the network by connecting payment channels
|
construct a _path_ through the network by connecting payment channels
|
||||||
@ -1152,7 +1152,7 @@ censorship, or blacklists. But how does Alice establish this payment
|
|||||||
path, without revealing anything to the intermediary nodes?
|
path, without revealing anything to the intermediary nodes?
|
||||||
|
|
||||||
The Lightning Network implements an onion-routed protocol based on a
|
The Lightning Network implements an onion-routed protocol based on a
|
||||||
scheme called https://bit.ly/2q6ZDrP[Sphinx]. This routing protocol
|
scheme called https://cypherpunks.ca/~iang/pubs/Sphinx_Oakland09.pdf[Sphinx]. This routing protocol
|
||||||
ensures that a payment sender can construct and communicate a path
|
ensures that a payment sender can construct and communicate a path
|
||||||
through the Lightning Network such that:
|
through the Lightning Network such that:
|
||||||
|
|
||||||
|
@ -194,7 +194,7 @@ point for the blockchain, a secure "root" from which to build a trusted
|
|||||||
blockchain.
|
blockchain.
|
||||||
|
|
||||||
See the statically encoded genesis block inside the Bitcoin Core client,
|
See the statically encoded genesis block inside the Bitcoin Core client,
|
||||||
in https://bit.ly/1x6rcwP[_chainparams.cpp_].
|
in https://github.com/bitcoin/bitcoin/blob/3955c3940eff83518c186facfec6f50545b5aab5/src/chainparams.cpp#L123[_chainparams.cpp_].
|
||||||
|
|
||||||
The following identifier hash belongs to the genesis block:
|
The following identifier hash belongs to the genesis block:
|
||||||
|
|
||||||
|
@ -459,7 +459,7 @@ There are hundreds of applications and websites that can provide the current mar
|
|||||||
|
|
||||||
https://bitcoinaverage.com/[Bitcoin Average]:: ((("BitcoinAverage")))A site that provides a simple view of the volume-weighted-average for each currency.
|
https://bitcoinaverage.com/[Bitcoin Average]:: ((("BitcoinAverage")))A site that provides a simple view of the volume-weighted-average for each currency.
|
||||||
https://coincap.io/[CoinCap]:: A service listing the market capitalization and exchange rates of hundreds of crypto-currencies, including bitcoin.
|
https://coincap.io/[CoinCap]:: A service listing the market capitalization and exchange rates of hundreds of crypto-currencies, including bitcoin.
|
||||||
https://bit.ly/cmebrr[Chicago Mercantile Exchange Bitcoin Reference Rate]:: A reference rate that can be used for institutional and contractual reference, provided as part of investment data feeds by the CME.
|
https://www.cmegroup.com/markets/cryptocurrencies/cme-cf-cryptocurrency-benchmarks.html?redirect=/trading/cryptocurrency-indices/cf-bitcoin-reference-rate.html[Chicago Mercantile Exchange Bitcoin Reference Rate]:: A reference rate that can be used for institutional and contractual reference, provided as part of investment data feeds by the CME.
|
||||||
|
|
||||||
In addition to these various sites and applications, some bitcoin
|
In addition to these various sites and applications, some bitcoin
|
||||||
wallets will automatically convert amounts between bitcoin and other
|
wallets will automatically convert amounts between bitcoin and other
|
||||||
|
@ -293,8 +293,6 @@ information, including:
|
|||||||
+BestHeight+:: The block height of this node's blockchain
|
+BestHeight+:: The block height of this node's blockchain
|
||||||
+fRelay+:: A field added by BIP37 for requesting not to receive unconfirmed transactions
|
+fRelay+:: A field added by BIP37 for requesting not to receive unconfirmed transactions
|
||||||
|
|
||||||
(See https://bit.ly/1qlsC7w[GitHub] for an example of the +version+ network message.)
|
|
||||||
|
|
||||||
The +version+ message is always the first message sent by any peer to
|
The +version+ message is always the first message sent by any peer to
|
||||||
another peer. The local peer receiving a +version+ message will examine
|
another peer. The local peer receiving a +version+ message will examine
|
||||||
the remote peer's reported +Version+ and decide if the remote peer is
|
the remote peer's reported +Version+ and decide if the remote peer is
|
||||||
@ -803,8 +801,7 @@ remove a pattern from a bloom filter, a client has to clear and resend a
|
|||||||
new bloom filter if a pattern is no longer desired.
|
new bloom filter if a pattern is no longer desired.
|
||||||
|
|
||||||
The network protocol and bloom filter mechanism for lightweight clients is defined
|
The network protocol and bloom filter mechanism for lightweight clients is defined
|
||||||
in https://bit.ly/1x6qCiO[BIP37 (Peer Services)].((("",
|
in BIP37.
|
||||||
startref="BNebloom08")))((("", startref="bloom08")))
|
|
||||||
|
|
||||||
Unfortunately, after the deployment of bloom filters, it became clear
|
Unfortunately, after the deployment of bloom filters, it became clear
|
||||||
that they didn't offer very much privacy. A full node receiving a bloom
|
that they didn't offer very much privacy. A full node receiving a bloom
|
||||||
|
Loading…
Reference in New Issue
Block a user