# Previous Issuers For full case studies on the issuers below, view our [Community Resources](https://docs.bondprotocol.finance/references/community-resources). * **Pendle**: Acquired ETH through bonds to establish liquidity on Arbitrum * **Threshold Network**: Deployed bonds in a multi-phase approach to deepen liquidity for tBTC and acquire protocol-owned liquidity on key Curve pools * **Redacted**: Acquired USDC through bonds to extend runway * **GMX**: Acquired DAI through bonds to fund growth initiatives * **Y2K Finance**: Acquired USDC to fund growth initiatives * **ShapeShift**: Acquired stablecoins to extend runway and fund operations * **JPEG’d:** Acquired CVX through bonds to bolster yield on their liquidity pools and increase protocol usage, establishing a revenue flywheel * **Ethos Reserve/ByteMasons**: Deployed a bond market to increase ERN (their stable asset) and OATH (their governance/revenue capturing token) liquidity and provide a low-friction path for new ecosystem entrants * **Lodestar Finance**: Acquired USDC through bonds to fund their security audit * **Dex Finance**: Utilized bonds to acquire a diverse range of assets to support multiple use cases * **Metavault DAO**: Acquired USDC through bonds to fund the development of their upcoming product and generate yield via their [new tokenomics model](https://twitter.com/MetavaultDAO/status/1654182302312693761?s=20) * **IQ.Wiki**: Acquired ETH through bonds to diversify the treasury --- # 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.bondprotocol.finance/products/permissionless-bonds/issuers/previous-issuers.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.