Skip to content

Update to chia-blockchain 2.7.0 - #462

Open
emlowe wants to merge 3 commits into
developfrom
EL.chia-blockchain2.7.0
Open

Update to chia-blockchain 2.7.0#462
emlowe wants to merge 3 commits into
developfrom
EL.chia-blockchain2.7.0

Conversation

@emlowe

@emlowe emlowe commented Apr 9, 2026

Copy link
Copy Markdown
Contributor

Update to chia-blockchain 2.7.0

@socket-security

socket-security Bot commented Apr 9, 2026

Copy link
Copy Markdown

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

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedzstd@​1.5.5.1 ⏵ 1.5.7.310010090100100
Updatedhsms@​0.3.1 ⏵ 0.3.296 +1100100100100
Addedchialisp@​0.4.3100100100100100
Updatedchia-rs@​0.27.0 ⏵ 0.41.1100 +1100100100100

View full report

@socket-security

socket-security Bot commented Apr 9, 2026

Copy link
Copy Markdown

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 Medium
Native binaries present: pypi chialisp

Location: Package overview

From: poetry.lockpypi/chialisp@0.4.3

ℹ Read more on: This package | This alert | Why is native code a concern?

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 support@socket.dev.

Suggestion: Verify that the inclusion of native code is expected and necessary for this package's functionality. If it is unnecessary or unexpected, consider using alternative packages without native code to mitigate potential risks.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/chialisp@0.4.3. 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 Low
Potential code anomaly (AI signal): pypi zstd is 100.0% likely to have a medium risk anomaly

Notes: The fragment implements a conventional and well-structured thread pool. The main security concern is the execution of user-provided callbacks (job.function) with arbitrary opaque context, which can perform any action permitted by the host process. No malicious behavior is evident within the pool code itself (no embedded backdoors or hidden data). The risk stems from untrusted callbacks and concurrency complexity; overall risk is moderate and contingent on downstream usage.

Confidence: 1.00

Severity: 0.60

From: poetry.lockpypi/zstd@1.5.7.3

ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly?

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 support@socket.dev.

Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/zstd@1.5.7.3. 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

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

Updates this service’s Chia dependencies and adapts wallet/full-node RPC integrations to the chia-blockchain 2.7.0 request/response types.

Changes:

  • Bump chia-blockchain from 2.5.6 to 2.7.0 (and update the lockfile accordingly).
  • Migrate several wallet RPC calls to typed request objects (e.g., GetWallets, GetTransactions, SelectCoins, CreateSignedTransaction).
  • Update CI test-cache version used by the GitHub Actions workflow.

Reviewed changes

Copilot reviewed 7 out of 8 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
pyproject.toml Bumps chia-blockchain dependency to 2.7.0.
poetry.lock Updates resolved dependency graph for chia-blockchain 2.7.0 (incl. Python >=3.10 constraints and new deps).
app/crud/chia.py Switches CoinRecord import to chia_rs to align with updated chia types.
app/core/utils.py Adds puzzle-hash-to-address helper and updates wallet RPC calls to typed request objects.
app/core/climate_wallet/wallet.py Updates wallet RPC calls (select coins, memos handling) and sets to_address for detokenization tx creation.
app/api/v1/transactions.py Updates transactions endpoints to typed RPC request/response objects.
app/api/v1/keys.py Updates GetPrivateKey call to use named parameter.
.github/workflows/tests.yaml Updates BLOCKS_AND_PLOTS_VERSION used for cached test data.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread app/api/v1/transactions.py Outdated
wallet_objs: list[ChiaJsonObject] = await wallet_rpc_client.get_wallets(
wallet_type=WalletType.CAT,
wallets_response = await wallet_rpc_client.get_wallets(
GetWallets(type=uint16(WalletType.CAT)),

Copilot AI Apr 9, 2026

Copy link

Choose a reason for hiding this comment

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

GetWallets(type=uint16(WalletType.CAT)) is inconsistent with the rest of the codebase which treats WalletType as an enum and uses .value when an int is required (e.g., wallet_info.type != WalletType.CAT.value). Passing the enum instance here may fail if WalletType is not an IntEnum. Use the numeric value consistently (e.g., uint16(WalletType.CAT.value)), or cast explicitly with int(WalletType.CAT) if that’s the intended contract.

Suggested change
GetWallets(type=uint16(WalletType.CAT)),
GetWallets(type=uint16(WalletType.CAT.value)),

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants