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-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1TfV5B-0000gg-N3 for bitcoin-development@lists.sourceforge.net; Mon, 03 Dec 2012 12:25:09 +0000 X-ACL-Warn: Received: from 2508ds5-oebr.1.fullrate.dk ([90.184.5.129] helo=mail.ceptacle.com) by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1TfV55-0000MI-V0 for bitcoin-development@lists.sourceforge.net; Mon, 03 Dec 2012 12:25:09 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.ceptacle.com (Postfix) with ESMTP id EF45C270E471 for ; Mon, 3 Dec 2012 13:24:57 +0100 (CET) X-Virus-Scanned: amavisd-new at ceptacle.com Received: from mail.ceptacle.com ([127.0.0.1]) by localhost (server.ceptacle.private [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4V4+pJVcDrWN for ; Mon, 3 Dec 2012 13:24:57 +0100 (CET) Received: from [109.105.106.201] (unknown [109.105.106.201]) by mail.ceptacle.com (Postfix) with ESMTPSA id B7A5B270E464 for ; Mon, 3 Dec 2012 13:24:57 +0100 (CET) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Michael Gronager In-Reply-To: Date: Mon, 3 Dec 2012 13:24:56 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <9CEDE4D4-3685-4F70-953E-15CC50A8AA3F@ceptacle.com> References: <80648682-E34A-455E-B34A-6BC24652C3EA@ceptacle.com> To: Bitcoin Dev X-Mailer: Apple Mail (2.1499) X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1TfV55-0000MI-V0 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 12:25:09 -0000 > If this were a proposal at the time Bitcoin was created, I would = definitely be in favor, but I feel we can't just change such a policy = right now - it's not what people signed up for when they started using = the system. I also see no way to implement this without a hard fork, = which would require planning at least 1-2 years in advance (imho). By = that time, the economic landscape of Bitcoin may be vastly different, = and either dust spam will have killed it, or we will have found another = solution already. Bitcoin aka the blockchain is defined by the majority of the miners. = This is what people have signed up to imo. A scheme that a) is of = benefit for us all and b) is also of economical benefit for the miners, = will likely be accepted quite fast - especially now when the bounty was = just halved... I also fear that there is a lot of BTCs that is = effectively un-owned and it could even drive Satoshi to use some of his = BTCs ;) > Personally, I think the best solution is to change the mining policy = to prioritize (and perhaps favor for free relay/inclusion) transactions = that reduce the number of UTXO's. Agree - initially (and possibly in parallel) this would be a nice path = to follow - it could be done solely by adjusting the relay fee: = Transactions that increases the # UTXOs pay extra, those that reduce it = pay less (symmetrical around a minimum fee). So in other words we 'tax' = increasing the size of the UTXOs. No matter how it is done - as long as a client is not punished for = getting rid of dust, and clients are rewritten to do this automatically = we could re-evaluate after a some time - but currently the number of = UTXOs is growing rapidly.=20 /M >=20 > --=20 > Pieter > =20 > = --------------------------------------------------------------------------= ---- > Keep yourself connected to Go Parallel:=20 > BUILD Helping you discover the best ways to construct your parallel = projects. > = http://goparallel.sourceforge.net_________________________________________= ______ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development