mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2024-12-24 23:48:32 +00:00
Edited ch12_mining.adoc with Atlas code editor
This commit is contained in:
parent
a4a33c0d1f
commit
9e86d04635
@ -1004,7 +1004,7 @@ market.
|
||||
[[mtp]]
|
||||
=== Median Time Past (MTP)
|
||||
|
||||
In Bitcoin there is a subtle, but very
|
||||
In Bitcoin ((("decentralized consensus", "timestamps and", id="decentral-consensus-timestamp")))((("consensus rules", "timestamps and", id="consensus-timestamp")))((("timestamps", id="timestamp")))((("median time past (MTP)", id="median-time-past")))((("bitcoins", "mining", "timestamps", id="bitcoin-mining-timestamps")))((("mining", "timestamps", id="mining-timestamps")))there is a subtle, but very
|
||||
significant, difference between wall time and consensus time. Bitcoin is
|
||||
a decentralized network, which means that each participant has his or
|
||||
her own perspective of time. Events on the network do not occur
|
||||
@ -1052,7 +1052,7 @@ MTP changes the implementation of time calculations for
|
||||
lock time, +CLTV+, sequence, and +CSV+. The consensus time
|
||||
calculated by MTP is usually about one hour behind
|
||||
wall clock time. If you create timelock transactions, you should account
|
||||
for it when estimating the desired value to encode in lock time,
|
||||
for it when estimating the desired value to encode ((("decentralized consensus", "timestamps and", startref="decentral-consensus-timestamp")))((("consensus rules", "timestamps and", startref="consensus-timestamp")))((("timestamps", startref="timestamp")))((("median time past (MTP)", startref="median-time-past")))((("bitcoins", "mining", "timestamps", startref="bitcoin-mining-timestamps")))((("mining", "timestamps", startref="mining-timestamps")))in lock time,
|
||||
sequence, +CLTV+, and +CSV+.
|
||||
|
||||
=== Successfully Mining the Block
|
||||
|
Loading…
Reference in New Issue
Block a user