Knowledge | Gastx Content Admin

Primary fields

Slug, title, summary

正文、语种、标签、关联 CTA 和更新时间都要纳入规划。

Growth angle

Long-tail acquisition

内容要服务 SEO、广告再营销和产品教育，而不是做泛 CMS。

Live articles

8 knowledge records now come from a local JSON source.

Last updated: 2026-05-04T13:55:00.000Z

What is TRON Energy and when does renting make sense?

A first-step guide for users who need to understand Energy cost, transfer timing, and when renting is more efficient.

en · energy-basics · published

Buy Energy via API: request shape, callback flow, and integration choices

A practical overview for teams that need automated orders, callback handling, and stable routing for Energy delivery.

en · api-guides · published

租了能量后转账仍失败的 6 个排查点

从到账时机、地址一致性、带宽补充、钱包路径、金额预估和升级支持六个角度排查问题。

zh-CN · troubleshooting · published

高级源文件维护

Source payload

{
  "version": 1,
  "collection": "knowledge",
  "updatedAt": "2026-05-04T13:55:00.000Z",
  "records": [
    {
      "id": "knowledge-what-is-tron-energy",
      "slug": "what-is-tron-energy",
      "locale": "en",
      "topic": "energy-basics",
      "title": "What is TRON Energy and when does renting make sense?",
      "summary": "A first-step guide for users who need to understand Energy cost, transfer timing, and when renting is more efficient.",
      "bodyBlocks": [
        {
          "type": "paragraph",
          "content": "TRON Energy is consumed by smart-contract actions such as USDT transfers. Renting makes sense when you want lower marginal transfer cost, repeat usage, or clearer operating budgets."
        },
        {
          "type": "list",
          "items": [
            "Good for repeated transfers and operator workflows",
            "Helps reduce direct TRX burn in many cases",
            "Works best when route selection and timing are clear"
          ]
        }
      ],
      "targetKeyword": "what is tron energy",
      "searchIntent": "awareness",
      "relatedFaqIds": [
        "faq-energy-vs-burn"
      ],
      "ctaTarget": "to-pricing",
      "status": "published",
      "updatedAt": "2026-05-04T13:20:00.000Z"
    },
    {
      "id": "knowledge-buy-energy-via-api",
      "slug": "buy-energy-via-api",
      "locale": "en",
      "topic": "api-guides",
      "title": "Buy Energy via API: request shape, callback flow, and integration choices",
      "summary": "A practical overview for teams that need automated orders, callback handling, and stable routing for Energy delivery.",
      "bodyBlocks": [
        {
          "type": "paragraph",
          "content": "The API path is intended for teams that batch requests or need to connect Energy delivery to their own operational flows."
        },
        {
          "type": "list",
          "items": [
            "Use signed requests and idempotent keys",
            "Separate test and production credentials",
            "Plan callback retries and internal reconciliation"
          ]
        }
      ],
      "targetKeyword": "buy energy api",
      "searchIntent": "comparison",
      "relatedFaqIds": [
        "faq-route-selection"
      ],
      "ctaTarget": "to-api",
      "status": "published",
      "updatedAt": "2026-05-04T13:20:00.000Z"
    },
    {
      "id": "knowledge-transfer-still-fails-after-rental",
      "slug": "transfer-still-fails-after-rental",
      "locale": "zh-CN",
      "topic": "troubleshooting",
      "title": "租了能量后转账仍失败的 6 个排查点",
      "summary": "从到账时机、地址一致性、带宽补充、钱包路径、金额预估和升级支持六个角度排查问题。",
      "bodyBlocks": [
        {
          "type": "paragraph",
          "content": "能量租赁成功不等于所有链上动作都会立即通过。很多失败来自到账时间差、下单地址和实际转账地址不一致，或者本次交易除了 Energy 还同时消耗了带宽。"
        },
        {
          "type": "paragraph",
          "content": "如果订单已经完成，但转账仍报错，先不要重复下单。先确认资源是否已到账，再核对钱包路径、金额和发起时间，避免把链路问题误判成单纯的能量不足。"
        },
        {
          "type": "list",
          "items": [
            "确认资源到账时间，避免下单后立刻转账",
            "核对下单地址和实际发起转账的钱包地址是否完全一致",
            "判断这次操作是否同时缺少带宽或少量 TRX 作为补充",
            "检查是否使用了交易所钱包、多签钱包或受限钱包路径",
            "复核当前金额和路线是否超出原本预估的资源范围",
            "若仍失败，整理订单时间、地址、报错截图后再升级支持"
          ]
        }
      ],
      "targetKeyword": "租了能量后转账失败",
      "searchIntent": "troubleshooting",
      "relatedFaqIds": [
        "faq-transfer-fail-after-rental"
      ],
      "ctaTarget": "to-help",
      "status": "published",
      "updatedAt": "2026-05-04T13:55:00.000Z"
    },
    {
      "id": "knowledge-judge-usdt-transfer-energy",
      "slug": "judge-usdt-transfer-energy",
      "locale": "zh-CN",
      "topic": "energy-basics",
      "title": "怎么判断这笔 USDT 转账该直接燃烧 TRX，还是先租能量？",
      "summary": "用频次、时效、钱包路径和成本预期四个维度，判断当前这笔转账是否适合先租能量。",
      "bodyBlocks": [
        {
          "type": "paragraph",
          "content": "判断是否先租能量，不要只看钱包里有没有 TRX。更关键的是你是单次转账还是连续转账、是否要求成本稳定、以及当前钱包路径是否适合标准 TRC20 发送流程。"
        },
        {
          "type": "paragraph",
          "content": "如果你只是偶发转账，且能接受直接燃烧 TRX 的即时成本，直接发送可能更省操作步骤。如果你需要连续转账、给客户代发，或者希望把每次成本控制在更清晰的区间，先租能量通常更合适。"
        },
        {
          "type": "list",
          "items": [
            "单次偶发转账，可优先比较直接燃烧成本和时间",
            "高频或批量转账，更适合提前准备能量池",
            "对成本稳定性敏感的团队，应优先走租能量路线",
            "使用交易所钱包或异常路径时，要先确认是否适合标准租用流程"
          ]
        }
      ],
      "targetKeyword": "usdt 转账 租能量 判断",
      "searchIntent": "awareness",
      "relatedFaqIds": [
        "faq-energy-vs-burn"
      ],
      "ctaTarget": "to-pricing",
      "status": "published",
      "updatedAt": "2026-05-04T13:55:00.000Z"
    },
    {
      "id": "knowledge-energy-cost-comparison",
      "slug": "energy-cost-comparison",
      "locale": "zh-CN",
      "topic": "energy-basics",
      "title": "租能量和直接燃烧 TRX，成本该怎么比较？",
      "summary": "不承诺固定价格，提供一套适合官网内容的成本比较口径，帮助用户判断什么时候租更划算。",
      "bodyBlocks": [
        {
          "type": "paragraph",
          "content": "比较成本时，不要执着于一个固定数值。TRON 上的实际消耗会随着钱包状态、转账路径和链上条件变化，所以更稳的做法是比较单次即时成本、连续多次使用成本，以及是否需要降低失败重试带来的额外消耗。"
        },
        {
          "type": "paragraph",
          "content": "对普通用户来说，核心问题是这次转账买多少更稳。对团队和批量用户来说，核心问题则是单位转账的平均成本是否可控，以及能否减少因临时缺资源导致的卡单。"
        },
        {
          "type": "list",
          "items": [
            "单次小额且不频繁时，可先比较即时燃烧成本",
            "多次重复转账时，租能量通常更有机会摊薄单次成本",
            "若失败重试会造成业务损失，稳定性本身也是成本的一部分",
            "批量场景应同时评估下单效率、回调对账和人工处理成本"
          ]
        }
      ],
      "targetKeyword": "租能量 成本 对比",
      "searchIntent": "comparison",
      "relatedFaqIds": [
        "faq-energy-vs-burn"
      ],
      "ctaTarget": "to-pricing",
      "status": "published",
      "updatedAt": "2026-05-04T13:55:00.000Z"
    },
    {
      "id": "knowledge-buy-energy-via-api-zh",
      "slug": "buy-energy-via-api-zh",
      "locale": "zh-CN",
      "topic": "api-guides",
      "title": "API 接入购买能量时，应该先确认哪些字段和回调逻辑？",
      "summary": "面向开发和运营团队，说明下单字段、幂等、回调、对账和失败兜底的最小接入框架。",
      "bodyBlocks": [
        {
          "type": "paragraph",
          "content": "API 接入适合批量下单、代发业务或需要把能量采购接进自己系统的团队。上线前最重要的不是先堆功能，而是先把地址字段、业务单号、签名、环境隔离和回调验签约定清楚。"
        },
        {
          "type": "paragraph",
          "content": "如果系统会自动发起订单，必须预留失败兜底和人工复核路径。否则一旦遇到回调延迟、重复通知或内部对账不一致，团队很容易把交付状态判断错。"
        },
        {
          "type": "list",
          "items": [
            "请求侧至少要明确地址、套餐、业务单号和签名字段",
            "对同一业务单号做幂等控制，避免重复下单",
            "回调侧要做验签、重试和状态去重处理",
            "测试环境与生产环境凭证必须隔离",
            "内部需要有定时对账和人工补单的兜底流程"
          ]
        }
      ],
      "targetKeyword": "能量 API 接入",
      "searchIntent": "comparison",
      "relatedFaqIds": [
        "faq-route-selection"
      ],
      "ctaTarget": "to-api",
      "status": "published",
      "updatedAt": "2026-05-04T13:55:00.000Z"
    },
    {
      "id": "knowledge-buy-energy-via-tg",
      "slug": "buy-energy-via-tg",
      "locale": "zh-CN",
      "topic": "api-guides",
      "title": "通过 TG 机器人买能量适合谁，操作时要注意什么？",
      "summary": "帮助用户判断 TG 机器人是否适合当前场景，并说明下单前后最容易出错的几个点。",
      "bodyBlocks": [
        {
          "type": "paragraph",
          "content": "TG 路径更适合轻量用户、临时补单用户或希望先快速试一次的人。它的优势是进入门槛低、操作直接，但当业务开始出现批量需求、多人协作或自动化要求时，就该考虑切换到网页或 API。"
        },
        {
          "type": "paragraph",
          "content": "使用 TG 机器人时，最容易出错的是地址复制、套餐理解和到账时机。用户在发送前应先确认钱包地址、期望用途和预计发起转账的时间，不要在状态未确认前连续重复操作。"
        },
        {
          "type": "list",
          "items": [
            "临时补能量、低频转账，TG 通常更方便",
            "下单前先核对地址和预期用途，避免买对了套餐却给错地址",
            "到账后再发起转账，不要边下单边尝试多次发送",
            "当出现批量、对账或权限管理需求时，应升级到网页或 API"
          ]
        }
      ],
      "targetKeyword": "TG 买能量",
      "searchIntent": "awareness",
      "relatedFaqIds": [
        "faq-route-selection"
      ],
      "ctaTarget": "to-help",
      "status": "published",
      "updatedAt": "2026-05-04T13:55:00.000Z"
    },
    {
      "id": "knowledge-partner-cooperation-path",
      "slug": "partner-cooperation-path",
      "locale": "zh-CN",
      "topic": "api-guides",
      "title": "如果你想做代理、合作代充或批量采购，应该怎么对接？",
      "summary": "面向合作方说明适合走网页、TG 还是 API，并列出合作前应准备的关键信息。",
      "bodyBlocks": [
        {
          "type": "paragraph",
          "content": "合作路径的核心不是先谈形式，而是先确认你的业务量级、是否需要自动化、谁来承担对账和售后。低频合作可以先从人工和半自动路径开始，高频团队则应尽早进入稳定 API 和结算流程。"
        },
        {
          "type": "paragraph",
          "content": "如果你是代理、工作室或交易团队，准备好基础业务说明、日均单量、主要钱包路径和期望结算方式，会比只问一个报价更快进入可执行的合作沟通。"
        },
        {
          "type": "list",
          "items": [
            "低频合作可先通过 TG 或网页验证交付体验",
            "稳定批量需求应优先评估 API 和对账能力",
            "合作前准备日均单量、地址类型、使用时段和结算需求",
            "明确是否需要分账户、回调通知和售后升级路径"
          ]
        }
      ],
      "targetKeyword": "能量 合作 代理",
      "searchIntent": "comparison",
      "relatedFaqIds": [
        "faq-route-selection"
      ],
      "ctaTarget": "to-help",
      "status": "published",
      "updatedAt": "2026-05-04T13:55:00.000Z"
    }
  ]
}

