Defines the block number or timestamp until this transaction is locked, or 0 if the transaction is always locked.

learn more… | top users | synonyms

2
votes
1answer
84 views

nLockTime transactions, how do they persist? Are they broadcast before they are valid?

If nLockTime transactions aren't added to the blockchain until the nLockTime is met, then aren't they just being stored in memory of the miners and is there a risk they could get "lost"? I guess I'm ...
0
votes
1answer
32 views

Can I cancel an offline transaction with this approach? (opposite of nLocktime)

I would like to cancel a transaction I sent offline, and am looking for ways to prevent it from being accepted by the network. Will the Bitcoin client prohibit the entire Tx if there is even on input ...
3
votes
1answer
60 views

Could I mine a non-final transaction?

I know that non-final transactions (locktime in future and sequence number < MAX_UINT) are not "accepted by miners". However, I could not figure out the exact behavior. If I mined my own block ...
1
vote
1answer
54 views

How do you publish a transaction which is cancelled if not claimed by a given time?

How do you publish a transaction which is cancelled if some output is not claimed by a given time? (ie returning all the spent coins to their inputs or else creating new conditions under which they ...
2
votes
1answer
91 views

Is the time value in transaction or block information the time it arrived at my client? [duplicate]

Both transactions and blocks have a time field when you use Bitcoin's getblock or gettransaction methods. The API method list defines the transaction time as " time the transaction occurred". Is this ...
3
votes
1answer
410 views

How is locktime enforced in the standard client?

I am trying to study the locktime feature of transactions ( https://en.bitcoin.it/wiki/Protocol_specification#tx ). I have created some raw transactions in the testnet with different locktimes, but, ...
1
vote
1answer
143 views

In a given contract, should the “LockTime” timestamp include an extra hour for confirmations to prevent a double spend?

Anytime a transaction has a timestamp attached to it, and there are signed but not submitted transactions at play, shouldn't the holder of the non-submitted tx have to take into account the ...