BOSL or MIT - Orchard

[zooko]

@aristarchus

Thoughts on BOSL exceptions for all projects building on top of Zcash? I’m thinking of wallets, zecpages, free2z etc.

I agree it’s also very important that BOSL not prevent friendly forks.

Aristarchus, I don’t understand your question. The two things you mention here are what I intended by these two parts in my post:

First, on the topic of BOSL exceptions for all projects (wallets, exchanges, zecpages, etc.) supporting Zcash — by which I mean Zcash-the-coin (ZEC), not just the Zcash-the-technology or the Zcash-the-network, unless their work thereby also supports Zcash-the-coin:

@zooko

This conversation makes me think it would be good for ECC to issue a blanket exception for everyone to be able to use our Orchard code to support Zcash (ZEC) without having to BOSL their other code. We’ll work on that, because I think it would help. However, in general the data points we have so far indicate that this concern isn’t currently a big deal.

Second, on the topic of friendly forks:

@zooko

So, I’m going to ask our lawyers how to craft a blanket exception which gives all users the necessary legal permissions to create their own Future Friendly Fork of the Zcash blockchain, meaning that all current ZEC holders before the fork become holders of the new coin, in the same proportions, and the same proportion of the total monetary base, as before, but not to give blanket permission for source-code-forkers who just want to clone the tech to launch their own blockchain without BOSL’ing their own codebase.

Does that answer your questions?