DE

RESKEY PRO · TECHNICAL QUESTIONS

Clear rules.
Independent paths.

Reskey Pro uses Liana, open-source Bitcoin wallet software developed by Wizardsardine. Liana describes the signing keys, thresholds and time delays in a Bitcoin wallet policy. Reskey can help co-sign, but cannot transfer your Bitcoin with its key alone.

Download Liana ↗Explore the three paths ↓

The button opens Liana's official Community Edition download page. Reskey is a separate service, not the publisher of Liana.

HOW THE SIGNING PATHS WORK

Three ways through time.

This is the illustrative basic setup shown on the Reskey Pro page. Your setup can be tailored to your needs. The wallet descriptor records your wallet’s full rules: the chosen keys, the number of signatures required and the delays in Bitcoin blocks. The 2-of-2, 2-of-3 and 1-of-2 paths below are only one example.

01 · AVAILABLE IMMEDIATELY2-of-2

Normal collaborative signing

Your primary key and Reskey's separate key must both sign a normal transaction. One stolen, lost or misused key cannot satisfy this path by itself. Reskey is a co-signer; it is not a custodian with unilateral spending power.

Benefit: Two independently controlled signatures make a forced or unauthorized immediate transaction far harder: coercion, a compromised device or a software error affecting only one signer cannot satisfy the 2-of-2 path on its own. If a key becomes unusable instead, the delayed recovery paths can avert permanent loss—provided their separate keys, backups and descriptor survive.

02 · AFTER THE FIRST DELAY2-of-3

Recovery with another pair

The example has two separately controlled keys on your side and one Reskey key. Once this path matures, any two can sign. Your two keys allow spending without Reskey. If you lose one, the remaining key and Reskey can help with recovery.

Boundary: the delay does not restore a missing key. You can add more independently held co-signers of your choice to this delayed path and adjust the number of signatures required. Wallet-policy and signing-device limits still apply. This makes losing all your usable keys at once less likely when keys and backups are kept separately. Reskey alone is still insufficient in the illustrated 2-of-3 path.

03 · AFTER A LONGER DELAY1-of-2

Independent long-term exit

The illustrated final path allows either a recovery key you control or a separately held inheritance key to spend after the longer delay. Reskey's signature is not part of this path. It can provide a route for inheritance or an exit if the company is gone.

Boundary: you can also add more independent recovery signers to this path. Wallet-policy and signing-device limits still apply. A 1-of-N version reduces the chance that all keys for this recovery path are lost, but every listed key can spend alone once the delay matures. Separate custody and clear access instructions therefore matter as much as the timelock.

A timelock is measured in Bitcoin blocks for each unspent output. It controls when a delayed path can be used; it does not automatically transfer bitcoin or make Reskey's key stronger. Exact delays are set at wallet creation, not by this illustration.

FAILURE MODES

What changes if something goes wrong?

The keys and delays create alternatives for specific failures. The outcome still depends on which keys and backups remain available when each path matures.

RESKEY UNAVAILABLE

You retain a later exit.

Normal 2-of-2 signing stops. After the first delay, your two keys can satisfy the 2-of-3 path without Reskey. After the longer delay, the independent 1-of-2 path can also be used by its designated keyholder.

ONE OF YOUR KEYS LOST

Recovery has time to work.

One of your remaining keys and Reskey can use the 2-of-3 path after its delay. The final path offers another route if its independently held key survives. Neither route helps if all required keys and their backups are gone.

RESKEY KEY COMPROMISED

One key is not enough.

Reskey's key alone cannot satisfy the 2-of-2 or 2-of-3 thresholds, and it is absent from the illustrated final path. Collusion with another eligible signer, however, can satisfy a matured 2-of-3 path.

DEATH OR INCAPACITY

Succession can be planned.

An heir with the designated inheritance key and the wallet descriptor can use the final path once its delay has matured. The heir needs secure instructions and a way to find the necessary backup; merely naming an heir does not deliver access.

TECHNICAL QUESTIONS

What you should verify.

The policy is only as useful as the keys, backups and ongoing operation behind it.

Does any transaction restart every delay?

No. Liana's relative timelocks apply to individual unspent outputs. Spending a coin into a new wallet output, including a send-to-self refresh, starts a new countdown for that new output. Other untouched coins keep their own countdown. Monitor and refresh each relevant coin before a recovery path becomes available if you intend to keep it dormant.

What must be backed up?

Back up every signing key or seed separately and preserve the wallet descriptor. The descriptor records the full policy, including keys and delays; seeds alone may not be enough to reconstruct the wallet. Verify the descriptor and receive addresses on compatible signing devices during setup.

What if Liana or Reskey disappears?

The rules are encoded in Bitcoin scripts, not a Reskey database. Liana is open source, and the descriptor can be restored with compatible tools and a Bitcoin backend. You still need the relevant keys, descriptor, technical access and—where applicable—to wait for a delayed path. Immediate 2-of-2 spending still needs Reskey while that is the only mature path.

Does this remove every security risk?

No policy protects against every scenario. Enough compromised or colluding keys can spend through an available path. Loss of all usable keys or the descriptor, an incorrect setup, unsafe backups, coercion of enough signers, a missed refresh or vulnerable devices can defeat the plan. The benefit is that those risks can be separated, documented and tested rather than concentrated in Reskey.

THE TRUST BOUNDARY

Verify the policy. Keep your own exit.

Reskey cannot spend alone in the illustrated policy, and after the configured delays you have paths that exclude Reskey. That is a concrete limit on Reskey's power—not a promise of instant access without its cooperation or a guarantee against all failures. Review the final descriptor, key custody, timelocks and recovery rehearsal before transferring Bitcoin to the wallet.

Back to Reskey Pro →

READ THE PRIMARY SOURCES

Learn more from Liana's open-source repository, the official setup guide and the recovery guide.