add crosslink reference to catchain #628
Conversation
|
To fix the formatting issues:
npx remark -o --silent --silently-ignore ton/catchain.mdx |
|
Thanks for the updates in this PR. I reviewed the changes and found no issues—no fixes needed from this review. |
|
To fix the formatting issues:
npx remark -o --silent --silently-ignore ton/catchain.mdx |
|
To fix the formatting issues:
npx remark -o --silent --silently-ignore ton/catchain.mdx |
|
To fix the formatting issues:
npx remark -o --silent --silently-ignore ton/catchain.mdx |
|
To fix the formatting issues:
npx remark -o --silent --silently-ignore ton/catchain.mdx |
|
To fix the formatting issues:
npx remark -o --silent --silently-ignore ton/catchain.mdx |
…tlify-ton-docs into crosslink-catchain
|
To fix the formatting issues:
npx remark -o --silent --silently-ignore ton/catchain.mdx |
|
To fix the formatting issues:
npx remark -o --silent --silently-ignore ton/catchain.mdx |
ton/catchain.mdx
Outdated
| ## Abstract | ||
|
|
||
| The aim of this text is to provide an outline of the Catchain Consensus Protocol, a Byzantine Fault Tolerant (BFT) protocol specifically crafted for block generation and validation in the TON Blockchain [\[3\]](#ref-3). This protocol can potentially be used for purposes other than block generation in a proof-of-stake (PoS) blockchain; however, the current implementation uses some optimizations valid only for this specific problem. | ||
| The aim of this text is to provide an outline of the Catchain Consensus Protocol, a Byzantine Fault Tolerant (BFT) protocol specifically crafted for block generation and validation in the TON Blockchain [[3, 2.1.12](/ton/ton#2-1-12-block-generation-intervals)][⁸](#footnote-8). This protocol can potentially be used for purposes other than block generation in a proof-of-stake (PoS) blockchain; however, the current implementation uses some optimizations valid only for this specific problem. |
There was a problem hiding this comment.
[3, 2.1.12]^8 notation is
- obscure
- not needed
We should have a link on "TON Blockchain" directly to 2.1.12 section of TON whitepaper, with an <Aside> telling that previous reference was incorrect.
There was a problem hiding this comment.
<Aside> section has been added
There was a problem hiding this comment.
@verytactical This links to the precise location on the TON blockchain and The Open Network, respectively. The footnote addition was me following this recommended approach by Alex: #627 (comment)
But I have switched to using <Aside>.
There was a problem hiding this comment.
@verytactical this is what the <Aside> block with the comment on reference change
fakela
changed the title
2 participants
This whitepaper has seven references cited.
Reference [1] is mentioned 3 times, [2] once, [3] 4 times, [4] 4 times, [5] once, [6] not mentioned, and [7] twice.
Closes issue: #561
I have also attached an external link to the reference N. Durov, “Telegram Open Network,” 2017 and 2018, for easier access.