mirror of
https://github.com/lightningnetwork/lnd.git
synced 2025-10-10 00:33:40 +02:00
docs: fix contribution guide links [skip ci]
This commit is contained in:
@@ -86,7 +86,7 @@ security and performance implications.
|
|||||||
- The original LN was written for a rather narrow audience, the paper may be a bit unapproachable to many. Thanks to the Bitcoin community, there exist many easily accessible supplemental resources which can help one see how all the pieces fit together from double-spend protection all the way up to commitment state transitions and Hash Time Locked Contracts (HTLCs):
|
- The original LN was written for a rather narrow audience, the paper may be a bit unapproachable to many. Thanks to the Bitcoin community, there exist many easily accessible supplemental resources which can help one see how all the pieces fit together from double-spend protection all the way up to commitment state transitions and Hash Time Locked Contracts (HTLCs):
|
||||||
- [Lightning Network Summary](https://lightning.network/lightning-network-summary.pdf)
|
- [Lightning Network Summary](https://lightning.network/lightning-network-summary.pdf)
|
||||||
- [Understanding the Lightning Network 3-Part series](https://bitcoinmagazine.com/articles/understanding-the-lightning-network-part-building-a-bidirectional-payment-channel-1464710791)
|
- [Understanding the Lightning Network 3-Part series](https://bitcoinmagazine.com/articles/understanding-the-lightning-network-part-building-a-bidirectional-payment-channel-1464710791)
|
||||||
- [Deployable Lightning](https://github.com/ElementsProject/lightning/blob/master/doc/deployable-lightning.pdf)
|
- [Deployable Lightning](https://github.com/ElementsProject/lightning/blob/master/doc/miscellaneous/deployable-lightning.pdf)
|
||||||
|
|
||||||
|
|
||||||
Note that the core design of the Lightning Network has shifted over time as
|
Note that the core design of the Lightning Network has shifted over time as
|
||||||
|
@@ -16,7 +16,8 @@ in `lnd` to help improve the overall readability.
|
|||||||
|
|
||||||
Blocks of code within `lnd` should be segmented into logical stanzas of
|
Blocks of code within `lnd` should be segmented into logical stanzas of
|
||||||
operation. Such spacing makes the code easier to follow at a skim, and reduces
|
operation. Such spacing makes the code easier to follow at a skim, and reduces
|
||||||
unnecessary line noise. Coupled with the commenting scheme specified above,
|
unnecessary line noise. Coupled with the commenting scheme specified in the
|
||||||
|
[contribution guide](./code_contribution_guidelines.md#code-documentation-and-commenting),
|
||||||
proper spacing allows readers to quickly scan code, extracting semantics quickly.
|
proper spacing allows readers to quickly scan code, extracting semantics quickly.
|
||||||
Functions should _not_ just be laid out as a bare contiguous block of code.
|
Functions should _not_ just be laid out as a bare contiguous block of code.
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user