add crosslink reference to catchain

[fakela]

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.

[github-actions]

To fix the formatting issues:

1. Install necessary dependencies: npm ci
2. Then, run this command:

npx remark -o --silent --silently-ignore ton/catchain.mdx 

[github-actions]

Thanks for the updates in this PR. I reviewed the changes and found no issues—no fixes needed from this review.

[github-actions]

To fix the formatting issues:

1. Install necessary dependencies: npm ci
2. Then, run this command:

npx remark -o --silent --silently-ignore ton/catchain.mdx 

[github-actions]

To fix the formatting issues:

1. Install necessary dependencies: npm ci
2. Then, run this command:

npx remark -o --silent --silently-ignore ton/catchain.mdx 

[github-actions]

To fix the formatting issues:

1. Install necessary dependencies: npm ci
2. Then, run this command:

npx remark -o --silent --silently-ignore ton/catchain.mdx 

[github-actions]

To fix the formatting issues:

1. Install necessary dependencies: npm ci
2. Then, run this command:

npx remark -o --silent --silently-ignore ton/catchain.mdx 

[github-actions]

To fix the formatting issues:

1. Install necessary dependencies: npm ci
2. Then, run this command:

npx remark -o --silent --silently-ignore ton/catchain.mdx 

[github-actions]

To fix the formatting issues:

1. Install necessary dependencies: npm ci
2. Then, run this command:

npx remark -o --silent --silently-ignore ton/catchain.mdx 

[github-actions]

To fix the formatting issues:

1. Install necessary dependencies: npm ci
2. Then, run this command:

npx remark -o --silent --silently-ignore ton/catchain.mdx 

[verytactical]

[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.

[fakela]

<Aside> section has been added

[fakela]

@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>.

[fakela]

@verytactical this is what the <Aside> block with the comment on reference change

[verytactical]

Previously requested changes were not applied. There's still a [3, 2.1.12] instead of link on "TON Blockchain".

[fakela]

Previously requested changes were not applied. There's still a [3, 2.1.12] instead of link on "TON Blockchain".

This is linking to the exact point in the TON Blockchain that it is called. It is linking to section 2.1.12 in the TON Blockchain and this applies to others.

We can't remove the ref number and add the link to the word "Ton Blockchain" they won't be able to get the reference.

[verytactical]

We can't remove the ref number and add the link to the word "Ton Blockchain" they won't be able to get the reference.

Who?

[reveloper]

@fakela, let's update this file (as the smallest pdf), then wait for the final review from @verytactical.

Please replace numbered references with textual ones. Change the links that relate to

1. The current document (internal) links

Old format:

Section [3] (#3-block-consensus-protocol)

New format:

[Section 3](#3-block-consensus-protocol)

2. TON blockchain whitepaper links

Old format:

(the block creation and validation software) and therefore is not the topic of this text (\[[4, 1.2](/ton/tblkch#1-2-principal-components-of-a-block-and-the-blockchain-state)] would be a more appropriate reference)

New format:

(the block creation and validation software) and therefore is not the topic of this text ([Block and the blockchain state](/ton/tblkch#1-2-principal-components-of-a-block-and-the-blockchain-state) would be a more appropriate reference)

3. TON whitepaper links

Old format:

(a shardchain or the masterchain of the TON Blockchain; cf. \[[3, 2.6](/ton/ton#2-6-creating-and-validating-new-blocks)]

New format:

[a shardchain or the masterchain of the TON Blockchain](/ton/ton#2-6-creating-and-validating-new-blocks)