import { type VaultAeadBackend, type VaultHashBackend } from "../namespaces/vault.crypto.js";
export declare const nodeVaultAeadBackend: VaultAeadBackend;
/**
 * Install the native backend when this OpenSSL has the cipher. Returns whether
 * it took, so a test can assert the guard rather than infer it. Any failure
 * leaves the `@noble` default untouched — the native path is an optimization,
 * never a correctness dependency.
 */
export declare function installNodeVaultAeadBackend(): boolean;
/**
 * The Node-native protocol-hash backend (vault-native-hash). Same seam
 * pattern, second slot: `sha256Hex` is the chokepoint every protocol hash
 * flows through, and on the receipt-verified open/seal paths it hashes whole
 * multi-megabyte frames on pure-JS `@noble/hashes` — the measured leftover
 * after the AEAD moved to OpenSSL. `createHash` is sync (the vault crypto
 * surface is sync public API), byte-compatible, and already hashes packs in
 * `vault-recover.ts`/`vault-mirror.ts`.
 */
export declare const nodeVaultHashBackend: VaultHashBackend;
/**
 * Install the native hash backend after a live probe (vault-native-hash
 * design D3): a backend that does not reproduce the known digest — or throws —
 * registers nothing and the `@noble` default keeps serving. The `backend`
 * parameter exists only so the byte-equality suite can drive the refusing
 * branch; production callers pass nothing.
 */
export declare function installNodeVaultHashBackend(backend?: VaultHashBackend): boolean;
//# sourceMappingURL=vault-native-crypto.d.ts.map