From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1TfcPy-0000wA-2h for bitcoin-development@lists.sourceforge.net; Mon, 03 Dec 2012 20:15:06 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.223.175 as permitted sender) client-ip=209.85.223.175; envelope-from=gmaxwell@gmail.com; helo=mail-ie0-f175.google.com; Received: from mail-ie0-f175.google.com ([209.85.223.175]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1TfcPv-0004oR-8t for bitcoin-development@lists.sourceforge.net; Mon, 03 Dec 2012 20:15:04 +0000 Received: by mail-ie0-f175.google.com with SMTP id qd14so4965568ieb.34 for ; Mon, 03 Dec 2012 12:14:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.237.103 with SMTP id vb7mr300548igc.29.1354565698064; Mon, 03 Dec 2012 12:14:58 -0800 (PST) Received: by 10.64.171.73 with HTTP; Mon, 3 Dec 2012 12:14:57 -0800 (PST) In-Reply-To: <50BD028F.3090206@petersson.at> References: <80648682-E34A-455E-B34A-6BC24652C3EA@ceptacle.com> <9CEDE4D4-3685-4F70-953E-15CC50A8AA3F@ceptacle.com> <50BCC28A.4060503@gmail.com> <50BD028F.3090206@petersson.at> Date: Mon, 3 Dec 2012 15:14:57 -0500 Message-ID: From: Gregory Maxwell To: Andreas Petersson Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gmaxwell[at]gmail.com) -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: 1TfcPv-0004oR-8t Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Chain dust mitigation: Demurrage based Chain Vacuuming 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, 03 Dec 2012 20:15:06 -0000 On Mon, Dec 3, 2012 at 2:50 PM, Andreas Petersson wr= ote: > These discussed features are all useful but quite contradicting. > > I imagine that a user will be able to switch between different coin > selection policies "minimize fees","max privacy","defragmentation","i > don't care" and even switch between them for individual sends. While thats a fine thing=E2=80=94 and a feature that I'd personally use=E2= =80=94 its not one that I expect to have a real measurable impact on the overall network behavior. For this kind of minutia especially, defaults are all powerful and must be the best they can be. :)