> For the complete documentation index, see [llms.txt](https://docs.beamdex.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.beamdex.xyz/protocol-overview/beams-ve-3-3-ecosystem/corelink/benefits-of-corelink.md). # Benefits of CoreLink **Picking up (3,3) where OlympusDAO left off**\ Outside of an ocean of $OHM liquidity and some psychological benefit for $OHM holders, the massive OlympusDAO treasury did not drive enough real value creation to self-sustain the protocol. Ultimately bonding alone was not enough to counter bear market conditions, and $OHM fell out of the spotlight along with most other cryptocurrencies after 2021. CoreLink takes the same bonding concept but intends to make the assets received from bonding work much harder for the ecosystem, which in a ve(3,3) environment can be hugely beneficial, the likes of which could not be realized in OlympusDAO's era. By perpetually growing Beam's most productive LPs with sticky liquidity that is never going to leave, regardless of $BEAM price, macromarket conditions, or any other reason, veBEAM holders can rest assured that there is always a floor of high-volume TVL on Beam, earning fees 24/7 for them. **The Backing Price, reimagined**\ $OHM was tied to a "hard" backing price that would cannibalize assets to maintain a certain price level. However, this was not a perfect solution, because as more assets were sold for $OHM, the hard backing price would reduce. If bonds could not keep up with sell pressure, this would (and did) continue to drive price, treasury, and sentiment down. Beam has instead elected not to guarantee a price with static assets, but instead have a soft price floor backed by the revenue that CoreLink's TVL generates. Protocol-owned bluechip liquidity constantly earns trading fees for veBEAM holders - and every $BEAM token bought through CoreLink grows that liquidity, forever. In a major selling event of $BEAM, protocol-owned liquidity will continue to generate fees for lockers, creating a backstop for the dreaded ve(3,3) "death spiral" (which is the reverse of the ve(3,3) flywheel seen [here](/protocol-overview/beams-ve-3-3-ecosystem/the-ve-3-3-flywheel.md)). At some point, $BEAM's price will drop, and voting APR will increase, to the point where buying $BEAM becomes a very easy decision, as the yield will outpace $BEAM's current entry price. **Removing $BEAM from circulation**\ Additionally, all $BEAM emissions farmed by protocol-owned liquidity will be permalocked and used to vote for the most productive LPs each week by the team. The more POL on Beam, the more emissions that will never be sold to the market. It's an organic approach to removing $BEAM from circulation without engaging 3rd party actors who would require fees for their services. --- # 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.beamdex.xyz/protocol-overview/beams-ve-3-3-ecosystem/corelink/benefits-of-corelink.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.