> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/announcement/zh-tw/dec-2025/20251217.md).

# Cregis更新通知 - 版本 \[V3.6.0]

尊敬的Cregis用戶，

您好！我們將於**2025年12月21日 07:00 - 09:00（UTC+8）**推出Cregis的最新版本 **V3.6.0**，此次更新爲**強制更新**。系統維護期間，登錄、轉賬、API接入、收單等功能都會受到影響，充值可能延遲到賬，收單結算將在維護結束後進行。我們非常抱歉給您帶來不便，請您提前安排業務，並在維護結束後視需要升級版本與調整權限。

**本次更新包括：**

1. 交易記錄與匯出內容優化（僅限桌面端）
2. MPC 分片管理優化
3. 交易手續費與加速相關優化
4. 修復已知問題

\
感謝您一直以來對Cregis的支持！如有任何疑問，請隨時聯繫我們。

Cregis團隊\
2025-12-17


---

# 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://support.cregis.com/announcement/zh-tw/dec-2025/20251217.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.