Komms Subnet miners relay, index and anchor every message and hold every file, so product use is the subnet's workload. Validators score it with probes.
Bittensor subnet 27
The network behind Komms.
Komms is Bittensor mainnet subnet 27. It follows the Kaspa event stream, verifies encrypted storage and serves every Komms workspace. Miners are scored on accuracy and uptime. Validators keep them honest.
Architecture
Order on Kaspa. Content on Hippius. Service on Bittensor.
Content is encrypted before it leaves the client. Only hashes and commitments touch the chain. Tap or click any component.
Animated packets show data flow. Tap or click a component for detail.
For investors
Due diligence, in one place
A subnet with a real product on top. Here's what it does, how it earns demand, and where it stands.
Fact sheet
- Products
- Komms Business · Komms Community
- Pricing
- Free plans · paid from $60/yr or $5.99/mo
- Network
- Bittensor mainnet
- Netuid
- 27 (mainnet) · 503 (testnet)
- Ledger
- Kaspa · Testnet 10
- Identity
- Kaspa covenant · user-held keys
- Storage
- Hippius · SN75
- Crypto
- MLS RFC 9420 · X-Wing for DMs
- Status
- Subnet 27 on mainnet · app on testnet
Miners front the Kaspa fee for each sponsored anchor. At least a quarter of subscription revenue buys subnet 27 alpha, which repays them at cost. Emissions are a separate reward.
Plans are paid in USD on the web. Customer revenue, emissions and treasury activity are three separate ledgers, and emissions are never reported as revenue.
MLS end-to-end encryption, with X-Wing hybrid post-quantum key exchange for direct messages. Signatures stay classical, and we say so.
Kaspa for ordering and identity, Bittensor for incentives, Hippius for storage, with interop to the Kasia messenger.
Public docs, including what the team still runs alone. The protocol spec and decision log are kept with the code.
Cryptography
Keys never leave the device. Neither does plaintext.
IETF standard with forward secrecy and post-compromise security as members join and leave.
Post-quantum key exchange combined with a classical curve, so both have to break.
Cryptography from a library with machine-checked proofs of correctness.
MLS commits follow Kaspa ordering, with rollback on reorg and key zeroisation at finality.
Per-device keys tie to the user's Kaspa identity. Unlock with passkeys or hardware keys.
Bodies and attachments are encrypted blobs on Hippius. Kaspa stores commitments, never content.
Miners
Run a Komms miner
We'll be releasing the miner onboarding process soon!
We're onboarding a small first group of miners to test the setup end to end before we publish the guide. Leave your email and we'll tell you as soon as it opens.
Network stats
Subnet status at a glance
● Example dataRegistered UIDs42 validators · 2 miners
Kaspa DAA score541,826,300~10 blocks per second
Median response182 mssigned query round-trip
Indexer lag0.4 sbehind virtual chain tip
| UID | Role | Hotkey | Trust | Incentive | Last response | Status |
|---|---|---|---|---|---|---|
| 0 | Validator | 5Hxx…a1F2 | 0.98 | n/a | n/a | Online |
| 1 | Validator | 5Hxx…c7Q9 | 0.97 | n/a | n/a | Online |
| 2 | Miner | 5Fxx…k3W8 | 0.95 | 0.71 | 164 ms | Online |
| 3 | Miner | 5Gxx…p0T4 | 0.00 | 0.00 | n/a | Syncing |
Validators
Keep the network honest
Validators check miners against the canonical Kaspa ordering and Hippius storage, then set weights every epoch.
Send known-answer queries against canonical Kaspa ordering: DAA ranges and checkpoint_ids.
Check response signatures and storage proofs for the encrypted blobs on Hippius.
Weight miners on correctness, freshness, latency and uptime.
Call set_weights each epoch, and sign entitlements such as workspace plans and create codes.
Join the network behind Komms.
Mine, validate, or talk to the team.