A capacity topic is a verification topic your compliance team registers so that a token can admit a custodian, a firm that holds tokens for its clients and runs the payout and fee operations of those holdings. Such a firm is not an investor, so the investor claims in a token's holder rule, the rule that says which identities may hold the token, may not describe it. DALP defines no capacity topic. You register one on your own system, issue it to the custodian's identity and decide which tokens accept it.
Here a custodian is the client-holding firm, not the asset role named Custodian that can freeze holdings and force transfers. A custodian firm needs no capacity topic when your claim issuers issue it the ordinary institutional claims the holder rule already asks of an institutional holder. Use a capacity topic when they do not.
Register the topic
Open “Compliance”, then “Verification topics”, and add a verification topic as Verification topics describes. The name is yours and cannot change once registered, because every issuer grant, rule and claim stores an identifier derived from it.
The examples on this page use intermediary, the name the Console's holder rule guidance uses for a capacity claim. Write your definition of the topic where your compliance team keeps its policies, for example “holds for clients and runs the payout and fee operations of those holdings, not own-book investment”, so a later reviewer knows what the claim attests.
Issue it to the custodian
Issue the capacity claim once for each custodian identity on each network, from the participant's “Verifications” tab with “Add verification”, as Verify a participant describes. Choose your capacity topic under “Verification topic”.
Your organisation's issuer identity signs the claim, through an account with the “Verification issuer” role. DALP does not issue a capacity claim for you, with one exception: a wallet recovery issues the organisation's standing claims again on the new identity, signed by the organisation's operations signer. You withdraw it later with “Revoke verification”, which keeps the record for audit and stops the claim counting. A revoked claim blocks the custodian's next transfer that depends on it and leaves settled transfers as they were.
Write the holder rule
The holder rule is the token's expression over verification topics. A holder of the token's Governance role sets it with “Edit holder rule” on the token's “Compliance” tab, or through PUT /api/, documented in the Platform API reference. When the token has an identity verification compliance module, the module's rule must pass as well.
Name the capacity topic as one more operand beside the investor claims:
sanctionsScreening AND (knowYourCustomer OR intermediary)Put every check that must apply to every holder outside the capacity branch. This form is wrong:
(sanctionsScreening AND knowYourCustomer) OR intermediaryIt passes any wallet whose identity carries the capacity claim without asking for sanctions screening. Read each OR in a rule as a second way in, and check what that branch skips. A wallet that holds the capacity claim from a trusted issuer passes its branch with no other check, so treat issuing the claim as an admission decision.
Choose how far trust reaches
A claim counts only when its issuer is trusted for its topic. Grant that trust to the issuer identity that signs the capacity claim, for the capacity topic and for the other topics the custodian's wallets need, in one of two places:
A token admits the custodian only when both hold: it trusts the issuer for the topic, and its holder rule names the topic. A grant with no rule that names the topic admits nobody, and a rule that names the topic with no grant admits nobody. Global controls, the compliance modules that run on every ordinary transfer in the system, apply in addition to the token's own rule, and the holder rule cannot switch them off. A custodian forced transfer and a recipient on the compliance bypass list skip them, as Compliance Policy describes.
Give each further capacity its own topic
A further holding capacity is a further topic with its own trust grant. Never widen an existing topic to cover it. A topic node in a rule carries only a topic id and a rule cannot test the data inside a claim, so a rule cannot tell two capacities apart inside one topic.
Check the custodian is admitted
Before the custodian's first transfer, run the transfer pre-check with the custodian's wallet as recipient. A missing capacity claim, or a claim from an issuer the token does not trust, appears as a blocker that lists the missing topic.