Integrate August source updates - #532
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b71512f4b2
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Recent 6.0.4 prerelease handling rejects invalid API inputs earlier: out-of-range `/blocks/chainSlice` requests, invalid scan IDs, wrong-length modifier, box, or token IDs, and malformed secret-proof-hint hex return errors instead of reaching deeper node logic. Public mining and script routes remain public even if older generated OpenAPI material showed incorrect security annotations. RC2 also fixes the `CommitmentWithSecret` schema indentation in `openapi.yaml`. | ||
| Node v6.0.4 rejects invalid API inputs earlier: out-of-range `/blocks/chainSlice` requests, invalid scan IDs, wrong-length modifier, box, or token IDs, and malformed secret-proof-hint hex return errors instead of reaching deeper node logic. Public mining and script routes remain public even if older generated OpenAPI material showed incorrect security annotations. The release also fixes the `CommitmentWithSecret` schema indentation in `openapi.yaml`. | ||
|
|
||
| The `PopowHeader` schema now matches the node encoder and decoder: `header`, `interlinks`, and `interlinksProof` are required. `interlinksProof` is a `BatchMerkleProof` containing indexed leaf digests and proof nodes with their side. Clients generated from an older OpenAPI file may omit this required proof field and should refresh against the v6.0.4 schema. |
There was a problem hiding this comment.
The site's OpenAPI Spec nav entry (mkdocs.yml:980) still publishes docs/node/swagger/openapi.md, while its source docs/node/swagger/openapi.yaml:1483 requires only header and interlinks and contains no interlinksProof. Readers and generators using the bundled specification therefore receive the exact outdated schema this paragraph warns against; update both generated artifacts from the current upstream spec.
AGENTS.md reference: AGENTS.md:L146-L149
Useful? React with 👍 / 👎.
| #### August | ||
|
|
||
| - [Ergo node](protocol.md): [v6.0.4](https://github.com/ergoplatform/ergo/releases/tag/v6.0.4) is the latest checked stable release. It includes stricter REST input validation, public-testnet activation corrections, duplicate-mempool protection, block-candidate and extra-index fixes, and recovery when a locally mined block fails validation. [v6.1.4](https://github.com/ergoplatform/ergo/releases/tag/v6.1.4) carries the same changes with RocksDB and is marked as a prerelease. | ||
| - [Sigma SDK](sigmastate-interpreter.md): [v6.0.6](https://github.com/ergoplatform/sigmastate-interpreter/releases/tag/v6.0.6) adds specification-generator drift checks, Bitcoin transaction-parsing examples, checked handling for non-OOM VM errors during typechecking, and better selector diagnostics. |
There was a problem hiding this comment.
After recording v6.0.6 here, this same roadmap still says Sigma SDK is released only through 6.0.5 in the Current Snapshot (docs/roadmap.md:243) and Detailed Roadmap Tracks (docs/roadmap.md:351). Readers using either summary get a stale current version, so both status rows should be advanced to 6.0.6.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b71512f4b2
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Recent 6.0.4 prerelease handling rejects invalid API inputs earlier: out-of-range `/blocks/chainSlice` requests, invalid scan IDs, wrong-length modifier, box, or token IDs, and malformed secret-proof-hint hex return errors instead of reaching deeper node logic. Public mining and script routes remain public even if older generated OpenAPI material showed incorrect security annotations. RC2 also fixes the `CommitmentWithSecret` schema indentation in `openapi.yaml`. | ||
| Node v6.0.4 rejects invalid API inputs earlier: out-of-range `/blocks/chainSlice` requests, invalid scan IDs, wrong-length modifier, box, or token IDs, and malformed secret-proof-hint hex return errors instead of reaching deeper node logic. Public mining and script routes remain public even if older generated OpenAPI material showed incorrect security annotations. The release also fixes the `CommitmentWithSecret` schema indentation in `openapi.yaml`. | ||
|
|
||
| The `PopowHeader` schema now matches the node encoder and decoder: `header`, `interlinks`, and `interlinksProof` are required. `interlinksProof` is a `BatchMerkleProof` containing indexed leaf digests and proof nodes with their side. Clients generated from an older OpenAPI file may omit this required proof field and should refresh against the v6.0.4 schema. |
There was a problem hiding this comment.
The site's OpenAPI Spec nav entry (mkdocs.yml:980) still publishes docs/node/swagger/openapi.md, while its source docs/node/swagger/openapi.yaml:1483 requires only header and interlinks and contains no interlinksProof. Readers and generators using the bundled specification therefore receive the exact outdated schema this paragraph warns against; update both generated artifacts from the current upstream spec.
AGENTS.md reference: AGENTS.md:L146-L149
Useful? React with 👍 / 👎.
| #### August | ||
|
|
||
| - [Ergo node](protocol.md): [v6.0.4](https://github.com/ergoplatform/ergo/releases/tag/v6.0.4) is the latest checked stable release. It includes stricter REST input validation, public-testnet activation corrections, duplicate-mempool protection, block-candidate and extra-index fixes, and recovery when a locally mined block fails validation. [v6.1.4](https://github.com/ergoplatform/ergo/releases/tag/v6.1.4) carries the same changes with RocksDB and is marked as a prerelease. | ||
| - [Sigma SDK](sigmastate-interpreter.md): [v6.0.6](https://github.com/ergoplatform/sigmastate-interpreter/releases/tag/v6.0.6) adds specification-generator drift checks, Bitcoin transaction-parsing examples, checked handling for non-OOM VM errors during typechecking, and better selector diagnostics. |
There was a problem hiding this comment.
After recording v6.0.6 here, this same roadmap still says Sigma SDK is released only through 6.0.5 in the Current Snapshot (docs/roadmap.md:243) and Detailed Roadmap Tracks (docs/roadmap.md:351). Readers using either summary get a stale current version, so both status rows should be advanced to 6.0.6.
Useful? React with 👍 / 👎.
1 participant
Summary
application.conf, refresh reviewed pages, and regenerate the inventoryTriage
Verification
.venv/bin/python tools/source_watch.py scan --strict.venv/bin/python tools/source_watch_inventory.py --check.venv/bin/python tools/nav_audit.py --strict.venv/bin/python tools/structure_audit.py --strictgit diff --check.venv/bin/python -m mkdocs build --site-dir /tmp/ergodocs-site-checkCloses #518
Closes #519
Closes #520
Closes #521
Closes #522
Closes #523
Closes #524
Closes #525
Closes #526
Closes #527
Closes #528
Closes #529
Closes #530
Closes #531