Frontend Contract

前台接线目标

服务知识文章列表、详情页、帮助教育内容和搜索长尾承接。

Consumer

gastx-web /[locale]/knowledge 与文章详情页

Primary key: slug

Status field: status

Collection shape

后续前台应按这个集合形状取数，而不是继续在页面里硬编码文案常量。

Fields: 13

Records: 3

Schema

统一内容 schema

Field	Type	Required	Notes
id Record ID	string	Required	集合内部唯一标识。
slug Slug	string	Required	详情页路径段。
locale Locale	enum	Required	支持语言分层。
topic Topic	enum	Required	energy-basics、api-guides、payment、bot 等。
title Title	string	Required	文章主标题。
summary Summary	text	Required	列表页摘要。
bodyBlocks Body blocks	rich-text	Required	正文内容块，按发布需要维护。
targetKeyword Target keyword	string	Optional	搜索词主轴。
searchIntent Search intent	enum	Optional	awareness、comparison、troubleshooting。
relatedFaqIds Related FAQ IDs	string[]	Optional	打通知识与问答。
ctaTarget CTA target	string	Optional	文章末尾主要跳转。
status Status	enum	Required	内容工作流状态。
updatedAt Updated at	date-time	Required	内容新鲜度和重写周期。

Records

用于前台替换静态内容的记录

