# CryptoLegacy: Protocol Integrations for Flexibility

CryptoLegacy integrations are designed to extend **what actions may be executed**, not who controls assets or how execution decisions are made. All integrations operate within the same execution model: predefined rules, explicit permissions, and on-chain enforcement.

Integrations are available either as native interfaces or as execution plugins that can be enabled by the contract owner and, where permitted, by beneficiaries under predefined confirmation thresholds.

### **dApp Integration**

CryptoLegacy is available as a **Safe App**, allowing users who custody assets in Safe wallets to interact with CryptoLegacy directly.

In practice, this integration is primarily used to **manage token approvals** — granting, reviewing, and revoking allowances required for execution — without changing custody models or moving assets. The Safe App provides a familiar and secure interface for preparing assets for execution while keeping full control within the Safe.

### **Execution Plugins and Future Integrations**

Additional protocol integrations are implemented or planned as **execution plugins**. These plugins allow specific, predefined actions to be executed during the Distribution phase, subject to protocol rules and confirmation thresholds.

Planned integrations include:

* **Aave Plugin**\
  Enables predefined lending, withdrawal, and position management actions during Distribution.
* **Uniswap Plugin**\
  Enables token swaps and position closure within predefined execution constraints.
* **1inch Plugin**\
  Enables token swaps through aggregated liquidity, subject to execution permissions.
* **Lido Plugin**\
  Enables staking and unstaking actions (ETH/WETH ↔ stETH/wstETH) as predefined execution steps.
* **DeBridge Plugin (Cross-Chain Swaps)**\
  A dedicated execution plugin planned to enable **explicit cross-chain swaps** between CryptoLegacy contracts deployed on different blockchains that share the same address. Cross-chain swaps will only be possible if this plugin is explicitly enabled and executed under predefined execution rules and confirmation thresholds.

All integrations operate strictly within the CryptoLegacy execution model. They do not introduce custody, discretionary control, or automatic asset movement beyond what is explicitly defined and approved in advance.


---

# 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.cryptolegacy.app/protocol-mechanics/cryptolegacy-protocol-integrations-for-flexibility.md?ask=<question>
```

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.