chore: bump dash-spv-ffi to v0.41-dev branch

[PastaPastaPasta]

Issue being fixed or feature implemented

bump dash-spv-ffi to use v0.41-dev

What was done?

How Has This Been Tested?

Built

Breaking Changes

None

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
• I have added "!" to the title and described breaking changes in the corresponding section if my code contains any
• 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

Summary by CodeRabbit

• Chores
  • Updated Core SDK integration dependency from a fixed version to a development branch to maintain alignment with ongoing development efforts.

[coderabbitai]

Walkthrough

The Rust SDK FFI package updates its Core SDK integration dependency from a fixed git tag (v0.40.0) to a moving development branch (v0.41-dev), while maintaining optional status.

Changes

Cohort / File(s)	Summary
Dependency version update packages/rs-sdk-ffi/Cargo.toml	Updated Core SDK FFI dependency reference from fixed tag v0.40.0 to development branch v0.41-dev

Estimated Code Review Effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A hop, skip, and version bump so spry,
From v0.40's tag we say goodbye,
To v0.41-dev we now align,
The SDK branch reaches for the sign,
Dependencies dance on the dev-branch line! 🌿

Pre-merge checks and finishing touches

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: updating the dash-spv-ffi dependency from v0.40.0 to the v0.41-dev branch in Cargo.toml.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/bump-dash-spv

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dee924e and 06b4c8b.

📒 Files selected for processing (1)

