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

# Security & Trust Model

Anti-rug isn't a slogan here — it's an architecture. This page states exactly what is immutable, what is configurable, and by whom. If a claim on this page ever contradicts the chain, the chain wins.

## What nobody can do — not even Socialhood

* **Mint, pause, or blacklist** any launched token, or edit its metadata.
* **Touch the airdrop**: redirect a claim, change a merkle root, alter a graduation target, or un-graduate a token. The escrow has no admin.
* **Fake a graduation**: it's a TWAP read from the pool. There's no oracle to feed and no override to call.
* **Bypass creator fees on keys**: keys are soulbound; all value flows through the curve.
* **Take a cut of tips**: the TipJar forwards 100% and has no owner.
* **Change fair-launch constants**: 5% initial-buy cap, anti-sniper window, 2.5% airdrop, 1B supply — compiled into bytecode.

## What the owner (multisig) can do — and its limits

| Power                                | Contract      | Limit                           |
| ------------------------------------ | ------------- | ------------------------------- |
| Enable/adjust launch pairs & pricing | Factory       | Future launches only            |
| Set a flat launch fee                | Factory       | Future launches only            |
| Change treasury addresses            | Keys, Factory | Fee routing only                |
| Rotate/renounce roles                | All           | 2-step ownership on the factory |

## The one big disclosed power

The **LP Locker emergency admin** (multisig) can move a locked LP position out of custody. It exists for incident response — the same pattern used by established launchers on this chain. Mitigations: pending creator fees are paid out before any move, every use emits a public event, the role is rotatable, and it can be **permanently renounced**. We list this openly because a trust model you have to discover isn't a trust model.

## Engineering practice

* Non-upgradeable contracts; no proxies anywhere.
* 96 unit/fuzz/invariant tests + 19 fork tests executed against the **live** Robinhood Chain Uniswap deployment before launch — including full launch → pump → TWAP graduation → claim → burn flows and sniper-cap scenarios.
* Financial numbers in the apps come exclusively from onchain events; client input is never trusted for money.
* Anti-impersonation: markets are anchored to verified X identities; recreated X accounts do not inherit markets.


---

# 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.socialhood.app/contracts/security.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.