From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WTXLT-0000v3-8T for bitcoin-development@lists.sourceforge.net; Fri, 28 Mar 2014 14:01:19 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.160.171 as permitted sender) client-ip=209.85.160.171; envelope-from=gavinandresen@gmail.com; helo=mail-yk0-f171.google.com; Received: from mail-yk0-f171.google.com ([209.85.160.171]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WTXLR-0001G7-Ca for bitcoin-development@lists.sourceforge.net; Fri, 28 Mar 2014 14:01:19 +0000 Received: by mail-yk0-f171.google.com with SMTP id q9so3642205ykb.2 for ; Fri, 28 Mar 2014 07:01:11 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.236.104.200 with SMTP id i48mr11256916yhg.61.1396015271763; Fri, 28 Mar 2014 07:01:11 -0700 (PDT) Received: by 10.170.133.195 with HTTP; Fri, 28 Mar 2014 07:01:11 -0700 (PDT) In-Reply-To: References: <612FFAAD-14FF-4261-927D-BD2E0F287257@bitsofproof.com> Date: Fri, 28 Mar 2014 10:01:11 -0400 Message-ID: From: Gavin Andresen To: Tamas Blummer Content-Type: multipart/alternative; boundary=001a11c2c5085ff4ec04f5ab22c2 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 (gavinandresen[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: 1WTXLR-0001G7-Ca Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] BIP 70 refund field X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Mar 2014 14:01:19 -0000 --001a11c2c5085ff4ec04f5ab22c2 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Mar 28, 2014 at 9:18 AM, Tamas Blummer wrote: > May I ask how the current payment protocol is supposed to handle salaries? > It doesn't. "walk before you run" and all that; lets see what problems we run into with the minimal payment protocol we have now (like refund outputs you have to remember forever) before we create an insurmountable set of problems by trying to solve everything we can think of all at once. -- -- Gavin Andresen --001a11c2c5085ff4ec04f5ab22c2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On F= ri, Mar 28, 2014 at 9:18 AM, Tamas Blummer <tamas@bitsofproof.com&= gt; wrote:
May I as= k how the current payment protocol is supposed to handle salaries?

It doesn't.

"walk bef= ore you run" and all that; lets see what problems we run into with the= minimal payment protocol we have now (like refund outputs you have to reme= mber forever) before we create an insurmountable set of problems by trying = to solve everything we can think of all at once.

--
--
Gavin Andresen
--001a11c2c5085ff4ec04f5ab22c2--