# CoreLink CoreLink is a unique and powerful component of Beam's ve(3,3) ecosystem that actually leans much deeper into the (3,3) concept than ve(3,3) DEXs that have come before it. It is the final piece of the ve(3,3) puzzle, closing the circuit on the flywheel and maximizing Beam's resiliency and strength. OlympusDAO bonded its $OHM token for assets like USDC and ETH, and used it for native liquidity pools (OHM/USDC, OHM/ETH) and static treasury assets to support a hard "backing price." This backing price was designed to offer peace of mind to investors, because if $OHM price fell below backing price, treasury assets would be liquidated to buy back $OHM and create equilibrium. The design was clever and was psychologically impactful - for a time. Solidly's ve(3,3) infrastructure built on OlympusDAO's (3,3) concept in 2022, completely revolutionizing the DEX experience at the time. Inexplicably, one of the core mechanics of (3,3) was left out of this new infrastructure - bonding. Similar to OlympusDAO's bonding mechanism, CoreLink offers $BEAM to the public at a discount that is determined dynamically based on market action on the $BEAM token. Users can purchase this discounted $BEAM directly from the CoreLink interface for USDC, ETH, and other bluechip tokens. These assets are then put to work in Beam's most trafficked and productive liquidity pools, earning trading fee revenue for veBEAM holders in perpetuity, regardless of market conditions and external liquidity provision. --- # 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/corelink.md?ask= ``` 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.