> For the complete documentation index, see [llms.txt](https://penguards.zer0luck.kr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://penguards.zer0luck.kr/core-features.md).

# Core Features

PENGUARDS concentrates its interface around six capabilities that support professional session oversight.

## 1. Comprehensive session ledger

* Enumerates every session key linked to the connected wallet in a structured, scrollable list.
* Presents issuer identity, signer address, originating transaction, and current validator status (Active, Expired, Closed).
* Provides card-level controls to copy the session hash, copy the signer, open the transaction on abscan, or initiate revocation.

## 2. Risk-prioritised presentation

* Automatically orders entries from Critical to Info so attention is directed to the most exposed sessions first.
* Severity badges disclose the score, label, and percentage without requiring an expanded view.
* The "Risk signals" summary identifies the dominant risk drivers (for example, "No expiry configured", "Unlimited spend permitted", "Approval target not reviewed").

![Severity badge and risk signals](/files/5aCH8aKcru1i5QsVf7MX)

## 3. Interpretable permission details

* Call and transfer policies are rendered in precise language describing target, selector, spend limits, and parameter constraints.
* Tooltips expose allowance periods, value caps, and registry status to aid rapid interpretation.
* Contextual help links route to the handbook for deeper reference when needed.

![Policy detail view](/files/KwqxDChzMJpsQChnZF7d)

## 4. Controlled revocation workflows

* Each session card offers a guarded **Revoke session** action with explicit confirmation to mitigate accidental execution.
* The global **Revoke all** button orchestrates bulk clean-up in a single flow.
* A dedicated revoke window persists while wallet confirmation is pending and reports success, failure, or cancellation outcomes.
* Toast notifications inside the popup confirm completion for audit purposes.

![Revoke workflow](/files/DNTWTFKKZsr42lUCR5ew)

## 5. Enriched context via Abstract Portal

* Integrates portal metadata (application name, verification tier, iconography) to assist with rapid identification.
* Surfaces contract metadata, verified selectors, and bytecode hints so the scope of each session is unambiguous before revocation.

## 6. Operational refinements

* **Copy utilities** for hashes, signers, and explorer URLs.
* **Automatic refresh** after each revoke and whenever the popup is reopened.
* **Keyboard affordances** (e.g., `Esc` to close modals) for efficient navigation.
* **Accessibility support** with high-contrast styling and screen-reader labels on signal and action elements.


---

# 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://penguards.zer0luck.kr/core-features.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.