Custody

Switch new accounts on or off#

Use the New accounts switch in the “Availability” row of the configuration. Its value reads “Available”, “Paused while unhealthy” or “Disabled”. A configuration can be available for new accounts while its execution health needs attention. Check both states before directing participants to it.

Switching “New accounts” off on a configuration that is offered to investors or is the default opens “Disable new accounts?”. For an offered configuration it says “This provider is offered to investors. Disabling new accounts also withdraws it from investors. Enabling new accounts later does not offer it again. You must turn on ”Offered to investors“ yourself.” For the default it adds that the switch removes it as the default and the owner must designate the default provider again. Select Disable and withdraw to continue or “Cancel” to keep it.

Make a provider the default and offer it to investors#

The Investors row holds two settings:

• Default provider reads “Default for new investors” on the default and “Not the default” on the others, which carry “Make default”. To use a healthy, enabled configuration during investor onboarding, select “Make default”.
• Offered to investors reads “Investors can choose it” or “Not offered”. The default is always offered to investors, and its “Offered to investors” switch is locked with “Always offered while it is the default investor provider”.

Both “Make default” and “Offered to investors” stay locked with “Available once the provider is healthy and open to new accounts.” until the configuration reads “Healthy” and “New accounts” reads “Available”.

To let investors choose another healthy configuration enabled for new accounts, turn on Offered to investors on it. When more than one configuration is offered, the investor portal asks the investor to choose during onboarding between an embedded wallet, a browser wallet and a managed account, and suggests the default. A Privy configuration is offered as the embedded wallet. Any other embedded-wallet configuration is listed as not available and cannot be selected. When only the default is offered, the investor goes straight to it.

A configuration that is not offered is never listed, and the platform refuses a participant that an investor creates on it. An Owner of the active organisation or a platform administrator can still create a participant's managed account on it, provided it is healthy, enabled for new accounts, and lists the account's network. When the organisation offers no configuration to investors, any member can create managed accounts on a healthy configuration that is enabled for new accounts, for the participants they create. Turning off new accounts on a configuration withdraws its offer.

Changing this selection does not move existing accounts to another provider. Check Default for new investors after saving.

Add a network to a managed provider#

You cannot remove a network from a configuration after you add it, so add a chain only when the configuration will serve it.

In the “Connection” row of a configuration whose “Signing” reads “Managed by DALP” and whose provider supports EVM, select Add network beside “Networks”. Enter the “EVM chain ID” and select “Add network”, or “Cancel”.

An invalid entry reads “Enter a positive whole number.” and a success toasts “Network added to custody provider”. The platform checks that the provider can sign on that network before adding it. Existing networks and accounts stay in place. “Networks” shows a network the organisation runs or may add by its name, and any other network by its chain ID. Adding the same chain again makes no change. You can then select the network on Networks, under “Infrastructure” in the sidebar.

For Utila, the platform checks the chain against the networks stored in the configuration's Networks field, not against anything you type in this step. “Add network” is refused for a chain that has no line there. To add a chain to a Utila configuration, first rotate the credentials with the new chain ID network name line added to “Networks”, as Rotate managed credentials describes, then enter the chain ID here and select “Add network”.

Use the provider actions menu#

The Provider actions menu in the card header holds four actions:

• Test connection checks the provider connection.
• Reconcile wallet roles reapplies, at the provider, the role the platform records for each wallet of that configuration, so a custodian policy can tell an investor wallet from an infrastructure wallet. On DFNS, Fireblocks and Ripple Custody it also renames each wallet that still carries a name the platform chose, so the name states the wallet's role and the organisation's current name. On Ripple Custody it rewrites the account description for that role too, and each rename waits for approval under your Ripple policies like any other account intent. A wallet name that a person chose stays as it is.
• Rotate credentials is offered only for a configuration whose credentials DALP manages.
• Copy configuration ID toasts “Configuration ID copied”.

Rotate managed credentials#

Open the “Provider actions” menu and select Rotate credentials. The sheet “Rotate credentials for <provider>” says “Replace credentials at the provider. The configuration is probed after rotation.” and has no reason field.

Fill in only the metadata and credential fields you want to change. A field left empty reads “Leave empty to keep the current value.” and keeps its stored value. “Replace every credential” appears only for a configuration on organisation credentials, not for the platform vault, and replaces the whole credential set with the fields you enter (“Enter the whole credential. Optional fields left empty are removed.”). Then select Probe and rotate credentials. The platform probes the replacement against the provider and saves it only when the probe succeeds. A failed probe leaves the current credentials in place. Rotation preserves the configuration's provider and credential source.

