) => {
+ state.backupBSMSForIKS = action.payload;
+ },
},
extraReducers: (builder) => {
builder.addCase(ADD_SIGINING_DEVICE, (state) => {
@@ -182,6 +187,7 @@ export const {
clearSigningDevice,
resetVaultMigration,
setTempShellId,
+ setBackupBSMSForIKS,
} = vaultSlice.actions;
export default vaultSlice.reducer;
diff --git a/src/store/sagaActions/vaults.ts b/src/store/sagaActions/vaults.ts
index 0142fea18..cc61c2381 100644
--- a/src/store/sagaActions/vaults.ts
+++ b/src/store/sagaActions/vaults.ts
@@ -8,6 +8,7 @@ export const ADD_NEW_VAULT = 'ADD_NEW_VAULT';
export const ADD_SIGINING_DEVICE = 'ADD_SIGINING_DEVICE';
export const MIGRATE_VAULT = 'MIGRATE_VAULT';
export const FINALISE_VAULT_MIGRATION = 'FINALISE_VAULT_MIGRATION';
+export const FINALIZE_IK_SETUP = 'FINALIZE_IK_SETUP';
export const addNewVault = (payload: {
newVaultInfo: NewVaultInfo;
@@ -37,3 +38,8 @@ export const finaliseVaultMigration = (payload: string) => ({
type: FINALISE_VAULT_MIGRATION,
payload: { vaultId: payload },
});
+
+export const finaliseIKSetup = (vault: Vault) => ({
+ type: FINALIZE_IK_SETUP,
+ payload: { vault },
+});
diff --git a/src/store/sagas/bhr.ts b/src/store/sagas/bhr.ts
index 8757860b1..a094f82a5 100644
--- a/src/store/sagas/bhr.ts
+++ b/src/store/sagas/bhr.ts
@@ -241,7 +241,10 @@ function* getAppImageWorker({ payload }) {
const primarySeed = bip39.mnemonicToSeedSync(primaryMnemonic);
const appID = crypto.createHash('sha256').update(primarySeed).digest('hex');
const encryptionKey = generateEncryptionKey(primarySeed.toString('hex'));
- const { appImage, vaultImage, subscription, UTXOinfos } = yield call(Relay.getAppImage, appID);
+ const { appImage, vaultImage, subscription, UTXOinfos, labels } = yield call(
+ Relay.getAppImage,
+ appID
+ );
// applying the restore upgrade sequence if required
const previousVersion = appImage.version;
@@ -267,7 +270,8 @@ function* getAppImageWorker({ payload }) {
subscription,
appImage,
vaultImage,
- UTXOinfos
+ UTXOinfos,
+ labels
);
} else {
const plebSubscription = {
@@ -286,7 +290,8 @@ function* getAppImageWorker({ payload }) {
plebSubscription,
appImage,
vaultImage,
- UTXOinfos
+ UTXOinfos,
+ labels
);
}
}
@@ -307,7 +312,8 @@ function* recoverApp(
subscription,
appImage,
vaultImage,
- UTXOinfos
+ UTXOinfos,
+ labels
) {
const entropy = yield call(
BIP85.bip39MnemonicToEntropy,
@@ -352,6 +358,7 @@ function* recoverApp(
// Vault recreation
if (vaultImage) {
const vault = JSON.parse(decrypt(encryptionKey, vaultImage.vault));
+
yield call(dbManager.createObject, RealmSchema.Vault, vault);
}
@@ -360,6 +367,12 @@ function* recoverApp(
yield call(dbManager.createObjectBulk, RealmSchema.UTXOInfo, UTXOinfos);
}
yield put(setAppId(appID));
+
+ //Labels Restore
+ if (labels) {
+ yield call(dbManager.createObjectBulk, RealmSchema.Tags, labels);
+ }
+
// seed confirm for recovery
yield call(dbManager.createObject, RealmSchema.BackupHistory, {
title: BackupAction.SEED_BACKUP_CONFIRMED,
diff --git a/src/store/sagas/index.ts b/src/store/sagas/index.ts
index f6f5e9055..0e3805637 100644
--- a/src/store/sagas/index.ts
+++ b/src/store/sagas/index.ts
@@ -18,6 +18,7 @@ import {
addWhirlpoolWalletsWatcher,
addWhirlpoolWalletsLocalWatcher,
updateWalletPathAndPuposeDetailWatcher,
+ finaliseIKSetupWatcher,
} from './wallets';
import {
addUaiStackWatcher,
@@ -97,6 +98,7 @@ const rootSaga = function* () {
addSigningDeviceWatcher,
migrateVaultWatcher,
finaliseVaultMigrationWatcher,
+ finaliseIKSetupWatcher,
updateSignerDetails,
// send and receive
diff --git a/src/store/sagas/login.ts b/src/store/sagas/login.ts
index 5a3eefed3..018bb6c90 100644
--- a/src/store/sagas/login.ts
+++ b/src/store/sagas/login.ts
@@ -131,81 +131,77 @@ function* credentialsAuthWorker({ payload }) {
}
key = yield call(decrypt, hash, encryptedKey);
yield put(setKey(key));
- if (!key) throw new Error('Encryption key is missing');
- const uint8array = yield call(stringToArrayBuffer, key);
- yield call(dbManager.initializeRealm, uint8array);
yield put(setPinHash(hash));
- const previousVersion = yield select((state) => state.storage.appVersion);
- const newVersion = DeviceInfo.getVersion();
- const versionCollection = yield call(dbManager.getCollection, RealmSchema.VersionHistory);
- const lastElement = versionCollection[versionCollection.length - 1];
- const lastVersionCode = lastElement.version.split(/[()]/);
- const currentVersionCode = DeviceInfo.getBuildNumber();
- console.log({ previousVersion, newVersion });
- if (semver.lt(previousVersion, newVersion)) {
- yield call(applyUpgradeSequence, { previousVersion, newVersion });
- } else if (currentVersionCode !== lastVersionCode[1]) {
- yield call(dbManager.createObject, RealmSchema.VersionHistory, {
- version: `${newVersion}(${currentVersionCode})`,
- releaseNote: '',
- date: new Date().toString(),
- title: `Upgraded from ${lastVersionCode[1]} to ${currentVersionCode}`,
- });
- }
- } catch (err) {
- if (payload.reLogin) {
- // yield put(switchReLogin(false));
- } else yield put(credsAuthenticated(false));
- return;
- }
-
- yield put(setKey(key));
-
- if (!payload.reLogin) {
+ if (!key) throw new Error('Encryption key is missing');
// case: login
- if (appId) {
- try {
- const { id, publicId, subscription }: KeeperApp = yield call(
- dbManager.getObjectByIndex,
- RealmSchema.KeeperApp
- );
- const response = yield call(Relay.verifyReceipt, id, publicId);
- yield put(credsAuthenticated(true));
- yield put(setKey(key));
+ if (!payload.reLogin) {
+ const uint8array = yield call(stringToArrayBuffer, key);
+ yield call(dbManager.initializeRealm, uint8array);
+
+ const previousVersion = yield select((state) => state.storage.appVersion);
+ const newVersion = DeviceInfo.getVersion();
+ const versionCollection = yield call(dbManager.getCollection, RealmSchema.VersionHistory);
+ const lastElement = versionCollection[versionCollection.length - 1];
+ const lastVersionCode = lastElement.version.split(/[()]/);
+ const currentVersionCode = DeviceInfo.getBuildNumber();
+ if (semver.lt(previousVersion, newVersion)) {
+ yield call(applyUpgradeSequence, { previousVersion, newVersion });
+ } else if (currentVersionCode !== lastVersionCode[1]) {
+ yield call(dbManager.createObject, RealmSchema.VersionHistory, {
+ version: `${newVersion}(${currentVersionCode})`,
+ releaseNote: '',
+ date: new Date().toString(),
+ title: `Upgraded from ${lastVersionCode[1]} to ${currentVersionCode}`,
+ });
+ }
+ if (appId) {
+ try {
+ const { id, publicId, subscription }: KeeperApp = yield call(
+ dbManager.getObjectByIndex,
+ RealmSchema.KeeperApp
+ );
+ const response = yield call(Relay.verifyReceipt, id, publicId);
+ yield put(credsAuthenticated(true));
+ yield put(setKey(key));
- const history = yield call(dbManager.getCollection, RealmSchema.BackupHistory);
- yield put(setWarning(history));
+ const history = yield call(dbManager.getCollection, RealmSchema.BackupHistory);
+ yield put(setWarning(history));
- yield put(fetchExchangeRates());
- yield put(getMessages());
- yield put(
- uaiChecks([
- uaiType.SIGNING_DEVICES_HEALTH_CHECK,
- uaiType.SECURE_VAULT,
- uaiType.VAULT_MIGRATION,
- uaiType.DEFAULT,
- ])
- );
- yield put(resetSyncing());
- yield call(generateSeedHash);
- yield put(setRecepitVerificationFailed(!response.isValid));
- if (subscription.level === 1 && subscription.name === 'Hodler') {
- yield put(setRecepitVerificationFailed(true));
- } else if (subscription.level === 2 && subscription.name === 'Diamond Hands') {
- yield put(setRecepitVerificationFailed(true));
- } else if (subscription.level !== response.level) {
- yield put(setRecepitVerificationFailed(true));
+ yield put(fetchExchangeRates());
+ yield put(getMessages());
+ yield put(
+ uaiChecks([
+ uaiType.SIGNING_DEVICES_HEALTH_CHECK,
+ uaiType.SECURE_VAULT,
+ uaiType.VAULT_MIGRATION,
+ uaiType.DEFAULT,
+ ])
+ );
+ yield put(resetSyncing());
+ yield call(generateSeedHash);
+ yield put(setRecepitVerificationFailed(!response.isValid));
+ if (subscription.level === 1 && subscription.name === 'Hodler') {
+ yield put(setRecepitVerificationFailed(true));
+ } else if (subscription.level === 2 && subscription.name === 'Diamond Hands') {
+ yield put(setRecepitVerificationFailed(true));
+ } else if (subscription.level !== response.level) {
+ yield put(setRecepitVerificationFailed(true));
+ }
+ yield put(connectToNode());
+ } catch (error) {
+ yield put(setRecepitVerificationError(true));
+ // yield put(credsAuthenticated(false));
+ console.log(error);
}
- } catch (error) {
- yield put(setRecepitVerificationError(true));
- // yield put(credsAuthenticated(false));
- console.log(error);
- }
+ } else yield put(credsAuthenticated(true));
} else yield put(credsAuthenticated(true));
- } else yield put(credsAuthenticated(true));
-
- yield put(connectToNode());
+ } catch (err) {
+ if (payload.reLogin) {
+ yield put(credsAuthenticated(false));
+ // yield put(switchReLogin(false));
+ } else yield put(credsAuthenticated(false));
+ }
}
export const credentialsAuthWatcher = createWatcher(credentialsAuthWorker, CREDS_AUTH);
diff --git a/src/store/sagas/notifications.ts b/src/store/sagas/notifications.ts
index 0039d6df5..39557e9a2 100644
--- a/src/store/sagas/notifications.ts
+++ b/src/store/sagas/notifications.ts
@@ -16,6 +16,11 @@ import {
UPDATE_MESSAGES_STATUS,
} from '../sagaActions/notifications';
import { createWatcher } from '../utilities';
+import dbManager from 'src/storage/realm/dbManager';
+import { RealmSchema } from 'src/storage/realm/enum';
+import { UAI, uaiType } from 'src/common/data/models/interfaces/Uai';
+import { addToUaiStack } from '../sagaActions/uai';
+import { setRefreshUai } from '../reducers/uai';
function* updateFCMTokensWorker({ payload }) {
try {
@@ -51,13 +56,52 @@ export const fetchNotificationsWatcher = createWatcher(
FETCH_NOTIFICATIONS
);
+export function* notficationsToUAI(messages) {
+ for (const message of messages) {
+ if (message.additionalInfo !== null && typeof message.additionalInfo === 'object') {
+ if (
+ message.additionalInfo.type === uaiType.IKS_REQUEST &&
+ message.additionalInfo.reqId !== null
+ ) {
+ const uais = dbManager.getObjectByField(
+ RealmSchema.UAI,
+ message.additionalInfo.reqId,
+ 'entityId'
+ );
+ if (!uais.length) {
+ yield put(
+ addToUaiStack({
+ title: `There is a request for your Inheritance Key. Please review`,
+ isDisplay: true,
+ uaiType: uaiType.IKS_REQUEST,
+ prirority: 100,
+ entityId: message.additionalInfo.reqId,
+ displayText:
+ 'There is a request by someone for accessing the Inheritance Key you have set up using this app',
+ })
+ );
+ } else {
+ const uai = uais[0];
+ let updatedUai: UAI = JSON.parse(JSON.stringify(uai)); // Need to get a better way
+ updatedUai = {
+ ...updatedUai,
+ isActioned: false,
+ };
+ yield call(dbManager.updateObjectById, RealmSchema.UAI, updatedUai.id, updatedUai);
+ }
+ yield put(setRefreshUai());
+ }
+ }
+ }
+}
+
export function* getMessageWorker() {
yield put(fetchNotificationStarted(true));
const storedMessages = yield select((state) => state.notifications.messages);
const appId = yield select((state: RootState) => state.storage.appId);
const timeStamp = yield select((state) => state.notifications.timeStamp);
-
const { messages } = yield call(Relay.getMessages, appId, timeStamp);
+
if (!storedMessages) return;
const newMessageArray = storedMessages.concat(
messages.filter(
@@ -88,7 +132,7 @@ export function* getMessageWorker() {
// })
// );
// }
-
+ yield call(notficationsToUAI, messages);
yield put(messageFetched(newMessageArray));
yield put(storeMessagesTimeStamp());
yield put(fetchNotificationStarted(false));
diff --git a/src/store/sagas/uai.ts b/src/store/sagas/uai.ts
index 35bc974dc..115d2bbe0 100644
--- a/src/store/sagas/uai.ts
+++ b/src/store/sagas/uai.ts
@@ -147,7 +147,7 @@ function* uaiChecksWorker({ payload }) {
} else {
yield put(
addToUaiStack({
- title: `Transfer fund to vault for ${wallet.presentationData.name}`,
+ title: `Transfer fund to Vault from ${wallet.presentationData.name}`,
isDisplay: false,
uaiType: uaiType.VAULT_TRANSFER,
prirority: 80,
diff --git a/src/store/sagas/wallets.ts b/src/store/sagas/wallets.ts
index 8e13f0a6e..a7e0061ca 100644
--- a/src/store/sagas/wallets.ts
+++ b/src/store/sagas/wallets.ts
@@ -5,12 +5,18 @@
import {
DerivationPurpose,
EntityKind,
+ SignerType,
VaultMigrationType,
VaultType,
VisibilityType,
WalletType,
} from 'src/core/wallets/enums';
-import { SignerException, SignerRestriction } from 'src/core/services/interfaces';
+import {
+ InheritanceConfiguration,
+ InheritancePolicy,
+ SignerException,
+ SignerRestriction,
+} from 'src/core/services/interfaces';
import { Vault, VaultScheme, VaultSigner } from 'src/core/wallets/interfaces/vault';
import {
TransferPolicy,
@@ -50,6 +56,8 @@ import {
ELECTRUM_NOT_CONNECTED_ERR,
ELECTRUM_NOT_CONNECTED_ERR_TOR,
} from 'src/core/services/electrum/client';
+import InheritanceKeyServer from 'src/core/services/operations/InheritanceKey';
+import { genrateOutputDescriptors } from 'src/core/utils';
import { RootState } from '../store';
import {
addSigningDevice,
@@ -80,7 +88,9 @@ import {
ADD_NEW_VAULT,
ADD_SIGINING_DEVICE,
FINALISE_VAULT_MIGRATION,
+ FINALIZE_IK_SETUP,
MIGRATE_VAULT,
+ finaliseIKSetup,
} from '../sagaActions/vaults';
import { uaiChecks } from '../sagaActions/uai';
import { updateAppImageWorker, updateVaultImageWorker } from './bhr';
@@ -519,6 +529,7 @@ function* addNewVaultWorker({
yield put(vaultCreated({ hasNewVaultGenerationSucceeded: true }));
yield put(relayVaultUpdateSuccess());
+ yield put(finaliseIKSetup(vault)); // update IKS, if inheritance key has been added
return true;
}
throw new Error('Relay updation failed');
@@ -616,6 +627,90 @@ export const finaliseVaultMigrationWatcher = createWatcher(
FINALISE_VAULT_MIGRATION
);
+function* finaliseIKSetupWorker({ payload }: { payload: { vault: Vault } }) {
+ // finalise the IK setup
+ const { vault } = payload;
+ const [ikSigner] = vault.signers.filter((signer) => signer.type === SignerType.INHERITANCEKEY);
+ const backupBSMSForIKS = yield select((state: RootState) => state.vault.backupBSMSForIKS);
+
+ if (!ikSigner) return;
+ let updatedIkSigner: VaultSigner = null;
+
+ if (ikSigner.inheritanceKeyInfo) {
+ // case: updating config for this new vault which already had IKS as one of its signers
+ const existingConfiguration = ikSigner.inheritanceKeyInfo.configuration;
+ const existingThresholdDescriptors = existingConfiguration.descriptors.slice(0, 2);
+
+ const newIKSConfiguration: InheritanceConfiguration = {
+ m: vault.scheme.m,
+ n: vault.scheme.n,
+ descriptors: vault.signers.map((signer) => signer.signerId),
+ bsms: backupBSMSForIKS ? genrateOutputDescriptors(vault) : null,
+ };
+
+ const { updated } = yield call(
+ InheritanceKeyServer.updateInheritanceConfig,
+ vault.shellId,
+ existingThresholdDescriptors,
+ newIKSConfiguration
+ );
+
+ if (updated) {
+ updatedIkSigner = {
+ ...ikSigner,
+ inheritanceKeyInfo: {
+ ...ikSigner.inheritanceKeyInfo,
+ configuration: newIKSConfiguration,
+ },
+ };
+ } else Alert.alert('Failed to update the inheritance key configuration');
+ } else {
+ // case: setting up a vault w/ IKS for the first time
+ const config: InheritanceConfiguration = {
+ m: vault.scheme.m,
+ n: vault.scheme.n,
+ descriptors: vault.signers.map((signer) => signer.signerId),
+ bsms: backupBSMSForIKS ? genrateOutputDescriptors(vault) : null,
+ };
+
+ const fcmToken = yield select((state: RootState) => state.notifications.fcmToken);
+ const policy: InheritancePolicy = {
+ notification: { targets: [fcmToken] },
+ };
+
+ const { setupSuccessful } = yield call(
+ InheritanceKeyServer.finalizeIKSetup,
+ vault.shellId,
+ config,
+ policy
+ );
+
+ if (setupSuccessful) {
+ updatedIkSigner = {
+ ...ikSigner,
+ inheritanceKeyInfo: {
+ configuration: config,
+ policy,
+ },
+ };
+ } else Alert.alert('Failed to finalise the inheritance key setup');
+ }
+
+ if (updatedIkSigner) {
+ // send updates to realm
+ const updatedSigners = vault.signers.map((signer) => {
+ if (signer.type === SignerType.INHERITANCEKEY) return updatedIkSigner;
+ return signer;
+ });
+
+ yield call(dbManager.updateObjectById, RealmSchema.Vault, vault.id, {
+ signers: updatedSigners,
+ });
+ }
+}
+
+export const finaliseIKSetupWatcher = createWatcher(finaliseIKSetupWorker, FINALIZE_IK_SETUP);
+
function* syncWalletsWorker({
payload,
}: {
diff --git a/src/utils/GenerateLetterToAtternyPDF.ts b/src/utils/GenerateLetterToAtternyPDF.ts
new file mode 100644
index 000000000..ebe687ab4
--- /dev/null
+++ b/src/utils/GenerateLetterToAtternyPDF.ts
@@ -0,0 +1,59 @@
+import RNHTMLtoPDF from 'react-native-html-to-pdf';
+
+const GenerateLetterToAtternyPDF = async (fingerPrints) => {
+ try {
+ const html = `
+
+
+
+
+
+ Letter to the Attorney
+ This document is one of three Inheritance Planning documents provided by Keeper. The other 2 being Key Security Tips and Restoring Inheritance Vault. This document is auto-produced by the Bitcoin Keeper app. The data shared in this document is sensitive. Please be cautious about revealing part or all of its contents to anyone. To learn more, please visit bitcoinkeeper.app
+ Subject: Bitcoin Bequest Information for Inclusion in My Will
+ Dear _________________ ,
+ I hope this letter finds you well. I am writing to provide you with the necessary information to include my bitcoin holdings in my estate plan. As a significant proportion of my wealth is held in bitcoin, it is crucial to address the legal transfer of these assets appropriately.
+ Below, I have outlined the specific details regarding my current bitcoin holdings:
+ 1. Bitcoin Key Information:
+ ${fingerPrints.map((keys, index) => `
Key ${index + 1} Master Fingerprint: ${keys}
`).join("")}
+ These master fingerprints act as unique identifiers for the respective keys without revealing sensitive details. Following the BIP32 (Bitcoin Improvement Proposal 32) standard, each fingerprint helps identify the associated extended public key (xPub). The xPub serves as a distinct identifier that can be utilized by a digital asset expert or software, adhering to standard BIP32 derivation paths, to locate and validate the keys during the transfer process.
+ Please note that the funds associated with these keys may be held in any combination of single-key or multi-signature (multisig) wallets. Regardless of the specific configuration, I intend that any wealth controlled by these keys be legally transferred to the designated heir or intended beneficiary.
+ My explicit intention is to transfer the legal title to my bitcoin holdings to the designated heir or intended beneficiary. However, it is important to note that access to the actual keys and the bitcoin will be provided separately to the intended beneficiary. This letter solely addresses the transfer of legal title and the inclusion of my bitcoin assets in my estate plan.
+ These master fingerprints and the accompanying explanation of their usage can be recorded in my will if it is of any help. Further details regarding the designated beneficiary, executor, and supplementary instructions will be provided separately during our estate planning discussions. I have complete faith in your expertise to handle this confidential information securely. Please do not hesitate to contact me if you require additional documentation or information. Your support and meticulous attention to detail in facilitating the transfer of the legal title to my bitcoin holdings are greatly appreciated.
+ Thank you for your professional assistance in preparing my estate plan and ensuring the proper transfer of the legal title to my bitcoin assets according to my wishes.
+ Sincerely,
+ ------------------------------------------------------------------------------------
+ This document is one of three Inheritance Planning documents provided by Keeper. The other 2 being Key Security Tips and Restoring Inheritance Vault. This document is auto-produced by the Bitcoin Keeper app. The data shared in this document is sensitive. Please be cautious about revealing part or all of its contents to anyone. To learn more, please visit bitcoinkeeper.app
+
+
+ `;
+ const options = {
+ html,
+ fileName: `RecoveryInstruction`,
+ directory: 'Documents',
+ base64: true,
+ };
+ const file = await RNHTMLtoPDF.convert(options);
+ return file.filePath;
+ } catch (error: any) {
+ return error;
+ }
+};
+
+export default GenerateLetterToAtternyPDF;
diff --git a/src/utils/GenerateRecoveryInstrPDF.ts b/src/utils/GenerateRecoveryInstrPDF.ts
new file mode 100644
index 000000000..685311c58
--- /dev/null
+++ b/src/utils/GenerateRecoveryInstrPDF.ts
@@ -0,0 +1,103 @@
+import RNHTMLtoPDF from 'react-native-html-to-pdf';
+
+const GenerateRecoveryInstrPDF = async (signers, descriptorString) => {
+ try {
+ const html = `
+
+
+
+
+
+ Vault Recovery Instructions with or without the Keeper App:
+ This document is one of three Inheritance Planning documents provided by Keeper. The other 2 are Letter to the Attorney and Key Security Tips. This document is auto-produced by the Bitcoin Keeper app. The data shared in this document is sensitive. Please be cautious about revealing part or all of its contents to anyone. To learn more, please visit bitcoinkeeper.app.
+ Getting Started:
+ An m-of-n multisig setup enhances security by distributing control and access, thus reducing the risk of unauthorized access or fraudulent activities. The bitcoin you inherited is within such a setup, i.e. the Vault. This document provides the method to recover the Vault and gain custody of your Inheritance.
+ If you have not previously handled bitcoin, we highly recommend contacting the people mentioned in the “Technical Assistance” section below.
+ Please note that failure to recover the Vault successfully may result in the loss of bitcoin forever. Great caution is advised.
+ Technical Assistance:
+ Recovering a multi-sig vault has a few steps involved. If you need assistance, you could reach out to any of the people in the list below for help. They are the trusted contacts of the person giving away the bitcoin (You do not have to share the keys with them)
+ Person 1:
+ Name:
+ Ph. No.:
+ Alt. Ph. No.:
+ Email:
+ Home Address:
+ Office Address:
+ Person 2:
+ Name:
+ Ph. No.:
+ Alt. Ph. No.:
+ Email:
+ Home Address:
+ Office Address:
+ Person 3:
+ Name:
+ Ph. No.:
+ Alt. Ph. No.:
+ Email:
+ Home Address:
+ Office Address:
+ Person 4:
+ Name:
+ Ph. No.:
+ Alt. Ph. No.:
+ Email:
+ Home Address:
+ Office Address:
+ Keeper Customer Support:
+ Telegram: https://t.me/bitcoinkeeper
+ Twitter: https://twitter.com/bitcoinkeeper_
+ Email: info@bithyve.com
+ Restoring the Vault:
+ We have attached the Output Descriptor file as an Annexure to this document. To recover the Vault, please input the Output Descriptor file in a wallet (such as Electrum or Sparrow) that supports a multi-sig setup. You could, of course, use Keeper to recover the Vault, but it’s not necessary that you do. Look for the “Recovery” button/section when setting up a wallet. Follow the steps from there.
+ Please note that the funds associated with these keys may be in any combination of single-key or multi-signature (multisig) wallets.
+ A) Key: Type Details
+ ${signers.map((keys, index) =>
+ `Key ${index + 1}: ${keys.signerId}
+ Type: ${keys.type}
`).join("")}
+ ${signers.map((keys, index) =>
+ `Key ${index + 1}: ${keys.signerId}
+ Location details:
+ Access details:
`).join("")}
+ Any other information:
+ ----------------------------------------------------------------------------------------------------
+ With the Output Descriptor file and the keys with you, you now have complete access to the Vault.
+ ----------------------------------------------------------------------------------------------------
+ This document is one of three Inheritance Planning documents provided by Keeper. The other 2 are Letter to the Attorney and Key Security Tips. This document is auto-produced by the Bitcoin Keeper app. The data shared in this document is sensitive. Please be cautious about revealing part or all of its contents to anyone. To learn more, please visit bitcoinkeeper.app.
+ ----------------------------------------------------------------------------------------------------
+ Annexure 1
+ Output Descriptor
+ ${descriptorString}
+
+
+ `;
+ const options = {
+ html,
+ fileName: `RecoveryInstruction`,
+ directory: 'Documents',
+ base64: true,
+ };
+ const file = await RNHTMLtoPDF.convert(options);
+ return file.filePath;
+ } catch (error: any) {
+ return error;
+ }
+};
+
+export default GenerateRecoveryInstrPDF;
diff --git a/src/utils/GenerateSecurityTipsPDF.ts b/src/utils/GenerateSecurityTipsPDF.ts
new file mode 100644
index 000000000..7e9779dc2
--- /dev/null
+++ b/src/utils/GenerateSecurityTipsPDF.ts
@@ -0,0 +1,151 @@
+import RNHTMLtoPDF from 'react-native-html-to-pdf';
+
+const GenerateSecurityTipsPDF = async () => {
+ try {
+ const html = `
+
+
+
+
+
+ Key Security Tips:
+ This document is one of three Inheritance Planning documents provided by Keeper. The other 2 being: Letter to the Attorney and Recovery Instructions for your heir. This document is auto-produced by the Bitcoin Keeper app. To learn more visit bitcoinkeeper.app
+ Getting Started:
+ A multisig enhances wallet security by distributing control and access, thus reducing the risk of unauthorized access, fraudulent activities, and loss of funds. The bitcoin your heir would inherit is within such a setup, i.e. your Vault. This document offers suggestions for storing keys and access & recovery mechanisms safely so that your intended beneficiary* can easily access your bitcoin when needed.
+ Also, the following information is only meant to help you start planning your bitcoin inheritance and should be considered as partial information for your bitcoin inheritance planning. We recommend you also speak with your estate planners to customize a plan that works best for you and to ensure that legal title also passes to your heir(s).
+ *Please note that the term intended beneficiary is not being used in legal terminology.
+ Checklist before storing away your keys:
+ Setup
+
+ - Initialize devices and update firmware
+ - Save one seed phrase in a tamper-evident bag
+ - Record the tamper-evident bag serial number in a password manager
+ - Record device PIN(s) in a password manager
+ - Connect devices to BitcoinKeeper
+
+ Testing
+
+ - Receive a transaction
+ - Send a transaction
+ - Complete a health check on all devices
+
+ Some prompts to consider a place safe:
+
+ - Please ensure that the safe place is easily accessible to your heir
+ - The place should not be prone to natural calamities like floods, earthquakes, etc.
+ - Keep your key in a place away from fire, water, moisture, corroding elements, electromagnets, etc.
+ - Please consider the political situation in the area being designated safe. The safe place should not be rendered inaccessible due to political turmoil in the region.
+ - Make sure that the key is away from children and pets!
+
+ Key Storage: We’ve identified five places where you could potentially store your keys. The remainder of the document offers cautions and considerations as you decide how and where to store them.
+ 1) Safety Deposit Box:
+
+ - Your Safety Deposit Box should be accessible 24/7/365.
+ - Make sure that the nominee of the locker is the same as the heir for your bitcoin so that they can access it after you’ve moved on.
+ - Keep different keys in different locations. You should never have two hardware wallets in the same place simultaneously.
+ - You may consider storing the key in a deposit box with a larger bank than a smaller one.
+ - Please ensure that the deposit box is at a bank branch that’s in a relatively safe neighbourhood.
+ - Ask the bank, if they go under, whether you would still have access to the deposit box seamlessly. There may be a possibility for the safety box to be frozen and thus inaccessible if the bank goes under. If the safety deposit box may be frozen, then you should know for how long. Try to get commitments from the bank on paper regarding this.
+ - Which bank personnel would have access to the deposit box under extraordinary circumstances? It is recommended to get their details with relevant commitments to you, the lessee of the deposit box.
+ - Do consider the state of affairs in the country where you’re leasing the deposit box.
+ - Keep your device in a Faraday bag to prevent it from being compromised by EMP’s and scanning devices.
+
+ 2) Soft Keys
+
+ - Make sure that you’ve not used the phone(s) with the soft keys to access untrustworthy websites and apps.
+ - Make sure that your wifi is private/ trustworthy.
+ - It is recommended that you do not use the phone with the soft keys for day-to-day use.
+ - Please store the device with the soft keys away from elements like moisture, heat, magnetic fields, etc.
+ - It is recommended that you store an extra charger with the device for the heir. It is better that you do it rather than depend on the heir as the charger may stop being manufactured, the technology may change, etc.
+ - It is recommended that you instruct your heir not to perform an OS update on the phone as the latest OS may not be compatible with the latest version of Keeper.
+ - If you plan to store the software key in a device for years on end, please consider the possibility that the battery in the device may degrade and stop working. Make sure to check on the device at least twice a year to see if its functional.
+
+ 3) With a trusted contact:
+
+ - Ensure that they are truly trustworthy.
+ - They should be happy for the heir to inherit the wealth and not hinder the transfer.
+ - They should not have access to the other keys. They should know this and be ok with this.
+ - Consider the possibility of their death as well (natural and unnatural). Who transfers the trusted contact’s key to your heir, then?
+ - If the trusted contact breaks trust or your relationship sours, please consider resetting the quorum of the signing keys. This way, you will render the key with the formerly trusted contact obsolete.
+ - Your trusted contact should be able to transfer the key to your heir as soon as possible in the event of your demise.
+
+ 4) With your Executor, Trustee, or Agent under Power of Attorney:
+
+ - Ensure that you trust them, as they will have access to your bitcoin. Conduct thorough research and consider their reputation, credentials, and experience before entrusting them with this responsibility.
+ - Ensure that this trusted person/company has robust security measures in place to protect your bitcoin keys from potential hacks, theft, or loss. Please inquire about the security measures they’ve instituted to ensure the safety of your keys. If you’re dissatisfied, you could request them to upgrade security or perhaps look for another entity to help you.
+ - It is essential that the person in this capacity has a solid understanding of how Bitcoin works and the intricacies of handling private keys. They should be familiar with wallet management, transaction processes, and recovery procedures in case of unforeseen circumstances.
+ - To tackle unexpected circumstances, a well-defined backup and recovery plan should be in place. This ensures that your heir can access your Bitcoin keys without any complications. Ensure your team has outlined a clear process for securely transferring the keys.
+ - Regular Communication: Maintain open and regular communication with your executor/trustee/agent under PoA. Stay informed about any changes in procedures, security measures, or regulations they may face/undertake, that may impact your keys. This ensures that you stay up-to-date and can make informed decisions regarding your estate planning.
+
+ 5) With your heir:
+
+ - Ensure that your heir has a solid understanding of how Bitcoin works, including key management, wallet security, and transaction processes. Please provide them with resources or educational materials to help them navigate the intricacies of holding and managing Bitcoin.
+ - Emphasize the importance of strong security practices to your heir. Please encourage them to use secure wallets, enable two-factor authentication (2FA), regularly update software, and avoid sharing sensitive information related to the Bitcoin keys. Additionally, advise them to be cautious of phishing attempts, scams, and malicious actors who may attempt to steal their Bitcoin.
+ - Instruct your heir on the importance of maintaining secure backups of the Bitcoin keys. This includes securely storing backup copies of the private keys or seed phrases in offline locations and keeping them confidential. In case of loss, theft, or damage to the keys, having proper backups will ensure that your heir can still access the inherited Bitcoin.
+ - Legal and Tax Implications: Seek legal advice to ensure that your estate planning and the transfer of Bitcoin to your heir align with applicable laws and regulations. Cryptocurrency regulations vary across jurisdictions, and it's essential to be aware of any tax obligations or legal requirements that may arise. Consulting with a lawyer experienced in cryptocurrency and estate planning will help ensure compliance.
+ - Regular Updates and Communication: Maintain open communication with your heir about your Bitcoin holdings and any updates or changes you make to your estate plan. Inform them about any changes in security measures, or relevant instructions they should be aware of. This will help avoid confusion or potential loss of access in the future.
+ - Contingency Planning: Prepare for unforeseen circumstances by having contingency plans in place. Consider appointing alternate beneficiaries or trusted individuals who can assist your heir if they cannot fulfil their responsibilities.
+
+ Storing keys comes with the responsibility of storing pins and recovery phrases. Here are a few suggestions to store them safely over the long term:
+ Access mechanisms: Pins
+ A PIN (Personal Identification Number) is a security measure to protect access to the wallet and its associated funds. It is typically a numeric code, similar to a password, that must be entered into the hardware wallet's interface to access the stored Bitcoin.
+ The primary purpose of a PIN is to ensure that only the authorized user can access and control the funds stored in the hardware wallet. By requiring a PIN, hardware wallets provide an additional layer of security against unauthorized access, even if the device itself is lost, stolen, or compromised.
+ Keeping the PIN safe is crucial because if it falls into the wrong hands, an attacker could potentially gain control of the Bitcoin stored on the hardware wallet. It is important to choose a PIN that is not easily guessable and not to share it with anyone. Additionally, it is recommended to avoid using obvious PINs like birthdates or repetitive numbers. Furthermore, consider storing the PIN separately from the hardware wallet and other associated information to prevent a single point of failure. However, you can consider using the same pin for all your devices. An important point of caution is to keep things simple!
+ By diligently protecting the PIN, users can significantly reduce the risk of unauthorized access and ensure the security of their Bitcoin holdings. Thus, ensuring pins' safety is step one in safeguarding your keys. Please consider using custom-made steel plates to note them down as they better resist degradation compared to writing/typing them on paper.
+ As an additional security step, consider storing your Pin in a Password Manager as well.
+
+ In case you change your PIN(s), please ensure that you change them at the place where you stored your previous pin as well. This is important as failing to do so may lead to the inaccessibility of keys.
+ Backup mechanism: Recovery phrases
+ Recovery phrases come into play when a key becomes inaccessible. Some of the reasons for inaccessibility may be the degradation of devices storing the keys or the souring of relationships with people entrusted with them. Thus it is important that you not only backup the device storing a key properly, but also test out your recovery mechanism. Once satisfied, please consider etching the seed words onto stainless steel plates for longevity. Please consider etching the seed words of your hardware wallets onto steel plates and storing them in tamper-evident bags.
+ When you are satisfied with the arrangements you’ve made to store access and backup mechanisms, a point to decide is whether you want to store them along with the devices that have your keys or store them separately. This is an important decision and should be taken carefully.
+ To be avoided:
+ Treasure hunts: Please do not simply share keys with people you trust in your lifetime. They may collude and access the Vault after you pass away.
+ Photographing things: Photographs of seed words and pins may give unintended access to your private keys. Please avoid photographing them.
+ Unprotected Storage: Avoid storing your pins/seed words in random files that could be easily accessed or hacked.
+ Entrusting all your keys to one person or storing them all in one place: This action beats the purpose of a multi-sig setup and creates a single point of failure.
+ Closing Notes:
+
+ - Don’t fret and overcomplicate your setup.
+ - Test your setup
+ - Avoid single points of failure
+ - Access your setup multiple times during your lifetime. Once a year at least.
+ - If you change something somewhere, like a device or a pin, please update the change in relevant places.
+
+ -----------------------------------------------------------------------------------
+ This document is one of three Inheritance Planning documents provided by Keeper. The other 2 being: Letter to the Attorney and Recovery Instructions for your heir. This document is auto-produced by the Bitcoin Keeper app. To learn more visit bitcoinkeeper.app.
+
+
+ `;
+ const options = {
+ html,
+ fileName: `KeySecurityTips`,
+ directory: 'Documents',
+ base64: true,
+ };
+ const file = await RNHTMLtoPDF.convert(options);
+ return file.filePath;
+ } catch (error: any) {
+ return error;
+ }
+};
+
+export default GenerateSecurityTipsPDF;
diff --git a/tests/electrum-client/ElectrumClient.test.js b/tests/electrum-client/ElectrumClient.test.js
index 6fef30043..710843e09 100644
--- a/tests/electrum-client/ElectrumClient.test.js
+++ b/tests/electrum-client/ElectrumClient.test.js
@@ -4,9 +4,15 @@ import ElectrumClient from 'electrum-client';
jest.setTimeout(150 * 1000);
-const hardcodedPeers = [{ host: 'electrum1.bluewallet.io', ssl: '443' }];
+const hardcodedPeers = [{
+ host: 'electrumx-core.1209k.com',
+ ssl: '50002'
+}];
-const hardcodedTestnetPeers = [{ host: '35.177.46.45', ssl: '50002' }];
+const hardcodedTestnetPeers = [{
+ host: '35.177.46.45',
+ ssl: '50002'
+}];
describe('Client', () => {
it('can connect and query to mainnet', async () => {
@@ -74,4 +80,4 @@ describe('Client', () => {
client.close();
}
});
-});
+});
\ No newline at end of file
diff --git a/tests/electrum-client/client.test.js b/tests/electrum-client/client.test.js
index 848b9d125..9bd4c8455 100644
--- a/tests/electrum-client/client.test.js
+++ b/tests/electrum-client/client.test.js
@@ -24,9 +24,8 @@ beforeAll(async () => {
describe('Client', () => {
it('Client can test connection', async () => {
- assert.ok(!(await ElectrumClient.testConnection('35.177.46.45', false, 444)));
- assert.ok(await ElectrumClient.testConnection('35.177.46.45', false, 50002));
- assert.ok(await ElectrumClient.testConnection('electrum1.bluewallet.io', false, 443));
+ assert.ok(!(await ElectrumClient.testConnection('testnet.qtornado.com', false, 51002)));
+ assert.ok(await ElectrumClient.testConnection('electrumx-core.1209k.com', false, 50002));
});
it('Client can ping', async () => {
@@ -40,4 +39,4 @@ describe('Client', () => {
assert.ok(features.protocol_min);
assert.ok(features.protocol_max);
});
-});
+});
\ No newline at end of file
diff --git a/yarn.lock b/yarn.lock
index fc0810489..da736df09 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -3967,7 +3967,7 @@ balanced-match@^1.0.0:
resolved "https://registry.yarnpkg.com/balanced-match/-/balanced-match-1.0.2.tgz#e83e3a7e3f300b34cb9d87f615fa0cbf357690ee"
integrity sha512-3oSeUO0TMV67hN1AmbXsK4yaqU7tjiHlbxRDZOpH0KW9+CeX4bRAaX0Anxt0tx2MrpRpWwQaPwIlISEJhYU5Pw==
-base-64@^0.1.0:
+base-64@0.1.0, base-64@^0.1.0:
version "0.1.0"
resolved "https://registry.yarnpkg.com/base-64/-/base-64-0.1.0.tgz#780a99c84e7d600260361511c4877613bf24f6bb"
integrity sha512-Y5gU45svrR5tI2Vt/X9GPd3L0HNIKzGu202EjxrXMpuc2V2CiKgemAbUUsqYmZJvPtCXoUKjNZwBJzsNScUbXA==
@@ -6415,7 +6415,7 @@ glob@7.1.6:
once "^1.3.0"
path-is-absolute "^1.0.0"
-glob@^7.0.0, glob@^7.1.3, glob@^7.1.4, glob@^7.1.6:
+glob@^7.0.0, glob@^7.1.3, glob@^7.1.4, glob@^7.1.6, glob@^7.2.3:
version "7.2.3"
resolved "https://registry.yarnpkg.com/glob/-/glob-7.2.3.tgz#b8df0fb802bbfa8e89bd1d938b4e16578ed44f2b"
integrity sha512-nFR0zLpU2YCaRxwoCJvL6UvCH2JFyFVIvwTLsIf21AuHlMskA1hhTdk+LlYJtOlYt9v6dvszD2BGRqBL+iQK9Q==
@@ -9989,6 +9989,14 @@ react-native-biometrics@2.2.0:
resolved "https://registry.yarnpkg.com/react-native-biometrics/-/react-native-biometrics-2.2.0.tgz#6fc3e801b83389ae1f6c9c41f7b37b50e7014c4e"
integrity sha512-V2O0s2ic7PxVP76CguCfBXvVEyazbjtWv7r20T7D+ZQqBB1XSZ1WzK/Gnr12CVRxHLUZ3/tKHOsz7mzIaXyNoA==
+react-native-blob-util@^0.18.3:
+ version "0.18.3"
+ resolved "https://registry.yarnpkg.com/react-native-blob-util/-/react-native-blob-util-0.18.3.tgz#e3b408dfdd5b175093bbef23f33811f8ef3407ee"
+ integrity sha512-Gx5n1rxl6OcE+Xvj4vFD03Lyhpt+1BmkwU/lIFjPHAUMbSFBvfsOf0TG1cOjMxhw18cDVW7xgcueYZLRscuKPw==
+ dependencies:
+ base-64 "0.1.0"
+ glob "^7.2.3"
+
react-native-camera@^4.2.1:
version "4.2.1"
resolved "https://registry.yarnpkg.com/react-native-camera/-/react-native-camera-4.2.1.tgz#caf74081f055e89d7e9b0cd5108965d808c60e90"
@@ -10150,11 +10158,6 @@ react-native-nfc-manager@^3.13.3:
dependencies:
"@expo/config-plugins" "^4.0.16"
-react-native-permissions@^3.6.1:
- version "3.6.1"
- resolved "https://registry.yarnpkg.com/react-native-permissions/-/react-native-permissions-3.6.1.tgz#73adcc1cef8cd57a9ef167b4507405f4ff5749c4"
- integrity sha512-fzPpPQXeD34inUccqtoResSwYubfrwUguP4qrVUUv8+KSMjYSaHGoS5HaIJLZHlN9gO+TvLJZ2L5ZljTsb6qnQ==
-
react-native-qr-decode-image-camera@^1.1.1:
version "1.1.2"
resolved "https://registry.yarnpkg.com/react-native-qr-decode-image-camera/-/react-native-qr-decode-image-camera-1.1.2.tgz#28ec7ee98e82a287d7b66052f824d1bbd66d4536"
@@ -10222,6 +10225,11 @@ react-native-shadow-2@^6.0.3:
dependencies:
polished "^4.1.4"
+react-native-share@^9.2.2:
+ version "9.2.3"
+ resolved "https://registry.yarnpkg.com/react-native-share/-/react-native-share-9.2.3.tgz#14eb07cb1ee503421df0e9a80fdbf3fb0180223b"
+ integrity sha512-y6ju4HS6ydJoPVoacZ/Hp3i47AfI9W4e76Jv00r01dVbr6SCCcuqk37kIbn+kYivdTxOW77UGEbhtBHHtXnhzg==
+
react-native-size-matters@^0.4.0:
version "0.4.0"
resolved "https://registry.yarnpkg.com/react-native-size-matters/-/react-native-size-matters-0.4.0.tgz#01bfd0d59454318f4e0b13fe9c1eb0523d70f2e0"