zolfa
/
tendermint
1
0
Fork 0
Code Issues 0 Pull Requests 0 Projects 0 Releases 221 Wiki Activity
Browse Source

Fixed hyperlinks

pull/7804/head
Sergio Mena 3 years ago
parent
0d610258f5
commit
af8a1a2ce3
2 changed files with 5 additions and 5 deletions
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. +2
    -2
      spec/abci++/abci++_basic_concepts_002_draft.md
  2. +3
    -3
      spec/abci++/abci++_methods_002_draft.md

+ 2
- 2
spec/abci++/abci++_basic_concepts_002_draft.md View File

@ -357,7 +357,7 @@ developers _really_ know what they are doing.
State sync allows new nodes to rapidly bootstrap by discovering, fetching, and applying State sync allows new nodes to rapidly bootstrap by discovering, fetching, and applying
state machine snapshots instead of replaying historical blocks. For more details, see the state machine snapshots instead of replaying historical blocks. For more details, see the
[state sync section](../spec/p2p/messages/state-sync.md).
[state sync section](../p2p/messages/state-sync.md).
New nodes will discover and request snapshots from other nodes in the P2P network. New nodes will discover and request snapshots from other nodes in the P2P network.
A Tendermint node that receives a request for snapshots from a peer will call A Tendermint node that receives a request for snapshots from a peer will call
@ -375,4 +375,4 @@ As the new node receives "chunks" it will apply them sequentially to the local
application with `ApplySnapshotChunk`. When all chunks have been applied, the application with `ApplySnapshotChunk`. When all chunks have been applied, the
Application's `AppHash` is retrieved via an `Info` query. The `AppHash` is then Application's `AppHash` is retrieved via an `Info` query. The `AppHash` is then
compared to the blockchain's `AppHash` which is verified via compared to the blockchain's `AppHash` which is verified via
[light client verification](../spec/light-client/verification/README.md).
[light client verification](../light-client/verification/README.md).

+ 3
- 3
spec/abci++/abci++_methods_002_draft.md View File

@ -233,7 +233,7 @@ title: Methods
can be spoofed by adversaries, so applications should employ additional verification schemes can be spoofed by adversaries, so applications should employ additional verification schemes
to avoid denial-of-service attacks. The verified `AppHash` is automatically checked against to avoid denial-of-service attacks. The verified `AppHash` is automatically checked against
the restored application at the end of snapshot restoration. the restored application at the end of snapshot restoration.
* For more information, see the `Snapshot` data type or the [state sync section](../spec/p2p/messages/state-sync.md).
* For more information, see the `Snapshot` data type or the [state sync section](../p2p/messages/state-sync.md).
### ApplySnapshotChunk ### ApplySnapshotChunk
@ -655,7 +655,7 @@ then _p_'s Tendermint decides block _v_ and finalizes consensus for height _h_ i
## Data Types existing in ABCI ## Data Types existing in ABCI
Most of the data structures used in ABCI are shared [common data structures](../spec/core/data_structures.md). In certain cases, ABCI uses different data structures which are documented here:
Most of the data structures used in ABCI are shared [common data structures](../core/data_structures.md). In certain cases, ABCI uses different data structures which are documented here:
### Validator ### Validator
@ -773,7 +773,7 @@ Most of the data structures used in ABCI are shared [common data structures](../
| metadata | bytes | Arbitrary application metadata, for example chunk hashes or other verification data. | 3 | | metadata | bytes | Arbitrary application metadata, for example chunk hashes or other verification data. | 3 |
* **Usage**: * **Usage**:
* Used for state sync snapshots, see the [state sync section](../spec/p2p/messages/state-sync.md) for details.
* Used for state sync snapshots, see the [state sync section](../p2p/messages/state-sync.md) for details.
* A snapshot is considered identical across nodes only if _all_ fields are equal (including * A snapshot is considered identical across nodes only if _all_ fields are equal (including
`Metadata`). Chunks may be retrieved from all nodes that have the same snapshot. `Metadata`). Chunks may be retrieved from all nodes that have the same snapshot.
* When sent across the network, a snapshot message can be at most 4 MB. * When sent across the network, a snapshot message can be at most 4 MB.


Write Preview
Loading…
Cancel
Save