Can spending $1k to $5k / mo with @bitsecai save companies from $100k or more in catastrophic exploits? We are entering Phase 1. Here's the short summary of where we are and a taste of where things are going. We have 3 companies in the pipeline with a growing backlog of companies we still need to meet. Each new potential client we want to knock them out with a simple message: "Your codebase has a couple exploits ready to fix, have it for free whether you want to join or not. Subscribe and we'll spend more resources to do a thorough end to end exploration with our AI security army." We are exploring distribution channels, where closing one deal allows us to reach many ideal clients. EOY goal is 50 company subscriptions, 1 enterprise subscription. What this means is building a book of revenue between $50k to $250k MRR, building good reputation with paying clients, which can offset the current upfront inference cost per client to show them sample exploits. We need to add key personnel to the Bitsec team as we grow to service more clients. Phase 2 post coming soon. $Bittensor $TAO

We originally designed our auditing around smart contract code. But it was built to reach further, and it does. Our founder John Yu will share one application that applies specifically to Bittensor IMs at Exploit 2026. Subnet founders and team devs, you’ll want to tune in for this one. See you all there. @bitsecai bittensor:native

An underflow bug let attackers credit their own balance far past what they'd actually deposited, on any chain running Cosmos EVM. Cosmos Labs opened a fix for it in May. They called it resolved. It wasn't. Four chains got hit by the same bug in August. No warning reached the teams running it, but a warning wouldn't have changed much. The fix underneath it didn't hold. The team that wrote the fix was the only one checking whether it worked. Independent auditing exists for exactly this gap. Not only do we put fresh eyes on code, we reverify. @bitsecai $TAO

Why did Bitsec outperform Fable at finding security exploits? On the @twistartups podcast, John explained that models have their own personas. Some are good at finding certain bugs and weaker at others. Bitsec combines a buffet of models with specialized agents and rigorous benchmarking, and the combination outperforms one “superhuman” model. That’s how SN60 found 160+ vulnerabilities in a client codebase, including 5 criticals and 10 highs that Fable missed. ⤵️ bittensor:native @bitsecai

"We’re focused on the high value teams that understand the value of security. Teams that already pay twenty thousand to one hundred thousand dollars for security audits." - John Yu That’s the sweet spot for us now. We can offer a block of four audits for less than the price they normally pay for one. And results have consistently shown we achieve better results. It’s just the beginning but we’re here to turn the tides on what it means to have audited code. @bitsecai $TAO

Bitsec announces our newest client. Talisman Sentios audited their new wallet extension update and wallet app. Welcome to Continuous Auditing @bitsecai $TAO @wearetalisman

"Instead of just having one security audit a year, or every couple of years, have something that’s continuously checking your code base." John announces sentios.io going live and explains to @Jason our core continuous auditing thesis, ingrained in everything we do. We’re here to change auditing as we know it. If you write code and vulnerabilities have serious consequences, reach out to us and let’s get your codebase continuously covered. sentios.io @bitsecai $TAO

For those of you who might have missed the announcement on TWIST: the new Bitsec site is LIVE. Continuous coverage, Sentios, and the pricing model behind it, no longer scattered across posts and threads. It’s now all in one place. Take a look and let us know what you think. sentios.io @bitsecai $TAO

Whooo!!!!

Subnet 60 on Bittensor speaking on one of the biggest tech podcasts on earth. Huuuuge! $TAO

We will be on TWIST today. Live in 5 minutes @Jason piped.video/live/Ynzj1JjoHzE

The more I see about @ExploitSummit, the more it feels like the best place to experience $TAO beyond the timeline. The session I’m looking forward to the most is the live security review of other subnets by @Bitsecai. Their approach to security, including finding ways subnet incentives can be gamed, goes straight at one of the most important questions in #Bittensor: are subnets actually rewarding the right behaviour? I think more people should be talking about SN60 in general, and I suspect this live demo will get a lot more people paying attention. Much more interesting than just another slide deck!

Two separate benchmarks published this week landed on the same conclusion. One tested AI agents against real black-box hacking challenges. The other ran AI security products against a shared vulnerability set. Both found the same thing: raw frontier model strength wasn't what separated the winners. Better multi-model methodology was, and didn't just perform better, it cost significantly less. It's why Bitsec was built around multiple models from the start. @bitsecai $TAO

Continuous coverage has always been the need. Price was the obstacle. At traditional audit rates, checking a codebase more than once gets expensive fast, so teams settle for one audit and move on. Now audit costs are mostly inference, not engineer-hours. That's what makes checking code more than once actually affordable. But affordable doesn’t automatically make it continuous. So we designed our pricing audits to be sold in blocks of four, triggered by changes in the code. Exhaust the block, reorder. Continuity isn’t optional. It’s the standard. @Bitsecai $TAO

Once-a-year audits are an illusion of safety in a world where attack vectors evolve every day. Bittensor enables Bitsec to continuously uncover code vulnerabilities. $TAO

This was from a conversation where @yubrew jumped on a call with the Beyond Finance community. They are a very special group. Some were familiar, some were totally unaware of @bitsecai, All are very warm and friendly, asking many good questions. If anyone's been vibecoding lately, the next step is ensuring your code is secure. That it doesn't leak secrets, hackers can not take over, etc. Highly engaged, very thoughtful members asking a lot of great questions. Thanks Louise for the warm welcome and help in putting this together.

A lending protocol is only worth its security. Mentat Lend already went through two full audit rounds with @burraSec, one of the top auditors in crypto. Every finding is public in our docs, with their fix commits. Market parameters are frozen at deployment. Logic changes pass through a public 48h timelock. Now @bitsecai adds continuous audits on top. Keeping your funds safe is our absolute priority.

Let’s go @MentatLend_

The main one is smart contract risk. Here is how we keep it as low as possible: Design. Mentat Lend derives from Morpho, the lending architecture securing billions on Ethereum. Its core contracts have never been exploited. Audit. Two audit rounds with @burraSec. Findings and fixes are public in our documentation, all closed before launch. And now @bitsecai runs continuous audits on Mentat Lend. Security is our first priority.