Expand description
The chain-defined compute core and native Rust SDK for Bittensor clients.
Rust owns the chain-defined pieces (crypto, SCALE, extrinsic payloads, metadata digests) and now also exposes a thin native client and semantic transaction executor over those primitives. Binding crates may reuse the same client or expose only the compute surface to another language.
See sdk/bittensor-core-spec.md for the full design.
Re-exports§
pub use client::Client;pub use error::CoreError;pub use transaction::Executor;pub use transaction::IntentCall;pub use transaction::Plan;pub use transaction::Policy;pub use transaction::SignerRole;pub use transaction::Spend;pub use transaction::Wallet;
Modules§
- client
- Native chain access for the Rust SDK.
- codec
- SCALE encode/decode against a
crate::runtime::Runtime. - digest
- RFC-0078 merkleized-metadata: the digest signed via
CheckMetadataHashand the type proof hardware wallets need to decode a transaction on-device. - error
- The single error type crossing the core’s boundary.
- keyfile_
env - Pure environment password compatibility, without changing process variables.
- keyfiles
- Bittensor wallet keyfile encryption and JSON codec — compatible with the
bittensor-walleton-disk format (absorbed frompy-sp-core). - keys
- Substrate
sp-corekey primitives (absorbed frompy-sp-core). - mlkem
- ML-KEM-768 + XChaCha20Poly1305 sealing (the MEV shield), absorbed from
bittensor-drandand rewritten as safe Rust (the old C ABI is gone). - pow
- Public registration challenge mining. GPU drivers are optional and loaded at runtime; no signing material enters the miner or device memory.
- runtime
Runtime: one immutable object per spec version, parsed from the rawMetadataVersionedbytes the transport already downloads and caches.- signers
- Hardware and remote signing backends.
- timelock
- Drand quicknet timelock encryption (absorbed from
bittensor-drand). - transaction
- Semantic transaction planning and policy for the native Rust SDK.