Who Actually Drives Bitcoin Locktime? Users or Miners?

Stumbling upon Bitcoin terms is wild. Just learned about Locktime. What even is it? Turns out it stops a transaction from being mined until a certain time or block is hit. Why would anyone want that?

Locktime is set right at the end of the transaction. But here’s the kicker: you need one of the inputs to be locked too. Just slapping on a locktime isn’t enough. The sequence value must be set to 0xfffffffe or lower to even make it work.

Quick question though... if you set a locktime but later wanna change it, can you? Or is it locked in once it’s set?

You can definitely cancel a transaction before your locktime hits. Just cancel and create a new one. But if you wanna change the amount or details, nope, can’t do that.

So there are two types of locktime, right? One based on time and the other on block height. If it's a low value, it’s height. High value? It's UTC time. Simple as that.

For a clearer example, imagine set a locktime for a child’s savings until they turn 18. You set that date and boom, they can access it then. But nodes might not keep it in their mempool for far future dates. Weird.

Locktime is actually super useful for things like inheritance. You can plan gifts ahead of time. Default is 0, but you can set it anywhere from 0 to 500 million.

Using nLockTime is like saying, ‘Hey, cash this check later’. It stops the transaction until a certain point. Some wallets use it to prevent miners from messing with the chain.

What if you create a transaction with a crazy high fee? If miners see that, they could redo a block just to grab those fees. Risky business.

So, just one locktime per transaction, right? It can either be a date or block height, but not both?

Exactly, there’s only one nLocktime for each transaction. It can represent either a date or a block height, depending on the value.

But how does the network agree on time? Seems messy without consensus on time itself. Mixing datetime and block height in one field feels wrong.

Actually, there is a way. Block headers have timestamps. Not super exact, but it works. 4 bytes for locktime is enough. The numbers range is enough to cover a long time.

Transactions with future locktimes get flagged as non-final and won’t make it to the mempool. They stay in your wallet or get stored somewhere else.

Kinda true, but there are sites that accept time-locked transactions briefly. They later drop them if they stay unconfirmed. Odd, huh?

I think certain nodes may not enforce those rules, allowing some flexibility. But generally, it’s for safety, especially against DDOS.

If a block with your locktime gets reorged, your transaction might just disappear. Better keep it safe if there’s a risk of being overlooked.

How much of a risk is that? Sounds sketchy. This feel like a hacky solution to me. Just make separate fields for time and block height!

Exactly. Having them mixed in one field just feels like poor design. It’s gonna be a nightmare in 2106 and beyond.

Totally agree on that. Satoshi definitely took some shortcuts. It’s not pretty and there’s a lot to fix. What’ll happen then?