Can ERC-3643 See Clients Behind an Omnibus Wallet?
An ERC-3643 omnibus wallet is one token-holding address used by a custodian for several clients. In the reviewed T-REX contracts, that address resolves to one registered identity and one country code. The token cannot infer the client allocations behind it. The operating design must therefore say which controls remain on-chain and which are delegated to a custody sub-ledger.
TL;DR — Key Takeaways
- ✓The identity registry resolves the wallet to one identity; it does not read a client allocation file.
- ✓Country checks see the stored wallet country, while MaxBalanceModule groups balances by identity.
- ✓A wallet freeze does not identify which client caused the restriction.
- ✓Segregated wallets and omnibus custody need different evidence and exception workflows.

Editorial slot: November 20, 2026. First released and sources checked on November 22, 2026.
Which identity does the token verify?
The reviewed T-REX registry verifies the identity linked to the wallet address. For a wallet registered to the custodian, those checks concern the custodian rather than each client.
This review uses T-REX commit f1390127, checked on November 22, 2026. IdentityRegistry registerIdentity accepts one address, one identity and one country. isVerified then evaluates required identity claims. This is a reading of that reference implementation, not an audit of a live token.
The registration interface has 3 inputs: wallet, identity and country. It has no client-allocation argument.
T-REX IdentityRegistry, registerIdentity
The institutional RWA custody framework covers the wider custody decision. The design issue here is whether the chain-level holder matches the person whose eligibility the issuer intended to enforce.
Which controls change when clients share an address?
Controls change at different levels: country checks use a wallet attribute, balance caps can use an identity aggregate, and freezes act on wallet balances. A custody design must map each separately.
| Reference control | What it reads or changes | Omnibus consequence |
|---|---|---|
| Identity verification | Claims on the linked identity | Client eligibility is not inferred |
| CountryRestrictModule | Receiver country in the registry | Mixed client residence is invisible |
| MaxBalanceModule | Aggregate for the linked identity | The custody book can consume one cap |
| Wallet or partial freeze | An address or amount | A separate client attribution is needed |
The country restriction module and maximum balance module illustrate why the word holder is too vague for an integration document. Name the wallet, identity and client account explicitly.
Can segregated wallets preserve investor controls?
Segregated wallets can expose each investor to on-chain rules when the registry maps them to the correct investor identity. Separate addresses alone do not establish that mapping.
Illustrative design: a custodian manages 20 client wallets but registers all 20 against its own identity. A per-identity cap can still aggregate those balances. Registering each client wallet against its respective client identity changes that result, subject to the actual module configuration and legal onboarding process.
MaxBalanceModule keeps its balance accounting by identity within each compliance instance, rather than by an omnibus client account.
T-REX MaxBalanceModule, _IDBalance
For admission limits in a fund subscription flow, also review the difference between receiver capacity and payer funding. The wallet chosen as receiver determines where a capacity check lands.
What must the custodian report off-chain?
An omnibus arrangement needs client allocations, eligibility evidence and restriction records that can be reconciled to the chain balance. A transaction hash alone does not provide client look-through.
Our proposed operating agreement assigns an owner to each data feed: the custodian owns client allocations, the issuer owns transfer policy, and the administrator owns the reconciliation and unresolved-break queue. Set an agreed cut-off and define how corrections are approved.
For each reporting period, compare opening allocations plus subscriptions, trades and transfers minus redemptions with closing allocations. Compare their total with the on-chain wallet balance at a named block. Internal custody trades can change the client book without producing a token transfer; the reporting process must capture them.
A missed feed should trigger the agreed exception process. Do not mark every client eligible merely because the custody wallet still passes isVerified. Those are different assertions with different evidence.
What happens when one client is restricted?
A client-specific restriction needs both a custody-book action and a decision about the on-chain wallet. Otherwise one layer can remain transferable after the other is blocked.
The reference Token contract exposes address freezes, partial freezes and forced transfers. These address token balances, not client account identifiers. The issuer and custodian must agree who can request an action, how the affected amount is calculated, and how releases are reconciled.
An illustrative incident involves one client holding 8% of a custody wallet. Freezing that amount does not label the 8% with the client identity. The custodian must separately prevent that client from selling its book allocation and preserve the approval and release records.
This technical mapping does not decide sanctions or legal title. The holders-of-record analysis and private-fund beneficial-owner count address distinct legal counting questions.
When should the issuer choose a different model?
Use a different custody structure when the issuer needs direct investor-level enforcement that the omnibus sub-ledger cannot evidence. Convenience is not a substitute for an assigned control owner.
Before launch, ask the custodian to demonstrate a mixed-country allocation, a client becoming ineligible, a wallet recovery and a reconciliation break. Record whether each action is visible on-chain, in the sub-ledger or in both. This is a proposed acceptance review, not a report of tests performed here.
For Blockmaze procurement, ask for the deployed identity mappings and the custody reporting contract. This article makes no claim that a particular vendor implements client look-through. The practical deliverable is a control matrix that names who can observe and stop each investor action.
Frequently Asked Questions
Does ERC-3643 forbid omnibus custody?
The reviewed T-REX registration path takes a wallet, an identity and a country. It does not contain a separate omnibus admission decision. Whether a custodian is permitted to use that structure depends on the token rules, issuer terms and applicable custody requirements. The absence of a technical prohibition is not approval of the legal arrangement.
Can one omnibus wallet have a country for each client?
Not through the single country field examined in the reference registry. A country module reading that field sees the country attached to the wallet, regardless of the client allocation behind it. A look-through process or a different custom control would be needed to apply client residence rules to internal custody transfers.
Do separate wallets always solve investor holding caps?
No. A segregated wallet must also be linked to the intended investor identity. If every wallet points to the custodian identity, an identity-based balance cap can still aggregate the custody book. The issuer should review the identity mapping and the selected compliance module, as well as the number of wallets.
Can a partial freeze isolate one custody client?
It can immobilize an amount at a wallet, but the token does not assign that amount to a named custody client. The custodian needs a corresponding sub-ledger restriction and a reconciliation process. Otherwise the chain and the client statements can disagree about whose position is available to move.
Related Articles
What Happens When an ERC-3643 Investor Changes Country?
An ERC-3643 investor country is a uint16 ISO 3166-1 numeric code stored per wallet in the Identity Registry Storage, written by an agent at registration and changed only through updateCountry. In the T-REX reference code it is not read from ONCHAINID claims, so when an investor moves, nothing changes on-chain until an agent updates every wallet.
Can You Add a Holding Cap to a Live ERC-3643 Token?
In the T-REX reference code, MaxBalanceModule caps holdings per investor ONCHAINID using its own ledger, so it will not bind to a token with holders until the compliance owner hand-writes every identity's balance. Adding a cap to a live token is a migration, not a setting.