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

learn more… | top users | synonyms

3
votes
2answers
40 views

Is it possible to schedule a transaction in the future?

Wondering if it's technically possible to set up a transaction to be sent in the future, for example 6 months? Is this related to block timestamps parameters? Transaction timestamps?
5
votes
1answer
26 views

Is it possible to determine the total amount of timelocked Bitcoin?

Now that is possible to lock funds until a certain date (https://coinb.in/#newTimeLocked). How to calculate how many of all bitcoin in existence is locked until a certain date? Any service that does ...
1
vote
1answer
57 views

Timelock Transactions

I would like to know if timelock transactions are considered standard with the current bitcoin client. If the answer is no, this means that you should use a different client or is it up to user ...
0
votes
1answer
85 views

Is my understanding of locktime correct?

I have been trying to understand locktimes and sequence numbers. I'm gradually building up a picture in my head based on code, code comments and info on the web. Rather than asking lots of questions, ...
3
votes
2answers
163 views

What will happen when nLockTime is used along with Counterparty transactions

I heard that Counterparty cannot handle lock time, but I cannot understand why. What will happen when we use nLockTime in a transaction which includes Counterparty transactions?
2
votes
0answers
46 views

Bitcoin contracts with stickK.com functionality

Does a BTC service/application allow me to set a nTimeLock transaction that can be interrupted by a single predetermined 3rd party before the transaction has been made public? If a service like this ...
4
votes
2answers
273 views

Is there any way to make an UTXO that cannot be spent until a certain block #?

In bitcoin, each transaction has an nLockTime integer to specify the earliest allowed block number/time that the transaction can be added to the blockchain. In addition, each transaction input has an ...
3
votes
1answer
220 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
67 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 ...
4
votes
1answer
96 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
60 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
124 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 ...
8
votes
2answers
435 views

Can nLockTime TX be used to flood Mempools?

What would happen, if I would create a large number of large transactions with a very high nLockTime? Would something stop me from filling not only the miners', but also regular nodes' mempools? ...
6
votes
1answer
698 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
181 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 ...