Making a transaction whose output is spendable only after n blocks are found?

[voileipa]

Making a transaction whose output is spendable only after n blocks are found?
Is that possible?`

[kolinko]

Bitcoin has a nLockTime mechanism within the protocol, but there are various issues with it: http://bitcoin.stackexchange.com/questions/5783/transactions-with-a-wait-time-using-nlocktime

You can achieve a similar feat using M of N oracles:
https://github.com/orisi/orisi
https://www.youtube.com/watch?v=boPW1FwNu4c

[yakuza699]

I may be wrong but nLockTime isn't correctly implemented. nLockTime only works if the sequence number is lower than 4294967295 but transactions which sequence number is lower than 4294967295 are considered non standard if you set the sequence number to 4294967295 miners will ignore the nLockTime and will mine your transaction before nLock expires so no there is no such thing implemented. Correct me if i am wrong.

[yakuza699]

Bitcoin has a nLockTime mechanism within the protocol, but there are various issues with it: http://bitcoin.stackexchange.com/questions/5783/transactions-with-a-wait-time-using-nlocktime

You can achieve a similar feat using M of N oracles:
https://github.com/orisi/orisi
https://www.youtube.com/watch?v=boPW1FwNu4c

If i am not mistaken (sorry didn't had enough time to read everything) your client invades multi sig transactions but what if user wants to create transaction like this : A sends money directly to B(not involving multi sig) transaction appears on block explorers such as blockchain.info as unconfirmed and will not be confirmed till block x and B (even though you can spend unconfirmed transaction now) will not be able to spend those btc until the transaction is confirmed. Can i do this kind of thing with orisi?

[DeathAndTaxes]

I may be wrong but nLockTime isn't correctly implemented. nLockTime only works if the sequence number is lower than 4294967295 but transactions which sequence number is lower than 4294967295 are considered non standard if you set the sequence number to 4294967295 miners will ignore the nLockTime and will mine your transaction before nLock expires so no there is no such thing implemented. Correct me if i am wrong.

That is how it works but it is implemented correctly.  nlocktime transactions which are not standard until the lock time is reached.  This is intentional because if it wasn't true one could spam the network at no cost by generating millions or billions of nlocktime transactions.   However this doesn't prevent you from giving the nlocktime transaction directly to the recipient out of band.

[rapport]

I may be wrong but nLockTime isn't correctly implemented. nLockTime only works if the sequence number is lower than 4294967295 but transactions which sequence number is lower than 4294967295 are considered non standard if you set the sequence number to 4294967295 miners will ignore the nLockTime and will mine your transaction before nLock expires so no there is no such thing implemented. Correct me if i am wrong.

That is how it works but it is implemented correctly.  nlocktime transactions which are not standard until the lock time is reached.  This is intentional because if it wasn't true one could spam the network at no cost by generating millions or billions of nlocktime transactions.   However this doesn't prevent you from giving the nlocktime transaction directly to the recipient out of band.

Here's my attempt to make above clearer (yakuza699 lack of punctation was a little confusing):
- nLockTime only works if the sequence number is lower than 4294967295
- transactions with sequence number lower than 4294967295 are considered non standard
- This is intentional because if it wasn't true one could spam the network at no cost by generating millions or billions of nlocktime transactions
- You can give the nlocktime transaction directly to the recipient out of band, and when the lock time is reached, the transaction becomes standard and the recipient can broadcast it

[gmaxwell]

- nLockTime only works if the sequence number is lower than 4294967295
- transactions with sequence number lower than 4294967295 are considered non standard

If and only if their locktime hasn't passed, I realize you know this, but your message was a bit confusing.

[kolinko]

If i am not mistaken (sorry didn't had enough time to read everything) your client invadesolves multi sig transactions but what if user wants to create transaction like this : A sends money directly to B(not involving multi sig) transaction appears on block explorers such as blockchain.info as unconfirmed and will not be confirmed till block x and B (even though you can spend unconfirmed transaction now) will not be able to spend those btc until the transaction is confirmed. Can i do this kind of thing with orisi?

For that, you'd need nLockTime, as others said