build: bump rust-dashcore to v0.42-dev 0093278

[lklimek]

Issue being fixed or feature implemented

Refresh our dashpay/rust-dashcore pin to the latest v0.42-dev HEAD (37 commits ahead of the previous pin, 88e8a9aa). Keeps platform aligned with ongoing key-wallet / dash-spv work and picks up several SPV, key-wallet, and FFI fixes that other clients are already consuming.

What was done?

Workspace bump from rev = 88e8a9aa1eadce79c8177f757f6741f8a55a83f5 to rev = 0093278609a22fc53086bfef569b74bf10544982 for:

• dashcore, dash-spv, dash-spv-ffi
• key-wallet, key-wallet-ffi, key-wallet-manager
• dashcore-rpc

Added dash-network (new standalone crate extracted from dashcore upstream in PR dashpay/rust-dashcore#679) to [workspace.dependencies], pinned to the same rev and required by rs-platform-wallet-ffi for FFINetwork (now behind the ffi feature of dash-network rather than re-exported from key-wallet-ffi).

Breaking changes from upstream that actually hit this codebase:

• WalletType::WatchOnly is now a unit variant (refactor(key-wallet): make WatchOnly / ExternalSignable unit variants rust-dashcore#654). Updated the create_dummy_wallet test helper in rs-platform-wallet/src/platform_wallet_info/contact_requests.rs — dropped the xpub payload and removed the now-unused ExtendedPubKey import.
• WalletInfoInterface::get_spendable_utxos removed (refactor(key-wallet): move spendable_utxos from wallet to account rust-dashcore#643, moved to account level). Dropped the matching impl stub on PlatformWalletInfo — no other platform callers.
• FFINetwork relocated (refactor: dashcore exposes a FFI compatible Network enum so dependents don't have to make their own wrapper rust-dashcore#642, feat: withdrawals status sync #679). Added dash-network as a workspace dep with features = ["ffi"] in rs-platform-wallet-ffi and repointed two imports to dash_network::ffi::FFINetwork.

Other upstream refactors (FFIExtendedPriv/PubKey renames, new FFIError, AssetLockTx DIP-00X fix, Address<NetworkChecked> serde fix) did not surface in the platform build — those APIs aren't referenced here.

How Has This Been Tested?

• cargo check --workspace --all-targets — pass
• cargo test --workspace --no-run — all test binaries compile
• cargo fmt --all --check — clean
• cargo clippy --workspace --all-targets -- -D warnings — same pre-existing warnings as v3.1-dev HEAD in rs-platform-value / rs-platform-serialization; not introduced by this bump

The full runtime test suite (yarn test) needs a running local node and was not executed. Recommend running it before merge.

Breaking Changes

None for platform consumers. All API shifts are internal (workspace-local dependency rev + the three call-site adjustments listed above).

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests — not applicable; pure dependency bump
• I have added "!" to the title and described breaking changes in the corresponding section if my code contains any — no platform-facing breaking changes
• I have made corresponding changes to the documentation if needed

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

_{🤖 Co-authored by Claudius the Magnificent AI Agent}

[coderabbitai]

Warning

Rate limit exceeded

@lklimek has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 19 minutes and 32 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 19 minutes and 32 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: de439145-6ce5-4a0e-8856-c4ff21bcef54

📥 Commits

Reviewing files that changed from the base of the PR and between 2b657d8 and a7e3000.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (6)

• Cargo.toml
• packages/rs-platform-wallet-ffi/Cargo.toml
• packages/rs-platform-wallet-ffi/src/platform_wallet_info.rs
• packages/rs-platform-wallet-ffi/tests/integration_tests.rs
• packages/rs-platform-wallet/src/platform_wallet_info/contact_requests.rs
• packages/rs-platform-wallet/src/platform_wallet_info/wallet_info_interface.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/bump-rust-dashcore-v0.42-dev

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[thepastaclaw]

🔍 Review in progress — actively reviewing now (commit a7e3000)
Queue position: 2/18

[thepastaclaw]

Code Review

I verified commit a7e300078e4bb2d53c4f0c8aada983cd7d3c4954 against the source and diff. The change removes only a two-line comment from the #[cfg(test)] helper create_dummy_wallet in packages/rs-platform-wallet/src/platform_wallet_info/contact_requests.rs; the executable code at line 486 is unchanged, and there are no consensus, correctness, or test-behavior implications.

Reviewed commit: a7e3000