On Mon, Oct 27, 2014 at 7:24 AM, Melvin Carvalho
wrote:
> Do you think it would a reasonable idea to put down some thoughts and
> proposals in a BIP?
It would certainly be nice to start with a document that reflects the
new REST interface. That makes a good starting point for further
discussion.
On 27 October 2014 08:49, Wladimir wrote:
> On Sun, Oct 26, 2014 at 12:44 PM, Melvin Carvalho
> wrote:
>
> > Firstly, apologies in coming in late to the conversation. As I am also
> > working on a REST API for electronic coins. Some questions:
> >
> > 1. Is there a BIP, or some other doc (e.g.
On Sun, Oct 26, 2014 at 12:44 PM, Melvin Carvalho
wrote:
> Firstly, apologies in coming in late to the conversation. As I am also
> working on a REST API for electronic coins. Some questions:
>
> 1. Is there a BIP, or some other doc (e.g. gist), outlining the REST output
> e.g. the response for
On Sun, Oct 26, 2014 at 9:53 AM, Luke Dashjr wrote:
> On Sunday, October 26, 2014 7:57:12 AM Wladimir wrote:
>> Let me know if there is anything else you think is ready (and not too
>> risky) to be in 0.10.
>
> At the very least, we need:
> #5106 Bugfix: submitblock: Use a temporary CValidationS
-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 wo
On 26 October 2014 08:57, Wladimir wrote:
> Now that headers-first is merged it would be good to do a 0.10 release
> soon. Not *too* soon as a major code change like that takes some time
> to pan out, but I'd like to propose the following:
>
> - November 18: split off 0.10 branch, translation mes
On Sun, Oct 26, 2014 at 9:55 AM, odinn 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)
>
> ~ doe
-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
http
On Sunday, October 26, 2014 7:57:12 AM Wladimir wrote:
> Let me know if there is anything else you think is ready (and not too
> risky) to be in 0.10.
At the very least, we need:
#5106 Bugfix: submitblock: Use a temporary CValidationState to determine ...
#5103 CreateNewBlock and miner_tests:
Now that headers-first is merged it would be good to do a 0.10 release
soon. Not *too* soon as a major code change like that takes some time
to pan out, but I'd like to propose the following:
- November 18: split off 0.10 branch, translation message and feature freeze
- December 1: release 10.0rc1
10 matches
Mail list logo
