> For the complete documentation index, see [llms.txt](https://docs.skydrome.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skydrome.finance/features/protocol-overview/aligning-rewards-with-emissions.md). # Aligning Rewards with Emissions **In Solidly, voting rewards (i.e. bribes) were claimable before the emissions from that vote were committed.** Velodrome addresses this with new mechanisms: * First, we allow voters to make only one "active" voting decision (i.e. `Voter.vote()`, `Voter.reset()`) every epoch (note: this does not include the `Voter.poke()` function). * Additionally, bribes from fees (internal) and external sources (external) are treated differently. Internal bribes function more or less the same way as they did in Solidly, streamed to voters who vote for them. External bribes, however, are rewarded per epoch rather than streamed, and are claimable only after the next epoch starts. This means that a bribe sent at the last minute of an epoch will accrue to all voters of that epoch, and be claimable once the epoch flips These modifications aim to strike a harmonious balance between voters and external actors offering bribes. By introducing these tweaks, we motivate bribers to present their incentives early in the week, luring initial voters. However, there's also a silver lining in delaying bribes, as this provides deeper insights into rival incentives. Similarly, voters grapple with a timing conundrum. Casting votes prematurely might mean missing out on enticing bribes unveiled later. Conversely, delayed voting might result in a diminished veSKY balance influence. It's worth highlighting that this latter impact is more accentuated for those who commit for shorter durations. For instance, those locked in for mere weeks as opposed to months or years might discern stark disparities in the incentives they accrue, based on whether they vote earlier or later in the epoch. --- # 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.skydrome.finance/features/protocol-overview/aligning-rewards-with-emissions.md?ask=&goal= ``` `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.