The work described below is all completed with the exception of the chain_state caching optimization (which is deferred).

I've also just completed work to implement two hard forks that Core integrated (without public discussion), and some work to generalize that and all other rule forks with testnet (which is just a single rule hard fork from mainnet). In doing this it became important to make the selection of rule forks a matter of configuration. I was going to do that in v4 but the new forks made it more immediate.

Your original/current question however appears to be limited to the main libbitcoin library. I'm not expecting any API changes there (apart from above with is in a PR not yet merged).

The remaining v3 work is primarily in blockchain. I need to reconnect the pools following the validation rewrite, and to finish an update in progress on initial block download (which is currently disabled). Apart from that there is a connection bug in network and a worker initialization race in server, both of which need to be resolved. I'm hopeful that this can be complete before the end of the year. Until that point the API can certainly change, but it should not change much in any area except blockchain.

e

-----Original Message-----
From: Libbitcoin [mailto:libbitcoin-bounces@lists.dyne.org] On Behalf Of Police Terror
Sent: Friday, November 25, 2016 2:02 AM
To: libbitcoin@???
Subject: Re: [Libbitcoin] v3 API stability

How's the progress on v3 API stability? I am ready to port the C and Python wrappers once we reach a stage where the API isn't changing too much.

Is there a rough timeline estimate for the new server release?

Eric Voskuil:
> It's close, I've got a couple of things left to move around. I'm going to flatten chain::script, inline script::program and script::number, rename message::block_message and message_transaction_message and I am about to merge a change of hash_number into compact number with a redesign of uint256_t (once I've completed tests). Phillip is also working on statsd integration into log via a new sink. That's all we've got planned. Prob another week before that all comes together. Potentially unforeseen changes as the need arises in completing node/server/bx for release, but I don't anticipate anything presently except a caching optimization in blockchain that would impact chain_state.
>
> e
>
>> On Nov 10, 2016, at 6:50 AM, Police Terror <PoliceTerror@???> wrote:
>>
>> So what's the status of the API in libbitcoin main library? Is it now
>> reaching the status of a stable API? Thanks.
>> _______________________________________________
>> Libbitcoin mailing list
>> Libbitcoin@???
>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/libbitcoin
_______________________________________________
Libbitcoin mailing list
Libbitcoin@???
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/libbitcoin