$ICP
StableSnapshot Window: 2026-07-20 13:10 UTC · ← Back to Crypto Overview
Social Momentum Summary
Total Engagement - Comments: 5, Retweets: 0, Likes: 5, Impressions: 4447
Verbatim Community Citations & Social Evidence 1 source posts analyzed
Answering Hard Questions: Our Protocol Why did the chain take so long to build, and looking back, was the delay worth it? [Spoken audio]: Why did the chain take so long to build and looking back, what's the delay worth there? Good question. I think first it's because we had overly ambitious goals. We were shooting for some certain performance threshold. The way we approached it was we internally had a few small teams working on individual optimizations to compound on each other to hit the performance goal. I think in hindsight it would be much better if we shipped the baseline plus the ability for us to launch future upgrades without any downtime. And if we did that, I think we could have shipped the chain much sooner. It would be not as performant as it is today, but we can upgrade. We can spring, but we didn't do that. I think another point is just objectively, it's actually pretty complicated of a job to launch a chain. In addition to us internally testing the chain well, we also have to coordinate before the launch with apps, of course, and with infrastructure partners. It's usually most of the time a three-way coordination game between app and the infra We have to ask the app. Hey, what are the infra pieces that would like to use and then talk to those infra pieces and even Work on commercial deals between the three parties. Then of course the token the launch of the token is another job I think neither Shui or nor I slept for 10 days leading up to the TG These kind of tasks just compounding on each other and just I think we're spread it to thing one final thing is I think in terms of our overall GTM strategy, we plan a lot of linear dependency. That's the way I would call it. So basically one step, depending on each other, happening perfectly on time to perfect execution. I think us betting a lot of things on basically every single step, executing perfectly as planned, it's too idealistic and also means that all the uncertainties from each individual step, they just compound. I think the lesson we learned is there's no limit to scope cutting. You can always cut scope. It's the lesson that we learned the hard way. And I think the other part of question was, was the delay worth it? I would say we gained something. The code base is something that I think every single engineer in the team is very proud of. The bad thing is we cost a lot of headache for our builders because of the repeated delays. I would say that what we lost was way more than what we gained.
