op-vault and op-screening pinned `rand_core = "0.10"` with the `getrandom`
feature, but rand_core 0.10 removed that feature — so the ENTIRE openpay
workspace failed to resolve (cargo build -p op-core failed identically).
The pin was doubly wrong: both crates use rand_core 0.6's RNG traits —
op-vault via aes-gcm-siv 0.11's `aead::OsRng`, op-screening via
`rand_core::OsRng` + ed25519-dalek's `SigningKey::generate` — both of
which are rand_core 0.6 (already locked at 0.6.4; there was never a 0.10).
Pin both to `rand_core = "0.6"` (which HAS the getrandom feature gating
OsRng). The workspace now resolves; op-vault + op-screening compile and
their 94 tests pass; op-rails-x402 (added in af27203) now builds in the
workspace, not just standalone.
Co-Authored-By: Claude Opus 4.8 <[email protected]>
55110b23b2