LaconicNetwork/cosmos-sdk
7
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 2 Wiki Activity

docs: fixes broken links (#19295)

Browse Source
This commit is contained in:
samricotta
2024-02-02 15:53:10 +00:00
committed by GitHub
parent a9b3ccac5a
commit 26c64364ac
50 changed files with 119 additions and 123 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/learn/advanced/03-node.md
+3 -3
View File
@@ -20,7 +20,7 @@ The full-node client of any Cosmos SDK application is built by running a `main`
In general, developers will implement the `main.go` function with the following structure:
* First, an [`encodingCodec`](./05-encoding.md) is instantiated for the application.
* First, an [`encodingCodec`](https://docs.cosmos.network/main/learn/advanced/encoding) is instantiated for the application.
* Then, the `config` is retrieved and config parameters are set. This mainly involves setting the Bech32 prefixes for [addresses](../beginner/03-accounts.md#addresses).
```go reference
@@ -92,5 +92,5 @@ https://github.com/cosmos/cosmos-sdk/blob/v0.50.0-alpha.0/server/start.go#L350-L
Upon starting, the node will bootstrap its RPC and P2P server and start dialing peers. During handshake with its peers, if the node realizes they are ahead, it will query all the blocks sequentially in order to catch up. Then, it will wait for new block proposals and block signatures from validators in order to make progress.
## Other commands
To discover how to concretely run a node and interact with it, please refer to our [Running a Node, API and CLI](../../user/run-node/01-run-node.md) guide.
<!-- markdown-link-check-disable-next-line -->
To discover how to concretely run a node and interact with it, please refer to our [Running a Node, API and CLI](../../user/run-node/01-run-node.md#configuring-the-node-using-apptoml-and-configtoml) guide.