1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1T0GUX-0006i0-ON
for bitcoin-development@lists.sourceforge.net;
Sat, 11 Aug 2012 18:32:53 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.217.175 as permitted sender)
client-ip=209.85.217.175; envelope-from=laanwj@gmail.com;
helo=mail-lb0-f175.google.com;
Received: from mail-lb0-f175.google.com ([209.85.217.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1T0GUX-0007dd-2H
for bitcoin-development@lists.sourceforge.net;
Sat, 11 Aug 2012 18:32:53 +0000
Received: by lban1 with SMTP id n1so1365767lba.34
for <bitcoin-development@lists.sourceforge.net>;
Sat, 11 Aug 2012 11:32:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.152.124.180 with SMTP id mj20mr6732659lab.43.1344709966407;
Sat, 11 Aug 2012 11:32:46 -0700 (PDT)
Received: by 10.112.83.161 with HTTP; Sat, 11 Aug 2012 11:32:46 -0700 (PDT)
In-Reply-To: <50268BB0.8080001@bitminter.com>
References: <CA+8xBpfeoNOte=GFGqAT7+4U+JCa4DP8CkEupe+oKdJL1dMFFQ@mail.gmail.com>
<50268BB0.8080001@bitminter.com>
Date: Sat, 11 Aug 2012 20:32:46 +0200
Message-ID: <CA+s+GJAooor=aCxt9g65m7Ytiut3WMjmG9838uzqUxwtH=xPHw@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Geir Harald Hansen <operator@bitminter.com>
Content-Type: multipart/alternative; boundary=f46d0434bfdedfa8ef04c701af36
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(laanwj[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1T0GUX-0007dd-2H
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Version 0.7 release planning
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sat, 11 Aug 2012 18:32:53 -0000
--f46d0434bfdedfa8ef04c701af36
Content-Type: text/plain; charset=UTF-8
By the way, by far the most common support request I have at my pool is
> users withdrawing coins and not seeing it in their wallet because it's
> not up-to-date with the block chain. Might be worth adding something in
> the bitcoin-qt GUI to make it more obvious that users can't see new
> transactions and why.
>
For 0.7 we've added a red "(out of sync)" warning to the balances when the
block chain is out of date.
However, due to the design of the protocol there is a large variance in
block timings, and it is not possible to determine up-to-date status with
certainty, so quite a large safety margin is used. To be precise the
warning is shown when the last received block was generated more than 90
minutes ago.
Wladimir
--f46d0434bfdedfa8ef04c701af36
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
By the way, by far the most common support request I have at my pool is<br>=
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
users withdrawing coins and not seeing it in their wallet because it's<=
br>
not up-to-date with the block chain. Might be worth adding something in<br>
the bitcoin-qt GUI to make it more obvious that users can't see new<br>
transactions and why.<br></blockquote><div><br>For 0.7 we've added a re=
d "(out of sync)" warning to the balances when the block chain is=
out of date.<br><br>However, due to the design of the protocol there is a =
large variance in block timings, and it is not possible to determine up-to-=
date status with certainty, so quite a large safety margin is used. To be p=
recise the warning is shown when the last received block was generated more=
than 90 minutes ago. <br>
<br>Wladimir<br><br></div></div>
--f46d0434bfdedfa8ef04c701af36--
|
