Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wgolv-0002bb-Bt for bitcoin-development@lists.sourceforge.net; Sun, 04 May 2014 05:15:31 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.212.174 as permitted sender) client-ip=209.85.212.174; envelope-from=jgarzik@bitpay.com; helo=mail-wi0-f174.google.com; Received: from mail-wi0-f174.google.com ([209.85.212.174]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wgolu-0003Pj-EX for bitcoin-development@lists.sourceforge.net; Sun, 04 May 2014 05:15:31 +0000 Received: by mail-wi0-f174.google.com with SMTP id r20so779464wiv.7 for ; Sat, 03 May 2014 22:15:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=RXvO7J0vywPb+LnVWPAyJld2uSsQrKb+1UgHUQoKyZU=; b=HMM9i0+1uIimRMbtS0mRQRlkR65wBl4uPhXxWlXZ80C4PAdQ1N1lTnZaO3tmsDBNVb 0LDT7NeAjEwOTM7k0NAzMAsanp+A5Mj8LnWXRz5rpZPv4XiFpBVsUJV7PzRgy85pFtyF SJZyujmpxns7Q3q29Voab6a/suZM+2BhC8bR3ixiM/+Tycfzi+r7BWlcjAmmLrnrhqwX pZdSWSx/M8H6ELwuxPwcCGfBzwrdClDv6jMtDhOdFYvZI6XAitu8qCPnDTlVNFwwLLsr amXtUqTvveszjaleEbynJNQ7wvZ90H608phCjtksFRFM2cwpHkpOoK0SwMiGnwuz0m8J GjnA== X-Gm-Message-State: ALoCoQmQXLhMfbPhQFZiokgY2LimeGG1tVJE900lPpJeD9pEcSwD3OKgF3TVxopU/76gfYcnT1je X-Received: by 10.180.93.101 with SMTP id ct5mr10128606wib.23.1399180523945; Sat, 03 May 2014 22:15:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.243.138 with HTTP; Sat, 3 May 2014 22:15:03 -0700 (PDT) In-Reply-To: References: From: Jeff Garzik Date: Sun, 4 May 2014 01:15:03 -0400 Message-ID: To: Flavien Charlon Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.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 SPF_PASS SPF: sender matches SPF record -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: 1Wgolu-0003Pj-EX Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Bug with handing of OP_RETURN? 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: Sun, 04 May 2014 05:15:31 -0000 On Sat, May 3, 2014 at 2:04 PM, Flavien Charlon wrote: > Outputs are above dust, inputs are not spent. OP_RETURN is supposed to be > standard in 0.9.1 and the data is well below 40 bytes, so why is this being > rejected? The carried data must all be contained within one pushdata. -- Jeff Garzik Bitcoin core developer and open source evangelist BitPay, Inc. https://bitpay.com/