Encyclopedia DeFi · Entry 75
DeFi composability: reusing capabilities and inheriting dependencies
In this article
At a glance
Key facts
| Fact | Detail | Source |
|---|---|---|
| Common interface | ERC-20 enables token reuse across applications. | [1] |
| Claim layer | ERC-4626 shares represent a claim on underlying vault assets. | [2] |
| Changing dependency | A dependency may itself have an upgradeable implementation. | [4] |
A standard interface makes integration possible
An application can call a token’s transfer interface without inventing a new transfer format for each asset. A vault interface similarly exposes shares and underlying-asset operations. Shared interfaces reduce the mechanical work needed to connect contracts.
They do not prove identical economic behavior. A token can have issuer restrictions, and a vault can have strategy losses or withdrawal limits. Compatibility with a method signature is a smaller claim than compatibility with every assumption an integrator makes.
Map each dependency in a composed position
Consider a vault share deposited as lending collateral. The position depends on the vault’s assets and strategy, its share conversion and withdrawal rules, the oracle’s interpretation of that share, the lending market’s thresholds, and any relevant upgrade authority.
An accurate token interface lets these contracts connect; it does not independently verify the assumptions each one makes about the others. A withdrawal limit or changed share value in the vault can affect the collateral position downstream. Record this chain of dependencies when assessing the combined product.
Atomic execution does not remove continuing dependencies
A single successful transaction can connect several operations, but the resulting position persists afterward. Its dependency can be upgraded, its withdrawal rules can apply, and its underlying assets can change in value. Atomic execution only answers whether that transaction completed as a unit.
A useful research record lists each layer, what it promises, who controls changes and how to exit. Count independent underlying exposures rather than dashboard rows: several receipts can ultimately depend on the same asset, oracle or administrative authority.
Direct answers
Questions people ask
Do standard interfaces make the combined system safe?
No. Standards specify interaction conventions. They do not validate every economic assumption, dependency, implementation or future upgrade in a composition.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
Composability lets one application use another application’s tokens, contracts or data as a building block. It can combine useful operations, but it also carries dependencies forward. A vault share used as collateral still depends on the vault, its assets, price interpretation and the lending market that accepts it.
Scope: DeFi. Verification: verified · 2026-10-02T18:17:57.897Z.
Link to this claimCommon interface: ERC-20 enables token reuse across applications.
Scope: DeFi. Verification: verified · 2026-10-02T18:17:57.897Z.
Link to this claimClaim layer: ERC-4626 shares represent a claim on underlying vault assets.
Scope: DeFi. Verification: verified · 2026-10-02T18:17:57.897Z.
Link to this claimChanging dependency: A dependency may itself have an upgradeable implementation.
Scope: DeFi. Verification: verified · 2026-10-02T18:17:57.897Z.
Link to this claimRevision history
- — First publication after primary-source research and independent automated verification.
- — Expanded explanation: Map each dependency in a composed position. Worked examples are illustrative; source checks and independent verification are recorded separately.
On the Understand a swap path · You have reached the final entry in this path.
Source register
Sources and references
Retrieval dates and locators are recorded individually.- ERC-20: Token StandardEthereum Improvement Proposals
The token spending allowance is separate from a website connection.
Locator: Methods: approve, allowance, transferFrom · Version / scope: ERC-20 final · Retrieved: 2026-10-02Open source - ERC-4626: Tokenized VaultsEthereum Improvement Proposals
Vault shares, assets, previews, withdrawal limits and rounding.
Locator: Specification; Security Considerations · Version / scope: ERC-4626 final · Retrieved: 2026-10-02Open source - Oraclesethereum.org contributors
External observations and the trust boundary between data and consensus.
Locator: What is an oracle?; The oracle problem · Retrieved: 2026-10-02Open source - Proxy contractsOpenZeppelin
Proxy implementation changes and the authorization requirement.
Locator: TransparentUpgradeableProxy; UUPSUpgradeable · Version / scope: OpenZeppelin Contracts 5.x · Retrieved: 2026-10-02Open source - PoolAave
Collateralization, available liquidity and liquidation operations.
Locator: supply; withdraw; borrow; liquidationCall · Version / scope: Aave V3 documentation · Retrieved: 2026-10-02T17:03:44.834ZOpen source - Using Data FeedsChainlink
Feed update conditions, chain/feed-specific configuration and consumer checks.
Locator: Heartbeat and deviation thresholds; Data quality · Retrieved: 2026-10-02T17:38:46.139ZOpen source
Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.
Editorial method and correctionsDegrees of Satoshi editorial project. “DeFi composability: reusing capabilities and inheriting dependencies.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/defi-composability/