# Bribes

Bribes add a strategic and gamified layer to Beam's ve(3,3) ecosystem.

While trading fees are automatically routed to an LP's reward pool, bribes are whitelisted assets that can be manually added by actors who wish to further incentivize a reward pool. There are many reasons that an individual or protocol would want to do this. Several examples include:

* The user or protocol controls much of the liquidity in a particular pool, and the $BEAM emissions that they receive will be greater than the bribe value placed
* A protocol wishes to bootstrap liquidity from the community, and bribes their native pool on Beam to incentivize veBEAM holders to vote for their pool even without trading fee rewards, to increase APRs for liquidity providers to move in and collect.

And many more possible strategies. Bribes give a measure of indirect control over $BEAM emissions to anyone with bribe assets, by manually incentivizing veBEAM holders to vote for the reward pool of their choice.

Of course, in the end it is veBEAM holders who win as there are now more rewards in the ecosystem for them to collect.


---

# 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://docs.beamdex.xyz/protocol-overview/beams-ve-3-3-ecosystem/bribes.md?ask=<question>
```

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.