• packages/rs-sdk-ffi/Cargo.toml (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

packages/rs-sdk-ffi/**

📄 CodeRabbit inference engine (AGENTS.md)

Keep iOS/FFI Rust SDK artifacts in packages/rs-sdk-ffi

Files:

• packages/rs-sdk-ffi/Cargo.toml

🧠 Learnings (8)

📓 Common learnings

Learnt from: lklimek
Repo: dashpay/platform PR: 2254
File: packages/rs-sdk/src/sdk.rs:585-585
Timestamp: 2024-10-18T15:39:51.172Z
Learning: The 'platform' project uses Rust version 1.80, so code in 'packages/rs-sdk' can use features available in Rust 1.80, such as the `abs_diff()` method.

Learnt from: QuantumExplorer
Repo: dashpay/platform PR: 2431
File: packages/rs-drive/Cargo.toml:55-60
Timestamp: 2025-01-19T07:36:46.042Z
Learning: The grovedb dependencies in packages/rs-drive/Cargo.toml and related files are intentionally kept at specific revisions rather than using the latest stable version, with plans to update them at a later time.

Learnt from: CR
Repo: dashpay/platform PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-09-12T13:18:08.661Z
Learning: Applies to packages/rs-sdk-ffi/** : Keep iOS/FFI Rust SDK artifacts in packages/rs-sdk-ffi

Learnt from: lklimek
Repo: dashpay/platform PR: 2232
File: packages/rs-sdk/src/mock/sdk.rs:90-95
Timestamp: 2024-10-10T10:30:19.883Z
Learning: In `packages/rs-sdk/src/mock/sdk.rs`, the `load_expectations` method in `MockDashPlatformSdk` remains asynchronous (`async`) for backward compatibility, even though it now delegates to the synchronous `load_expectations_sync` method.

Learnt from: CR
Repo: dashpay/platform PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-07T22:18:50.883Z
Learning: Applies to packages/rs-sdk-ffi/**/*.{h,rs} : Follow unified SDK function prefixes: dash_core_sdk_* for Core, dash_sdk_* for Platform, dash_unified_sdk_* for unified APIs

📚 Learning: 2025-01-19T07:36:46.042Z

Learnt from: QuantumExplorer
Repo: dashpay/platform PR: 2431
File: packages/rs-drive/Cargo.toml:55-60
Timestamp: 2025-01-19T07:36:46.042Z
Learning: The grovedb dependencies in packages/rs-drive/Cargo.toml and related files are intentionally kept at specific revisions rather than using the latest stable version, with plans to update them at a later time.

Applied to files:

• packages/rs-sdk-ffi/Cargo.toml

📚 Learning: 2025-09-07T22:18:50.883Z

Learnt from: CR
Repo: dashpay/platform PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-09-07T22:18:50.883Z
Learning: Applies to packages/rs-sdk-ffi/**/*.{h,rs} : Follow unified SDK function prefixes: dash_core_sdk_* for Core, dash_sdk_* for Platform, dash_unified_sdk_* for unified APIs

Applied to files:

• packages/rs-sdk-ffi/Cargo.toml

📚 Learning: 2024-10-18T15:39:51.172Z

Learnt from: lklimek
Repo: dashpay/platform PR: 2254
File: packages/rs-sdk/src/sdk.rs:585-585
Timestamp: 2024-10-18T15:39:51.172Z
Learning: The 'platform' project uses Rust version 1.80, so code in 'packages/rs-sdk' can use features available in Rust 1.80, such as the `abs_diff()` method.

Applied to files:

• packages/rs-sdk-ffi/Cargo.toml

📚 Learning: 2025-03-11T09:39:23.071Z

Learnt from: shumkov
Repo: dashpay/platform PR: 2489
File: packages/rs-dpp/Cargo.toml:32-32
Timestamp: 2025-03-11T09:39:23.071Z
Learning: In the Dash Platform project, dependencies are currently managed using Git repository references with tags (repo+tag format in Cargo.toml) rather than published crates, as the team is not currently publishing crates to crates.io.

Applied to files:

• packages/rs-sdk-ffi/Cargo.toml

📚 Learning: 2025-09-03T16:37:11.605Z

Learnt from: QuantumExplorer
Repo: dashpay/platform PR: 2756
File: packages/rs-drive-abci/src/execution/platform_events/core_based_updates/update_masternode_list/update_state_masternode_list/v0/mod.rs:11-11
Timestamp: 2025-09-03T16:37:11.605Z
Learning: In packages/rs-dpp/Cargo.toml, the abci feature already includes core_rpc_client, and core_rpc_client is defined as ["dep:dashcore-rpc"]. This means rs-drive-abci can access dashcore-rpc types through dpp when using the abci feature.

Applied to files:

• packages/rs-sdk-ffi/Cargo.toml

📚 Learning: 2025-09-12T13:18:08.661Z

Learnt from: CR
Repo: dashpay/platform PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-09-12T13:18:08.661Z
Learning: Applies to packages/rs-sdk-ffi/** : Keep iOS/FFI Rust SDK artifacts in packages/rs-sdk-ffi

Applied to files:

• packages/rs-sdk-ffi/Cargo.toml

📚 Learning: 2024-10-10T10:30:19.883Z

Learnt from: lklimek
Repo: dashpay/platform PR: 2232
File: packages/rs-sdk/src/mock/sdk.rs:90-95
Timestamp: 2024-10-10T10:30:19.883Z
Learning: In `packages/rs-sdk/src/mock/sdk.rs`, the `load_expectations` method in `MockDashPlatformSdk` remains asynchronous (`async`) for backward compatibility, even though it now delegates to the synchronous `load_expectations_sync` method.

Applied to files:

• packages/rs-sdk-ffi/Cargo.toml

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (8)

• GitHub Check: Build Docker images (Dashmate helper, dashmate-helper, dashmate-helper) / Build Dashmate helper image
• GitHub Check: Build Docker images (Drive, drive, drive-abci) / Build Drive image
• GitHub Check: Build Docker images (RS-DAPI, rs-dapi, rs-dapi) / Build RS-DAPI image
• GitHub Check: Build JS packages / Build JS
• GitHub Check: Build rs-sdk-ffi for iOS targets (aarch64-apple-ios)
• GitHub Check: Rust crates security audit
• GitHub Check: Build rs-sdk-ffi for iOS targets (aarch64-apple-ios-sim)
• GitHub Check: Swift SDK and Example build (warnings as errors)

🔇 Additional comments (1)

packages/rs-sdk-ffi/Cargo.toml (1)

25-25: Verify intent and impact of dash-spv-ffi branch reference.

The review raises reproducibility concerns, but two key findings affect the assessment:

1. Cargo.lock enforces determinism: A root-level Cargo.lock is committed to the repository, which locks all dependencies to specific revisions regardless of Cargo.toml branch references. Reproducible builds are enforced at lock time, not at branch-reference time.

2. Branch references are an established pattern: The codebase already uses branch references in multiple packages (e.g., packages/rs-sdk/Cargo.toml tracks bip37-bloom-filter on develop, packages/rs-dpp/Cargo.toml tracks jsonschema on configure_regexp). Using branch refs is not a new or inconsistent pattern in this project.

However, tracking a development branch (v0.41-dev) remains a decision that should be intentional. Verify:

• Is tracking v0.41-dev intentional (e.g., to stay aligned with upcoming Core SDK releases), or should this pin to a specific commit (rev = "...")?
• Was this tested against v0.41-dev before merge?
• If this is intentional, add a comment to Cargo.toml or document in the PR to explain the rationale.

---

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.}

[github-actions]

✅ DashSDKFFI.xcframework built for this PR.

• Workflow run: https://github.com/dashpay/platform/actions/runs/19050177971
• Artifacts: DashSDKFFI.xcframework (folder), DashSDKFFI.xcframework.zip, xc_checksum.txt

SwiftPM (host the zip at a stable URL, then use):

.binaryTarget(
  name: "DashSDKFFI",
  url: "https://your.cdn.example/DashSDKFFI.xcframework.zip",
  checksum: "fb985038ba2e844997086084eb2bab0bf0928c575773b7a8fc0fe4e8aae2af89"
)

Xcode manual integration:

• Download 'DashSDKFFI.xcframework' artifact from the run link above.
• Drag it into your app target (Frameworks, Libraries & Embedded Content) and set Embed & Sign.
• If using the Swift wrapper package, point its binaryTarget to the xcframework location or add the package and place the xcframework at the expected path.