bitcoinwarrior1 / crypto-timelocked-backup Goto Github PK

Instead of using just approval transactions, we could create approval transactions that approve a not yet deployed CREATE2 contract. This contract could then be deployed and the approval transaction broadcasted.

The advantage of this would be that you could add time constraints to the contract and prevent the transfer of tokens from it if the time constraints are not met.

Related: #10

Sender can set the timestamps and recipient inside another already deployed contract. This allows the sender to change the outcome of the transactions whenever they want.

If registry values are not set, use the constructor arguments

This should be implemented for each coin.

• Sign nlocktime tx with trezor
• Download backup as a .md or .txt
• If recipient is not set, generate a new key, set it as the recipient and add the private key to the backup file
• Download calendar reminder
• Include a revoke transaction that spends the funds back to the signer's address

This would be completely non custodial and could later include alerts that watch the user's wallet for transactions that invalidate the backup.

Explain the how, why and process better.

This might be tricky as many injected providers don't allow signing but not sending transactions.

1. Allow the user to select a list of whitelisted addresses (they should only send coins to these addresses and no others)
2. Have the user sign but not send all their balance to a backup address with a very high fee
3. If a transaction from the user's wallet to an unauthorised wallet is detected, publish the transaction to the backup address

https://wiki.polkadot.network/docs/build-protocol-info#transaction-mortality

Save approval transactions for each token.

This makes it easier for the user and exchanges like Binance don't typically change their deposit address for their users.

This would require modification of the erc20/721 approach as approvals won't work. We could use transfer.