blockdev | Devcon Mumbai

Tim, I really respect you and your engineering team. You all are really smart, which is why it's hard to feel like any of this is in good faith: • A few weeks ago, we put out new numbers for proving costs. Members of your team replied to that tweet, so I know you guys saw it, and you could have cited those. xitter.gq/JacobEv3rly/status/184… We have since improved SP1's perf further and gotten to the numbers I reference in my most recent tweet (release coming soon)! • As @fede_intern mentioned, a blog post from 2 months ago in a space that moves very quickly is outdated (your team knows this very well): xitter.gq/fede_intern/status/185… He ran the stack himself and arrived at numbers an order of magnitude better than the above: xitter.gq/fede_intern/status/185… • Even when taking numbers from an outdated blog post, in the same table you cite, for Base we have numbers of 0.61 cents/tx. Why take the highest number out of all of them? • Our post doesn't reference numbers for "fixed proving cost" (it's simplified, for readability), so I'm not sure where that number came from at all. Unfortunately, it's totally off. In my reply, I simply wanted to clarify what costs we offer today, for any potential customers that might have the wrong info. Taking a step back, all of this Twitter back and forth is just a waste of time for both of our teams and the space. We're focused on actually deploying our stack and having people use it. The costs I cited in my reply are what we offer to real customers today. And they're rapidly getting better. Now that our info is out there, will try to not engage any further on this topic and focus on shipping, thanks.