​
信号提案目前主要用于什么？

信号提案用于在链上记录社区对某个主题或某些想法的支持或共识。文本提案不包含任何代码。也就是说，文本提案一旦通过，并不会直接对 Hub 造成任何变更。 过去，信号提案曾被用于多种场景：
  • 就未来版本是否采纳某项功能达成共识（或明确不采纳）(7, 31, 38, 49, 69)
  • 向验证者发出高信号提醒 (8)
  • 在链上记录社区意见 (12)
  • 对某项社会规范进行确认 (75)

​
关于历史文本提案的说明

在 Cosmos Hub 的早期，text 是唯一的提案类型。如果你阅读旧提案，会发现当时很多现在由其他提案类型处理的事项，过去都是通过 text 提案完成的，例如修改参数 (10) 或进行软件升级 (19)。 这些历史提案的流程是：先通过链上信号授权在链下进行开发或变更，并将其纳入 Cosmos Hub 代码。随着新提案类型的加入，如今这些开发或支出决策可以在投票统计完成后立即由 Gaia 代码执行。

​
为什么要发起信号提案？

在为某个项目投入更多资源之前，信号提案是一种很好的方式，可以对社区情绪进行一次正式且公开的投票调查。文本提案最常见的用途，是在尚未准备好为开发申请资金、预算也还不够明确时，先确认社区是否真的对提案人想推动的内容感兴趣。 由于信号提案的结果会保留在链上，并且任何人都可以轻松访问，因此它也是将社区意见正式化的良好方式。记录在文档或 Github 仓库中的信息，对新加入的社区成员来说可能不容易找到；而区块浏览器或钱包中的信号提案则更容易获取。 你可以发起一个信号提案，来收集社区对你希望为 Hub 推动工作的看法；也可以因为你认为，有必要把社区整体持有的某种观点正式记录下来。

​
信号提案通过后会发生什么？

从技术上讲，链上不会发生任何事情。不会有代码被执行，而文本提案这种“不可强制执行”的特性，也是这种形式受到批评最多的地方之一。不过，无论信号提案的结果是否由代码强制执行，只要提案被记录在链上并经过讨论，它依然具有价值。无论提案通过还是失败，只要它被认真审议过，社区就能从中获得信息。
  • 社区可能会围绕某个主题展开一次原本不会发生的、充分而深入的讨论。
  • 对某项功能感兴趣的开发团队，可能会更清楚社区将如何看待他们的工作。
  • 社区对某个主题的了解，可能会比之前更加充分。
  • 社区可能会更有信心，确认我们在某个定义或社会规范上已经达成一致。

​
提交文本提案

按照以下说明创建文本提案，并将其提交到区块链。 
➜ gaiad tx gov draft-proposal

Use the arrow keys to navigate: ↓ ↑ → ←
? Select proposal type:
  ▸ text  # choose this
    community-pool-spend
    software-upgrade
    cancel-software-upgrade
    other
在 draft-proposal 菜单中选择 text，并填写所有可用字段。 
✔ text
Enter proposal title: Title
Enter proposal authors: Author
Enter proposal summary: Proposal summary
Enter proposal details: Details, all the details
Enter proposal forum url: /
Enter proposal vote option context: Vote yes if <...>
Enter proposal deposit: 100001uatom
检查 draft_proposal.json，你的结果应当与下面类似： 
{
  "metadata": "ipfs://CID",
  "deposit": "100001uatom",
  "title": "Title",
  "summary": "Proposal summary"
}
将你的 draft_metadata.json 上传到你选择的分发平台。draft_proposal.json 用于通过 submit-proposal 提交治理提案。 
gaiad tx gov submit-proposal <path_to_proposal.json>
   --from <submitter address> \
   --chain-id cosmoshub-4 \
   --gas <max gas allocated> \
   --fees <fees allocated> \
   --node <node address> \
包含调试信息的更多说明可在提交治理提案页面查看。

​
What are signaling proposals currently used for?

Signaling proposals are used to make an on-chain record of support or agreement on a certain topic or ideas. Text proposals do not contain any code. That is, they do not directly cause any changes to the Hub once passed. Past signalling proposals have been used for a variety of reasons:
  • Agreement to adopt (or not adopt) a feature in a future release (7, 31, 38, 49, 69)
  • A high-signal alert to validators (8)
  • On-chain record of community opinion (12)
  • Ratification of a social norm (75)

​
A note on historical text proposals

In the early days of the Cosmos Hub, ‘text’ was the only proposal type. If you read old proposals, you will find ‘text’ proposals being used for things we use other proposal types now, such as changing a parameter (10) or upgrading the software (19). The process for these historical proposals was that an on-chain signal was used to give permission for development or changes to be made off-chain and included in the Cosmos Hub code. With the addition of new proposal types, these development or spending choices can now be executed by the Gaia code immediately after the vote is tallied.

​
Why make a signaling proposal?

Signaling proposals are a great way to take an official, public poll of community sentiment before investing more resources into a project. The most common way for text proposals to be used is to confirm that the community is actually interested in what the proposer wants to develop, without asking for money to fund development that might not be concrete enough to have a budget yet. Because the results of signaling proposals remain on-chain and are easily accessible to anyone, they are also a good way to formalize community opinions. Information contained in documentation or Github repos can be hard to find for new community members but signaling proposals in a block explorer or wallet is very accessible. You might make a signaling proposal to gather opinions for work you want to do for the Hub, or because you think it’s important to have a record of some perspective held by the community at large.

​
What happens when a signaling proposal passes?

Technically, nothing happens on-chain. No code executes, and this ‘unenforceable’ property of text proposals is one of the biggest criticisms of the format. Regardless of whether the results of a signaling proposal are enforced by code, there can still be value from having a proposal on-chain and subject to discussion. Whether a proposal passes or fails, we all get information from it having been considered.
  • The community might have had a thorough, thoughtful discussion about a topic that they otherwise wouldn’t have had.
  • A dev team interested in a feature might have a better idea of how their work will be received by the community.
  • The community might be more informed about a topic than they previously were.
  • The community might feel confident that we are aligned on a particular definition or social norm.

​
Submitting a text proposal

Follow the instructions below to create a text proposal and submit it to the blockchain. 
➜ gaiad tx gov draft-proposal

Use the arrow keys to navigate: ↓ ↑ → ←
? Select proposal type:
  ▸ text  # choose this
    community-pool-spend
    software-upgrade
    cancel-software-upgrade
    other
Choose text from the draft-proposal menu and populate all the available fields. 
✔ text
Enter proposal title: Title
Enter proposal authors: Author
Enter proposal summary: Proposal summary
Enter proposal details: Details, all the details
Enter proposal forum url: /
Enter proposal vote option context: Vote yes if <...>
Enter proposal deposit: 100001uatom
Check draft_proposal.json, your result should be similar to this: 
{
  "metadata": "ipfs://CID",
  "deposit": "100001uatom",
  "title": "Title",
  "summary": "Proposal summary"
}
Upload your draft_metadata.json to a distribution platform of your choice. draft_proposal.json is used to submit a governance proposal using submit-proposal. 
gaiad tx gov submit-proposal <path_to_proposal.json>
   --from <submitter address> \
   --chain-id cosmoshub-4 \
   --gas <max gas allocated> \
   --fees <fees allocated> \
   --node <node address> \
Additional instructions with debugging information is available on the submitting page.