Eman

[Eman @Emanriles]

@0xLuciferCore Make sense

[Eman @Emanriles]

@LilyNguyen1906 @m477lander But i wonder how many protocols actually have this assumption buried in production

[Eman @Emanriles]

@m477lander The real question is how many more hidden 400ms assumptions are still sitting in production ?

[Eman @Emanriles]

Every module can pass its own test and the full system can still fail

[Eman @Emanriles]

@oxfordox8742382 @m477lander Safer can still hurt users

[Eman @Emanriles]

@ohmy_missmolly @m477lander Thats why the boring edge cases deserve attention too

[Eman @Emanriles]

@hesaysdanielle @m477lander Old assumptions always come back for payment 😂

[Eman @Emanriles]

@narinderr @m477lander Speed is basically a stress test for everything around it

[Eman @Emanriles]

@Dylan_Hardaway @m477lander Speed exposes old shortcuts pretty fast
one forgotten constant can ruin the whole u

[Eman @Emanriles]

@Chloe_Kaia_ @m477lander Somewhere an old timeout is getting nervous

[Eman @Emanriles]

@Chloe_Kaia_ @m477lander 400ms is basically the ghost of solana past now

[Eman @Emanriles]

@Tokyo599560 @m477lander Thats gonna be interesting 😂

[Eman @Emanriles]

@m477lander Every time they make slots faster some random assumption in protocols just dies, this is that moment

[Matt lander @m477lander]

Solana won my network poll, so I took the hint and spent some time looking through the latest network changes.

the obvious headline is SIMD-0525: the 350ms slot target is now live. Faster slots and the shorter blockhash window have already been covered. I wanted to see what this changes higher up the stack, so I went through the proposal, docs and public protocol code.

What I hadn't seen discussed much is what happens one layer above it:: the chain clock moved, while some app logic still reads time through the old 400ms assumption

The SIMD warns about this directly. anything measured in slots now covers less real time, and programs that treat slot distance as wall-clock time may need an update Static SDK constants also stay unchanged for now.

@switchboardxyz's Solana tutorial gave me the cleanest example:

`.max_age(30)` rejects data older than 30 slots and describes that as roughly 12 seconds..

At the 350ms target, those 30 slots are nominally 10.5 seconds. At 200ms, 6 seconds.

Same code. Same parameter. Different risk policy.

Switchboard is doing exactly what it says. If you meant 30 slots, the rule still does exactly what you asked. If you meant roughly 12 seconds, you don't have 12 seconds anymore.

I checked @kamino's public kLend code and found the same handoff. The path starts with Switchboard's last update slot, uses DEFAULT_MS_PER_SLOT to manufacture a timestamp, then checks that against a max age in seconds. the SDK constant is still 400ms, so against the 350ms target the nominal age comes out 14.3% higher.

At the 200ms target, it would read as 2x older than it really is. A 30-second policy would trip after roughly 15 seconds of wall time, without anyone changing the policy.

The deeper problem isn't the number 400. It's that a risk check silently translates between two clocks. And this is why "just use `Clock::unix_timestamp`" isn't the whole fix. the current time is in seconds, but this oracle update starts in slots Both sides of the check still need to speak the same clock

No exploit claim here. The bias is conservative: valid data can look stale sooner. This is an availability risk, not a direct value-extraction path. The important part is that the handoff exists in real code.

This is exactly why I keep banging on about the full execution path. The network can report the right slot. The oracle can report the right update. The check can run exactly as written. the final behavior still changes at the handoff between protocol time and real time.

This actually makes me like @Solana's staged rollout more. A faster clock is good infra, and every gate gives builders a real checkpoint to catch these assumptions before 200ms.

Before the next gate, grep for every `max_age`, staleness check, cooldown, retry and timeout expressed in slots. Did you mean slots or seconds?

@bw_solana, should apps stop converting between the two entirely: slots for protocol ordering, timestamped data for wall-clock policy? And if so, what should an oracle expose so apps never have to manufacture that timestamp themselves?

SIMD-0525:
https://t.co/GRZMxPDlti

Switchboard example:
https://t.co/HYhQE7X4Yw

SDK constant:
https://t.co/QtzmoQQItE

Public code example:
https://t.co/EFJ2bXV7NB
https://t.co/xm1gTjQEPc

[Eman @Emanriles]

@GaRam37554749 @m477lander This makes the threat model much easier to understand

[Eman @Emanriles]

@trinitymorgan23 @m477lander Keep the authority outside the model