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