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
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <zgenjix@yahoo.com>) id 1QiPuJ-0001Zs-Ot
for bitcoin-development@lists.sourceforge.net;
Sun, 17 Jul 2011 11:53:11 +0000
X-ACL-Warn:
Received: from nm10-vm6.bullet.mail.ne1.yahoo.com ([98.138.91.103])
by sog-mx-2.v43.ch3.sourceforge.com with smtp (Exim 4.76)
id 1QiPuI-0004Iy-RQ for bitcoin-development@lists.sourceforge.net;
Sun, 17 Jul 2011 11:53:11 +0000
Received: from [98.138.90.51] by nm10.bullet.mail.ne1.yahoo.com with NNFMP;
17 Jul 2011 11:53:05 -0000
Received: from [98.138.87.10] by tm4.bullet.mail.ne1.yahoo.com with NNFMP;
17 Jul 2011 11:53:05 -0000
Received: from [127.0.0.1] by omp1010.mail.ne1.yahoo.com with NNFMP;
17 Jul 2011 11:53:05 -0000
X-Yahoo-Newman-Property: ymail-5
X-Yahoo-Newman-Id: 500341.1070.bm@omp1010.mail.ne1.yahoo.com
Received: (qmail 78372 invoked by uid 60001); 17 Jul 2011 11:53:05 -0000
X-YMail-OSG: 5Y7iyakVM1mINO1ckvoApqCfQci3DwFp6eEP2OYhbc4510h
Dbc9KHP4bqTzKA0y8xT9tzySpZ3AcxJJmGhU1N4ltHUBZrOjJZhvIKAcB6AO
nm4tiXA.x7mAKPhpZnCZMU7PrgU7hkabqtpxHRbBz.tWs25487PHYuJcDU57
KQb6YzoG71g8uOJo3AwNb8m1bvc7m7IaAiB9v4GZCh889PazdvmZ6ge5csRJ
yuLDoeLb6KeauS.tat7yBMUFXriCKDU_sigO05iF4rMciX09_nYMeC0SIpIH
IoSOr2hj8sHRwnls0SjU0vEG1DFFL6ssTDna7_ET.jbreN5lSLH0weHtYnvb
_BDyz_JY6R_8j0T3BxfvigO_b0gfKj0s7d7RoYKp3CuagS.Qbe6ExCtUSMOs
KDBoKsvR1SahrykGbElwk3xgZqT6z5zJR0gzq5_9LLgxW2XyoVW__UGpiez4
ZmpM2FkIqV798e1EBK0QAfxNY56cNyliObZiR.CSmmkkDO1USERaAv00BrMU
pLJP.QPIbm.7fCYRz5titS64-
Received: from [178.42.79.228] by web121007.mail.ne1.yahoo.com via HTTP;
Sun, 17 Jul 2011 04:53:05 PDT
X-Mailer: YahooMailWebService/0.8.112.307740
References: <201107161314.13267.luke@dashjr.org>
<20110716195907.GA311029@tenebreuse>
<201107161603.08960.luke@dashjr.org>
<CABsx9T2qhLiYAQNOCigXOMySgVqDqqQMotqYQwSPZEwkSYbY=g@mail.gmail.com>
Message-ID: <1310903585.65859.YahooMailNeo@web121007.mail.ne1.yahoo.com>
Date: Sun, 17 Jul 2011 04:53:05 -0700 (PDT)
From: Amir Taaki <zgenjix@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
In-Reply-To: <CABsx9T2qhLiYAQNOCigXOMySgVqDqqQMotqYQwSPZEwkSYbY=g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1922963698-1310903585=:65859"
X-Spam-Score: 1.3 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [98.138.91.103 listed in list.dnswl.org]
1.5 TVD_PH_BODY_ACCOUNTS_PRE BODY: TVD_PH_BODY_ACCOUNTS_PRE
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(zgenjix[at]yahoo.com)
-1.1 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain 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: 1QiPuI-0004Iy-RQ
Subject: Re: [Bitcoin-development] [RFC] listtransactions reformatting
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Amir Taaki <zgenjix@yahoo.com>
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: Sun, 17 Jul 2011 11:53:11 -0000
--0-1922963698-1310903585=:65859
Content-Type: text/plain; charset=us-ascii
Oops, sorry Gavin. Meant to reply to the mailing list.
---------------
People should not be using accounts for receiving funds on
merchant sites. There are too many bugs associated with it, and it has
innumerable problems. Like not being able to merge wallets or lack of
find grained control when moving funds around.
https://gitorious.org/intersango/bitcoind/commit/50a6ab79ed8c5398648c52fbdc4be07f70dedadb
This is the recommended & most safest way to receive funds on a merchant site ATM.
listreceivedsince <timest> is called every so often by a cron job.
The output is parsed and placed into another table and then another job
will go and create a deposit request from that table. The next call to listreceivedsince <timest> will call with the time of the last
transaction, and doubles must be discarded using the txid.
Polling listtransactions is less convenient since you always repeat old
transactions that you may not need, get generated transactions and have
to pick a good number that goes back far enough, but not too far.
________________________________
From: Gavin Andresen <gavinandresen@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Sent: Sunday, July 17, 2011 5:02 AM
Subject: Re: [Bitcoin-development] [RFC] listtransactions reformatting
Fixing listtransactions (and listreceivedby/etc) so coin generation
transactions to particular addresses/accounts are credited to that
address/account is a good idea.
I don't think changing listtransactions output would be on the
priority list for any web services operators (in fact, I think most
would scream bloody murder if the output changed in a way that forced
them to change their code). The accounts-related things that I think
ARE on their high-priority list are:
1) Fixing getbalance and listtransactions performance problems when
you have hundreds of thousands of transactions and thousands of
accounts.
2) push-notification of coins received to accounts, so they don't have
to poll for changes.
--
--
Gavin Andresen
------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Methodology on "Lean Startup
Secrets Revealed." This video shows you how to validate your ideas,
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development
--0-1922963698-1310903585=:65859
Content-Type: text/html; charset=us-ascii
<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>Oops, sorry Gavin. Meant to reply to the mailing list.</span></div><div><br></div><div>---------------<br></div><div><br><span></span></div><div><span>People should not be using accounts for receiving funds on
merchant sites. There are too many bugs associated with it, and it has
innumerable problems. Like not being able to merge wallets or lack of
find grained control when moving funds around.</span></div><div><br><span></span></div><div><span>https://gitorious.org/intersango/bitcoind/commit/50a6ab79ed8c5398648c52fbdc4be07f70dedadb</span></div><div><br><span></span></div><div><span>This is the recommended & most safest way to receive funds on a merchant site ATM.</span></div><div><br><span></span></div><div><span>listreceivedsince <timest> is called every so often by a cron job.</span></div><div><span>The
output is parsed and placed into another table and then another job
will go and create a deposit request from that table. The next call to
listreceivedsince <timest> will call with the time of the last
transaction, and doubles must be discarded using the txid.</span></div><div><br><span></span></div><span>Polling
listtransactions is less convenient since you always repeat old
transactions that you may not need, get generated transactions and have
to pick a good number that goes back far enough, but not too far.</span><div><br></div><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"><font face="Arial" size="2"><hr size="1"><b><span style="font-weight:bold;">From:</span></b> Gavin Andresen <gavinandresen@gmail.com><br><b><span style="font-weight: bold;">To:</span></b> bitcoin-development@lists.sourceforge.net<br><b><span style="font-weight: bold;">Sent:</span></b> Sunday, July 17, 2011 5:02 AM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [Bitcoin-development] [RFC] listtransactions reformatting<br></font><br>Fixing listtransactions (and listreceivedby/etc) so coin generation<br>transactions to particular addresses/accounts are credited to that<br>address/account is a good idea.<br><br>I don't think changing listtransactions output would be on the<br>priority
list for any web services operators (in fact, I think most<br>would scream bloody murder if the output changed in a way that forced<br>them to change their code). The accounts-related things that I think<br>ARE on their high-priority list are:<br><br>1) Fixing getbalance and listtransactions performance problems when<br>you have hundreds of thousands of transactions and thousands of<br>accounts.<br><br>2) push-notification of coins received to accounts, so they don't have<br>to poll for changes.<br><br>-- <br>--<br>Gavin Andresen<br><br>------------------------------------------------------------------------------<br>AppSumo Presents a FREE Video for the SourceForge Community by Eric <br>Ries, the creator of the Lean Startup Methodology on "Lean Startup <br>Secrets Revealed." This video shows you how to validate your ideas, <br>optimize your ideas and identify your business strategy.<br><a href="http://p.sf.net/sfu/appsumosfdev2dev"
target="_blank">http://p.sf.net/sfu/appsumosfdev2dev</a><br>_______________________________________________<br>Bitcoin-development mailing list<br><a ymailto="mailto:Bitcoin-development@lists.sourceforge.net" href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a><br><a href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development" target="_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a><br><br><br></div></div></div></body></html>
--0-1922963698-1310903585=:65859--
|
