# Bounty security ### Guarantees **No withdrawal** Deposited rewards cannot be taken back by the creator. This prevents “bait” bounties where the pool disappears. **Deadline enforcement** Distribution is only possible after the end date. This gives participants the full activity window. **Reentrancy protection** Uses OpenZeppelin `ReentrancyGuard` patterns to reduce common contract risks. ### What this does not guarantee * It does not guarantee submission quality. * It does not prevent sybil accounts or bought engagement. * It does not verify that creators judge fairly. ### Best practices for fair bounties * Publish criteria before the bounty starts. * Disqualify duplicates and stolen content consistently. * Keep review evidence (URLs, screenshots) until after payout. --- # Agent Instructions: 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: ``` GET https://creator-vault.gitbook.io/documentation/creator-vault/bounties/bounty-security.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.