> For the complete documentation index, see [llms.txt](https://docs.plenty.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenty.network/v2-docs/plenty-v2-introduction/understanding-bribes.md).

# Understanding Bribes

Plenty natively supports gauge bribes and automatically adjusts them according to weekly `vePLY` NFT votes. In addition to traditional bribes, which allows a protocol to expand their on-chain liquidity by bribing vote escrow holders to vote in a specific way (e.g. Convex bribing `veCRV` token holders). Plenty allows any user to attach bribes onto a gauge.

The concept of bribes was made popular by Convex which came to control a large share of Curve voting power. As users kept chasing high `CRV` rewards, protocols realized they could grow their protocol and on-chain liquidity by bribing `veCRV` holders to vote for their pool.

On Plenty, it’s possible for anyone to attach bribes onto a gauge and those who vote for it are then able to claim them.

## Who can bribe?

Anyone can issue a bribe to attract voters to a specified gauge in a specified epoch. However, bribers would most likely be:

* Protocol owners who are aiming to bootstrap liquidity for their protocol's token.
* Liquidity providers who have high stakes in a certain pool.

{% hint style="danger" %}
Bribes must be given in **fungible tokens**. A bribe given in NFTs won't be divisible amongst the voters. Moreover, really small bribes especially in low-precision tokens should be avoided.
{% endhint %}

{% embed url="<https://whitepaper.plenty.network/amm/vote-escrow-architecture#briber>" %}

![Adding a bribe to a gauge will attract more votes, which will result in a higher gauge weight, which will attract liquidity.](/files/AkdKNWvyR0BtXGNx4hSP)


---

# 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.plenty.network/v2-docs/plenty-v2-introduction/understanding-bribes.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.