We're excited to announce that the RITREK app is now available on Google Play. Create, upload, monitor, and initiate Bitcoin Timelock-Recovery plans from your Android device. Your seed phrase remains secure on your hardware wallet. Here's how to create a Timelock-Recovery plan with the RITREK app: Step 1: Get the app play.google.com/store/apps/d… Step 2: Generate a Bitcoin address on a second, easily accessible wallet. This is the destination wallet your Bitcoin will move to during a recovery event. For example, if you use a passphrase on your hardware wallet (also known as "the 25th word" of your 24-word seed), your second wallet could be the same hardware wallet but without the passphrase. Another option is a wallet held by a friend or family member. Step 3: Connect your Trezor or Ledger wallet. Trezor users should download Trezor Suite Lite first: play.google.com/store/apps/d… Advanced users with hardware wallets other than Trezor or Ledger can use Electrum's built-in Timelock-Recovery plugin. Cable connection only - the app does not support Bluetooth yet. Step 4: Sign the two Timelock-Recovery transactions. Enter the timelock that you wish (default: 90 days) and a reasonable fee rate* - then sign the two timelock-recovery transactions from your main wallet to the second-wallet address. As always, verify the destination address on your hardware wallet screen! Step 5: Your Recovery-Plan is ready. Lost access to your main wallet? Swipe the button to initiate the transaction that will move your Bitcoin from your main wallet to the second wallet within the timelock period. You can also download the pre-signed transactions as a JSON file and send it to friends and family - no one can change the destination or timelock of these transactions. Your relatives could then initiate the recovery by going to ritrek.com/send If your data leaks and the pre-signed transactions are broadcast against your will, you'll receive a push notification and have the full timelock period (i.e. 90 days) to move your Bitcoin elsewhere. Limitations RITREK is suitable as a recovery solution for wallets that are not used frequently. Spending any amount of Bitcoin from your main wallet will invalidate the recovery plan (the pre-signed transactions) that was created before - and you will have to start over. Additionally, new funds received after the recovery plan is created will not be covered by the existing plan. If you want to keep using the same hardware wallet with the same seed phrase, we recommend using a different account for any new funds you may receive: trezor.io/guides/trezor-suit… RITREK only works with modern Native SegWit wallets (your addresses should start with "bc1q..."). * Fee rate recommendation: it is hard to predict the fee rate that will be needed far in the future for your Bitcoin transaction to be mined in a reasonable timeframe. Your transactions can always be accelerated via CPFP techniques or by using accelerator services (mempool.space/accelerator), but this requires some technical skill. At the moment, fee rates are very low (1-2 sat/vB), but to be safe for the future, we recommend using a higher fee rate of 50 sats/vB, which would amount to ~$4-$40 for typical transactions - a negligible amount in recovery situations. Try the free plan now with up to 0.05 BTC of recovery-plan coverage!

New Tutorial Video #TimelockRecovery #BIP128

YOU 👏 MIGHT 👏 FORGET 👏 YOUR 👏 PASSPHRASE 👏 OVER 👏 THE 👏 NEXT 👏 20 👏 YEARS! If you're hodling a significant amount of Bitcoin in a passphrase-protected wallet, don't assume you'll always remember it. Follow this tutorial to learn how to create a Timelock-Recovery plan, ensuring you always have pre-signed transactions ready to move your Bitcoin from your passphrase-protected wallet to a standard wallet (after a timelock period of your choice): ritrek.gitbook.io/ritrek-doc…

Two days ago somebody uploaded a Javascript file to the ritrek.com/send page. While checking the logs to see why the error happened, I've noticed that the file contained a 12-words seed inside that file - which contains a small amount (around 9k sats). The /send page is for uploading and executing Timelock-Recovery JSON files as defined in BIP-128: bips.dev/128 - I'm not sure why you tried to upload a Javascript file. Anyways, I haven't touched the funds and I recommend moving that small amount elsewhere.

Happy #WorldBackupDay 2026! Don't depend on a single point of failure. No backup = no Bitcoin.

I took this photo a few days ago, after an Iranian cluster munition hit ~1km from my home. Thankfully no one was hurt and the damage is probably repairable - but in worse cases, buildings can be declared unsafe, with owners not even allowed to enter. Putting the politics of this war aside: storing your Bitcoin seed phrase in a single geographic location is a real risk - especially in regions affected by war or natural disasters. One approach is redundancy: Shamir Secret Sharing, multisig setups, or splitting your seed (e.g. a 2-of-3 scheme where each part contains 18 of the 24 words). But these come with tradeoffs - complexity for less tech-savvy inheritors, risk of misconfiguration, and multiple locations to secure against an immediate break. In practice, more Bitcoin has been lost due to overly complex setups than stolen. Another approach: pre-signed timelocked transactions. They allow you to move funds from a "local" wallet to a "remote" one after a delay (e.g. 90 days), without splitting or duplicating your keys. With solutions like RITREK (Android) or @ElectrumWallet's Timelock Recovery plugin: * Transactions are pre-signed and immutable - destinations can't be altered, so backups can safely be stored in multiple locations (even online) and shared with 3rd parties. * No need to change hardware wallets or switch from a standard 24-word seed to multisig/shamir. * Easy for inheritors: Your "local" wallet can be very complex (with a memorized passphrase, seed split and mixed, etc.) - but the emergency "remote" wallet could be a simple 12 words wallet anyone can operate. * You retain a cancellation window if something is triggered unexpectedly - a time period (i.e. 90 days) has to pass from the broadcast of the pre-signed transactions until the funds actually move to the "remote" wallet. Learn more about Timelock Recovery at timelockrecovery.com, or try the RITREK.com app on Android (free up to 0.05 BTC). Don’t wait for a disaster. Secure your self-custody Bitcoin today.

My talk about timelocks and RITREK starts at 2:03:00

Self-custody is a pain - but it's what #Bitcoin is all about. Too many seed backups → your Bitcoin could be stolen. Too few → an accident could lock your Bitcoin away forever. Join me tomorrow for a talk about how relative & absolute timelocks enable safer recovery mechanisms - and how the new RITREK Android app is different from previous solutions.

Bottom is in. #Bitcoin

We're sorry.

Had a great time yesterday at @BitcoinemBassy diving into self-custody, recovery & inheritance - the risks, the trade-offs, and how not to lose your ₿itcoin. Loved sharing what we’re building at @RitrekRecovery, more soon! #Bitcoin #SelfCustody

. @oren_z0, CTO at RITREK, confirmed as panelist at @btcplusplus If you’ll be in Taipei, come join the conversation!

Every week, stories like this appear. A family loses not just someone they loved, but also access to what they built together. Bitcoin gives freedom, but freedom without recovery is fragile. RITREK helps you prepare for the unthinkable, without ever giving up your keys.

Another week - another lost bitcoin case: Just talked to a guy that permanently lost access to his coins. He didn't have a backup plan and relied 100% on a hot wallet application on his iphone. He factory-reset his device, not knowing that the private keys will be lost forever. This kind of story is the reason why we started @RitrekRecovery, to make self-custody easy and recoverable.

A ghost can’t haunt you. But a lost seed can. Happy Halloween 🎃

Timelocks decide when your Bitcoin can move. They’re essential for recovery and inheritance solutions. But here’s the catch: Most hardware wallets don’t show them, leaving users in the dark about timelock conditions. A silent UX security gap.

Full read: medium.com/@oren_ritrek/why-…