# Ecosystem Resources #### Official Links * Interactive App: [https://dotswap.app](https://dotswap.app/) * X (Twitter): [https://x.com/dot\_swap](https://twitter.com/dot_swap) * Telegram: * Discord: * Medium (Research & Announcements): [https://dotswap.medium.com](https://dotswap.medium.com/) * Media Kit: [Download Here](https://drive.google.com/drive/folders/1_XxAqMj6EV-yqZIEx7FiUD_apmB7HBzW) *** #### Technical & Strategic Roadmap (2026 Focus) Nexus Protocol follows a systematic development approach that balances foundational UTXO innovation with high-frequency capital efficiency. Institutional Custody Integration (Fireblocks) Partnering with Fireblocks to bring enterprise-grade custody and transfer networks to our PSBT workflows. This enhances capital efficiency and internal policy compliance, bridging the gap between rigorous self-custody rules and high-frequency intent matching. Enhanced Private Key Management Upgrading the core Nexus node cryptographic architecture to completely eliminate single points of failure, granting institutional makers flexible, distributed key management options (MPC) while operating the node. Splicing: Dynamic Channel Capacity Leveraging Lightning-adjacent Splicing technology, Nexus State Channels will dynamically adjust capacity in real-time "invisibly" based on settlement volume needs. This maximizes capital efficiency without requiring channel closure and service interruption. Options Trading & Automated Hedging Moving beyond spot AMM execution, the Nexus engine is actively integrating options primitives. By connecting automated hedging scripts directly into the Nexus Composer, liquidity providers can dynamically delta-hedge their FPSSL positions natively on Bitcoin. Vaults: Leverage & Lending Unlocking capital velocity by working with ecosystem collateralization protocols. Asset managers will be able to borrow against their productive Nexus LP positions or utilize dynamic leverage to amplify returns while enforcing strict programmatic liquidation boundaries within State Channels. --- # 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.on.nexus/resources-and-legal/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.