Namit

Great live

[Namit @Namit3394]

@death_jokes @m477lander Yeah, pure slots is cleaner. Devs can convert to seconds themselves if they need to.

[Namit @Namit3394]

@realjoejordan1 @m477lander Slots and second both are different
As i think

[Namit @Namit3394]

@leoemma @m477lander Valid data need to be properly validated
Rejecting early will affect users

[Namit @Namit3394]

@kns_ma @m477lander How checks are measured there

[Namit @Namit3394]

@Canan752 @m477lander Faster slots expose all those close conversation is a twist

[Namit @Namit3394]

@fakinghcrold @m477lander That was good explanation fr

[Namit @Namit3394]

@m477lander kinda wild how a network change can quietly affect liquidations without anyone updating the apps.

[Namit @Namit3394]

@Menks20 @m477lander That was really a good tek, we need more like this who work well on app layer rather then paper

[Namit @Namit3394]

@NativeSoundGod @m477lander yo the 30 slot example hits different, policy stays the same but real time just got shorter. how many more protocols got these hidden assumptions baked in? risky af for us traders

[Namit @Namit3394]

@m477lander faster slots quietly tighten every slot-based max age. Same code, shorter real window - liquidations can hit earlier.

[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

[Namit @Namit3394]

@Melanson_2 @m477lander So we had users to verify against the original intent.

[Namit @Namit3394]

@JoseSilvaAC @m477lander User approval via signature is must

[Namit @Namit3394]

@we_dette @m477lander Independent layer policy is solving it fr.

[Namit @Namit3394]

@VuyaniVinqishe @m477lander Letting the AI’s words just greenlight a transfer is asking for it. Keep the chat and the wallet completely separate.

[Namit @Namit3394]

@eenbright @m477lander Mixing those two is how you end up with language becoming a spend key.

[Namit @Namit3394]

@Cody_Pluck @m477lander

[Namit @Namit3394]

@Fortunate_0100 @m477lander Vulnerability was in the authorization is the real flaw.

[Namit @Namit3394]

@ThawahlaH @m477lander Agreed. The absence of an independent check for actual user-signed intent was the critical gap

[Namit @Namit3394]

@m477lander No keys stolen and still lost $155k. That’s the scary part.