For Utila, the rotation form opens with the stored metadata, Networks included, and the platform saves the fields as the form holds them when you rotate. Edit “Networks” to add, change or remove a chain line. A chain with no line has no signing lane, so do not remove the line of a chain that has accounts.

To add a chain: bind the chain in “Networks”, leave every credential field empty so the stored key stays, and rotate. The platform probes with the new “Networks” before it saves them. Then select “Add network” for the chain. Fill in only the key, standby key or “Signing agent secret” you replace, and leave the others empty to keep their stored values.

Select “Replace every credential” to remove the optional standby key or “Signing agent secret”: the credentials you enter then replace the whole set.

To undo a rotation, rotate again with the earlier values. Each rotation is probed before it is saved, so the earlier values must still work in the provider.

If another administrator rotates the same configuration at the same time, a version conflict can reject one request. Refresh the configuration and check the saved state before retrying. Do not assume that an error means no change was saved.

Quarantine or recover execution#

Select Quarantine execution in the danger area at the foot of the card. The sheet “Quarantine <provider>” asks for the “Audit reason for quarantine or recovery” (“Recorded in the audit log.”). “Quarantine execution” stays unavailable until the reason is not empty, and “Cancel” closes the sheet. The card then shows the notice “Execution is quarantined and signs nothing” and the health reads “Quarantined”. Each notice names its provider in its title, and a screen reader announces “Recover execution” together with that title, so several quarantined providers stay apart.

Correct the underlying incident, then select Recover execution on that notice, enter a new reason and confirm in “Recover <provider>”. The Console probes the provider first and recovers the configuration only when the probe succeeds. When the probe fails, it reads “The provider failed the probe, so execution stays quarantined. Fix the provider, then recover again.”

Delete a provider#

Delete provider sits beside “Quarantine execution” in the danger area. The sheet “Delete <provider>” says “Deletes the configuration. The platform refuses while any account or custody record still uses it.” Select “Delete provider” to confirm. The Console toasts “Unused provider deleted”. There is no reason field.

Utila fields#

Utila custody appears in the provider list only when the deployment operator has switched Utila on with custody.providers.utila.enabled, as Prerequisites describes. If the provider list does not show it, ask the platform operator who runs the deployment to switch it on. Before you start, the Utila vault admin creates the service account and the platform operator lists the DALP egress addresses, as Set up Utila custody describes. Then enter:

Network identifier names the network the configuration serves. “Networks” maps every network the configuration will serve to its Utila network name, so list each of them there. The form marks every optional field with (optional) after its label. List the chain from “Network identifier” in “Networks” too. A chain with no Utila network in “Networks” is refused, and the refusal names the fix. The form shows “Enter one network per line: a chain ID, a space, then the network name.” for a line that does not follow the format.

Provider card#

Each configuration is a card, named for its provider. From the top:

The latest audit event names one of these actions:

• Quarantined
• Recovered
• Custodian tenant recorded
• Custodian tenant backfilled
• Designated as the investor provider
• Offered to investors
• Withdrawn from investors
• Designation as the investor provider removed
• Switched off for new accounts
• Switched on for new accounts

A quarantine or recovery also shows, in brackets, the reason typed for it. Quarantine, recovery, designation as the investor provider, offering the configuration to investors or withdrawing it, and switching new accounts off or on each record an audit event. Disabling new accounts on a configuration that was offered to investors, or that was the investor provider, also records that it was withdrawn or is no longer the investor provider. Adding a configuration, rotating its credentials and deleting it are recorded in the Audit trail with the configuration before and after. They do not appear under Latest audit event.

Custody providers and the custody gateway#

The provider configurations on this page hold the platform's own custody accounts. They do not create gateways, enable coins or grant gateway roles. A client's custody gateway is set up on the custody gateway add-on under “Asset lifecycle”. A coin set to wait for custody on the add-on holds the client's receipts until the custodian accepts the coins. Set up the custody gateway says how, Create a client gateway opens one, and Review deposits and withdrawals covers the records it produces.

Troubleshooting#

For historical tab names and their current operator surfaces, read Legacy custody books. The reference explains which journal tasks are retired and where Cases, destination review and reconciliation remain.