Pinned Tweet
Sentios badges are now LIVE!
Show Sentios coverage anywhere.
Githug, explorers, wallets, dashboards, websites
The badge is now a hot link that opens to our active projects page on the Sentios website:
sentios.io/active-projects
Let the world know Sentios agents are continuously auditing your codebase on significant feature releases.
Want your project listed? Contact us to put Sentios on your codebase.
@bitsecai $TAO
NEW CLIENT ANNOUNCEMENT
We’re happy to announce that Beam is now covered by Sentios Continuous Coverage.
Beam has a live badge on their Github README linked to the Sentios Active Projects Page.
sentios.io/active-projects
Let everyone know your code has Continuous Coverage.
DM us to join the ranks.
@Bitsecai $TAO
“$200,000 bug found with $1000 in AI costs. That’s a huge difference!”
this first discovery is what has become @bitsecai continuous audit system
- interview with @TheStreet at @ExploitSummit
reqd the full interview covered by thestreet, yahoo finance, MSN and AOL
TheStreet - thestreet.com/crypto/innovat…
Yahoo! Finance - finance.yahoo.com/technology…
AOL - aol.com/articles/blockchains…
MSN - msn.com/en-us/news/other/how…
Apple News - apple.news/ANbiG2kdISZupiNEP…
Bitsec | Bittensor Subnet 60 τ retweeted
NEW: @bitsecai has launched Sentios badges: hot links for websites, explorers and dashboards that open its active-projects page. The badges make continuous audit coverage visible where a project is viewed.
xitter.cf/bitsecai/status/211082…
Sentios badges are now LIVE!
Show Sentios coverage anywhere.
Githug, explorers, wallets, dashboards, websites
The badge is now a hot link that opens to our active projects page on the Sentios website:
sentios.io/active-projects
Let the world know Sentios agents are continuously auditing your codebase on significant feature releases.
Want your project listed? Contact us to put Sentios on your codebase.
@bitsecai $TAO
"There are brilliant people from everywhere in the world looking to do something good." – John Yu, Bitsec founder / CEO
The secret sauce is Bittensor and its Incentive Mechanism.
We find these brilliant people and have them compete to build the best strategies comprised of multiple large models, agents, sub agents, prompts, memory management, context management, and tool use into a strategic harness.
These become models of sorts and only the best performing ones win.
Speaking of models, we’re moving toward a security audit future where we develop actual models, like a cluster of small expert auditing models with their own specialty features that in combination will be far more robust than not only large single models, but also the harness strategies that are cutting edge today.
We’re taking it there.
$TAO @bitsecai
PARTNERSHIP ANNOUNCEMENT
Bitsec is happy to announce our newest client: TWIF
The attitude regarding meme coins is sharply divided in web3 but we see this move as a signal that TWIF cares about its code base and that signing up for continuous coverage means they intend to be around for awhile. Kudos to the TWIF team.
Welcome to Sentios Continuous Coverage
@bitsecai @TaoWifHood $TAO
Catch Bitsec founder John Yu’s full Exploit ‘26 talk here:
stream.vidaio.io/vod.html?ta…
In the talk, John announces code audits for Bittensor subnet Incentive Mechanisms and goes over a couple example exploits.
He makes the case that it’s much more effective for a team dedicated to security audits to review code than the ones that developed it.
And of course, the obvious benefits of having continuous coverage for your code base.
Special thanks to the @vidaio_ team for their excellent LIVESTREAM and VOD coverage of the event.
@bitsecai $TAO
Did you miss any of the great presentations at @ExploitSummit ?
Or do you have any talks you’d like to watch again?
Great news. Our LIVESTREAM website has them all.
stream.vidaio.io/vod.html
Video On Demand (VOD) allows you to watch all the action.
At the top of the page, look for the “Watch again” tab.
Filter by Day 1 or 2, and which stage the talk was given.
Optionally, use the search bar on the right to search by speaker, subnet, or talk title.
Every talk will have subtitles in English, French, Spanish, Chinese, German, and Italian, prepared after the event with our most accurate models, plus the key takeaways and highlights. Dubbed voices are being added talk by talk as well. Choose your language in the top right pull-down list. Currently, all videos have English and French subtitles, and many have all 6 available. (The rest coming as soon as we get back home)
Open any talk for the full presentations, and see Key Takeaways and Highlights as well as other events from that day on the right. Download the subtitles/transcript in multiple languages.
We appreciate our community and welcome any feedback regarding your user experience for both the LIVESTREAM and the WATCH AGAIN services. Please let us know if there are any features you’d like to see.
Happy viewing!
@vidaio_ bittensor:native
The Sentios Badge
Ever more powerful LLM models have made the hunt for code exploits a race for token spend: who can be the first to throw the most tokens at a fresh codebase.
You’re a hacker. You’ve got your models and your search strategies. You’re hunting for fresh codebase. You search Github looking for possibilities and you come across a project with the Sentios Badge.
What does that mean? A skilled team has already been here, spent tokens, found and fixed vulnerabilities, and continues to do so with each fresh code release. The question becomes, “Do I want to try to spend even more tokens looking for less valuable exploit opportunities or move on?”
The Sentios Badge is a Proof of Spend.
This code is covered, continuously.
Not only a deterrent to hackers, but a signal to users and investors the mission critical technology you depend on is secure.
@bitsecai $TAO
Can miners find the answers before doing the work?
@yubrew of @bitsecai shows how Bitsec flagged exposed confirmation seeds in @heydittoai's incentive mechanism. He says Ditto fixed the reported issues within days, and explains why seed timing matters.
you can see an example of sentios badge on bitsec's subnet repo github.com/Bitsec-AI/sandbox
“...it’s difficult to build and go into a security mindset and find these different dishonest miner attacks.”
John Yu explains why a dedicated team focused on security with developed strategies performs better security checks than the building team.
In this clip from his talk at Exploit 2026, he gives an example of a specific way Incentive Mechanisms can be gamed and how to prevent it.
The point is to raise awareness about different attacks, close the gaps, and direct more of the emissions to reward the desired outcomes.
Contact us if you’d like us to audit your IM for maximum efficiency.
@bitsecai $TAO
Can miners find the answers before doing the work?
@yubrew of @bitsecai shows how Bitsec flagged exposed confirmation seeds in @heydittoai's incentive mechanism. He says Ditto fixed the reported issues within days, and explains why seed timing matters.
Bitsec | Bittensor Subnet 60 τ retweeted
Can miners find the answers before doing the work?
@yubrew of @bitsecai shows how Bitsec flagged exposed confirmation seeds in @heydittoai's incentive mechanism. He says Ditto fixed the reported issues within days, and explains why seed timing matters.
Sentios already audits beyond smart contracts. Now we're pointing it at something native to Bittensor.
Incentive Mechanisms.
Sentios now audits subnet IMs continuously, so every change to the mechanism gets tested before miners get the chance to game it.
What better way to celebrate Exploit than to offer audits for something core to our own ecosystem? Great products get built in Bittensor. They should benefit Bittensor.
DM us to get your IM covered.
@bitsecai $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
We found a critical remote code execution vulnerability in an open source project. Reported and patched.
If an attacker gets basic access that way, they can run any command directly on the machine with no way to stop them.
Full compromise. Machine and everything on it.
Same tooling we built for smart contract audits at Bitsec. Expands to find vulnerabilities in general codebases as well.
Want proof? Here it is.















