Hi! This is a pinned post inviting you to check out Quint ✨
Quint is an executable specification language based on TLA+, and I have been working on it since 2022. You can use it to define and interact with algorithms/protocols in any abstraction level.
https://t.co/Ihlo3o9QjK
"There is no magical checkmark for software correctness."
At Bug Bash 2026, @bugarela made the case for chasing confidence instead, and showed why the AI era raises the stakes.
Here's a breakdown 🧵
Quint just got merged into GitHub Linguist. Starting with the next release, GitHub detects Quint as a language: syntax highlighting on .qnt files and Quint in the language stats bar.
One requirement to qualify: hundreds of repos outside the maintaining org. We're in!
Shout out to @beu5a for submitting and landing the PR.
We’ve raised $8.7M to bring clearing to the masses. Our new round was led by Blockchange to work on the most powerful idea in finance.
It’s not just about moving money faster & cheaper; it’s about moving less while doing more.
One of the most valuable things about Quint is not just that it finds bugs, it exposes behaviors engineers often don’t think to test.
The Turso team used Quint to model SQLite’s C API contracts, automatically generate traces, and replay them against the real implementation.
The result: 10+ bugs uncovered in SQLite while hardening Turso.
What’s especially compelling is the kind of behavior Quint explored systematically:
→ unexpected API call sequences
→ subtle state transitions
→ edge-case interactions
→ assumptions hidden inside implementation details
Instead of relying only on humans to imagine “what could go wrong?”, Quint explored the state space automatically and generated concrete counterexamples when contracts were violated.
Huge kudos to @Pavan4820, @Glcst, and the @tursodatabase team for the fantastic work.
Turso wants to match and surpass SQLite's reliability. When I say "surpass", usually ppl just look funny at me. But this is one such example: One of our OSS contributors have just found 10+ bugs in SQLite using validation he built for Turso. @pavan4820 used @quint_lang to build a formal model of the system and then executed its traces to find corner cases where SQLite deviated from the spec.
It is a great demonstration of how modern reliability tools, formal methods in particular, can lead to reliable systems and find *many* issues even on the most stable software on Earth.
Read more: https://t.co/Y6soBNs2PD
Four more things the Quint community built and shared. A production session lifecycle, a distributed app spec, formally verified RPG, and Quint Connect for Elixir.
I've been thinking so much about testing since this conference! If you think Quint can potentially help in your test suite, I'd love to hear about your needs, even if you don't really get what Quint is or can do.
And looking forward for the videos to be out so you can watch all of the amazing talks that I watched!
Three ways to drive testing from a Quint spec, depending on how much control your runtime gives you:
→ Model-Based Testing: replay traces from the model
→ Hybrid: model proposes the next action based on results from runtime
→ Trace Validation: capture from production, check it against the model
A peek at @bugarela's BugBash by @AntithesisHQ 2026 talk. Full video soon!
https://t.co/rDgp2WKSqz : "But for me personally, my entire growth as an engineer has been built on top of doing the things. It's why I have the skills I have today."
How come I don't see enough takes like this? Are most people learning by just looking at the docs?
I really love this blogpost from Zicklag! It's amazing how he reached, on his own, many of the same insights we had about @quint_lang.
People who think specs can be just markdown files don't understand how valuable the thinking we do while writing code is.
https://t.co/OygUPZVxfV
New podcast with @bugarela on @ColorsofWeb3pod talking spec-driven development and how we benefit from precision and executability of specs, especially in the AI era.
Why specs can't just be English and markdown↓