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

# FAQ

<details>

<summary><strong>Why signatures from EOAs are rejected even if they are valid?</strong></summary>

TargetBase is built for **smart account–based execution**, not direct EOA calls. All protected functions must be executed **via a DelegatedAccount** that has been pre-approved. This creates an enforcement layer where **EOAs cannot bypass authorization logic**.

</details>

<details>

<summary><strong>What happens if someone tries to reuse the same signed authorization twice?</strong></summary>

They can’t. TargetBase prevents this via **dual-layer replay protection**:

1. **Nonce Check** — must match `nonces[msg.sender]`
2. **Authorization Hash Tracking** — once a signature hash is used, it’s permanently recorded and rejected on future calls

This means even if an attacker copies calldata across chains, it still won’t execute.

</details>

<details>

<summary><strong>Can I rotate the master key without breaking existing signatures?</strong></summary>

Yes. When rotating the master key, all future authorizations must be signed with the new key, but **already-executed signatures remain final**. Pending signatures signed by the old key become invalid, this is intentional for security. This means that you also need to create a new attestor image which includes the private key of the latest master key.

</details>

<details>

<summary><strong>Does the contract owner have god mode? Can they bypass requireAuth?</strong></summary>

No. TargetBase does **not** implicitly grant owner privileges over normal functionality. The owner **only controls**:

* Master key rotation
* Recovery key update
* Emergency nonce reset

Actual business logic must still pass through `requireAuth`.

</details>


---

# 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://docs.krnl.xyz/smart-contract/faq.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.