# Protocol Overview Plutus is a **multichain DeFi yield platform and an Arbitrum-native governance aggregator**, designed to optimize user rewards, maintain liquidity, and consolidate both governance power and protocol yield into the $xPLUTUS token. By leveraging [plsASSETs](/products/plsassets.md), liquid, yield-bearing versions of xTokens and veTokens, users can earn rewards without needing to lock capital for long periods. While users forgo direct governance rights from the underlying veTokens, that voting power is **aggregated and redirected through $xPLUTUS stakers**, who steer protocol-level decisions across the integrated partners. Plutus has collaborated with protocols such as **Berachain**, **Camelot, Stryke (formerly Dopex), Radiant, GMX, Sperax, and Jones** to launch governance-aligned products that offer users **enhanced yield and liquidity**, **without the need for long-term lockups**. Beyond governance aggregation, Plutus has expanded its offering through a line of vaults, [plvASSETs](/products/plvassets.md), yield-maximizing vaults built to serve as native DeFi primitives everywhere including Berachain, Superseed, Botanix, and Arbitrum. Plutus offers multiple automated yield strategies, including plvHEDGE, plvLOOP, and plvDOLO, with additional vaults under active development. All live vaults are accessible across supported chains at [plutus.fi/Vaults](https://plutus.fi/Vaults). As the protocol evolves, **vaults will become an increasingly central pillar of Plutus**, offering dynamic, composable strategies that complement the passive nature of plsASSETs and unlock new opportunities for DeFi-native yield generation across **not only Arbitrum but all chains**. ### From Team to Community: A New Era of Plutus On **May 13th, 2024**, the original Plutus team announced a planned [transition to a decentralized, community-led model](https://medium.com/@plutusdao.io/decentralizing-plutus-b8456dfbbbbe). Rather than allow momentum to fade, the Plutus community stepped up, assuming full control over treasury operations, development, and protocol direction. The transition was formalized on July 7th, 2024, when the [official Snapshot proposal](https://snapshot.box/#/s:plutus-dao.eth/proposal/0x02e5ab42e8c3391a70842d59272a2cb91762bdfbc366e3bc4868c040b63120df) passed with overwhelming support, marking the beginning of the community-led era of Plutus. This was the moment Plutus truly **became a DAO**. The core team was selected by community vote, and all major protocol decisions, from emissions and buybacks to product priorities, are now governed through on-chain proposals and Snapshot voting. For the first time, the direction of the protocol is fully determined by its stakeholders, aligning power, responsibility, and rewards in the hands of the Plutus community. Since the transition, Plutus has: * **Unwound unsustainable legacy systems** that had left many Plutons with locked capital and unstable pegs. * **Established transparent**, **decentralized treasury management,** including **weekly team reviews**, **quarterly reports**, and **annual performance summaries** to keep the community fully informed and accountable. * Introduced high-performing vault primitives, including the launch of [plvHEDGE](https://medium.com/@plutusdao.io/introducing-plvhedge-an-automated-funding-arbitrage-vault-f2f222fa8c56), our first **in-house designed trading strategy**. * **Reaffirmed its commitment to sustainable**, **real yield**, including the implementation of a **1:0.8 soft floor on all plsASSETs** to ensure long-term value retention across the ecosystem. This initiative, backed by **treasury buybacks**, swiftly addressed one of old Plutus’ core issues: **unstable pegs and unreliable redemption value**. * And much, much more... from **expanding chains** to **new vaults** and **ecosystem-wide improvements**. To stay up to date and get involved, [join the community on Discord](https://discord.gg/plutusdao-io). Today, Plutus continues to build toward a resilient, Pluton-owned future, guided by the same values that empowered its community to take the reins. --- # 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.plutus.fi/protocol-overview.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.