Had a chat with one of the Aptos engineers who's basically in charge of the blocktime settings.
Told him straight up — we've been hovering around 70ms for way too long, and honestly, I'm running dry on things to talk about if this doesn't improve soon.
He actually apologized and dropped some news: they're targeting 50ms by next week. Turns out the Thanksgiving holiday weekend threw things off track a bit.
Not gonna lie, it's wild that you can literally just... talk to the person who tweaks these numbers. That's the beauty of working in this space — direct line to the engineers making it happen.
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
13 Likes
Reward
13
5
Repost
Share
Comment
0/400
StableGenius
· 11h ago
lmao "running dry on things to talk about" — the most honest thing i've heard all week. so they're basically admitting 70ms was just... vibes? and thanksgiving broke the blockchain infrastructure? 🤦 50ms next week sounds like every other "we promise bro" deadline tbh. let's see if it actually ships.
Reply0
TeaTimeTrader
· 12h ago
50ms? Is this guy for real? Feels like Aptos is still slacking a bit with this speed.
Having some insider info is better than nothing. Confronting the engineers directly really does feel satisfying.
70 to 50? Alright, let's wait and see. Just hope they don't miss the deadline again.
Why does it feel like every week there's a "surprise coming next week"? I just want to know when it'll actually be faster than Ethereum.
This guy's ability to make connections is impressive, I have to say.
View OriginalReply0
OnchainHolmes
· 12-05 17:52
70ms has been stuck for so long, feels like Aptos is kind of disappointing.
View OriginalReply0
ProposalManiac
· 12-05 17:41
50ms? Sounds like a promise made to rush progress, but it's hard to say what will actually happen upon delivery.
---
Direct communication is indeed convenient, but if the governance process is bypassed like this, who will oversee things in the long run?
---
Blaming it on Thanksgiving... sounds like the engineering side's progress management also needs optimization.
---
The key is, how did this 50ms target get included in an official proposal? Otherwise, it'll just be another verbal promise next time.
---
Being able to directly ask engineers to change parameters—this needs to be handled carefully. Too much power is being centralized.
---
From 70 to 50, results in one week? Maybe we should look at the test data before boasting.
---
Interesting, if this kind of decision-making process were made transparent on-chain, I'd be even more convinced.
---
Projects rushed to meet deadlines often hide problems. If blocktime is sped up, can stability keep up?
View OriginalReply0
PumpAnalyst
· 12-05 17:40
Will 50ms be up and running next week? Bro, if there's a delay, I'll short it right away. Don't say I didn't warn you.
Had a chat with one of the Aptos engineers who's basically in charge of the blocktime settings.
Told him straight up — we've been hovering around 70ms for way too long, and honestly, I'm running dry on things to talk about if this doesn't improve soon.
He actually apologized and dropped some news: they're targeting 50ms by next week. Turns out the Thanksgiving holiday weekend threw things off track a bit.
Not gonna lie, it's wild that you can literally just... talk to the person who tweaks these numbers. That's the beauty of working in this space — direct line to the engineers making it happen.