Solana moves fast.
ZK on Solana moves… vibes faster.
Everyone talks about compression, light clients, zkVMs, proving pipelines.
Formal methods? Mostly absent where it actually matters.
So you end up with this beautiful illusion:
high throughput
low latency
“verified proofs”
…sitting on top of undefined invariants.
ZK without formal methods is just expensive ambiguity.
And Solana right now is dangerously close to optimizing the ambiguity layer.
A protocol isn’t your happy path.
It’s what still holds under adversarial execution.
If you can’t define invariants over all state transitions, you’re not designing a protocol. You’re describing intent.
“Exploits” are just valid executions you failed to model.
Rijndael (@rot13maxi)
TLA+의 작동 원리를 설명하는 트윗입니다. 전체 시스템을 상태 기계로 모델링하고, 변수와 상태를 업데이트하는 액션으로 시스템 동작을 표현한다는 점을 강조합니다. 다음에 취할 수 있는 액션은 현재 상태에 따라 달라지며, TLA+의 흥미로운 기능 중 하나로 액션이 (트윗에서 이어지지 않지만) 특정 선택이나 결정을 할 수 있음을 언급합니다. 형식적 사양 및 검증 관점에서 유용한 설명입니다.

@KingBootoshi The way TLA+ works is you write up your whole system as a state machine. There are basically variables and then actions that update those variables. The actions that can be taken next depend on the current state. One of the (many) cool things about tla+ is an action can pick a