面向首次接触 TRON 用户，解释能量用途、计费逻辑和租赁时机。

Topicenergy-basics
Keywordwhat is tron energy
Intentawareness
CTAto-pricing

为开发者提供 API 路径说明、回调预期和批量集成入口。

Topicapi-guides
Keywordbuy energy api
Intentcomparison
CTAto-api

中文排错类文章，承接 FAQ 和帮助中心的更深层解释。

Topictroubleshooting
Keyword租了能量后转账失败
Intenttroubleshooting
CTAto-help

Editor

编辑面板

先把编辑器分区收口，后续不论接真实 CMS 还是 API，都能按这个面板结构推进。

Editorial identity

先固定 slug、主题、语种和主关键词，避免文章上线后频繁改 URL。

slug
locale
topic
title
targetKeyword
searchIntent

Article payload

摘要和正文块分离，后续前台可直接按 block renderer 接入。

summary
bodyBlocks
relatedFaqIds
ctaTarget

Lifecycle

把内容审核和刷新节奏显性化，不把文章状态藏在代码里。

status
updatedAt

Module Flow

上下游协作关系

Upstream inputs

SEO Pages定义搜索意图、canonical 和内容聚类。Locale Content确认哪些文章需要本地化优先上线。

Feeds into

FAQ高频问答可从文章中抽出结构化答案。Channel Landing投放页可复用教程摘要和可信任解释。

