# Introducing the taostats blog Product news, Bittensor research and practical guides from the people who build taostats. Here is what you will find, and how to follow along. _Source: https://beta.taostats.io/blog/introducing-the-taostats-blog_ _Author: taostats Team, Editorial_ _Published: 2026-10-06_ _Category: Annonces_ _Tags: Announcement, Bittensor, taostats_ Bittensor moves quickly. Subnets launch and fade, emissions shift with every epoch, and the tooling around the network changes almost weekly. taostats exists to make that activity legible, and today we are adding a place to explain it: the taostats blog. ## Why a blog A dashboard is good at answering "what is happening right now". It is less good at answering "why does it look like that" or "what should I do about it". Most of the questions we hear fall into that second group: - Why did I receive less alpha than the price implied? - What does a validator's VTrust actually tell me? - How do I pull this data into my own tools? Each of those deserves a proper explanation, with diagrams, worked examples and links to the underlying data. A blog lets us write that down once and point people at it, instead of repeating ourselves. ## What you will find here Posts are grouped into five categories, and you can filter the archive by any of them: - **Announcements.** What shipped, what changed and what is coming next. - **Product.** How taostats features work, and why they are built the way they are. - **Research.** Analysis of subnets, emissions, validators and the mechanics underneath, from the taostats Research team. - **Guides.** Step-by-step walkthroughs, from reading a subnet page to calling the API. - **Ecosystem.** Notes on what is happening around the network. > [!TIP] > **Read it your way** > > Every post has a plain-markdown twin: add `.md` to its address and you get the same text without the page chrome, which is handy for note-taking tools and AI assistants. There is also an [RSS feed](https://beta.taostats.io/blog/rss.xml) if you would rather follow along in a reader. ## How we write We try to hold every post to the same few rules. 1. **Show the working.** When we quote a formula, we say where it comes from, and where we can we link to the documentation or the data behind it. 2. **Label illustrations.** Worked examples often use small, round numbers because they are easier to follow. Whenever a post uses made-up figures, it says so, and nothing in a diagram should be mistaken for a measurement. 3. **Say what we do not know.** Bittensor changes. If a mechanism is in flux, or a number depends on something we cannot observe, we will say that rather than guess. 4. **Stay practical.** Each post should leave you able to do something: read a page, check a trade, make a request. None of it is investment advice. We explain how things work; what you do with that is up to you. ## Where to start If you are new here, these four posts are a good way in. They cover reading prices, understanding validators, trading safely and getting at the data. - [Reading subnet prices after dTAO](https://beta.taostats.io/blog/a-field-guide-to-reading-subnet-prices-after-dtao) — Why the price on a subnet page is not what a trade fills at, and how to check before you stake. - [What validator weights tell you](https://beta.taostats.io/blog/what-validator-weights-tell-you-about-a-subnet) — How validators' scores become emissions, and what to read in the metagraph. - [Staking with MEV protection](https://beta.taostats.io/blog/staking-with-mev-protection-on-taostats) — What MEV Shield does, how to choose a mode, and when it switches itself off. - [Getting started with the API](https://beta.taostats.io/blog/getting-started-with-the-taostats-api) — From a key to your first response in a few minutes. ## Tell us what to cover The best posts start as questions. If there is something about the network, the data or the product that you would like us to explain, send us a note on X at @taostats. We read everything, and the answers that come up most often will end up here.