Software licenses for DeFi (FOSS, BSL, and co) are a prominent example of DeFi's latest clash between ideals and realities. Flop from the Collective expanded on the topic in our newest article, a must-read for all DeFi projects

In DeFi's early days, the consensus was to use fully open-source. However, DeFi staple protocols (Uniswap, Aave, Liquity...) recently opted for BSL

The business source license (BSL) is a standard software license that sits in the middle between Free & open-source software (FOSS) and traditional proprietary licenses.

The source code is published openly and can be fully verified ('source available'), but for a given period, cannot be used for commercial purposes. However, projects can give out additional use grants or additional commercial licenses.

Once this period has expired, the software automatically transitions to a recognized open-source license

The most discussed point is whether BSL is aligned with the core values of DeFi or not.

Some people think BSL is "anti-DeFi", as many DeFi projects that implement BSL are themselves built on resources provided by the open-source community in the first place, and undermine innovation.

Others approve the use of BSL as it allows alternative monetization for a protocol, and incentivizes teams to build genuinely new DeFi solutions rather than "killing" the original protocol

However, there are other perspectives to be considered beyond the DeFi-values argument. Think alternative biz models, product scaling under BSL, DeFi regulation, etc.

It is yet to be seen what impact BSL will ultimately have on DeFi, and whether it may lead to a more long-term and sustainable (albeit probably slower) pace of innovation in DeFi.

Full article: deficollective.org/blog/software-licenses-for-defi/

deficollective.org/blog/tdc-july-2024-report/
The monthly report for July is out; here are the highlights:

Revenues

• Revenues are up 42.66% compared to June ⏫
• The Collective secured a healthy surplus of 82.97%, which will be recycled into supporting mission-critical projects ⏫

Impact
The liquidity management strategy changed course slightly on @velodromefi and @aerodromefi during July.

The Collective is moving away from concentrated liquidity positions and got back to legacy volatile or stableswap pools, while providing supplementary voting support to the CL pools of these positions.

As a result, we provide full-range liquidity and the most active liquidity providers get more yields.

Impact Dashboard
In July, we also launched the Impact page on the website, which enables our community members to easily track the liquidity growth support we provide

Full details below 👇

@liquityprotocol will be published under a BUSL

That means Liquity v2 will still be source available on the GitHub repo and verified onchain, just like major protocols have done (@uniswap, @aave, @morpho....) Any project that wishes to fork v2 will first need to receive a license to do so.

We believe that BUSL is a net positive for Liquity

35 Liquity V1 forks were launched, and most of them were “wild” forks. In other words, they were deployed without prior communication with Liquity

The wild forks had a minimal will for collaboration, which ultimately penalized users

BUSL is a relevant way to promote the development of "friendly forks", which actively collaborate with the original protocol

Liquity V1's friendliest fork is Gravita, this is the kind of fork Liquity needs to highlight decentralized stablecoins, and BUSL will help in building this way

In addition, the collective will be happy to support Liquity V2’s friendly forks willing to add value for genuine DeFi

GM Ants 🐜, the Collective keeps supporting @liquityprotocol

with these two $LUSD / $USDC CL pools this week

- On Base with Aerodrome : <aerodrome.finance/deposit?token0=0x368181499736d0c0CC614DBB145E2EC1AC86b8c6&token1=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913&type=1>

- On Optimism with Velodrome : <velodrome.finance/deposit?token0=0x0b2C639c533813f4Aa9D7837CAf62653d097Ff85&token1=0xc40F949F8a4e094D1b49a23ea9241D289B7b2819&type=1>