source avatarLegrand Rico 🐊

Share

I've been public about my conviction on @quipnetwork all week. I want to be equally public about what I got wrong early on, because I think intellectual honesty is the only thing that makes opinion accounts worth following. What I underestimated initially: 1. The post-quantum wallet story. I came in focused on the mining/PoUW angle. I underweighted how significant wrapping MetaMask and Ledger with quantum-resistant cosigners is. That's not a secondary feature it might be the higher-adoption product in the near term. 2. The compute marketplace angle. I thought of @quipnetwork as a blockchain project with quantum hardware. It's more accurate to say it's a quantum compute marketplace with a blockchain settlement layer. That reframe changes the entire valuation model. 3. The team's enterprise connections. A co-founder who came from Acorns, YC, and industrial engineering isn't just building for CT. The eventual buyers of optimization compute aren't crypto native. I underweighted how that changes the go-to-market. What I got right: the D-Wave validation story, the timeline urgency, and the PoUW mechanism. My opinion: updating your views publicly is more valuable to your audience than performing certainty you don't have. I was right on some things and wrong on others and I think the overall position still holds. What did you get wrong about Quip when you first looked at it?

No.0 picture
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.