# 12.5 Smart-Contract–Centric Web3 Stacks

When cryptographic authority is the foundation, tokens and complex on-chain logic become unnecessary.

***

### Token-Based Model vs PTERI

| Category            | Traditional Model                     | Problems                  | PTERI Replacement                                                              |
| ------------------- | ------------------------------------- | ------------------------- | ------------------------------------------------------------------------------ |
| Identity Primitive  | Tokens represent identity and access  | Identity leakage          | <mark style="color:$primary;">**No tokens**</mark>                             |
| Execution Model     | Complex smart contracts               | Large attack surface      | <mark style="color:$primary;">**No smart contracts**</mark>                    |
| On-Chain Design     | On-chain logic and metadata           | Poor UX, heavy state      | <mark style="color:$primary;">**Minimal on-chain footprint**</mark>            |
| Incentive Structure | Speculation-first incentives          | Misaligned priorities     | <mark style="color:$primary;">**Utility-first cryptographic authority**</mark> |
| Verification        | Logic embedded in contracts           | Hard to audit and upgrade | <mark style="color:$primary;">**Off-chain deterministic verification**</mark>  |
| System Complexity   | Multiple layers of programmable state | Increased failure modes   | <mark style="color:$primary;">**Cryptography only**</mark>                     |

***

### Core Principle

> *"Cryptography is kept. Everything else is removed."*

Authority is proven by signature.\
Execution is verified deterministically.\
No tokens. No speculative layers. No unnecessary state.

***


---

# Agent Instructions: 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:

```
GET https://docs.kakrlabs.com/12.-comparisons-and-obsolescence/12.5-smart-contract-centric-web3-stacks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.