> 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/76-sekyurititosukrabiriti.md).
# 7.6 セキュリティとスケーラビリティ設計
**セキュリティ面：**
* スマートコントラクトの段階的監査体制の導入
* マルチシグによる運営ウォレットの権限分散
* プラットフォームにおける操作ログの取得と不正検知
**スケーラビリティ面：**
* GET Platformの処理をフロント／バックで分割し、トランザクション負荷を抑制
* ユーザー数増加に伴う処理分散のためのL2導入（Hydra等）を検討
* NFT・RWA取引データの一部をIPFSやArweaveといった分散型ストレージと連携
---
# 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/76-sekyurititosukrabiriti.md?ask=&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.
