On Tue, Sep 27, 2011 at 4:08 PM, Luke-Jr <l...@dashjr.org> wrote: > Is it certain that it cannot be triggered by a peer having some huge number > more blocks than you?
Might be better to have a global flag that indicates when the node thinks its current with the network (this could have other UI impacts, like letting the user know if they send and their connectivity looks non-current), and only enforce this check when the node believes that its current. Currency could be =height>last_checkpoint&&top_timestamp>now()-safe_amount; with safe_amount to be high enough that it's very unlikely to be falsely triggered by an improbably long gap. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
