Skip to content
Monolythium docs
GitHub

Recovery phrase — SDK boundary

Testnet

Exactly @monolythium/[email protected] exposes standard 24-word BIP-39 helpers on its /crypto export. mnemonicToAddress returns raw hexadecimal; convert it explicitly for user-facing bech32m display.

import { addressToBech32 } from "@monolythium/core-sdk";
import {
  generateMnemonic,
  mnemonicToAddress,
  validateMnemonic,
} from "@monolythium/core-sdk/crypto";


const mnemonic = generateMnemonic();
if (!validateMnemonic(mnemonic)) throw new Error("invalid mnemonic");


const addressHex = mnemonicToAddress(mnemonic);
const displayAddress = addressToBech32(addressHex);
console.log(displayAddress);

The repository compiles and runs this API shape. It does not print the phrase. Generating a phrase creates a live secret in the JavaScript process and is suitable only for an isolated SDK test—not operator key custody, a hosted service, an agent, or a website.

Custody warning

Section titled “Custody warning”
  • Never paste a real mnemonic into a documentation example, shell history, issue, chat, browser page, or hosted MCP.
  • Do not invent CLI import or keystore commands from old docs; verify them against the exact binary and operator release.
  • Do not assume one mnemonic safely covers consumer, operator, consensus, transport, or agent roles.
  • No supported agent-wallet or SLH-DSA alternate backup-key path is released.
  • Testnet 69420 is value-less and resettable; do not use real funds.

For production operator custody, require an independently reviewed key ceremony, role separation, backup and restore rehearsal, access control, compromise response, and exact release guidance.

Next

Section titled “Next”