KasCoven VaultsGitHub repo

DECENTRALIZED RECOVERY

Access your on-chain vaults without relying on this website

KasCoven vaults are designed so the important recovery data is written into Kaspa transaction payloads. The website is a convenient interface, but it should not be the only path to your funds.

WALLET-ENABLED RECOVERY

Run recovery independently

Clone the GitHub repository and start it locally or on an independent mirror. Then open http://localhost:3000/recovery/tool, connect Kaspire or Kasware, and import or scan your vaults.

Get recovery tool on GitHub
01

What stays on-chain

Vault type, owner, beneficiary, vault address, timing data and redeem script are embedded in the vault creation transaction. A compatible scanner can find those records from the Kaspa blockDAG.

02

What the website does

This site scans your wallet history, reconstructs the vault state, prepares unlock or claim transactions and broadcasts them. Losing the site does not erase the vault UTXO.

03

What you should save

Export a recovery file after creating a vault. It contains no private keys, but keeps the exact protocol data close at hand if you later need another app, mirror or local CLI.

END USER GUIDE

If vaults.kaslab.space is unavailable

  1. Do not panic.

    Your funds are not stored on the website. They remain in Kaspa vault UTXOs.

  2. Start an independent local copy.

    Clone the GitHub repository, install, build and start it, then open http://localhost:3000/recovery/tool. By default it uses api.kaspa.org for chain data and the Kaspa public wRPC resolver for broadcast, so no own node is required.

  3. Connect the matching wallet and import.

    Connect Kaspire or Kasware in the local recovery workspace. Import recovery JSON or scan the connected owner or beneficiary address, then refresh live chain data before acting.

  4. Or scan directly by address.

    The CLI can scan public Kaspa transaction history for vault creation payloads associated with an owner or beneficiary address.

  5. Create the unlock or claim transaction.

    When the time lock or inactivity period has passed, create a transaction draft with a compatible KasCoven API, then review, sign and broadcast it with compatible wallet tooling.

CLI RECOVERY

Run recovery without the hosted website

The CLI scans on-chain creation payloads through a Kaspa history API. It can export portable recovery JSON and request unsigned release drafts from a compatible KasCoven API. Wallet review and signing remain separate.

git clone https://github.com/KaspaHUB21/KasCoven-Vaults---Kaspa-Covenant-Vaults.gitcd KasCoven-Vaults---Kaspa-Covenant-Vaultspnpm installpnpm buildpnpm startOpen http://localhost:3000/recovery/toolpnpm recovery scan --address kaspa:YOUR_ADDRESS --mode allpnpm recovery export --address kaspa:YOUR_ADDRESS --mode all --out recovery.jsonpnpm recovery claim-draft --file recovery.json --vault 0 --api http://127.0.0.1:3000/api/timelock-vault

Important limits

Recovery files do not contain private keys and cannot steal funds by themselves, but they reveal vault metadata. Keep them somewhere you trust. A saved record is not proof that its referenced UTXO is still unspent. Always refresh live chain state before acting; covenant rules and the current unspent vault UTXO are authoritative.