Are any web3 builders here open sourcing their UI/Frontend layers?

The pro open-sourcing case seems aligned philosophically and for ecosystem development but the potential security / phishing issues are a strong deterrent. (Just Google a famous dapp to see the phishing site ads)

ceo, proofofplay.gg; building onchain games starting with piratenation.game. 

Prev: co-creator FarmVille; managing partner, Presence Capital

andyjagoe.com // denim.vc // tokenizing real-world assets / onchain venture funds @fairmint

Yeah this needs to be sorted at the wallet level. Similar to the green lock icon (and DNS mis-spelling / phishing checks) in browsers.

maybe wallets need a feature to verify that the app being used is running on a valid URL? could be a smart contract app registry or built into ENS

not sure how you decentralize if you don't open source

this is true for the web. it's kind of like locking your door, it's not gonna stop a determined thief but def makes it less trivial to break-in.

For native-code clients, it's a much larger deterrent to creating phishable builds especially on Android

Not open-sourcing does nothing to prevent phishing attacks...

The very nature of the web means it's trivial to copy/paste/modify any frontend code, regardless of it being obscured/minified.

Personally, I think not open-sourcing in web3 is a bigger risk.

Before: @StanfordGSB, Kubernetes @Google, @Blackstone

I think that if you're trying to create a protocol. Open sourcing the UI lowers the friction to and encourages more client exploration. IMO it's kind of the point of a lot of these decentralized experiences. 

Let a thousand UI/UX flowers bloom.

That's interesting -- traditionally open sourcing infra (rather than UI) is the classic GTM for developers. Do think the effects are different for web3?