Why xBPP uses Apache 2.0 and what it means for adopters.
xBPP is licensed under the Apache License 2.0. This applies to the protocol specification, reference implementation, and all materials in the VanarChain/vanar-xbpp repository.
xBPP governs financial transactions between AI agents. The choice of license has real implications for enterprise adoption, patent safety, and long-term ecosystem health. Apache 2.0 was selected after careful analysis of how open protocol standards are licensed across blockchain, Web3, and AI.
Apache 2.0 includes an explicit patent grant - every contributor automatically licenses their relevant patents to all users. If any contributor files a patent lawsuit against a user, they lose their license. MIT has no patent clause whatsoever. For a protocol that governs agent spending, this protection is essential.
Corporate legal teams prefer Apache 2.0's explicit IP clarity over MIT's ambiguity. The license is ASF-endorsed and the patent retaliation clause protects adopters. Enterprises building on xBPP - exchanges, payment processors, custodians - need this level of legal certainty.
Open protocol standards overwhelmingly use Apache 2.0. MIT is more common for SDKs and libraries.
| PROJECT | LICENSE | TYPE |
|---|---|---|
| OpenAPI Specification | Apache 2.0 | API Spec Standard |
| Hyperledger Projects | Apache 2.0 | Enterprise Blockchain |
| Polkadot / Substrate | GPL-3.0 + Apache 2.0 | L1 Protocol |
| CosmWasm | Apache 2.0 | Smart Contract VM |
| IPFS / libp2p | MIT + Apache 2.0 (dual) | P2P Protocol |
| OpenZeppelin Contracts | MIT | Solidity SDK |
| ElizaOS | MIT | AI Agent Framework |
| DIMENSION | MIT | APACHE 2.0 |
|---|---|---|
| Patent Grant | None | Explicit grant + retaliation clause |
| Attribution | Copyright notice only | Copyright + NOTICE file |
| Copyleft | No | No |
| Proprietary Forks | Allowed | Allowed |
| Enterprise Preference | Accepted | Preferred |
| Complexity | Minimal (~170 words) | Moderate (~4,500 words) |
| Common Use | SDKs, libraries, tools | Protocol specs, standards |
Apache 2.0 - patent protection and enterprise-grade IP clarity for the standard itself.
MIT or Apache 2.0 - either works for SDK implementations. MIT is more common for developer libraries and has lower friction. Dual licensing (MIT + Apache 2.0) is also viable, as used by IPFS/libp2p.