import { VaultContextInput } from './context';
/**
 * The fixed `appName` passed to the wallet's `deriveContextHash` for
 * Babylon vault derivations. The wallet displays this in its approval
 * dialog. Defined by `derive-vault-secrets.md` §2.2 — must not be
 * changed without coordinating a spec revision and a downstream
 * migration plan, as it provides app-level domain separation across
 * applications using the same wallet.
 */
export declare const VAULT_APP_NAME = "babylon-btc-vault";
/**
 * Minimal structural shape for the wallet capability needed by this
 * helper. Typed against the method directly so callers can pass any
 * value that implements `deriveContextHash` — `BitcoinWallet` from
 * this SDK, `IBTCProvider` from `@babylonlabs-io/wallet-connector`,
 * or a test mock — without depending on the rest of either interface.
 */
export interface DeriveContextHashCapableWallet {
    deriveContextHash(appName: string, context: string): Promise<string>;
}
/** Forward the deriveContextHash capability only when the wallet actually has it,
 * so seam guards (ensurePrePeginTermsApproval) can fire their typed error instead
 * of a mid-ceremony TypeError. */
export declare function forwardDeriveContextHash(wallet: Partial<DeriveContextHashCapableWallet>): Partial<DeriveContextHashCapableWallet>;
/**
 * Derive the 32-byte vault root from a wallet by encoding the
 * canonical {@link VaultContextInput} and forwarding to
 * `wallet.deriveContextHash`.
 *
 * Validates the wallet's output strictly: must be exactly 64
 * lowercase hex characters per `derive-context-hash.md` §2.1. A
 * conformant wallet always satisfies this, but we re-check at the
 * SDK boundary so a non-conformant wallet (or a wallet returning a
 * malformed value through a buggy adapter) fails loud here rather
 * than producing silently-wrong derived secrets downstream.
 *
 * The helper itself produces only valid spec inputs (`appName` is
 * the hardcoded `VAULT_APP_NAME`; `context` is hex of the 72-byte
 * `vaultContext`, always 144 chars lowercase), so input-side
 * validation is unnecessary.
 *
 * @param wallet - Any value implementing `deriveContextHash`.
 * @param input  - The canonical {@link VaultContextInput} that
 *                  uniquely identifies the vault. Encoded by
 *                  {@link buildVaultContext} into a 72-byte structure
 *                  before being hex-encoded for the wallet.
 * @stability frozen — on-chain-binding. The pair (`VAULT_APP_NAME`,
 * `vaultContext` encoding) is the wallet's input space; changing
 * either rotates the root and invalidates every secret derived from
 * it. `VAULT_APP_NAME` is fixed by `derive-vault-secrets.md` §2.2
 * and must never change without a coordinated spec revision.
 *
 * @returns 32-byte root suitable for {@link expandAuthAnchor},
 *          {@link expandHashlockSecret}, {@link expandWotsSeed}.
 * @throws If the wallet returns a non-64-char or non-lowercase-hex
 *         string. Errors from the wallet (user rejection,
 *         method-not-supported, etc.) propagate unchanged.
 */
export declare function deriveVaultRoot(wallet: DeriveContextHashCapableWallet, input: VaultContextInput): Promise<Uint8Array>;
//# sourceMappingURL=deriveVaultRoot.d.ts.map