Which Contract Holds an ERC-7575 Fund Position?
An ERC-7575 external share token is the contract that records investor share balances when a vault separates its entry point from its ERC-20 representation. Custodians importing the vault address as the holding token can query the wrong contract or count one position more than once. The integration must resolve the share address before reconciling ownership.
TL;DR — Key Takeaways
- ✓Record the entry point, asset token and share token separately.
- ✓Group entry points by the common share contract before totaling holdings.
- ✓Validate the redemption authorization route when vault and share are different contracts.

Why can the vault address be the wrong balance source?
ERC-7575 exposes share() to identify the ERC-20 representation of a vault position. That method may return the vault itself or a different contract, so address equality must be checked.
A conventional ERC-4626 adapter often queries balanceOf on the same address used for deposits. Reusing that assumption for an external-share vault can produce a failed query, a meaningless zero or an incorrectly classified holding. The operational error is the address model, even if the subscription executed correctly. Even the right share token can mislead a holder report, because ERC-7540 vaults may lock or burn shares under a pending redemption.
Create separate registry fields for chain, entry point, underlying asset and share token. Resolve those fields from the deployed contracts and approved product configuration. Symbols and display names can help a reviewer, but they cannot replace contract identity.
ERC-7575 introduces share() so the ERC-20 share representation can be external to the entry point. One deposit address need not be one holding token.
ERC-7575 share method
How do several entry points create one position?
Multiple ERC-7575 entry points can use a common share token while accepting different asset tokens. The investor share balance belongs to the common token, not to a separate balance for each entry route.
Consider an illustrative fund with entry points V1 and V2, assets A1 and A2, and common share S. If an investor holds 250 units of S, querying that same balance through both configured routes must not produce a reported holding of 500. Deduplicate by chain and share contract before calculating the position.
Keep the subscription history by route for cash reconciliation, while maintaining a single holding record where the share contract is common. Depositing two different assets does not itself establish two legal share classes or different investor rights; verify those rights against the fund documents.
For the wider custody record, connect this mapping to institutional RWA custody controls. The contract map should explain how transaction records become a position statement.
Does share-to-vault lookup replace an approved registry?
ERC-7575 describes an optional share-to-vault lookup by asset. An integration should handle its absence explicitly and still verify the entry point selected for a transaction.
The optional lookup supports discovery, but a custodian also needs network identity, approved assets and lifecycle controls. An unsupported lookup should create a reviewable configuration exception. It should not cause an adapter to guess a vault from the token symbol or reuse a route from another chain.
When a mapping changes, retain its previous value and the evidence approving the new route. A new entry point can be compatible with the same share while changing operational dependencies. Reconcile transactions around the effective change so cash does not disappear between the old and new records.
In the V1/V2/S example, two entry points still reference one 250-unit share balance. Route count is not position count.
ERC-7575 multi-asset architecture; editorial example
Why can delegated redemption need different approval logic?
When vault and share contracts are separate, ordinary token approval assumptions require review. ERC-7575 explicitly flags delegated redemption where the owner and caller differ as a security consideration.
Trace which contract checks the investor authorization and which contract changes the share balance. Determine whether the deployment uses a trusted-forwarder design, an operator mechanism or another documented path. These are implementation choices; the external-share interface does not establish that any arbitrary caller can redeem.
Test an owner calling directly and an authorized service acting for that owner. Also test an unauthorized caller and an unintended receiver. A successful balance lookup proves only that the adapter found the share contract, not that its delegated exit flow is correct.
What belongs in the custodian acceptance record?
The acceptance record should join subscription cash, the share balance change and the fund register using explicit contract identities. A display label alone cannot connect those three records reliably.
For each supported entry point, retain asset(), share(), token precision, implementation identity and a traced subscription or redemption in a safe test environment. Confirm the shared position is counted once and the route-specific cash movement remains attributable. Record whether each entry point is an entry-only pipe without a reverse exit or a two-way route.
This procedure is for custody adapters and fund administrators integrating external shares. It does not determine legal title from a token interface. Use the RWA token standards framework to distinguish the technical representation from the issuer obligations described by the product.
Sources: ERC-7575 specification; ERC-4626 share model. Sources checked October 25, 2026. Numerical scenarios and acceptance procedures are editorial analysis, not reports of live fund incidents.
Frequently Asked Questions
Is the ERC-7575 vault always the share token?
No. The share method may return the vault itself, but it may also return an external ERC-20 token. Resolve the address and record it explicitly before querying investor balances. Existing adapters that assume the deposit contract is always the holding token need a separate integration path.
Can two deposit contracts represent one holding?
Yes. Multiple entry points can connect different asset tokens to a common share token. A custodian should preserve the cash history by entry route while deduplicating the holding by network and share contract. Otherwise the same investor balance can appear more than once in a portfolio statement.
Must the share token provide a vault lookup?
The ERC-7575 specification describes the share-to-vault lookup as optional for compatibility with existing shares. An integration should therefore support a documented registry or another verified configuration path when the lookup is absent. Missing discovery support should not trigger a guess based on token names.
Does this interface establish legal fund ownership?
The interface identifies the technical share representation and entry route. Legal ownership, register priority and enforcement depend on the product documents and applicable framework. Reconcile the technical balances with the appointed administrator rather than treating a successful contract query as a legal determination.
Related Articles
Should Tokenized Funds Use ERC-7540 Async Vaults?
ERC-7540 is Final and adds a mandatory Pending to Claimable to Claimed lifecycle that ERC-4626 cannot express. The spec concedes that shares received may not match convertToShares at request time, and defines no mandatory cancellation path.
Who Is the Transfer Agent for a Tokenized Security?
Legal ownership of a security lives in the master securityholder file, not in a wallet balance. SEC staff has confirmed a registered transfer agent may keep that file on a blockchain — but Section 17A registration, three-business-day turnaround under Rule 17Ad-2, and five-business-day posting under Rule 17Ad-10 still apply.