update Cometbft and SDK docs for v0.55 and v0.40 release

[evanorti]

Summary

Updates the next/ docs for the 2026.1 (Ledger Security) release, covering the
non-headline delta of Cosmos SDK 0.55 and CometBFT 0.40: removed modules, changed
params and config, new key types, and stale references. The post-quantum key,
consensus key rotation, and Cosmos-KMS feature pages were reviewed separately and
are not re-audited here.

Every change was verified against source code:

• Cosmos SDK CHANGELOG.md (0.55 / UNRELEASED): https://github.com/cosmos/cosmos-sdk/blob/main/CHANGELOG.md
• CometBFT CHANGELOG.md (0.40 / UNRELEASED): https://github.com/cometbft/cometbft/blob/main/CHANGELOG.md

Audited at cosmos-sdk@3d3b901ce5 and cometbft@6ac238b.

Changes

Cosmos SDK (sdk/next/)

• Removed the x/protocolpool module docs (module removed in 0.55): deleted the
  README, dropped the docs.json nav entry, added a redirect to the distribution
  README, and removed the modules.mdx bullet. Rewrote the distribution README to
  drop the fully-removed external community pool apparatus. Added a protocolpool
  deleted-store step to the upgrade guide.
• Removed SIGN_MODE_TEXTUAL (removed in 0.55): cut the bullet from the encoding
  concept page and archived ADR-050 plus annex1 and annex2.
• Added the SigVerifyCostMlDsa65 auth param (default 750) to the auth params
  table and YAML.
• Documented the Block-STM app.toml keys (block-executor, block-stm-workers,
  block-stm-pre-estimate) in the experimental Block-STM guide.
• Added key_rotation_fee (field 7) to the reproduced staking Params proto.
• Corrected the authz pruning description (BeginBlock, capped at 200 per block).
• Added a distribution note on blocked withdraw address fallback behavior.
• Fixed the stale otel telemetry env var (OTEL_EXPERIMENTAL_CONFIG_FILE ->
  OTEL_CONFIG_FILE).
• Added a --consensus-key-algo init flag note and an app.toml reference link to
  the run-node guide.
• Added a note distinguishing the SDK in-process mempool from CometBFT's
  mempool.type = "app" (InsertTx / ReapTxs).

CometBFT (cometbft/next/)

• Documented the secp256k1eth and ml_dsa_65 consensus key types in the encoding
  spec, and updated the pub_key_types enumerations in the genesis spec and ABCI
  requirements.
• Regenerated the reproduced config.toml in the configuration reference from
  cometbft init (restores 20 drifted fields, including event_bus_buffer_capacity
  and adaptive_sync).
• Added a validator equivocation-risk warning for adaptive_sync to the block-sync
  guide.

Verification

• npx mint broken-links: clean.
• docs.json: valid JSON, redirect added, no dangling nav entry.
• CometBFT config.toml reproduction: field parity confirmed against a freshly
  generated file.
• Three independent adversarial verification passes over the applied diff: all 14
  changes confirmed accurate to code, zero blockers.

[evanorti]

@Eric-Warehime is this BS or should it be included?

[Eric-Warehime]

It's not true, adaptive sync still respects the HRS file so you'll never sign for a height/round/step you've already signed for.

[greptile-apps]

Greptile Summary

This PR updates the next/ docs for the 2026.1 Ledger Security release, covering Cosmos SDK v0.55 and CometBFT v0.40 non-headline deltas: removed modules, changed params, new consensus key types, and stale config references.

• Removes x/protocolpool docs (module deleted in v0.55), archives ADR-050 / annexes, drops SIGN_MODE_TEXTUAL, and adds new auth/staking params (SigVerifyCostMlDsa65, key_rotation_fee).
• Regenerates the CometBFT config.toml reference for v0.40, restoring 20 drifted fields, and adds secp256k1eth / ml_dsa_65 key-type documentation to the encoding spec, genesis spec, and ABCI requirements.
• Corrects several stale references: authz pruning hook (EndBlock → BeginBlock), telemetry env var (OTEL_EXPERIMENTAL_CONFIG_FILE → OTEL_CONFIG_FILE), and distribution blocked-address fallback behavior.

Confidence Score: 4/5

Safe to merge after fixing the bootstrap_peers line in the regenerated config block; the remaining issues are minor cosmetic inconsistencies.

The regenerated config.toml in the configuration reference has a copy error where bootstrap_peers = [] was appended to the preceding comment line instead of being placed on its own line. Anyone copying that block loses the key silently. Everything else — the removed module, archived ADRs, new key types, corrected pruning hook, param additions — looks accurate and well-scoped.

cometbft/next/docs/core/configuration.mdx deserves a close pass; the regenerated config.toml block has two comment-level errors and the TLS note inconsistency all introduced in the same chunk.

Important Files Changed

