From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Vad61-0005fc-2E for bitcoin-development@lists.sourceforge.net; Mon, 28 Oct 2013 03:02:25 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.223.170 as permitted sender) client-ip=209.85.223.170; envelope-from=pieter.wuille@gmail.com; helo=mail-ie0-f170.google.com; Received: from mail-ie0-f170.google.com ([209.85.223.170]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Vad60-0002nu-7n for bitcoin-development@lists.sourceforge.net; Mon, 28 Oct 2013 03:02:25 +0000 Received: by mail-ie0-f170.google.com with SMTP id at1so10508217iec.15 for ; Sun, 27 Oct 2013 20:02:18 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.50.45.34 with SMTP id j2mr6902018igm.13.1382929338697; Sun, 27 Oct 2013 20:02:18 -0700 (PDT) Received: by 10.50.141.136 with HTTP; Sun, 27 Oct 2013 20:02:18 -0700 (PDT) Received: by 10.50.141.136 with HTTP; Sun, 27 Oct 2013 20:02:18 -0700 (PDT) In-Reply-To: References: <274a1888-276c-4aa6-a818-68f548fbe0fa@me.com> <9DCDB8F6-E3B2-426B-A41E-087E66B3821A@gmail.com> <526B45DB.2030200@jerviss.org> Date: Mon, 28 Oct 2013 04:02:18 +0100 Message-ID: From: Pieter Wuille To: Gavin Andresen Content-Type: multipart/alternative; boundary=089e0122f00cfb90cc04e9c45320 X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: doubleclick.net] -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 (pieter.wuille[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: 1Vad60-0002nu-7n Cc: Bitcoin Dev , kjj Subject: Re: [Bitcoin-development] Feedback requested: "reject" p2p message 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: Mon, 28 Oct 2013 03:02:25 -0000 --089e0122f00cfb90cc04e9c45320 Content-Type: text/plain; charset=ISO-8859-1 Categories that make sense to me: 1) protocol related problems 1.a) failed to deserialize transaction 2) core principle violations 2.a) script evaluation fail (only owner is allowed to spend) 2.b) outputs larger than inputs (no creation of new money) 2.c) outputs not found/already spent (no double spending) 3) policy rules 3.a) not standard 3.b) ... -- Pieter On Oct 27, 2013 11:54 PM, "Gavin Andresen" wrote: > RE: use HTTP-like status codes: > > Okey dokey, I'll add a one-byte machine-readable HTTP-like status code. > Unless y'all want a 32-bit status code. Or maybe a varint. Or a > three-character numeric string. I really and truly don't care, but I am > writing this code right now so whatever you want, decide quickly. > > If anybody has strong feelings about what the reject categories should be, > then please take the time to write a specific list, I can't read your > mind.... > > > -- > -- > Gavin Andresen > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most > from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > --089e0122f00cfb90cc04e9c45320 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Categories that make sense to me:
1) protocol related problems
1.a) failed to deserialize transaction
2) core principle violations
2.a) script evaluation fail (only owner is allowed to spend)
2.b) outputs larger than inputs (no creation of new money)
2.c) outputs not found/already spent (no double spending)
3) policy rules
3.a) not standard
3.b) ...

--
Pieter

On Oct 27, 2013 11:54 PM, "Gavin Andresen&q= uot; <gavinandresen@gmail.com= > wrote:
RE: use HTTP-like status codes:

Okey do= key, I'll add a one-byte machine-readable HTTP-like status code. Unless= y'all want a 32-bit status code. =A0Or maybe a varint. Or a three-char= acter numeric string. I really and truly don't care, but I am writing t= his code right now so whatever you want, decide quickly.

If anybody has strong feelings about what the reject ca= tegories should be, then please take the time to write a specific list, I c= an't read your mind....


--
--
Gavin Andresen

-----------------------------------------------------------------------= -------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most fr= om
the latest Intel processors and coprocessors. See abstracts and register &g= t;
http://pubads.g.doubleclick.net/gam= pad/clk?id=3D60135991&iu=3D/4140/ostg.clktrk
___________________= ____________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--089e0122f00cfb90cc04e9c45320--