OpenSea CEO responds to Vanity Fair controversy: wife developing independently, team will focus on long-term growth

BTC-1,94%

Gate News, March 18 — OpenSea CEO Devin Finzer responded to the controversy reported by Vanity Fair on the X platform. He stated that despite repeated pessimism from the outside that “OpenSea is finished,” the team continues to develop, and crypto startups can be profitable. Since its founding, OpenSea has always focused on creating products that users truly love, and this core direction will not change. Devin Finzer also pointed out that his partner has been involved in Bitcoin since 2011, developing independently and supporting his career over the years, emphasizing the importance of mutual growth. He criticized Vanity Fair’s coverage for serious misinterpretations of the crypto industry and company narrative. He further explained that the crypto industry is still in its early stages and widely misunderstood, with future potential to seamlessly integrate into culture and daily life. This is also one of OpenSea’s key visions. He emphasized that creating meaningful products requires long-term commitment, enduring misunderstandings, and continuous iteration. Previously, Vanity Fair described Devin Finzer’s wife, Yu-Chi Lyra Kuo, as his “product mommy,” who provided guidance during his entrepreneurial journey.

View Original
Disclaimer: The information on this page may come from third parties and does not represent the views or opinions of Gate. The content displayed on this page is for reference only and does not constitute any financial, investment, or legal advice. Gate does not guarantee the accuracy or completeness of the information and shall not be liable for any losses arising from the use of this information. Virtual asset investments carry high risks and are subject to significant price volatility. You may lose all of your invested principal. Please fully understand the relevant risks and make prudent decisions based on your own financial situation and risk tolerance. For details, please refer to Disclaimer.
Comment
0/400
No comments