Skip to content

docs: sync example tutorials from cosmos/example - #340

Merged
evanorti merged 1 commit into
mainfrom
docs-sync/example-20260825-140643
Aug 25, 2026
Merged

docs: sync example tutorials from cosmos/example#340
evanorti merged 1 commit into
mainfrom
docs-sync/example-20260825-140643

Conversation

@evanorti

Copy link
Copy Markdown
Contributor

Auto-synced from cosmos/example. Transforms docs/.md to sdk/next/tutorials/example/.mdx. Do not edit these files directly — edit the source in cosmos/example and let the sync bot update them.

@evanorti evanorti added the docs-sync Automated docs sync PR label Aug 25, 2026
@mintlify

mintlify Bot commented Aug 25, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
cosmos-docs 🟢 Ready View Preview Aug 25, 2026, 2:10 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@greptile-apps

greptile-apps Bot commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

The PR synchronizes the six Cosmos SDK example tutorials from cosmos/example, updating prerequisites and module behavior while substantially expanding localnet operation and testing guidance.

  • Raises the documented Go prerequisite and refreshes command output.
  • Documents corrected counter overflow handling, authority options, error codes, and gas configuration.
  • Adds detailed four-node localnet health checks, transaction instructions, configuration, and troubleshooting guidance.

Confidence Score: 4/5

The PR appears safe to merge after removing the prohibited bold emphasis from the new localnet paragraph.

The synced tutorial content has no established functional or security defect, but one added sentence violates the repository's explicit formatting convention.

Files Needing Attention: sdk/next/tutorials/example/05-run-and-test.mdx

Important Files Changed

Filename Overview
sdk/next/tutorials/example/01-prerequisites.mdx Raises the Go prerequisite to 1.26 and refreshes example tool versions.
sdk/next/tutorials/example/04-counter-walkthrough.mdx Expands the authority and overflow explanations and updates error-code, AutoCLI, and gas-setting examples.
sdk/next/tutorials/example/05-run-and-test.mdx Adds detailed multi-node localnet and configuration guidance, with one repository style violation in the new prose.

Reviews (1): Last reviewed commit: "docs: sync example tutorials from cosmos..." | Re-trigger Greptile

## Localnet (multi-node)

Use localnet when you want a setup that is closer to a real network. It runs multiple validators in Docker so you can test multi-node behavior locally.
Localnet runs four nodes in Docker to give you a setup closer to a real network than the single-node chain. `scripts/localnet/init.sh` creates a genesis transaction for `node0` only, so the network is **one validator plus three full nodes**, not four validators. The chain ID is `example-localnet`, and each node has a single key named `validator` rather than the `alice` and `bob` accounts used by `make start`.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Bold emphasis violates documentation style

This new paragraph uses bold emphasis for two phrases even though the repository prohibits bold and italic text in documentation, introducing formatting that maintainers must remove.

Suggested change
Localnet runs four nodes in Docker to give you a setup closer to a real network than the single-node chain. `scripts/localnet/init.sh` creates a genesis transaction for `node0` only, so the network is **one validator plus three full nodes**, not four validators. The chain ID is `example-localnet`, and each node has a single key named `validator` rather than the `alice` and `bob` accounts used by `make start`.
Localnet runs four nodes in Docker to give you a setup closer to a real network than the single-node chain. `scripts/localnet/init.sh` creates a genesis transaction for `node0` only, so the network is one validator plus three full nodes, not four validators. The chain ID is `example-localnet`, and each node has a single key named `validator` rather than the `alice` and `bob` accounts used by `make start`.

Context Used: CLAUDE.md (source)

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

@evanorti
evanorti merged commit 507ef64 into main Aug 25, 2026
3 checks passed
@evanorti
evanorti deleted the docs-sync/example-20260825-140643 branch August 25, 2026 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs-sync Automated docs sync PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant