From: odinn <odinn.cyberguerrilla@riseup•net>
To: Wladimir <laanwj@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Core 0.10 release schedule
Date: Sun, 26 Oct 2014 18:17:33 +0000 [thread overview]
Message-ID: <544D3ABD.8080200@riseup.net> (raw)
In-Reply-To: <CA+s+GJANOtiqt1ypkZZeTQX=2k+y=F8uZhLJ69=6Li1GLhmYkQ@mail.gmail.com>
-----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
>>
>> Q., re. transaction fee changes / txconfirmtarget described at
>> https://github.com/bitcoin/bitcoin/blob/c8a25189bcb1381eddf46b9a9743ba48e929439e/doc/release-notes.md
>>
>>
>>
(for Core 0.10)
>>
>> ~ does this include the floating fees for 0.10 as described at
>> https://bitcoinfoundation.org/2014/07/floating-fees-for-0-10/ ?
>>
>> thanks in advance for clarifications
>
> Yes, floating/smart fees has been merged a while ago
>
> - https://github.com/bitcoin/bitcoin/pull/3959 -
> https://github.com/bitcoin/bitcoin/pull/4250
>
> Wladimir
>
- --
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=
=xn6P
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-10-26 18:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 7:57 Wladimir
2014-10-26 8:53 ` Luke Dashjr
2014-10-27 7:31 ` Wladimir
2014-10-26 8:55 ` odinn
2014-10-26 9:10 ` Wladimir
2014-10-26 18:17 ` odinn [this message]
2014-10-26 11:44 ` Melvin Carvalho
2014-10-27 7:49 ` Wladimir
2014-10-27 11:24 ` Melvin Carvalho
2014-10-27 11:37 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=544D3ABD.8080200@riseup.net \
--to=odinn.cyberguerrilla@riseup$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=laanwj@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox