New feature request: Locking sending the bitcoin address, bitcoin banking

[tonychow]

I think technically, it is implementable. That is, bitcoin owner can state somewhere in the block chain that bitcoins in that address cannot be sent, which can add one more level of security. Also, the owner can voluntarily reveal his identity in public, or to a trusted third party.

Anonymity should be an added feature, not a mandatory feature, and that will improve the overall security.   

[BitCoinDream]

I think technically, it is implementable. That is, bitcoin owner can state somewhere in the block chain that bitcoins in that address cannot be sent, which can add one more level of security. Also, the owner can voluntarily reveal his identity in public, or to a trusted third party.

Anonymity should be an added feature, not a mandatory feature, and that will improve the overall security.   

+1

Its a required feature indeed. But I doubt if the current protocol can support it w/o relying on a third party.

[cr1776]

I think technically, it is implementable. That is, bitcoin owner can state somewhere in the block chain that bitcoins in that address cannot be sent, which can add one more level of security. Also, the owner can voluntarily reveal his identity in public, or to a trusted third party.

Anonymity should be an added feature, not a mandatory feature, and that will improve the overall security.   

1. Anyone can state "this public address is me" right now.  You can be non-anonymous without any feature changes.

2. A private key states that coins cannot be sent. That is its function. No additional feature is required there either.  If you require a second or third signature for more security, then use multi-sig for the trusted third party.

[softron]

If u do this how do u unlock the wallet when u need it. U might look at using multi-sig addresses, they work well for securing coins.

[TierNolan]

You could implement a "fake" version of this.

Create a private/public key-pair.

Create a transaction which sends money to the corresponding address

Submit to the network

Create a new transaction that sends that money onwards to one of your other address.  This transaction should be locked for 3 months in the future.

Wait a while for the transaction to be buried in the chain.  There is a risk due to malleability.  Once the transaction is buried 10-20 blocks deep, it should be very safe (unless it is a very large transaction).

The wait isn't needed if malleability is fixed.

Once you are confident that no reversal will happen, store the redeem transaction and delete the private key.

This means that the only way to spend your coin is with the transaction that you just created.

Since it is a locked transaction, you can't spend it for 3 months.

A hacker would need to steal the redeem transaction and also the key for the address that you sent it to.

[dewdeded]

Feature exists.

https://en.bitcoin.it/wiki/NLockTime

Maybe for your use-case you have to do Multi-Signature-TX with NLockTime.
(Could be that what you want cant be done with one TX, so -> Multi-Sig-TX.)

[DannyHamilton]

bitcoin owner can state somewhere in the block chain that bitcoins in that address cannot be sent, which can add one more level of security. Also, the owner can voluntarily reveal his identity in public, or to a trusted third party.

This is already how bitcoin works.  There is no feature request necessary.