Before creating a policy, the owner of the Binance account in the whitelist enters the static IP address of the KeycoSafe server. We will make sure that this address never changes.
If the policy is stolen, the attacker will need to somehow change the recipient's address in the policy.
This sounds better and somewhat reassuring. I'm somewhat still not 100% convinced (
but I can't say clearly why), but you seem to be going on the right direction.
I guess it's still too technical for many and people will prefer to pass on a seed - in a way or another - but your service can easily have its niche.
I agree this does look to be a more certain way to ensure nobody takes advantage of the owner's death but still, this relies on KeycoSafe servers to always have the same IP address and or the same device. But definitely too technical for majority of people, including me (which I can fix by reading a manual but not everyone will).
What happens if the company or the ISP is forced to make a change?
- after testing, we will add backup servers at different hosting providers, trusted will be several different ip addresses
- we will notify our users on the forum, discord, twitter that they need to change the trust ip