Decentralized Intelligence | Bittensor ΟΟ | Privacy β’ Freedom β’ Community .β‘β‘
U.K
Joined February 2021
- Tweets5.3K
- Following371
- Followers506
- Likes18.1K
ππ¦π―π΄π°π³πππ°πΈ ΟΟ retweeted
I got a chance to catch up @KommsApp and the team and man was I impresses with developer. Here @argonmining gives 5 strong use cases for @KommsApp
Make sure to follow for more bittensor:native updates!
Wowπ, another must read from @TensiaFDN
Thank you for all the work you do.
Unsung heroes of Bittensor π―
ππ
People haven't clocked onto what @cascade_sn91 are truly up to.
They build their own forecasting model + they provide forecasting inference.
Have you ever tried to get inference for forecasts? The models are easy to download, but only if you locally host. Not everyone can do that.
Cascade provide that inference via their platform (Ephemeris).
1 API key unlocks 7 frontier models. They've got an MCP now, too.
With @heydittoai, users can forecast credits using Cascade's platform, built directly into the app so you never need to leave.
With @numinous_ai, Cascade help improve forecasts for future relationships, and past confirmed relationships help feed Cascade's currently training model.
@TargonCompute helped them run forecasting experiments so they could build a stronger network.
@lium_io has become one of Cascade's compute providers for miners.
They're making #Bittensor into the home of forecasting.
ππ¦π―π΄π°π³πππ°πΈ ΟΟ retweeted
Your data lives in Cloud A.
Your compute lives in Cloud B.
Your AI workload is stuck in the middle asking for directions.
Beam connects storage, apps and AI compute with open, programmable data transport.
ππ¦π―π΄π°π³πππ°πΈ ΟΟ retweeted
Bittensor bittensor:native ecosystem is on fire. Revenue run rate is growing 40% month over month
$35M β $50M β $70M.
Another month, another 40% MoM increase in annualized revenue across the Bittensor ecosystem.
When we published the first SubConnect Bittensor Revenue Index, we estimated that revenue-generating subnets were collectively doing around $35M in annualized revenue.
A month later, that number had grown to approximately $50M.
Today, we're estimating $70M in annualized revenue.
That's a 100% increase in just two months.
Of course, annualized revenue is a snapshot, and the real challenge is sustaining that growth while improving margins and reducing dependence on emissions, but the direction is clear.
Bittensor is growing from the inside out.
And our expectation of $100M+ in annualized revenue by the end of 2026 is getting closer.
We'll continue tracking the numbers every month through the SubConnect Bittensor Revenue Index.
ππ¦π―π΄π°π³πππ°πΈ ΟΟ retweeted
It genuinely doesnβt get easier than bittensor:native .
People will look back at this as the easiest and most undervalued investment. Contingent on $BTC's success, I see this inevitably booming once it gains attention alongside BTC price action.
Donβt let your emotions dictate your decisions! Buy #bittensor
$35M β $50M β $70M.
Another month, another 40% MoM increase in annualized revenue across the Bittensor ecosystem.
When we published the first SubConnect Bittensor Revenue Index, we estimated that revenue-generating subnets were collectively doing around $35M in annualized revenue.
A month later, that number had grown to approximately $50M.
Today, we're estimating $70M in annualized revenue.
That's a 100% increase in just two months.
Of course, annualized revenue is a snapshot, and the real challenge is sustaining that growth while improving margins and reducing dependence on emissions, but the direction is clear.
Bittensor is growing from the inside out.
And our expectation of $100M+ in annualized revenue by the end of 2026 is getting closer.
We'll continue tracking the numbers every month through the SubConnect Bittensor Revenue Index.
π
No More Buts series continues:
βBut Switching chat tools is always a nightmare; data migration, training the team, people just wonβt move.β
Most tools make switching painful because they own your data and charge you more the bigger you get.
Komms is the opposite: your identity lives on Kaspa (not in our database), history is exportable and verifiable, and pricing is one flat fee per workspace, not per person.
Start free, invite the whole team (and clients) without the bill exploding, and keep a full copy of everything if you ever leave. Less lock-in usually means less resistance.
$TAO $KAS
ππ¦π―π΄π°π³πππ°πΈ ΟΟ retweeted
Welcome to the start of our new "No more Buts" series.
In sales the best salesperson is the one that can understand hesitation and objections and let people keep asking the "but" questions until there are no "buts" left to ask. At that point it becomes a no brainer to try something new. So now we are dedicating a series to pre-empt all of your "But" questions and answer them for you!
βBut itβs crypto, my team doesnβt want to set up wallets, buy tokens, or learn a new system just to chat.β
Fair. Thatβs exactly why Komms keeps all of that in the background. You sign in with a passkey (like your phone or laptop already does). No wallet knowledge needed. No KAS or TAO to buy. Plans are paid by card like any other software.
The Kaspa/Bittensor side just handles identity, ordering, and incentives so the network stays independent.
Your team uses it like Slack or Discord. The crypto stays out of the way
$TAO $KAS
Most "secure" messaging apps give you a binary: encrypt everything and accept terrible UX, or use Slack and hand your conversations to a company that can read them, lose them, or lock you out.
@KommsApp is Bittensor SN27, and it's trying to collapse that choice.
Decentralisation that actually means something
Three networks share the work, and none of them is a company server:
π£ @kaspaunchained a proof-of-work blockchain that records the order of messages and your identity. Anyone can verify what was sent and when. Nobody can quietly rewrite it.
π’ @Hippius_cloud (SN75) β stores the encrypted message content and files. The storage network never sees plaintext.
π @KommsApp SN27 β pays independent miners to relay, index and anchor every message. Validators probe them for accuracy, freshness and uptime, and set weights every epoch.
The design point: no single operator can change, censor or lose the record. If Komms itself disappeared tomorrow, your identity lives on Kaspa and your history is exportable in a verifiable format. That's not a roadmap feature. That's the architecture.
Encryption that's post-quantum, not marketing
- Group chats and channels use MLS (RFC 9420) the IETF standard with forward secrecy and post-compromise security as members join and leave
- Direct messages add X-Wing hybrid KEM (ML-KEM-768 + X25519) post-quantum and classical combined, so both have to break
- Primitives from libcrux machine-checked proofs of correctness, not just "audited"
- Content is encrypted on your device before it leaves it. Only hashes and commitments touch the chain. Kaspa stores ordering, never content
- Sign-in is passkeys, not passwords. Nothing to phish, nothing to leak
They're honest about scope too: signatures stay classical (not post-quantum), and they say so. Public channels in community servers are readable by design. Private channels, DMs and group chats are end-to-end encrypted. No ambiguity.
The team
Founded by brothers Tom Hutchinson (@TomHutchinson27) and Chris Hutchinson (@Chris_Hutch7), with lead developer Ashton (@argonmining).
UK-based. In crypto since 2018-19. Chris co-founded Blockchain Banter X Spaces. Tom co-hosts Rock The Kaspa on YouTube and has a substantial business track record. They've worked together across businesses for 15+ years. Ashton builds infrastructure in the Kaspa ecosystem and leads the Komms codebase (GitHub: Komms-protocol/komms-docs).
Komms acquired SN27 on October 23, 2026 the subnet was previously SILX AI's "Orion" data project. The on-chain identity was updated to Komms; the registration and owner coldkey are unchanged.
Why this matters for free speech and privacy
The real threat to private communication isn't bad encryption it's centralisation of the infrastructure layer. When one company holds your messages, your identity, and your history, a subpoena, a policy change, or a breach can expose everything at once.
Komms splits that power across three independent networks. Your identity isn't in a Komms database it's on Kaspa, bound to device keys you hold. Your messages aren't on one company's servers they're encrypted blobs on Hippius, served by competing miners who can't read them. The ordering is provable on-chain. The history is exportable. There's no lock-in by design.
And critically: users don't need to touch crypto. Passkey sign-in. No wallet required. No KAS, no TAO, no per-seat fees. One flat price per workspace.
Cypherpunk principles β self-sovereign identity, encryption by default, verifiable history, no trusted third party β wrapped in something a business can actually adopt without friction.
That's the bet.
Public beta targeted for late November. Docs and whitepaper at komms.app/docs.
πππ
Now Live: Beamπ« x @huggingfaceπ€.
Nearly 3 million public models. 1 million datasets. Hugging Face has become a major hub for open AI, with its dataset count growing from 711,000 to 1 million in the first seven months of 2026.
That scale creates a practical challenge: getting massive datasets to the compute that needs them.
Beam will enable teams to move large datasets into and out of Hugging Face through its distributed network, connecting the data behind AI to the infrastructure that puts it to work.
ππ¦π―π΄π°π³πππ°πΈ ΟΟ retweeted
ππ¦π―π΄π°π³πππ°πΈ ΟΟ retweeted
Now Live: Your OpenClaw agent can use Beam.
Thatβs over tens of thousands of agent skills and projects at the ready.
Whatβs the first thing youβd ask it to move?
The skill is live on ClawHub.
ππ¦π―π΄π°π³πππ°πΈ ΟΟ retweeted
AI needs data to move. It also needs applications that can act when it arrives.
Now Live: Beamβs Bittensor EVM integration puts data transfer and Room delivery receipts onchain, where smart contracts and agentic workflows can read them. Opening up a world of possibility for cross-chain bandwidth.
Hereβs why that matters. π§΅
Amazing work π₯π₯π₯π₯
Moving forward π₯π₯
We will win together assembling & combining the best skills of the ecosystem to fuel the global Bittensor Growth.
This is @kusanagi_vntrs vision and we will lead by exemple.
Today, with our @taodotcom friends, we integrate their bridge technology in @taoswap_org to promote more seamless investment in TAO & Subnets
Kudos to @Rapido_ai and @VictorVL_EN from @kusanagi_vntrs team
Moving onβ @Gylez @askyoav
Let's go! @KommsApp SN27 not only have a great product they are shouting from the rooftops about it.π₯π₯π₯
Not only that they are combining the best tech in crypto to get the desired outcome they need.
Very exciting times indeed.
Great team β
Great products β
Great commsβ
Most apps say "we won't harvest your data" and point to their terms. That's a promise, and promises can be changed. Komms is built so the promise isn't needed. The architecture decides what we can see, not a policy page.
Start on your device. Private messages and files are encrypted and signed locally, before anything leaves. Your keys and decryption stay with you. Komms never holds the keys, so we can't read private content even if we wanted to.
Next, where the data goes. Encrypted content is stored on Hippius, #Bittensor Subnet 75, as ciphertext. The storage network holds data it can't open. Nobody in the chain of custody has the means to read it.
#Kaspa records the order, timestamps and references. Never message content. Plaintext never goes on-chain. What's public is proof that something was sent and when, not what it said.
Then the indexing layer. The Komms subnet is built to index activity and power search, with an open network of operators scored by validators. It works on references and encrypted data, not on your private plaintext.
Public channels are different, by design. They're readable by anyone, like an open forum, with verifiable authorship and tamper-proof ordering. Private stays encrypted. Public stays readable. The line is enforced by keys, not by policy.
Compare "trust us" with "verify it." A policy can change after you've signed up. A system where Komms holds no decryption keys and plaintext never touches the chain can't be quietly reconfigured to read your private messages.
This also means no single company can switch you off or lock you out of your history. Your business owns its data, not a platform. Decentralisation is what makes the privacy claim hold up.
The point: a privacy promise is only as strong as the architecture behind it. Komms is built so that not harvesting your data is a property of the system, not a clause in our terms. Communication you can verify.
$TAO $KAS
ππ¦π―π΄π°π³πππ°πΈ ΟΟ retweeted
π The Decentralized G Suite Killer is Here! πβ‘
βKaspa ($KAS) and Bittensor ($TAO) have officially joined forces to power Kommsβa post-quantum secure, sovereign alternative to Slack, Zoom, and Google Workspace! ππΌ
βHere is why this collaboration is massive:
ββ‘ Powered by Kaspa & Bittensor: Fast on-chain verification meets heavy off-chain computation.
βπΈ Massive Cost Savings: Offers enterprise-grade features up to 98% cheaper than traditional centralized platforms.
βπ‘οΈ True Data Sovereignty: Zero single points of failure, post-quantum encryption, and full data ownershipβno tracking or selling your info!
βπ Ecosystem Fuel: Drives Kaspa node growth & transaction fees, while allocating 25% of top-line revenue to Bittensor alpha token buybacks! ππ₯
π¬ youtu.be/xdBCVXbtemY?is=7qE2β¦
#Komms #Bittensor #Kaspa #TAO #KAS #SN27 #DataSovereignty
