> For the complete documentation index, see [llms.txt](https://docs.mutuum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mutuum.com/protocol-updates/006.md).

# #006

<figure><img src="/files/q5CFQrGB1yTGopD5TlBF" alt=""><figcaption></figcaption></figure>

### Mutuum Protocol Update #006 — Testnet Deploy Scripts Live, FE GraphQL Reads, QA Harness Ready

#### ✅ Completed

**Deployment scripts**\
Initial protocol contracts deployed to testnet using automated pipelines. GitHub Actions now runs contract tests on every PR and enforces minimum coverage before merge. Versioned artifacts and environment configs are tracked for repeatable rollouts.

**Contracts FE queries**\
Front-end queries implemented via GraphQL to read core contract state and user positions. Queries are typed and paginated to support portfolio, market, and health views.

**QA setup of test scripts**\
Dedicated QA environments prepared with scripted checks for deposit/withdraw, borrow/repay, and liquidation paths. Fixtures seed accounts and markets for consistent runs.

**Test scenarios preparation**\
Comprehensive scenarios drafted for edge cases: under-collateralization, bad-debt detection, slashing events in the Safety Module, and fee-withdrawal workflows.

***

#### ⌛ In Progress

**GraphQL & Subgraph integration**\
Connecting the UI to a custom Subgraph for real-time protocol state. Subgraph deployments will track TVL, position data, and liquidation events.

**AWS setup**\
Provisioning core infrastructure and access controls to support indexing, APIs, and CI/CD.

**Historical APY visualization**\
Building UI components to chart historical and live APY per market using indexed on-chain events.

**Contract interactions (FE)**\
Refining front-end transaction flows: trigger deposits, withdrawals, borrows, and interface with fee-collector actions under multisig governance.

**Testing front-end data**\
Validating data across staking workflows, liquidation status, and protocol analytics to ensure accurate rendering and alerts.

***

Released: **07 Nov 2025** (UTC) · Update **#006**


---

# 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:

```
GET https://docs.mutuum.com/protocol-updates/006.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
