> For the complete documentation index, see [llms.txt](https://docs.global-entertainment-token.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.global-entertainment-token.org/ja/7-kitekuchato/74-sumtokontorakutonoto.md).

# 7.4 スマートコントラクトの適用と範囲

<figure><img src="https://445040947-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOxry6bBJam0UPRlzLhGl%2Fuploads%2FeZvz6lUQ5WMDyk6PWK9C%2Fshotaueyama_A_futuristic_3D_CG_scene_illustrating_the_applica_6acd253c-528f-43cc-9471-41941c492c90_0.png?alt=media&amp;token=dc607d02-6e3a-45b4-90e9-e29654e65754" alt=""><figcaption></figcaption></figure>

GETでは、Plutusスマートコントラクトを用いて、以下の領域で自動化と透明性の高い運用を実現します。

<table><thead><tr><th width="250.337890625">領域</th><th>スマートコントラクトの活用内容</th></tr></thead><tbody><tr><td>ガバナンス</td><td>投票、提案、承認、実行の自動処理</td></tr><tr><td>ステーキング</td><td>ロック条件、報酬分配、満期処理の自動化</td></tr><tr><td>NFT発行・販売</td><td>発行、所有権管理、二次流通時のロイヤリティ分配</td></tr><tr><td>RWAトークン化</td><td>所有証明NFT発行、分割権利記録、転送履歴管理</td></tr><tr><td>クラウドファンディング</td><td>支援金の段階配分／未達時の自動返金処理</td></tr></tbody></table>

Plutusは形式検証（Formal Verification）を導入できるため、スマートコントラクトの論理的正当性を高いレベルで担保可能です。

<br>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.global-entertainment-token.org/ja/7-kitekuchato/74-sumtokontorakutonoto.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.