> For the complete documentation index, see [llms.txt](https://docs.arcv.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcv.network/6.-protocol-economics-and-tokenomics/6.3-treasury-and-capital-allocation.md).

# 6.3 Bounty Allocation & Accountability

## Public bounty split

For each gross accepted bounty settlement, the specified allocation is:

| Destination       | Share of gross settlement |
| ----------------- | ------------------------: |
| Contributors      |                       90% |
| Protocol treasury |                        5% |
| Token buybacks    |                        5% |

For 100 USDC of accepted settlement value, 90 USDC is allocated to contributors, 5 USDC to treasury, and 5 USDC to buybacks. Unused campaign deposits are not earned settlement revenue.

## Payment evidence

Each completed settlement should identify its campaign, accepted work, contributor payment, treasury allocation, and buyback allocation. Reverted transactions do not create completed payouts. Pending balances and executed transfers must be reported separately.

Contributor rewards must clearly state whether the displayed amount is before or after the protocol deduction. Existing funded campaign terms must not be silently changed.

## Buyback evidence

An allocated buyback budget is not an executed purchase. Verify successful trade receipts and acquired token quantities. A supply-reducing burn and a transfer to a designated dead address are distinct operations and must be reported separately.

## Implementation boundary

This split is the specified protocol policy. The current registry pays the full configured reward and does not implement the split or buyback execution. Interface animations and synthetic activity streams are not settlement evidence.

See [the revenue engine](/6.-protocol-economics-and-tokenomics/6.2-protocol-revenue-engine.md) for settlement arithmetic and [contract architecture](/5.-smart-contracts-and-arc-network-settlement/5.1-contract-architecture.md) for implemented behavior.


---

# 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.arcv.network/6.-protocol-economics-and-tokenomics/6.3-treasury-and-capital-allocation.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.