build(deps): bump solana-stake-program from 3.1.5 to 4.0.0

[dependabot]

Bumps solana-stake-program from 3.1.5 to 4.0.0.

Changelog

Sourced from solana-stake-program's changelog.

Changelog

All notable changes to this project will be documented in this file.

Please follow the guidance at the bottom of this file when making changes The format is based on Keep a Changelog. This project adheres to Semantic Versioning and follows a Backwards Compatibility Policy

Release channels have their own copy of this changelog:

• edge - v4.0
• beta - v3.1
• stable - v3.0

4.0.0-Unreleased

RPC

Breaking

• --public-tpu-address and --public-tpu-forwards-address CLI arguments and setPublicTpuForwardsAddress, setPublicTpuAddress RPC methods now specify QUIC ports, not UDP.

Changes

• Added --enable-scheduler-bindings which binds an IPC server at <ledger-path>/scheduler_bindings.ipc for external schedulers to connect to.

Validator

Breaking

• Removed deprecated arguments
  • --accounts-db-clean-threads
  • --accounts-db-hash-threads
  • --accounts-db-read-cache-limit-mb
  • --accounts-hash-cache-path
  • --disable-accounts-disk-index
  • --dev-halt-at-slot
  • --monitor (exit subcommand)
  • --wait-for-exit (exit subcommand)

Deprecations

• Using mmap for --accounts-db-access-storages-method is now deprecated.

CLI

Changes

• Support Trezor hardware wallets using usb://trezor

Platform tools

Breaking

• cargo-build-sbf --debug now generates a file program.so.debug instead of program.debug.
• cargo-build-sbf --debug places all debug related objects inside target/deploy/debug.

Geyser

Changes

• Account update notifications have their fields populated from the account values post transaction execution. This means notifications for closed accounts (accounts with a balance of zero lamports) will no longer have their owner/data/etc manually zeroed out. Note that if the on-chain program does zero out any fields itself, those will remain zeroed out in the notification.

3.1.0

RPC

Breaking

• A signature verification failure in simulateTransaction() or the preflight stage of sendTransaction() will now be attached to the simulation result's err property as TransactionError::SignatureFailure instead of being thrown as a JSON RPC API error (-32003). Applications that already guard against JSON RPC exceptions should expect signature verification errors to appear on the simulation result instead. Applications that already handle the materialization of TransactionErrors on simulation results can now expect to receive errors of type TransactionError::SignatureFailure at those verification sites.

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)