Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <odinn.cyberguerrilla@riseup.net>) id 1XiSNt-0001XS-Sm for bitcoin-development@lists.sourceforge.net; Sun, 26 Oct 2014 18:17:45 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of riseup.net designates 198.252.153.129 as permitted sender) client-ip=198.252.153.129; envelope-from=odinn.cyberguerrilla@riseup.net; helo=mx1.riseup.net; Received: from mx1.riseup.net ([198.252.153.129]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1XiSNs-0006K6-E6 for bitcoin-development@lists.sourceforge.net; Sun, 26 Oct 2014 18:17:45 +0000 Received: from plantcutter.riseup.net (plantcutter-pn.riseup.net [10.0.1.121]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 879B841A92; Sun, 26 Oct 2014 18:17:38 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: odinn.cyberguerrilla) with ESMTPSA id CADB222784 Message-ID: <544D3ABD.8080200@riseup.net> Date: Sun, 26 Oct 2014 18:17:33 +0000 From: odinn <odinn.cyberguerrilla@riseup.net> MIME-Version: 1.0 To: Wladimir <laanwj@gmail.com> References: <CA+s+GJA3-qK71TcUCYQ3xOdi+zgE_fB9N6NJkNBUDtWnA-0dcA@mail.gmail.com> <544CB6F2.4000200@riseup.net> <CA+s+GJANOtiqt1ypkZZeTQX=2k+y=F8uZhLJ69=6Li1GLhmYkQ@mail.gmail.com> In-Reply-To: <CA+s+GJANOtiqt1ypkZZeTQX=2k+y=F8uZhLJ69=6Li1GLhmYkQ@mail.gmail.com> Content-Type: text/plain; charset=utf-8 X-Virus-Scanned: clamav-milter 0.98.4 at mx1 X-Virus-Status: Clean Content-Transfer-Encoding: quoted-printable X-Spam-Score: -2.0 (--) 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 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [198.252.153.129 listed in list.dnswl.org] -0.0 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record -0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid 0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay lines X-Headers-End: 1XiSNs-0006K6-E6 Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> Subject: Re: [Bitcoin-development] Bitcoin Core 0.10 release schedule X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: <bitcoin-development.lists.sourceforge.net> List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> List-Post: <mailto:bitcoin-development@lists.sourceforge.net> List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> X-List-Received-Date: Sun, 26 Oct 2014 18:17:46 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Thanks, Followup question on https://github.com/bitcoin/bitcoin/pull/3959 : This describes current dust change handling: (gavinandresen) https://github.com/bitcoin/bitcoin/pull/3959/files#r13494256 Related Question: This describes how wallets would let you know a transaction is 'precious' with a flag -- (jgarzik) https://github.com/bitcoin/bitcoin/pull/3753#issuecomment-49464772 - -- however, it doesn't appear to be part of 0.10 anymore ~ what is it that would keep it from being incorporated into 0.10? (or was that addressed by a later commit?) Possibly also related (suggested dusting feature): https://github.com/bitcoin/bitcoin/issues/4079#issuecomment-41010593 Thanks in advance for your responses. Wladimir wrote: > On Sun, Oct 26, 2014 at 9:55 AM, odinn > <odinn.cyberguerrilla@riseup.net> wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 >>=20 >> Q., re. transaction fee changes / txconfirmtarget described at=20 >> https://github.com/bitcoin/bitcoin/blob/c8a25189bcb1381eddf46b9a9743ba= 48e929439e/doc/release-notes.md >> >> >>=20 (for Core 0.10) >>=20 >> ~ does this include the floating fees for 0.10 as described at=20 >> https://bitcoinfoundation.org/2014/07/floating-fees-for-0-10/ ? >>=20 >> thanks in advance for clarifications >=20 > Yes, floating/smart fees has been merged a while ago >=20 > - https://github.com/bitcoin/bitcoin/pull/3959 - > https://github.com/bitcoin/bitcoin/pull/4250 >=20 > Wladimir >=20 - --=20 http://abis.io ~ "a protocol concept to enable decentralization and expansion of a giving economy, and a new social good" https://keybase.io/odinn -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJUTTq8AAoJEGxwq/inSG8C8PYH/jrZIgecpEiwUYdRGT/dxvrE qHrlsJz8aPY/E/ojNE4MY4Con5seH2IRL+qg14pZvIQNJSipRYejh0BeqQ2YkfAF leEt8PlpblNqV0Ieq1VmdJK5wnF3crNZsNdPv73Z7UXplXo8sG+lYGENgC11s+wN QI29F3Kkrqk66aa6VmRbNzRIgL1JYfTkZLba9ApZNxJsugeOgmlOQw6+q5hgChKy lxN5s+P/wohH0n047ksYdiMnXbZwPL2scUEN87D74KYqYdCa6AB7vMkLETO2msSg ndC9ge8LfTODlEuFA9rQ8CgLAkwVWCaCbqph7iqTt6Cvdnqeo9XvlrpcB2B31hI=3D =3Dxn6P -----END PGP SIGNATURE-----