Source-level SDK orientation while development network 69420 is stale. Verify the published package, tag, exports, protocol compatibility, and current endpoint status before use; keep economic signing disabled.
Start with fixtures or a local node, classify remote responses as registered, stale, degraded, or advancing, and keep private keys inside a wallet or local signer. A hosted MCP service cannot hold a wallet or sign for you.
Compare the registry package to the canonical repository tag and release notes. Do not assume this page reflects the latest exports or a published package.
Validate serialization, address handling, error cases, and version negotiation without depending on a remote economic network.
Read the registered chain identity, head height, and latest timestamp independently. A successful response must not be labeled live if the head is stale.
The browser wallet uses standard BIP-39-to-ML-DSA-65 recovery and an encrypted extension-local vault. Never pass a mnemonic or raw key to Stele, hosted MCP, logs, or browser storage outside the wallet.
No mainnet is running. Treat transaction creation, broadcast, finality, markets, escrow, and spending-policy behavior as unavailable until a versioned release proves each capability.
This dated snapshot was observed on 16 July 2026. Re-probe before use and require actual advancement over time before changing the classification.
Use the canonical SDK documentation and source tag for exact APIs. Move to remote reads only with explicit degraded-state handling, and do not enable economic writes before mainnet and capability release gates are complete.