Skip to content

Conversation

@Sosthene00
Copy link
Collaborator

A proposal to move the whole cygnet3/rust-silentpayments#110 crate inside spdk as a protocol module.

  • Isolate sp-address in its own crate so that project that only need silent payment address parsing can do it without pulling a lot of dependencies
  • Preserve the feature gating so that you can basically build spdk-core with only a subset of features: sending/receiving only, scanner without sending, full wallet...
  • Anticipate the deprecation of rust-silentpayment when libsecp module will get merged
  • Hopefully easier to manage dependencies and versioning (esp https://docs.rs/bitcoin/latest/bitcoin/ and https://crates.io/crates/secp256k1)
  • Still a lot of optimisation and refactoring to be done

Not sure if it's the right approach so getting feedback on that design first.

@Sosthene00 Sosthene00 added the enhancement New feature or request label Jan 7, 2026
@cygnet3
Copy link
Owner

cygnet3 commented Jan 8, 2026

I agree with this concept, though I still haven't looked at the workspace PR too in-depth to make a proper judgement. I'd like to dedicate some time to SPDK (this PR but also the workspace one in general), once the dana address stuff is merged and released. Either way, I agree that it's probably good idea to unite the crates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants