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

# CatFee Guard

`CatFee Guard` is CatFee's web transaction workspace. Its core positioning is:\
`Online transaction management, offline signing.`

It is not just a warning or risk-notice page. It is an online coordination tool built around signer management, transaction creation, signature collection, and transaction broadcasting.

## Core Capabilities

Based on the current repository README and page structure, `CatFee Guard` currently includes:

* Wallet dashboard
* My signatures
* Signing tasks
* My transactions
* Signed list

Across these pages, users can:

* Bind offline signers
* Manage signer status
* Create transactions
* Review pending signing tasks
* Import offline signature results
* Broadcast transactions after signature conditions are satisfied

## Intended Readers

* Product stakeholders reviewing the transaction workspace positioning
* Engineers and QA members who need to understand the online/offline collaboration model
* Operations or support teams documenting internal workflows

## Suggested Next Reading

1. [Transaction Workflow](/catfee-guard/transaction-workflow.md)


---

# 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://wallet-docs.catfee.io/catfee-guard.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.