Quote from: escrow.ms on November 11, 2013, 02:13:16 AM

You can check some info about it here:
http://bitcoin.stackexchange.com/questions/5783/transactions-with-a-wait-time-using-nlocktime

Some more research I have just found:

From Satoshi: https://bitcointalk.org/index.php?topic=1786.msg22119#msg22119
https://bitcointalk.org/index.php?topic=131443.0
https://people.xiph.org/~greg/signdemo.txt

However, from the brief amount of time I have researched this - this comment from the second link is worrisome:

Quote from: etotheipi on January 04, 2013, 06:32:32 AM

One thing that wasn't mentioned yet was that there's not currently a mechanism for replacement. Locked transactions can be "introduced" into the blockchain fairly easily, and nodes will accept them and hold them in their memory pool (and thus drop conflicting transactions), but they won't forward otherwise-valid replacements, and only miners with custom rules will mine them for you. If you want to replace a time-locked transaction, you're going to have to mine it yourself, or go find a miner to agree to help you. Once a replacement is mined (or even just a regular transaction spending one of the inputs), all nodes holding the time-locked tx will see the conflict and drop the one in their memory pool.

So, if you can create the tx, you can get the "time-delay" aspect out of the network right now, but you have to work pretty hard if you use the "replacement" aspect of it.

P.S. - Congrats on being the most well-spoken, research-driven, single-post Newbie I've seen on these forums

And this makes it seem like it is not even supported what-so-ever

from Gavin himself....

Quote from: Gavin Andresen on October 27, 2013, 11:44:02 PM

Time-in-the-future transactions are non-standard (as of 0.8? I can never remember when things happened...)

Why: because there is a fill-up-memory denial of service attack, and it really isn't reasonable to expect the entire network to store your timelocked transactions "forever".

Even in the past, the statement "unspendable by the sender because of replacement not being implemented" was not true. Wait long enough and only a subset of the network will have the timelocked transaction (because new nodes, old nodes restarting, etc). Broadcast a double-spending version without a timelock and it will get mined fairly soon.

Seems like this feature is totally dead...wtf bitcoin!

Anyone knowledgeable in the subject feel free to offer your wisdom!