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

# Signer

### You control the wallet. Not us. Not anyone else.

BONKbot’s signing system is not a vault. It’s a firewall. Engineered to give you full control of your keys - without ever exposing them to anyone.

We call it The Signer.

### Non-Custodial by Design

Your private key is generated, encrypted, and sealed in a secure execution environment. No one - not us, not Telegram, not a cloud vendor - can view, extract, or use it. Only you can initiate a transaction.

### Intent-Only Execution

The Signer doesn’t just protect your key. It protects your intent.

Every transaction is matched to a human-readable blueprint you’ve approved. There are no hidden steps, no added instructions, no smart contract sleight-of-hand. If the payload doesn’t match exactly, it doesn’t move.

### Built to Withstand Compromise

Even if a protocol is exploited, even if your Telegram account is compromised, even if someone controls your device - your funds remain secure. BONKbot enforces:

* 2FA for seed phrase exports and withdrawals
* Optional per-transaction 2FA authorization
* Zero-access key memory, wiped after each use

No passwords. No custodians.\
Just hardware-grade security at the heart of BONKbot.\
We call it The Signer.\
You’ll call it peace of mind.

<br>
