Quilibrium

I expect this to get a little bit of controversy so I wanted to start the discussion now:

Quilibrium’s codebase needs a license. We want to choose one that prevents Amazon grift — AWS should not be allowed to deploy an alt net either as a service or to power their own infra, but they are free to join the mainnet.

BDFL of Quilibrium, Eng @ Farcaster, ex-Coinbase, always opinionated, never hydrated

/quilibrium

Some thoughts:

- Amazon will be able to build a Q-like protocol once you publish the source, regardless of the license. The only way to prevent that would be with patents.

- Imho a better play is to make it irrelevant whether Amazon launches a private competitor.

1/n

OSS + Rust. My goal in life is the ability to stop thinking at will

- So to fight off Amazon, the best play is imo to make sure there is a lot of good stuff on Q before they’d launch their competitor. And to achieve that it helps being as permissive with licensing as possible.

3/n

Side note: 

The way AWS builds products is that they observe what their customers do manually at scale and then build managed solutions for those use cases. This implies that by the time they’d launch a Q competitor, Q would have to be popular and protected by network effects.

4/n

They could ofc change their doctrine, but few non-founder lead bigcos ever do.

5/5

- Data composability through tokenization produces incredibly strong network effects. It lets devs bootstrap apps with existing data which brings more apps which brings more users which produces more data which brings more devs…

2/n