> For the complete documentation index, see [llms.txt](https://tatsu.gitbook.io/tatsu-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tatsu.gitbook.io/tatsu-whitepaper/the-tatsuos-thesis.md).

# The TaτsuOS Thesis

TaτsuOS rests on three claims.

**Claim 1: Feature unlocking is the right primitive.** Most attempts to "put IoT on-chain" reach immediately for full device-to-chain communication. This is the wrong altitude. The thing a user actually wants to do is enable a capability — turn on remote configuration, unlock a higher sample rate, authorize a third-party module. Modeling that as a periodic TATSU burn that activates a subscription tier and generates verifiable, cryptographic receipts for each period is dramatically simpler than having every device maintain its own on-chain state.

**Claim 2: ECDSA over secp256k1 is sufficient.** The same curve that secures Ethereum is supported by every relevant microcontroller, often in hardware. A receipt is a small structured payload, signed once, verified once, and stored once. No new cryptographic primitives are required.

**Claim 3: BLE is the right last-mile.** The end-user already has a phone in their hand. The phone can talk to the chain and to the device. Receipts move from chain to phone over HTTPS, and from phone to device over BLE. WiFi provisioning, MQTT brokers, and cellular gateways are optional for the receipt flow — which means TaτsuOS works even on devices that have no internet connectivity at all.

These three claims, taken together, describe a system that is small enough to fit on a $2 microcontroller and decentralized enough to outlive any single operator.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://tatsu.gitbook.io/tatsu-whitepaper/the-tatsuos-thesis.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.