Skip to content

Relicense to dual MIT OR Apache-2.0 #78

Description

@notmandatory

This licensing scheme gives maximum flexibility for downstream users. Apache 2.0 includes an explicit patent grant and retaliation clause, which protects users from patent litigation. With dual MIT and Apache-2.0 licensing, the user may choose any of these two at their discretion.

This is a well established standard in the rust-bitcoin and Rust ecosystems:

In order to relicense we would need explicit approval from all contributors which have made meaningful contributions.

If you're on the below list and agree with this change please add a comment with

I hereby re-license my previous contributions to bdk-tx under Apache 2.0 in addition to the existing MIT license.

Metadata

Metadata

Assignees

Labels

choreNon-coding tasks

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions