-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> The goal is to produce an easy-to-install Darkwallet server, so
> there's no point in packaging the version2 stuff if its server part
> isn't ready yet. It would make more sense to package version1 for now.

That basically is what I would have concluded, too.
So I think the primary goal for Pablo and me would now be to get the
version1 stack packaged so that it will preferably be available along
with darkwallet 1.0.



On Thu, 1 Jan 2015 23:39:48 -0800
William Swanson <swansontec@???> wrote:

> On Wed, Dec 31, 2014 at 5:22 PM, Eric Voskuil <eric@???> wrote:
> > No, I'm leaving that question to Amir. However, in previous discussions there was talk about adoption of the Obelisk protocol changes, which presupposes adoption of the blockchain work.
>
> Well, this question is really the crux of the matter.
>
> The goal is to produce an easy-to-install Darkwallet server, so
> there's no point in packaging the version2 stuff if its server part
> isn't ready yet. It would make more sense to package version1 for now.
>
> Even if the version2 server were ready today, there are still the
> slight protocol changes to deal with. This is really unfortunate,
> since we already have three projects that depend on the old protocol
> (AirBitz, OpenBaazar, and DarkWallet). This is not the time to be
> breaking compatibility! We at AirBitz certainly won't be able to
> deploy the version2 server, regardless of how nice it is, unless it
> has binary compatibility with the old one. We already have too many
> customers using our stuff in the wild.
>
> I wonder if there is some way to retain binary-compatibility between
> the version1 obelisk and version2 libbitcoin-server. For instance, I
> believe the "subscribe" message has changed to allow prefix
> subscriptions. We could fix this by bringing back the old,
> more-limited "subscribe" message, and putting the new, enhanced
> functionality in a "subscribe2" message. This might be worth looking
> into if the version2 libbitcoin-server is getting close to release.
>
> -William
> _______________________________________________
> Libbitcoin mailing list
> Libbitcoin@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/libbitcoin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUpugpAAoJEKB7Ks3Q6ZKiusgP/i3hTWGHidjHA8TFgAQzxeSg
RllB1sprxaep7adQChLA2EOCWaky7uIf2OlCDvc/+i39pUefeRzKrT9KHqkCFM1h
tuuHv6dEcZZJsiZk/RC3BDK+VChhEBKxc6jI5cNq45wg1l0mJxRFmNfY4o/JEWaw
GqAbmOVSyD2GOi7ztjU/3y5hd3K8LQIt2Py/tdNk6b08Fd5/5ZY1NfvrFqLK8cjY
LLFUQ9AHEvt4kbod9Jmx4MNwoLbyqg8u9jK5w1QlOYTZDW95SO5KG6lSGgUYmbEG
sa2+9A6Y7jUlOQ6TdkQ6ZZm2rL+OLb2DQeAYgVgta0/8rc0t80OsysbuJkBs8DtB
XKLQM4ulxgg0mNkDUU8fzPwMG+MXqueF8FRc49xxgwSys3UzzNOCewmEBQyfEGQ+
ggRs0ghjhQESTcCVjdAMPhTF6OhWjClSZln3VBL2wY62B+vKWKbXfEN1ki+6sMNe
z9CMTKCV2/txX6lQ/79jHkB7qf4wLfSkzLEuGHty7wuVR1iwqlXlHIXh3opPfigk
XJ9oo7GB/AdYcYnM29VjrYP/AL54WA3pghYuDS8pdjAjc8GQ8FUGcVl9vTftr0oS
hWQpg4V8HFWdq6QOYd2rLT4YiBZ4VF+gJ58UBxccQfoLCAMuwHdtedpOAETcv1nR
ICCAnsUqCLrTF+mAsHQP
=z0Wt
-----END PGP SIGNATURE-----