j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM[<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1786.msg22014#msg22014">Quote from: ByteCoin on November 15, 2010, 02:47:30 AM</a></div><div class="quote">Hmm.. If clients disagree about what the current block count is then they already disagree about whether certain transactions are valid or not and therefore the problem you mention exists already without my proposal.<br/>Please go into more detail about why this is not good for the network.<br/></div><br/>You may be right about this. Bitcoin's segmentation-fixing mechanisms would seem to keep everything in order.<br/><br/>A similar feature seems to already be planned. Every transaction has the currently-unused "nLockTime" field, and this bit of code exists for the UI (the text would appear in the same place as "x confirmations"):<br/><div class="codeheader">Code:</div><div class="code"> if (!wtx.IsFinal())<br/> {<br/> if (wtx.nLockTime < 500000000)<br/> return strprintf(_("Open for %d blocks"), nBestHeight - wtx.nLockTime);<br/> else<br/> return strprintf(_("Open until %s"), DateTimeStr(wtx.nLockTime).c_str());<br/> }</div><br/>Sounds very much like what you're thinking of.</div> text/html
https://whatsonchain.com/tx/a0e7df3790bbf33a9bb92415cda1dfc87149be5c0b32d48d5f4f79d09bf4e2c3