
Summary
Everything this inheritance service supports, grouped by category.
| Brand | Jinca |
|---|---|
| Headquarters |
Every spec, organized
Browse the full breakdown by category. Tap the on any row for what it means, or the for sources and documentation.
Subscription Payment Methods
Which methods of payments you can use to pay the Inheritance Service
BTC On Chain
YES
Accepts Bitcoin payments via on-chain transactions for subscription fees.
BTC Lightning
NO
Accepts Bitcoin payments via the Lightning Network for subscription fees.
Alt Coins
YES
Accepts alternative cryptocurrency payments for subscription fees.
Credit/Debit Card
YES
Accepts traditional credit and debit card payments for subscription fees.
Private Keys
Non-custodial
YES
The user retains full control and ownership of their funds.
Third-Party Independence
NO
When you depend on a third-party to store a part of your private keys, you're essentially trusting them with a crucial aspect of your security. This dependency means that if the third-party were to disappear (e.g., go out of business) or lose their own key, you could face serious consequences is the other keys are not properly stored.
You're also vulnerable to a hostage situation. This means that the third-party could potentially exploit their control over your keys, demanding ransom or imposing other unfavorable conditions for releasing them.
Finally, if beneficiaries collude with the third-party, they may attempt to gain unauthorized access to your funds.
Single-Sig
Optional
Official Documentation
You need to upload to Jinca a Seedphrase fraction
Multi-sig (PSBTs)
Optional
Bitcoin multi-sig allows having up to 15 possible signers to approve any transaction. When using multi-sig, you will have at least one seed phrase per signer, so you can store them in multiple locations.
Official Documentation
You need to upload to Jinca a Seedphrase fraction. No native support for multisig.
Required Hardware Wallet
NO
Requires the use of a specific hardware wallet for the inheritance setup.
Key Replacement Assisted Support
NO
If a key becomes compromised or your seed phrases are misplaced, it's best practice to replace this key in your multisig quorum.
Beneficiary Key Lost Protection
NO
If the beneficiaries lose their keys, your inheritance could be inaccesible. Some services offer a protection against this risk
Health Checks
NO
Health Checks are a simple way to ensure that your keys are ready to sign transactions securely.
Health Checks Reminders
NO
Sends reminders to perform regular health checks on your keys and setup.
Passing Down Alternatives
Direct Inheritance
YES
Give the Beneficiaries direct control to claim the inheritance for themselves
Indirect Inheritance
YES
Give a trusted guardian the control so it can help the Beneficiary claim the inheritance on their behalf
Joint Control
NO
Split the control between the Beneficiary and the Trustee. This will help ensure that each one only has partial control over your bitcoins. The Beneficiary and Trustee will need to work together in order to claim the inheritance.
Multiple Beneficiaries
YES
Supports designating multiple beneficiaries for your Bitcoin inheritance.
Assign Percentage to each Beneficiary
YES
Allows assigning specific percentages of the inheritance to different beneficiaries.
Privacy
Non-KYC
YES
Not proof of identity required.
Coin Control
Depending of the used wallet
In your wallet, the Bitcoin balance you see is the sum of smaller units called Unspent Transaction Outputs (UTXOs). Each UTXO has a history that may or may not belong to you. If your wallet automatically chooses which UTXOs to use in a transaction, you could be revealing unwanted information to the recipient or anyone monitoring the blockchain.
On the other hand, if your wallet allows you to view and select UTXOs for transactions, you may not know the source of each one. This makes it difficult to decide which ones are suitable for different transactional situations. By using a wallet that enables UTXO labeling and Coin Control, you can minimize the amount of information shared during transactions.
For example, suppose your wallet contains both KYC and no-KYC Bitcoin. It's best not to combine these sources in a single transaction because it will link the no-KYC Bitcoin to the KYC Bitcoin associated with your true identity. If you label your coins as 'KYC' or 'no-KYC', you can make an informed decision when spending your sats in the future.
Custom Node
Depending of the used wallet
For bitcoin to function reliably and securely, it relies on the voluntary participation of thousands of individuals worldwide. Nodes, which make up the bitcoin network and verify transactions and blocks, are crucial to this process. There are many reasons to consider running your own bitcoin node, including personal benefits and the benefits to the security and resilience of the bitcoin ecosystem.
Tor
Depending of the used wallet
Tor (The Onion Router) aims to make all users look the same, making it difficult for you to be fingerprinted based on your browser and device information. With Tor, your traffic is relayed and encrypted three times as it passes over the Tor network. The network is comprised of thousands of volunteer-run servers known as Tor relays. Connecting to your custom Bitcoin node using Tor can provide a number of benefits for privacy and security.
Tor is an anonymity network that helps to conceal your IP address and online activity from potential eavesdroppers, such as your Internet Service Provider (ISP) or other network intermediaries. By using Tor, you can ensure that your Bitcoin node's IP address is not publicly visible and that your node's traffic is encrypted and routed through multiple servers, making it more difficult for someone to trace it back to you.
Connecting to your node using Tor can help to reduce your reliance on centralized services or intermediaries, such as Bitcoin wallet providers or exchanges. By running your own node and connecting to it using Tor, you can have more control over your Bitcoin transactions and data, and reduce your exposure to potential hacks or data breaches at centralized services.
Features
Bitcoin-only
NO
Bitcoin-only services only supports Bitcoin. Less code usually means less attack surface which further improves your security when only storing Bitcoin.
If you are a Bitcoiner, you probably will prefer a BTC-only service.
Crypto Specific Solution
YES
Designed specifically for cryptocurrency inheritance, not traditional assets.
Exchanges Integration
YES
Official Documentation
Jinca Integrates to your exchanges with their API to automatically transfer your assets to preconfigured wallets of your loved ones.
Message for Beneficiary
NO
Allows leaving a personal message for beneficiaries along with the inheritance.
Notifications to Beneficiary
YES
On the activation date, the beneficiary can be notified
Onchain Timelock
NO
Uses Bitcoin's native timelock features to enforce inheritance conditions on-chain.
Timelock Refresh Method
Entering a PIN
Method used to refresh or extend the timelock period to prevent premature inheritance activation.
Zero Cost to Update Timelock
YES
Allows updating or refreshing the timelock without incurring transaction fees.
Waiting Period to Claim
Defined by the owner
Time period beneficiaries must wait before they can claim the inheritance.
Official Documentation
Android Support
Supported
NO
Google Play
-
Direct APK Download
-
Release Notes
-
Source-available
-
A wallet with source-available is released through a source code distribution model where the source can be viewed, and in some cases modified, but without necessarily meeting the criteria to be called open-source. Any wallet is source-available as long its source code is distributed along with it, even if the user has no legal rights to use, share, modify, or even compile it.
Open Source
-
A wallet being open source means that the source code is publicly available and can be freely viewed, used, modified, and distributed by anyone. Users have the legal rights to access, study, modify, and distribute the firmware according to the terms of the open-source license it is released under. This transparency and freedom allow the community to review and contribute to the development of the firmware, ensuring its security, reliability, and trustworthiness.
License
-
Open source licenses grant permission for anybody to use, modify, and share licensed software for any purpose, subject to conditions preserving the provenance and openness of the software.
Reproducible Builds
-
Whilst anyone may inspect the source code of free and open source software for malicious flaws, most software is distributed pre-compiled with no method to confirm whether they correspond.
A build is reproducible if given the same source code, build environment and build instructions, any party can recreate bit-by-bit identical copies of all specified artifacts.
iOS Support
Supported
NO
Release Notes
-
Source-available
-
A wallet with source-available is released through a source code distribution model where the source can be viewed, and in some cases modified, but without necessarily meeting the criteria to be called open-source. Any wallet is source-available as long its source code is distributed along with it, even if the user has no legal rights to use, share, modify, or even compile it.
Open Source
-
A wallet being open source means that the source code is publicly available and can be freely viewed, used, modified, and distributed by anyone. Users have the legal rights to access, study, modify, and distribute the firmware according to the terms of the open-source license it is released under. This transparency and freedom allow the community to review and contribute to the development of the firmware, ensuring its security, reliability, and trustworthiness.
License
-
Open source licenses grant permission for anybody to use, modify, and share licensed software for any purpose, subject to conditions preserving the provenance and openness of the software.
Reproducible Builds
-
Whilst anyone may inspect the source code of free and open source software for malicious flaws, most software is distributed pre-compiled with no method to confirm whether they correspond.
A build is reproducible if given the same source code, build environment and build instructions, any party can recreate bit-by-bit identical copies of all specified artifacts.
Web Support
Supported
YES
MacOS Support
Supported
NO
Release Notes
-
Source-available
-
A wallet with source-available is released through a source code distribution model where the source can be viewed, and in some cases modified, but without necessarily meeting the criteria to be called open-source. Any wallet is source-available as long its source code is distributed along with it, even if the user has no legal rights to use, share, modify, or even compile it.
Open Source
-
A wallet being open source means that the source code is publicly available and can be freely viewed, used, modified, and distributed by anyone. Users have the legal rights to access, study, modify, and distribute the firmware according to the terms of the open-source license it is released under. This transparency and freedom allow the community to review and contribute to the development of the firmware, ensuring its security, reliability, and trustworthiness.
License
-
Open source licenses grant permission for anybody to use, modify, and share licensed software for any purpose, subject to conditions preserving the provenance and openness of the software.
Reproducible Builds
-
Whilst anyone may inspect the source code of free and open source software for malicious flaws, most software is distributed pre-compiled with no method to confirm whether they correspond.
A build is reproducible if given the same source code, build environment and build instructions, any party can recreate bit-by-bit identical copies of all specified artifacts.
Linux Support
Supported
NO
Release Notes
-
Source-available
-
A wallet with source-available is released through a source code distribution model where the source can be viewed, and in some cases modified, but without necessarily meeting the criteria to be called open-source. Any wallet is source-available as long its source code is distributed along with it, even if the user has no legal rights to use, share, modify, or even compile it.
Open Source
-
A wallet being open source means that the source code is publicly available and can be freely viewed, used, modified, and distributed by anyone. Users have the legal rights to access, study, modify, and distribute the firmware according to the terms of the open-source license it is released under. This transparency and freedom allow the community to review and contribute to the development of the firmware, ensuring its security, reliability, and trustworthiness.
License
-
Open source licenses grant permission for anybody to use, modify, and share licensed software for any purpose, subject to conditions preserving the provenance and openness of the software.
Reproducible Builds
-
Whilst anyone may inspect the source code of free and open source software for malicious flaws, most software is distributed pre-compiled with no method to confirm whether they correspond.
A build is reproducible if given the same source code, build environment and build instructions, any party can recreate bit-by-bit identical copies of all specified artifacts.
Windows Support
Supported
NO
Release Notes
-
Source-available
-
A wallet with source-available is released through a source code distribution model where the source can be viewed, and in some cases modified, but without necessarily meeting the criteria to be called open-source. Any wallet is source-available as long its source code is distributed along with it, even if the user has no legal rights to use, share, modify, or even compile it.
Open Source
-
A wallet being open source means that the source code is publicly available and can be freely viewed, used, modified, and distributed by anyone. Users have the legal rights to access, study, modify, and distribute the firmware according to the terms of the open-source license it is released under. This transparency and freedom allow the community to review and contribute to the development of the firmware, ensuring its security, reliability, and trustworthiness.
License
-
Open source licenses grant permission for anybody to use, modify, and share licensed software for any purpose, subject to conditions preserving the provenance and openness of the software.
Reproducible Builds
-
Whilst anyone may inspect the source code of free and open source software for malicious flaws, most software is distributed pre-compiled with no method to confirm whether they correspond.
A build is reproducible if given the same source code, build environment and build instructions, any party can recreate bit-by-bit identical copies of all specified artifacts.
Hardware Wallets Support
Bitbox02
Exporting private keys
Official Documentation
You need to export your private key and load into Jinca
Bitkey
NO
Coldcard Mk4
Exporting private keys
Official Documentation
You need to export your private key and load into Jinca
Coldcard Q
Exporting private keys
Official Documentation
You need to export your private key and load into Jinca
Cypherock X1
Exporting private keys
Official Documentation
You need to export your private key and load into Jinca
Jade
Exporting private keys
Official Documentation
You need to export your private key and load into Jinca
Keystone 3 Pro
Exporting private keys
Official Documentation
You need to export your private key and load into Jinca
Ledger Nano S Plus
Exporting private keys
Official Documentation
You need to export your private key and load into Jinca
Ledger Nano X
Exporting private keys
Official Documentation
You need to export your private key and load into Jinca
Passport Core
Exporting private keys
Official Documentation
You need to export your private key and load into Jinca
Portal
Exporting private keys
Official Documentation
You need to export your private key and load into Jinca
SeedSigner
Exporting private keys
Official Documentation
You need to export your private key and load into Jinca
Specter DIY
Exporting private keys
Official Documentation
You need to export your private key and load into Jinca
Tapsigner
NO
Trezor Model One
Exporting private keys
Official Documentation
You need to export your private key and load into Jinca
Trezor Safe 3
Exporting private keys
Official Documentation
You need to export your private key and load into Jinca
Trezor Safe 5
Exporting private keys
Official Documentation
You need to export your private key and load into Jinca
Trezor Model t
Exporting private keys
Official Documentation
You need to export your private key and load into Jinca

Support Us on Ko-fi