If a web3 product deploys smart contracts for users, but those contracts are not open-source, there's zero accountability.

Neither customers nor the broader public can verify whether there have been any bugs in those contracts.

Opensea's contract always intrigued me.. would this count as closed source?

Co-Founder at sablier.com, and open-source developer. I have a broad range of interests, including longevity, epistemology, physics, and psychology.

👨‍💻 Building web2 meets web3 analytics @ arcxanalytics.com
⛓️

If it's not in a GitHub repo and it's not verified, then yes

Opensea's contract always intrigued me.. would this count as closed source? https://etherscan.io/token/0x495f947276749Ce646f68AC8c248420045cb7b5e

There’s a difference between open-source and verified, published contract code. Open-source needs license. 

But totally agree with your point. 💯

How can a smart contract not be open source? Like technically how is that possible