fc-updates

Proposing a copyleft license for Snapchain 

We need to release Snapchain under an open source license for people to be able to use the code safely. We're proposing using GPL v3, which is a copy left license. 

This means that you can use, modify and redistribute it freely as long as any changes are also made public and available to all.

We've previously favored the MIT license for Farcaster repos, but Vitalik has a good argument for the use of copyleft here, which we largely agree with:

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

Wrapped Ether

We've previously favored the MIT license for Farcaster repos, but Vitalik has a good argument for the use of copyleft here, which we largely agree with: https://vitalik.eth.limo/general/2025/07/07/copyleft.html

If you have thoughts on open source licenses, please respond here:

If you have thoughts on open source licenses, please respond here: https://github.com/farcasterxyz/snapchain/pull/654

I'm still in favor of permissive:

1. Not all copyleft licenses are compatible between them. So, you may be able to use A||B but not A&&B.

2. Downstream from #1, you end up seeking legal assistance in order to build the thing you want to build and understand what is the proper license you have to use for the result using A&&B.

3. Permissive made much more sense when we actually distributed software. When it's all about services, it doesn't matter, does it?

Pls check the sub thread here: https://farcaster.xyz/vrypan.eth/0xd9bf7856

@shazow.eth and @deanpierce.eth share some good points too.

A doodler and computerer. I like permissive/permissionless open source, smart contracts, p2p systems, room-scale VR, and NixOS.

shazow.net

Currently: WhatsABI

Ethereum

Dad, geek, conversation liquidity provider. @l--o--l | @wdimapp

I've become a lot less opinionated on licencing now that all open source code gets thrown into the public code blender and can be trivially reimplemented in any language, or under any license 😁