catchup: into long_lived/datalayer_merkle_blob from main @ cac84b5e057a074da6a72e2a8bbcc70ec0a09668 #19892

altendky · 2025-08-01T16:00:47Z

Source hash: cac84b5
Remaining commits: 0

…ns (#19801) * simplify MempoolManager by removing EligibilityAndAdditions * review comment * review comments

* fewer mutable defaults * catchup

* our miniupnpc_wheels * Update poetry.lock

* initial commit * fix precommit errors * test passing * ruff * remove SpendInfo and mempool_check_conditions * no need to call it _rust now * fix mempool test * fix precommit errors * fix test generator tools * add comment about impending chia_rs fix

…nt/main_from_release_2.5.5_96aeaf3e685f51a3ef9901228005109fc97687ed

…letTestFramework` and R-CATs (#19818) * Port `test_cat_endpoints` to `WalletTestFramework` * Use mint_cat from cat tests * Add RCAT parametrization * Delete now unnecessary `from_zero` * Minor clarification. --------- Co-authored-by: Amine Khaldi <[email protected]>

Source hash: 96aeaf3 Remaining commits: 0

Newest Mozilla CA cert

…ipts/npm_linux (#19810) build(deps): bump brace-expansion in /build_scripts/npm_linux Bumps [brace-expansion](https://github.com/juliangruber/brace-expansion) from 1.1.11 to 1.1.12. - [Release notes](https://github.com/juliangruber/brace-expansion/releases) - [Commits](juliangruber/brace-expansion@1.1.11...v1.1.12) --- updated-dependencies: - dependency-name: brace-expansion dependency-version: 1.1.12 dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

@altendky

* Port `get_wallets` * Suggestion by @altendky

…nt/main_from_release_2.5.5_590317c47fe5ef3406ee04835b7f730b80ce7fd0

* update zstd to 1.5.7.2 * Update poetry.lock

* Port `did_set_wallet_name` * Port `did_get_wallet_name` * Port `did_update_recovery_ids` * Port `did_message_spend` * Port `did_get_info` * Port `did_find_lost_did` * fix test * Port `did_update_metadata` * Port `did_get_did` * Port `did_get_recovery_list` * Port `did_get_metadata` * Port `did_get_pubkey` * Port `did_get_information_needed_for_recovery` * Port `did_get_current_coin_info` * Port `did_create_backup_file` * Port `did_transfer_did` * Add extra_conditions uniformly in CLI tests * test coverage * Delete DID recovery endpoints * Delete `create_exit_spend` as well * Missed one

* Update to node 20 * Update another script for minimum npm version * update check for npm >= 10 * update npm version --------- Co-authored-by: Zlatko <[email protected]>

update GUI pin to 1d95322

update GUI pin to efa99a4

Upgrade `ruff` to 0.12.4.

Revert "update zstd to 1.5.7.2 (#19804)" This reverts commit 13917fc.

* use strict for poetry check * ignore another * and request all

Source hash: 590317c Remaining commits: 1

--- updated-dependencies: - dependency-name: boto3 dependency-version: 1.39.4 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* integrate PLOT_V1_PHASE_OUT constant * current test chains won't work after the plot v1 phase-out

…708 (#19794) Bumps [types-aiofiles](https://github.com/typeshed-internal/stub_uploader) from 24.1.0.20250606 to 24.1.0.20250708. - [Commits](https://github.com/typeshed-internal/stub_uploader/commits) --- updated-dependencies: - dependency-name: types-aiofiles dependency-version: 24.1.0.20250708 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [setuptools](https://github.com/pypa/setuptools) from 80.8.0 to 80.9.0. - [Release notes](https://github.com/pypa/setuptools/releases) - [Changelog](https://github.com/pypa/setuptools/blob/main/NEWS.rst) - [Commits](pypa/setuptools@v80.8.0...v80.9.0) --- updated-dependencies: - dependency-name: setuptools dependency-version: 80.9.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* remove extra exception catching * clean up node errors + tests * forgot to pre-commit * address using pytest wrong * clean up error handling * seperate out pytest tests

--- updated-dependencies: - dependency-name: aiohttp dependency-version: 3.12.14 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Source hash: a5640a8 Remaining commits: 3

### Purpose:  ### Current Behavior: ### New Behavior:  ### Testing Notes:

* prover protocol and v2Prover * format name * format * refactor filename * tests/raise unimplemented * add get_filename_str to mock * rename methods * rename * refactor * improve coverage * test from bytes

…_windows (#19855) build(deps): bump form-data in /build_scripts/npm_windows Bumps [form-data](https://github.com/form-data/form-data) from 4.0.0 to 4.0.4. - [Release notes](https://github.com/form-data/form-data/releases) - [Changelog](https://github.com/form-data/form-data/blob/master/CHANGELOG.md) - [Commits](form-data/form-data@v4.0.0...v4.0.4) --- updated-dependencies: - dependency-name: form-data dependency-version: 4.0.4 dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* use per-puzzle cost to estimate DEDUP savings, rather than rerunning puzzles * restore SpendBundleAddInfo to have an optional cost. remove unused max_cost parameter from get_deduplication_info() * restore call to make_test_conds() taking cost as int * update test_dedup_by_fee() and fix big in make_bundle_spends_map_and_fee() * review comments * review comments * Addendum to use per-puzzle cost to estimate DEDUP savings (#19816) Addendum to use per-puzzle cost to estimate DEDUP savings. --------- Co-authored-by: Amine Khaldi <[email protected]>

…_linux (#19886) build(deps): bump form-data in /build_scripts/npm_linux Bumps [form-data](https://github.com/form-data/form-data) from 4.0.0 to 4.0.4. - [Release notes](https://github.com/form-data/form-data/releases) - [Changelog](https://github.com/form-data/form-data/blob/master/CHANGELOG.md) - [Commits](form-data/form-data@v4.0.0...v4.0.4) --- updated-dependencies: - dependency-name: form-data dependency-version: 4.0.4 dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Simplify `BlockStore` * Update chia/full_node/block_store.py Co-authored-by: Arvid Norberg <[email protected]> --------- Co-authored-by: Arvid Norberg <[email protected]>

…long_lived_datalayer_merkle_blob_from_main_cac84b5e057a074da6a72e2a8bbcc70ec0a09668

socket-security · 2025-08-01T16:01:38Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Package	Supply Chain Security	Quality	Maintenance
npm/n@8.2.0 ⏵ 10.2.0			^-4
pypi/aiohttp@3.12.13 ⏵ 3.12.14	⁺¹
pypi/ruff@0.11.11 ⏵ 0.12.4
pypi/botocore@1.39.1 ⏵ 1.39.11	⁺¹
pypi/cffi@1.16.0 ⏵ 1.17.1	⁺¹
pypi/boto3@1.39.1 ⏵ 1.39.11
pypi/aiosignal@1.3.1 ⏵ 1.4.0		⁺²
pypi/markupsafe@2.1.3 ⏵ 3.0.2	⁺¹
pypi/types-aiofiles@24.1.0.20250606 ⏵ 24.1.0.20250708

View full report

socket-security · 2025-08-01T16:01:39Z

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		`pypi/[email protected]` has a License Policy Violation. License: GPL-3.0-or-later (ruff-0.12.4/LICENSE) From: poetry.lock → `pypi/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore pypi/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`pypi/[email protected]` has a License Policy Violation. License: GPL-3.0-or-later (ruff-0.12.4.dist-info/licenses/LICENSE) From: `?` → `pypi/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore pypi/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`pypi/[email protected]` has a License Policy Violation. License: GPL-3.0-or-later (ruff-0.12.4.dist-info/licenses/LICENSE) From: `?` → `pypi/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore pypi/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`pypi/[email protected]` has a License Policy Violation. License: GPL-3.0-or-later (ruff-0.12.4.dist-info/licenses/LICENSE) From: `?` → `pypi/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore pypi/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`pypi/[email protected]` has a License Policy Violation. License: GPL-3.0-or-later (ruff-0.12.4.dist-info/licenses/LICENSE) From: `?` → `pypi/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore pypi/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`pypi/[email protected]` has a License Policy Violation. License: GPL-3.0-or-later (ruff-0.12.4.dist-info/licenses/LICENSE) From: `?` → `pypi/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore pypi/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`pypi/[email protected]` has a License Policy Violation. License: GPL-3.0-or-later (ruff-0.12.4.dist-info/licenses/LICENSE) From: `?` → `pypi/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore pypi/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`pypi/[email protected]` has a License Policy Violation. License: GPL-3.0-or-later (ruff-0.12.4.dist-info/licenses/LICENSE) From: `?` → `pypi/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore pypi/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`pypi/[email protected]` has a License Policy Violation. License: GPL-3.0-or-later (ruff-0.12.4.dist-info/licenses/LICENSE) From: `?` → `pypi/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore pypi/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`pypi/[email protected]` has a License Policy Violation. License: GPL-3.0-or-later (ruff-0.12.4.dist-info/licenses/LICENSE) From: `?` → `pypi/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore pypi/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`pypi/[email protected]` has a License Policy Violation. License: GPL-3.0-or-later (ruff-0.12.4.dist-info/licenses/LICENSE) From: `?` → `pypi/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore pypi/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`pypi/[email protected]` has a License Policy Violation. License: GPL-3.0-or-later (ruff-0.12.4.dist-info/licenses/LICENSE) From: `?` → `pypi/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore pypi/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`pypi/[email protected]` has a License Policy Violation. License: GPL-3.0-or-later (ruff-0.12.4.dist-info/licenses/LICENSE) From: `?` → `pypi/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore pypi/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`pypi/[email protected]` has a License Policy Violation. License: GPL-3.0-or-later (ruff-0.12.4.dist-info/licenses/LICENSE) From: `?` → `pypi/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore pypi/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`pypi/[email protected]` has a License Policy Violation. License: GPL-3.0-or-later (ruff-0.12.4.dist-info/licenses/LICENSE) From: `?` → `pypi/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore pypi/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`pypi/[email protected]` has a License Policy Violation. License: GPL-3.0-or-later (ruff-0.12.4.dist-info/licenses/LICENSE) From: `?` → `pypi/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore pypi/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`pypi/[email protected]` has a License Policy Violation. License: GPL-3.0-or-later (ruff-0.12.4.dist-info/licenses/LICENSE) From: `?` → `pypi/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore pypi/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`pypi/[email protected]` has a License Policy Violation. License: GPL-3.0-or-later (ruff-0.12.4.dist-info/licenses/LICENSE) From: `?` → `pypi/[email protected]` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `[email protected]`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore pypi/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

github-actions · 2025-08-01T18:01:37Z

File	Coverage	Missing Lines
`chia/_tests/core/test_merkle_set.py`	0.0%	lines 282
`chia/_tests/wallet/rpc/test_wallet_rpc.py`	98.2%	lines 284, 289
`chia/cmds/configure.py`	9.1%	lines 46-51, 56-59
`chia/cmds/peer_funcs.py`	12.5%	lines 12-14, 16, 21-23
`chia/consensus/block_rewards.py`	33.3%	lines 24, 26, 28, 30, 47, 49, 51, 53
`chia/full_node/full_node_rpc_api.py`	84.6%	lines 796-797
`chia/full_node/full_node_rpc_client.py`	92.2%	lines 55, 59-60, 190
`chia/plotting/check_plots.py`	0.0%	lines 12, 136
`chia/plotting/prover.py`	98.8%	lines 123
`chia/simulator/block_tools.py`	0.0%	lines 1314
`chia/wallet/cat_wallet/cat_wallet.py`	50.0%	lines 262
`chia/wallet/cat_wallet/r_cat_wallet.py`	75.0%	lines 145
`chia/wallet/did_wallet/did_wallet.py`	83.3%	lines 226
`chia/wallet/vc_wallet/cr_cat_wallet.py`	50.0%	lines 142
`chia/wallet/wallet_request_types.py`	95.0%	lines 1008
`chia/wallet/wallet_rpc_api.py`	92.0%	lines 1024, 1105

Total	Missing	Coverage
856 lines	45 lines	94%

richardkiss and others added 30 commits July 11, 2025 19:38

BlockHeightMapProtocol (#19798)

d01758f

[CHIA-2827] simplify MempoolManager by removing EligibilityAndAdditio…

46bc14b

…ns (#19801) * simplify MempoolManager by removing EligibilityAndAdditions * review comment * review comments

ruff issues (#19787)

7cee2b2

fewer mutable defaults (#19800)

ab9e729

* fewer mutable defaults * catchup

our miniupnpc wheels (#19814)

96aeaf3

* our miniupnpc_wheels * Update poetry.lock

Merge commit '96aeaf3e685f51a3ef9901228005109fc97687ed' into checkpoi…

e653170

…nt/main_from_release_2.5.5_96aeaf3e685f51a3ef9901228005109fc97687ed

recover chiabip tgz in poetry lock (#19806)

590317c

checkpoint: into main from release/2.5.5 @ 96aeaf3 (#19819)

2757c59

Source hash: 96aeaf3 Remaining commits: 0

CA Cert updates (#19817)

d3c165b

Newest Mozilla CA cert

[CHIA-3293] Port get_wallets to @marshal decorator (#19770)

018c3fe

* Port `get_wallets` * Suggestion by @altendky

Merge commit '590317c47fe5ef3406ee04835b7f730b80ce7fd0' into checkpoi…

0f0f2a0

…nt/main_from_release_2.5.5_590317c47fe5ef3406ee04835b7f730b80ce7fd0

update zstd to 1.5.7.2 (#19804)

13917fc

* update zstd to 1.5.7.2 * Update poetry.lock

Change minimium node version to 20 and npm version to 10 (#19845)

8b8035f

* Update to node 20 * Update another script for minimum npm version * update check for npm >= 10 * update npm version --------- Co-authored-by: Zlatko <[email protected]>

Update GUI to 1d95322 (#19849)

a586c5a

update GUI pin to 1d95322

Update GUI pin to efa99a4 (#19851)

a5640a8

update GUI pin to efa99a4

Update to ruff 0.12.4 (#19852)

ddc5a73

Upgrade `ruff` to 0.12.4.

Revert "update zstd to 1.5.7.2" (#19844)

5da9e79

Revert "update zstd to 1.5.7.2 (#19804)" This reverts commit 13917fc.

use strict for poetry check (#19840)

b23a980

* use strict for poetry check * ignore another * and request all

use now allowed randbytes and other helpers (#19838)

8bba601

checkpoint: into main from release/2.5.5 @ 590317c (#19835)

d048576

Source hash: 590317c Remaining commits: 1

integrate PLOT_V1_PHASE_OUT constant (#19820)

4576684

* integrate PLOT_V1_PHASE_OUT constant * current test chains won't work after the plot v1 phase-out

CHIA-3396 Remove Exception Catching from node RPC (#19825)

a10df3b

* remove extra exception catching * clean up node errors + tests * forgot to pre-commit * address using pytest wrong * clean up error handling * seperate out pytest tests

AmineKhaldi and others added 17 commits July 29, 2025 20:18

Update the anchor.

8c56bef

zstd 1.5.5.1 update available wheels in lock (#19876)

824da61

checkpoint: into main from release/2.5.5 @ a5640a8 (#19867)

d5e91a3

Source hash: a5640a8 Remaining commits: 3

Plotmanager v2 (#19832)

19a8329

* prover protocol and v2Prover * format name * format * refactor filename * tests/raise unimplemented * add get_filename_str to mock * rename methods * rename * refactor * improve coverage * test from bytes

markupsafe-3.0.2 (#19875)

97747d0

cffi-1.17.1 (#19874)

b500593

update cryptography to 45.0.5 (#19885)

f25a195

chiavdf 1.1.12 (#19882)

ee6c1d9

chiabip158 1.5.3 (#19881)

e9e5138

chiapos 2.0.11 (#19879)

b1ed7c8

Update .repo-content-updater.yml (#19884)

91ca11a

Simplify BlockStore (#19880)

cac84b5

* Simplify `BlockStore` * Update chia/full_node/block_store.py Co-authored-by: Arvid Norberg <[email protected]> --------- Co-authored-by: Arvid Norberg <[email protected]>

Merge commit 'cac84b5e057a074da6a72e2a8bbcc70ec0a09668' into catchup/…

70c3bdb

…long_lived_datalayer_merkle_blob_from_main_cac84b5e057a074da6a72e2a8bbcc70ec0a09668

altendky requested a review from a team as a code owner August 1, 2025 16:00

altendky added checkpoint_merge Changed Required label for PR that categorizes merge commit message as "Changed" for changelog labels Aug 1, 2025

altendky requested a review from a team as a code owner August 1, 2025 16:00

altendky removed request for a team August 1, 2025 16:01

emlowe approved these changes Aug 1, 2025

View reviewed changes

github-actions bot added the coverage-diff label Aug 1, 2025

altendky merged commit 6b5ee60 into long_lived/datalayer_merkle_blob Aug 2, 2025
483 of 489 checks passed

altendky deleted the catchup/long_lived_datalayer_merkle_blob_from_main_cac84b5e057a074da6a72e2a8bbcc70ec0a09668 branch August 2, 2025 00:03

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

catchup: into long_lived/datalayer_merkle_blob from main @ cac84b5e057a074da6a72e2a8bbcc70ec0a09668 #19892

catchup: into long_lived/datalayer_merkle_blob from main @ cac84b5e057a074da6a72e2a8bbcc70ec0a09668 #19892

Uh oh!

altendky commented Aug 1, 2025

Uh oh!

socket-security bot commented Aug 1, 2025

Uh oh!

socket-security bot commented Aug 1, 2025

Uh oh!

github-actions bot commented Aug 1, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

10 participants

catchup: into long_lived/datalayer_merkle_blob from main @ cac84b5e057a074da6a72e2a8bbcc70ec0a09668 #19892

catchup: into long_lived/datalayer_merkle_blob from main @ cac84b5e057a074da6a72e2a8bbcc70ec0a09668 #19892

Uh oh!

Conversation

altendky commented Aug 1, 2025

Uh oh!

socket-security bot commented Aug 1, 2025

Uh oh!

socket-security bot commented Aug 1, 2025

Uh oh!

github-actions bot commented Aug 1, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

10 participants