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

# TRON 引言

本系列文章假定读者：

* 对区块链及以太坊有一定的了解
* 具有一定的编码能力
* 至少浏览过 <\<Mastering Ethereum: Building Smart Contracts and DApps>> 一书

### 抛开广告词, 从开发者角度看, TRON 是什么？

一条**较高程度兼容以太坊智能合约体系**的公链。大部分以太坊智能合约可以无缝迁移。对以太坊的资源消耗机制做了修改，智能合约调用的代价远远低于以太坊。

**基于 DPoS 共识治理**的公链。产块稳定，交易处理性能优秀。（与 PoW 链相比，对用户和开发者更友好）

**底层和 API 层重度使用 protobuf 和 gRPC** 的公链。为兼容，同时提供了 HTTP API.

唯一官方承认和**唯一可用的实现是 java-tron**, 项目地址 <https://github.com/tronprotocol/java-tron> .


---

# 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://andelf.gitbook.io/tron/introduction/tron-intro.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.