> For the complete documentation index, see [llms.txt](https://docs.bloxchain.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloxchain.app/platform-bloxchain.app/overview/approve-and-sign.md).

# Approve and sign

**Audience:** Member / approver · **App path:** Workspace → **Transactions → Open**

Approve, cancel, sign meta-transactions, or execute as broadcaster.

## Open an item

1. **Workspace → Transactions** → **Open** tab.
2. Select the row → detail drawer opens.
3. Review operation, target, amount, and timelock (`releaseTime` if shown).

## Pending (on-chain approval path)

1. Wait for **timelock** if `releaseTime` is in the future.
2. **Approve** or **Cancel** — confirm in wallet.
3. Complete any separate finalize step if the schema requires it.

## Meta-transaction path

1. **Sign** EIP-712 typed data in your wallet.
2. Item stays in **Open** with **Signed** status until executed.
3. **Broadcaster** wallet → open same item → **Execute** ([Security settings](/platform-bloxchain.app/overview-1/security-settings.md)).

### Optional relayer (environment-dependent)

Some deployments may offer **Sign and broadcast** or automatic relay after you sign — when enabled, the platform submits the signed meta-tx without a manual broadcaster step. If relay is disabled or fails, the **Broadcaster** wallet must **Execute** from the **Open** queue (always valid on-chain).

> **Default expectation:** treat broadcaster execute as the reliable path unless your operator confirms relayer is enabled. See [Known limitations](/security/known-limitations.md) and [Roadmap](/resources/roadmap.md).

## Reference

| Open item state | Your actions          |
| --------------- | --------------------- |
| **Pending**     | Approve, Cancel       |
| **Signed**      | Execute (broadcaster) |

## Verify

* Status moves toward `COMPLETED` — check **Completed** tab ([Transactions](/platform-bloxchain.app/overview/transactions.md)).

## Next steps

* [How this works](/introduction/operational-model.md) · [Use a contract](/platform-bloxchain.app/overview.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://docs.bloxchain.app/platform-bloxchain.app/overview/approve-and-sign.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.