crypto: Re-export key types at crate root
What changed, and why it matters
This commit simply makes several existing key types easier to import by re-exporting them at the top level of the crypto crate. It does not change any behavior, logic, or security properties of the code.
No security action needed; this is a routine API ergonomics change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The patch adds a pub use re-export block in crypto/src/lib.rs for FullPublicKey, Keypair, PrivateKey, LegacyPublicKey, and XOnlyPublicKey from the key module, gated behind the alloc feature. No implementation code was modified.
Changed components
crypto/src/lib.rsInspect captured patch +6 / −0
diff --git a/crypto/src/lib.rs b/crypto/src/lib.rs
index 20a6c692..e108ef3e 100644
--- a/crypto/src/lib.rs
+++ b/crypto/src/lib.rs
@@ -32,5 +32,11 @@ pub mod key;
#[cfg(feature = "alloc")]
pub mod sighash;
+#[doc(inline)]
+#[cfg(feature = "alloc")]
+pub use self::{
+ key::{FullPublicKey, Keypair, PrivateKey, LegacyPublicKey, XOnlyPublicKey},
+};
+
#[cfg(feature = "alloc")]
include!("../include/newtype.rs"); // Explained in `REPO_DIR/docs/README.md`.
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.