Wowπ, another must read from @TensiaFDN
Thank you for all the work you do.
Unsung heroes of Bittensor π―
Thank you for all the work you do.
Unsung heroes of Bittensor π―
View quoted post on X
ππ¦π―π΄π°π³πππ°πΈ ΟΟ
Verified account This account is verified. Learn more@Tensor_Flow_
Decentralized Intelligence | Bittensor ΟΟ |
Privacy β’ Freedom β’ Community .β‘β‘
Privacy β’ Freedom β’ Community .β‘β‘
371 Following 504 Followers 5.3K Posts
Latest posts 5
ππ
People haven't clocked onto what @cascade_sn91 are truly up to.View quoted post on X
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.
π
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 $KASView quoted post on X
π«‘
View quoted post on X
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.
@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.
komms.app Komms Docs Guides for Komms Business and Komms Community: accounts, messaging, files, security, plans and the network behind Komms.