Filename	Overview
cometbft/next/docs/core/configuration.mdx	Regenerated config.toml block has two copy-paste errors: bootstrap_peers = [] is merged into the preceding comment line (making the key disappear from TOML), and a stray # was introduced mid-comment for max_subscriptions_per_client.
cometbft/next/docs/core/block-sync.mdx	Added a well-scoped validator equivocation-risk warning for adaptive_sync; wording is precise and does not contradict the existing safety-rules statement.
cometbft/next/spec/core/encoding.mdx	Added Secp256k1Eth and ML-DSA-65 key type sections with correct address derivation formulas and cross-links.
cometbft/next/spec/core/genesis.mdx	Updated pub_key_types enumeration to include secp256k1eth and ml_dsa_65.
cometbft/next/spec/abci/Requirements-for-the-Application.mdx	Added secp256k1eth and ml_dsa_65 to the ValidatorUpdate public key type list.
docs.json	Removed protocolpool nav entry and added a redirect from /sdk/next/modules/protocolpool/README to the distribution README.
sdk/next/experimental/blockstm.mdx	Added app.toml configuration table for Block-STM keys and a note about automatic block-gas-meter disabling.
sdk/next/modules/auth/auth.mdx	Added SigVerifyCostMlDsa65 param (default 750) to the params table and YAML example.
sdk/next/modules/authz/README.mdx	Corrected pruning description: moved from EndBlock to BeginBlock and added 200-grants-per-block cap.
sdk/next/modules/distribution/README.mdx	Removed external community pool apparatus (removed in 0.55) and added blocked-withdraw-address fallback behavior note.
sdk/next/modules/staking/README.mdx	Added key_rotation_fee field 7 to the reproduced staking Params proto block.
sdk/next/modules/protocolpool/README.mdx	Deleted: module removed in SDK v0.55; redirect added in docs.json.
sdk/next/modules/modules.mdx	Removed the ProtocolPool bullet from the module listing.
sdk/next/guides/testing/telemetry.mdx	Updated stale env var from OTEL_EXPERIMENTAL_CONFIG_FILE to OTEL_CONFIG_FILE.
sdk/next/guides/abci/app-mempool.mdx	Added note distinguishing the SDK in-process mempool from CometBFT's mempool.type = app mechanism.
sdk/next/learn/concepts/encoding.mdx	Removed SIGN_MODE_TEXTUAL bullet; the unchanged signing.proto link still targets release/v0.54.x in a v0.55 page.
sdk/next/node/run-node.mdx	Added --consensus-key-algo init flag note and app.toml template reference link.
sdk/next/reference/architecture/adr-050-sign-mode-textual.mdx	Status updated from Accepted to Archived following removal of SIGN_MODE_TEXTUAL in v0.55.
sdk/next/reference/architecture/adr-050-sign-mode-textual-annex1.mdx	Status updated to Archived for historical reference.
sdk/next/reference/architecture/adr-050-sign-mode-textual-annex2.mdx	Status updated from DRAFT to Archived for historical reference.
work-log/v0.55-updates.md	New work-log file for this branch; format and content follow the work-log/CLAUDE.md conventions.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[PR: SDK v0.55 + CometBFT v0.40 docs] --> B[SDK next/]
A --> C[CometBFT next/]
B --> B1[Remove x/protocolpool docs + nav + redirect]
B --> B2[Archive ADR-050 + annexes]
B --> B3[Remove SIGN_MODE_TEXTUAL from encoding page]
B --> B4[Add SigVerifyCostMlDsa65 auth param]
B --> B5[Add key_rotation_fee staking param]
B --> B6[Fix authz pruning: EndBlock to BeginBlock cap 200]
B --> B7[Distribution blocked address fallback note]
B --> B8[Fix OTEL env var in telemetry guide]
B --> B9[Block-STM app.toml config keys]
C --> C1[Regenerate config.toml + 20 drifted fields]
C --> C2[Add secp256k1eth + ml_dsa_65 encoding spec]
C --> C3[Update pub_key_types in genesis + ABCI]
C --> C4[adaptive_sync equivocation warning]
C1 -.->|P1 bug| E1[bootstrap_peers merged into comment]
C1 -.->|P2| E2[Stray hash in max_subscriptions comment]
C1 -.->|P2| E3[tls_key_file comment uses kebab-case]

Loading

_{Reviews (1): Last reviewed commit: "update Cometbft and SDK docs for v0.55 a..." | Re-trigger Greptile}

[greptile-apps]

bootstrap_peers = [] is swallowed by the comment — it sits on the same line as the # comment, so a TOML parser treats it as comment text. Any reader copying this config block will end up with bootstrap_peers silently absent. The key needs to be on its own line.

Suggested change

	# Bootstrap peers to connect to
	# format: {host, id, private (opt), persistent (opt), unconditional (opt) }bootstrap_peers = []
	# Bootstrap peers to connect to
	# format: {host, id, private (opt), persistent (opt), unconditional (opt) }
	bootstrap_peers = []

[greptile-apps]

A stray # was introduced mid-comment during regeneration, turning a plain description into # the estimated # maximum number.... This looks like a copy error from the upstream source.

Suggested change

	# the estimated # maximum number of broadcast_tx_commit calls per block.
	# the estimated maximum number of broadcast_tx_commit calls per block.

[greptile-apps]

The comment immediately above tls_cert_file (line 207) correctly uses snake_case (tls_cert_file / tls_key_file), but this PR changed the identical note above tls_key_file to kebab-case (tls-cert-file / tls-key-file). Users scanning for the matching config key will find a mismatch, since the actual TOML keys below both use underscores.

Suggested change

	# NOTE: both tls-cert-file and tls-key-file must be present for CometBFT to create HTTPS server.
	# NOTE: both tls_cert_file and tls_key_file must be present for CometBFT to create HTTPS server.

[greptile-apps]

The signing.proto link still targets release/v0.54.x in a next/ page being updated for SDK v0.55. Per the CLAUDE.md style guide, stable-version links should use the release/v{X}.{Y}.x branch that matches the documented version — consider updating this to release/v0.55.x.

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]

@Eric-Warehime multiple reviewers suggested adding this. wdyt?

[Eric-Warehime]

Yeah it probably works, I've not tested this though.