> For the complete documentation index, see [llms.txt](https://docs-v4.venus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-v4.venus.io/technical-reference/reference-periphery.md). # Periphery Venus Protocol periphery contracts extend the lending markets with product workflows, swap execution, price-deviation monitoring, and emergency controls. They are separate contracts with their own upgrade, ownership, signer, or Access Control Manager (ACM) trust boundaries. > **Version scope:** These references follow the stable [`venus-periphery` v1.2.0 release](https://github.com/VenusProtocol/venus-periphery/tree/v1.2.0). Most deployed components are upgradeable proxies, while `SwapHelper` and PositionAccount implementations use different deployment patterns. Use the [deployed-contract registry](/deployed-contracts/periphery.md) to find an address, then verify its current implementation and configuration on the relevant explorer before integrating or granting approvals. ## Overview The public references cover the following systems: * [**RelativePositionManager**](/technical-reference/reference-periphery/relative-position-manager.md) — orchestrates Venus Trade positions and deterministic PositionAccount clones on BNB Chain. * [**LeverageStrategiesManager**](/technical-reference/reference-periphery/leverage-strategies-manager.md) — enters and exits leveraged positions using Core Pool flash loans on BNB Chain. * [**SwapHelper**](/technical-reference/reference-periphery/swap-helper.md) — executes backend-signed batches of approvals, arbitrary calls, and token sweeps for BNB trading flows. * [**SwapRouter**](/technical-reference/reference-periphery/swap-router.md) — swaps an input token and supplies or repays through BNB Core Pool markets. * [**DeviationSentinel**](/technical-reference/reference-periphery/deviation-sentinel.md) — compares configured oracle and DEX prices and routes qualifying incidents to EBrake on the networks listed in the registry. * [**EBrake**](/technical-reference/reference-periphery/ebrake.md) — exposes selected tighten-only Comptroller actions to explicitly authorized incident-response callers. ## Key Features * Flash-loan-based atomic leverage execution * EIP-712 authorization for SwapHelper call batches * EIP-1153 transient callback state in LeverageStrategiesManager * Post-operation account-liquidity validation * Caller-selected output floors for quoted swap paths; full-repayment SwapRouter paths instead bound token input with `maxAmountIn` or `msg.value` * On-chain deviation checks and restricted emergency parameter tightening ## Deployment The trading contracts are deployed on BNB Chain. DeviationSentinel and EBrake also have deployments on selected additional networks. See [Deployed Contracts](/deployed-contracts/periphery.md) for the current published network and address list; a contract's presence in source does not establish that it is deployed on every Venus network. --- # 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-v4.venus.io/technical-reference/reference-periphery.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.