Checkpoints

运营收口要求

文章必须服务具体搜索意图或产品教育问题。
每篇内容都要有明确 CTA，回流官网主路径。
不要把它做成承载订单、报表或开发者控制台的文档站。

Field Planning

第一阶段字段边界

Editorial core

Slug
Title
Summary
Body blocks
Locale
Author tag

SEO support

Search intent
Target keyword
Canonical note
FAQ links
Related CTA

Lifecycle

Draft status
Review owner
Publish window
Refresh cadence

Workflow

内容工作流说明

Draft

Content editor

录入文案、FAQ、SEO 字段和基础 CTA，不在这里接真实业务执行。

Review

SEO / Growth ops

检查索引策略、多语言一致性、渠道文案边界和合规提示。

Ready

Site owner

确认发布窗口、关联页面和投放节奏，避免内容与渠道错配。

Publish

System hook later

后续由 CMS 发布流或内容 API 接管；当前阶段只保留流程说明。

Future Hooks

后续扩展预留

后续可接知识分类、相关推荐和内链建议，但不在第一阶段做完整文档站。
文章详情模板和 block editor 以后再接，现在先把字段责任划清楚。
允许为 API、TG Bot、批量购买等场景保留 CTA block 入口。

Knowledge management

Live articles

What is TRON Energy and when does renting make sense?

Buy Energy via API: request shape, callback flow, and integration choices

租了能量后转账仍失败的 6 个排查点

Knowledge JSON editor

前台接线目标

Consumer

Collection shape

统一内容 schema

用于前台替换静态内容的记录

What is TRON Energy and when does renting make sense?

Buy Energy via API: overview and callback expectations

租了能量后转账仍失败的 4 个排查点

编辑面板

Editorial identity

Article payload

Lifecycle

上下游协作关系

Upstream inputs

Feeds into

运营收口要求

第一阶段字段边界

Editorial core

SEO support

Lifecycle

内容工作流说明

后续扩展预留