Fix Cargo toml

Cargo.toml

@@ -29,11 +29,16 @@ frame-support = { path = "frame/support" }
 
 node-cli = { path = "bin/node/cli" }
 
-# This list of dependencies is necessary to build sassafras primitives.
-# `bandersnatch-experimental` is transitively passed between:
-# sp-consensus-sassafras → sp-application-crypto → sp-io → sp-keystore
-# Thus we end up having the bandersnatch functions "unlocked" in the `Keystore` trait.
-# Follow that we require bandersnatch implementations in the client keystore as well.
+# Dependencies necessary to optionaly build Sassafras related crates.
+#
+# Sassafras requires to enable `bandersnatch-experimental` feature.
+# This feature ends up being transitively enabled in:
+#  sp-consensus-sassafras → sp-application-crypto → sp-io → sp-keystore
+# Thus the bandersnatch experimental api is exposed in the `Keystore` trait.
+# Follow that we require to expose these functions in the client keystore as well.
+# At this stage, by default, we don't want this.
+# We prefer instead to keep sassafras crates (and thus bandersnatch feature) hidden
+# and optionally enabled via the `sassafras-experimental` feature.
 sp-consensus-sassafras = { path = "primitives/consensus/sassafras", optional = true }
 sc-keystore = { path = "client/keystore" }
 
@@ -327,6 +332,10 @@ members = [
 	"utils/binary-merkle-tree",
 ]
 
+exclude = [
+	"primitives/consensus/sassafras",
+]
+
 # The list of dependencies below (which can be both direct and indirect dependencies) are crates
 # that are suspected to be CPU-intensive, and that are unlikely to require debugging (as some of
 # their debug info might be missing) or to require to be frequently recompiled. We compile these