Funny you mentioned that. Just had an interesting talk with someone about a BTC wallet that could do such things. Seems very possible to do that here as well.
Yes, of course, everyone is going to start talking about this, just like they are talking about many of our other features. This particular feature is in the news because it is low hanging fruit for today's crypto programmers, and very juicy fruit I might add $$$.
love this idea! only suggestion is to enable some way to stop payment to an address in case one gets compromised. we'd need a clever way to make sure that doesn't become an attack vector for the wallet with a third party able to shut down all transfer channels...
No, that is the whole value of the "zombify" button. The immutability of this contract is exactly the feature that makes it valuable. It's a derivative of the value that the immutable blockchain concept has already proved in practice, and why every crypto project currently exists.
If there is only one thing that the success of bitcoin has taught us, is that immutability has mad real world value (currently $3 billion in value jack). So this is a direct derivative feature of bitcoin's immutability, that we must exploit ASAP (only because it is one of the easier features to implement).
You cannot ever ever (therein lies the true value) ever ever for eternity change the parameters of the wallet. It just pays out, on time, until it is empty. How can you attack a zombie wallet besides stealing the destination private keys? That is the same attack vector to the private keys you now own, so there is zero added security issue.
Step 1. you designate the walets you want to send funds to and the frequency. Make sure you have these keys protected.
Step 2. You hit the kill switch
Step 3. If one of the destination wallets gets compromised, too bad (just like losing your private key, there is no recourse). This is an eternal 1 way transaction. The only way to get around that snafu, if you are still alive is to stop funding this annuity and set up another. These are indestructible contracts that have extremely high real world value and are critical to our platform ability. Since the majority of the work is structuring the annuity software portion, I imagine that coding the "kill switch" would be the easy part.
Please, and pretty please.
All I'm begging for is a "kill switch" for the annuity function, is that too difficult to code?
Annuity "kill switch" = wallet can no longer send funds or be modified in any way, but it continues to frequently pay destination wallets, and can accept funds.