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 1Uznie-0005xI-5b for bitcoin-development@lists.sourceforge.net; Thu, 18 Jul 2013 12:54:04 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bitpay.com designates 74.125.82.50 as permitted sender) client-ip=74.125.82.50; envelope-from=jgarzik@bitpay.com; helo=mail-wg0-f50.google.com; Received: from mail-wg0-f50.google.com ([74.125.82.50]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Uznic-0008TS-2G for bitcoin-development@lists.sourceforge.net; Thu, 18 Jul 2013 12:54:04 +0000 Received: by mail-wg0-f50.google.com with SMTP id k14so2867683wgh.29 for ; Thu, 18 Jul 2013 05:53:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=dgRH/2JxezsSm+CHnOhUCWDpJ+ePT+Iy3zXGpYoT9YQ=; b=diiIAzDfZRQzzLa0KPR+3OkgzgsUVG0If8YYJBEYVbkhmu1+BZpZyasfaX4Iv0p8Vx 1nKcr7cASW0izPFgMmWJ8PFvI3zGiJw3aRKTzTGGaHeAb6aDo3gk0A5r9R5tCfvT95H3 k4zhexrcZx38UaeIe7hs2nUzS4k/9ZfWwnBXNZmsX87dQvDwEgqUTY5ZTJ6iDNO3lLhH Ww+aWF1cca6X4uoXBJ2Xp+U+W3+v7te4WG2ZhQ+A3+FJzYZcYSAWzFYmKalvu7nkCZiu 51YW7DOgWJVWMrlvyAg8HK0sghAltbiX2e2o/otI5kqjZe/ZtXOpeUm+WtzA6tzgPG82 XmBg== MIME-Version: 1.0 X-Received: by 10.180.74.162 with SMTP id u2mr19059627wiv.36.1374152035591; Thu, 18 Jul 2013 05:53:55 -0700 (PDT) Received: by 10.194.242.36 with HTTP; Thu, 18 Jul 2013 05:53:55 -0700 (PDT) In-Reply-To: <20130718111353.GA11385@savin> References: <20130718111353.GA11385@savin> Date: Thu, 18 Jul 2013 08:53:55 -0400 Message-ID: From: Jeff Garzik To: Peter Todd Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQnyBtHguqe9v7BvyTIRW9fOVq//kbe0wU5d8PNP6Won7tuee9WV5U8pmPRQG8inQsgUTEkj 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: 1Uznic-0008TS-2G Cc: bitcoin-development@lists.sourceforge.net, Jeremy Spilman Subject: Re: [Bitcoin-development] Anti DoS for tx replacement 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: Thu, 18 Jul 2013 12:54:04 -0000 On Thu, Jul 18, 2013 at 7:13 AM, Peter Todd wrote: > Note that with OP_DEPTH we can remove the small chance of the payee > vanishing and putting the funds in limbo: What are the costs, benefits, and risks associated with scripts no longer being stateless, as OP_DEPTH would seem to introduce? -- Jeff Garzik Senior Software Engineer and open source evangelist BitPay, Inc. https://bitpay.com/