# Documentation - Business - [Business documentation](/docs/business): Choose the right DALP business guide for evaluation, market context, use-case routing, compliance posture, market data infrastructure, terminology, and legal notices before an architecture review. - [Digital asset lifecycle management](/docs/business/introduction): Learn what digital asset lifecycle management means in DALP, how regulated EVM asset workflows connect lifecycle controls, compliance, custody-routed signing, settlement, and audit evidence. - [What institutions require](/docs/business/market-challenges): Institutional digital asset programmes require operating controls after the first token is issued: lifecycle control, compliance enforcement, custody-routed signing, settlement coordination, servicing, deployment choice, and audit evidence. - [Lifecycle platform](/docs/business/digital-asset-lifecycle-platform): What a digital asset lifecycle platform does, how DALP applies that model to regulated EVM-compatible tokens, and where institution-owned responsibilities begin. - [DALP solution model](/docs/business/dalp-solution): Digital Asset Lifecycle Platforms (DALPs) provide regulated digital asset operations infrastructure for asset control, compliance-aware transfers, settlement coordination, and operating evidence. - [Platform capabilities](/docs/business/dalp-overview): DALP combines issuance, compliance, custody controls, settlement, servicing, exception handling, and operating evidence in one platform for regulated digital asset operations after launch. - Use cases - [Use cases](/docs/business/use-cases): Compare DALP asset classes and instrument templates against the same EVM asset lifecycle: issuance, holder controls, servicing actions, event history, and integration APIs. - [Corporate bonds](/docs/business/use-cases/corporate-bonds): DALP gives fixed-income programmes an EVM foundation with compliant asset creation, atomic settlement, pull-based coupon claims, and maturity redemption controls. - [Equities](/docs/business/use-cases/equities): Model common shares, preferred shares, and employee equity awards on DALP with holder eligibility, transfer controls, template-specific governance features, and balance snapshots for shareholder records. - [Private equity](/docs/business/use-cases/private-equity): Model private equity and venture capital fund units in DALP with NAV pricing, fund metadata, management fee parameters, compliance checks, and clear operator responsibilities. - [Funds](/docs/business/use-cases/funds): Model open-end mutual funds, money-market funds, ETFs, and private-equity funds on DALP with NAV-priced subscription, AUM and transaction fees, holder eligibility, and historical balance evidence for investor reporting. - [Real estate](/docs/business/use-cases/real-estate): Model digital real estate as a capped real-asset instrument with property metadata, controlled issuance, compliance checks, and investor-facing asset details. - [Precious metals](/docs/business/use-cases/precious-metals): Issue gold, silver, platinum, and palladium tokens in DALP with metal type, purity, unit-of-account pricing, vault storage context, and holder eligibility controls. - [Stablecoins](/docs/business/use-cases/stablecoins): Bank-issued stablecoin programmes use DALP for controlled EVM issuance, role-gated minting, holder transfers, redemption burns, collateral-claim checks, compliance controls, operational history, and API integration around the token lifecycle. - [Deposit certificates](/docs/business/use-cases/deposits): Model digital bank deposits and certificate-of-deposit style products on DALP with controlled issuance, holder eligibility, maturity terms, deposit detail claims, price feeds, and auditable token records. - [Structured products](/docs/business/use-cases/structured-products): Use DALP structured instrument templates to govern token issuance, holder controls, and lifecycle events for products whose payoff terms and reserve processes remain outside the platform. - [Trading venue](/docs/business/trading-venue): How the DALP Trading Venue runs session-based exchange trading on the platform your institution already governs: trading calendars, opening auctions, private placements, stop orders, market-maker quoting, and an audited trade-bust remedy, all non-custodial and compliance-gated. - [Compliance & security](/docs/business/compliance-security): DALP embeds regulatory controls into transaction execution so regulated asset programmes can enforce eligibility, identity, and transfer rules before state changes settle. - [Market data infrastructure](/docs/business/market-data-infrastructure): How DALP market data feeds connect issuer-signed prices, exchange-rate feeds, directory registration, adapter reads, and token valuation controls. - [Glossary](/docs/business/glossary): Buyer-friendly definitions for digital assets, regulated assets, compliance, custody, settlement, and DALP platform terms. - Legal - [Terms of Service](/docs/business/legal/terms-of-service): Terms and conditions governing the use of the SettleMint Digital Asset Lifecycle Platform. - [Privacy Policy](/docs/business/legal/privacy-policy): How the SettleMint Digital Asset Lifecycle Platform collects, uses, stores, and protects personal data. - Architects - [Architecture documentation](/docs/architects): Choose the right DALP architecture guide for the platform map, design principles, concepts, components, flows, integrations, data availability, operability, and self-hosting decisions. - Overview - [Architecture overview](/docs/architects/overview): Map the DALP control plane before your architecture review: what the platform owns, what the institution still decides, and which detail pages to read next. - [Principles and scope](/docs/architects/overview/principles-and-scope): Client-facing architecture responsibilities for DALP, written for review teams evaluating regulated digital asset operations on EVM networks. - [System context](/docs/architects/overview/system-context): See who connects to DALP, where each trust boundary sits, and how system-scoped infrastructure keeps assets, identities, compliance rules, and factory registries separated by operating context. - [Asset model](/docs/architects/overview/asset-model): See how DALP structures institutional digital asset lifecycle management across asset templates, SMART Protocol contracts, identity, compliance controls, custody routing, settlement, monitoring, and APIs. - [Key flows](/docs/architects/overview/key-flows): Index of the main DALP system flows, covering shared platform operations, asset lifecycle capabilities, feed updates, and settlement workflows with links to detailed walkthroughs. - [Lifecycle after issuance](/docs/architects/overview/lifecycle-after-issuance): How DALP operators manage an issued asset after deployment, from the asset detail workspace through supply, transfer, pause, role, compliance, feature, and audit operations. - [Quality attributes](/docs/architects/overview/quality-attributes): Assign security, reliability, operability, and evidence questions to the layer that owns them: request control, durable execution, on-chain enforcement, or indexed visibility. Each layer has a distinct failure mode and a distinct support path. - [Deployment topology](/docs/architects/overview/deployment-topology): Current DALP process topology, runtime zones, data paths, external dependencies, scaling boundaries, recovery domains, and operator ownership across managed, customer-hosted, hybrid, and restricted deployments. - [Data domains](/docs/architects/overview/data-domains): Client-facing data-domain map for DALP, showing which records are on-chain, which are off-chain, which are indexed, and who owns each governance decision. - **Reference** - [Architecture one-pager](/docs/architects/overview/architecture-one-pager): All eight DALP systems, their sub-components, and their external dependencies on one page, formatted for RFP, security, and integration reviews. - [Capability docs matrix](/docs/architects/overview/capability-docs-matrix): Map DALP capabilities to the public documentation pages that explain the architecture, operator workflow, API integration path, and review notes for each capability. - Concepts - [Digital asset modeling](/docs/architects/concepts/tokenization-modeling): How DALP composes a deployable digital asset from an instrument template, metadata, token features, and compliance rules without requiring a new contract for every business case. - [Trading venue market structure](/docs/architects/concepts/trading-venue-market-structure): How the Trading Venue combines order reservation, trading authorization, price bands, trading calendars, call auctions, stop orders, private markets, and trade busting into a session-aware permissioned exchange without pooled custody. - Components - [Component catalog](/docs/architects/components): Use the DALP component catalog to find the platform surface, infrastructure service, asset contract layer, token feature, or capability that owns an architecture decision, integration handoff, control, or evidence trail. - Platform - [Overview](/docs/architects/components/platform): The platform layer is where operators, integrators, and administrators enter DALP. It explains how the Console, Platform API, and System Factory route requests through shared authentication, authorization, wallet verification, and audit controls. - [Console](/docs/architects/components/platform/console): The Console is DALP's authenticated web interface for asset lifecycle operations. It gives operators a guided view over asset design, holdings, compliance checks, and theme configuration while keeping execution, policy, and audit evidence in the platform services behind it. - [Platform API](/docs/architects/components/platform/platform-api): The Platform API is the programmatic entry point for DALP asset, compliance, servicing, and settlement operations. It exposes versioned API documentation, authenticated routes, tenant-scoped data access, and consistent request and response contracts for integration teams. - [System Factory](/docs/architects/components/platform/system-factory): How DALP creates a system for an organisation, keeps assets scoped to that system, and uses the token factory registry to isolate multi-tenant reads. - Infrastructure - [Infrastructure overview](/docs/architects/components/infrastructure): The infrastructure layer coordinates the execution services that preserve DALP workflows, prepare EVM transactions, route signing, submit chain operations, index events, route RPC traffic, and provide trusted feed data behind the platform interfaces. - [Workflow Engine](/docs/architects/components/infrastructure/workflow-engine): How DALP persists long-running operations, serializes work by domain key, resumes after interruption, and coordinates signing, broadcast, confirmation, and indexed visibility. - Advanced accounts - [Advanced accounts architecture](/docs/architects/components/infrastructure/advanced-accounts): Understand how DALP uses ERC-4337 smart accounts, EntryPoint routing, bundlers, paymasters, and validator modules for sponsored and threshold-controlled transactions. - [Advanced accounts design](/docs/architects/components/infrastructure/advanced-accounts/advanced-accounts-design): How DALP's account abstraction layer is structured, why the transaction queue owns the EOA-vs-smart-wallet decision, and the invariants that keep the system consistent across setup, invitations, and ordinary transaction flow. - [UserOperations](/docs/architects/components/infrastructure/advanced-accounts/user-operations): How UserOperations carry smart-account requests through DALP's smart wallet, bundler, EntryPoint, signing, and transaction tracking path. - [Bundlers](/docs/architects/components/infrastructure/advanced-accounts/bundlers): How DALP exposes an authenticated bundler JSON-RPC endpoint for ERC-4337 discovery, UserOperation submission, and ERC-7677 paymaster sponsorship. - [Paymasters and gas sponsorship](/docs/architects/components/infrastructure/advanced-accounts/paymasters-and-gas-sponsorship): How DALP uses system paymasters to sponsor eligible advanced accounts transactions without changing identity, custody, or asset policy checks. - [Nonce lanes and ordering](/docs/architects/components/infrastructure/advanced-accounts/nonce-lanes-and-ordering): How DALP maps UserOperations to ERC-4337 nonce lanes, why three distinct work states matter, and the trade-offs between strict, grouped, and independent ordering. - [Key Management](/docs/architects/components/infrastructure/key-management): Understand how DALP routes each signing request to local signing, DFNS, Fireblocks, or Luna HSM while keeping custody-provider policy outside the business workflow. - [Transaction Signer](/docs/architects/components/infrastructure/transaction-signer): The Transaction Signer prepares, signs, broadcasts, and confirms EVM contract transactions through EOA, smart-wallet, custody-provider, and HSM-backed signing paths. - [Contract Runtime](/docs/architects/components/infrastructure/contract-runtime): The Contract Runtime turns DALP operations into typed smart contract reads and writes. It validates target contracts, encodes calls from ABIs, routes writes through custody or local signing paths, waits for receipts when required, and normalises contract errors for API and workflow callers. - [Broadcast](/docs/architects/components/infrastructure/broadcast): The Broadcast is DALP's in-platform RPC control plane for outbound EVM JSON-RPC traffic. It routes every chain call across a pool of configured upstreams, scores them on tip lag and health, and retries and fails over transparently so application code keeps using one network configuration. - [EVM RPC Node](/docs/architects/components/infrastructure/evm-rpc-node): The EVM RPC Node is the configured EVM JSON-RPC endpoint that DALP uses for transaction submission, chain reads, event indexing, and private or managed node access. - [Feeds system](/docs/architects/components/infrastructure/feeds-system): The Feeds system maps subjects and topics to active price or foreign exchange feeds, so DALP workflows, token contracts, APIs, and external consumers can resolve current market data without hard-coding feed addresses. - Asset Contracts - [Asset Contracts](/docs/architects/components/asset-contracts): DALPAsset is the recommended configurable contract type for new digital asset projects, with legacy specialized types remaining supported for existing deployments. - [SMART Protocol integration](/docs/architects/components/asset-contracts/smart-protocol-integration): How DALP uses SMART Protocol (ERC-3643) for identity-aware asset tokens, per-asset compliance checks, and regulated transfer enforcement. - [ERC-3643 compliance standard](/docs/architects/components/asset-contracts/erc-3643-compliance-standard): How ERC-3643 maps to DALP's SMART Protocol token model, including the Solidity and Hardhat contract stack, supported ERC standards, permissioned token controls, identity registries, trusted issuers, claim topics, compliance modules, and EVM-only transfer enforcement. - [DALPAsset](/docs/architects/components/asset-contracts/dalp-asset): Reference for the configurable DALP asset contract: factory inputs, always-included controls, feature ordering, role gates, and operating boundaries. - [Legacy-equivalent presets](/docs/architects/components/asset-contracts/instrument-profiles): How DALPAsset presets compose token features, compliance modules, and instrument parameters for bond, equity, fund, stablecoin, deposit, real estate, and precious metal assets. - [Legacy types](/docs/architects/components/asset-contracts/legacy-types): DALP still supports the seven specialized contract types. Use DALPAsset for new configurable instruments, and keep legacy types when an existing token or fixed feature composition depends on them. - [Per-asset RBAC](/docs/architects/components/asset-contracts/rbac): Assign a role on one asset and a compromised credential can only affect that asset. Separate keys for governance, supply, custodian, and emergency duties contain the blast radius to the specific token where the breach occurred. - [Deployment Architecture](/docs/architects/components/asset-contracts/deployment-architecture): Factory deployment pattern for DALP asset tokens, covering CREATE2 deterministic addressing, initialization invariants, deployment failure modes, and custodian administrative controls. - Token Features - [Token features overview](/docs/architects/components/token-features): Token features attach fees, governance, lifecycle, yield, permit, and conversion behavior to DALPAsset tokens during issuance or later configuration. - [Feature constraints](/docs/architects/components/token-features/feature-constraints): Understand DALP token feature dependencies, mutually exclusive pairs, feature-closure expansion, validated configuration ranges, and the split between UI, API, and smart-contract enforcement. - [AUM Fee](/docs/architects/components/token-features/aum-fee): Time-based management fee on DALPAsset. Accrues over time against time-weighted token supply and is collected by minting new tokens to the configured fee recipient. - [Transaction Fee](/docs/architects/components/token-features/transaction-fee): Per-transaction token fee that deducts a basis-point fee from mint, burn, transfer, and redemption events before downstream checks and audit reads consume the final amount. - [Transaction fee accounting](/docs/architects/components/token-features/transaction-fee-accounting): Explains how DALP records per-operation fee obligations for off-chain invoicing without collecting tokens on-chain. Covers rates, exemptions, reconciliation, and audit events. - [External Transaction Fee](/docs/architects/components/token-features/external-transaction-fee): Fixed mint, burn, and transfer fees collected in a separate ERC-20 token. Covers fee token approvals, governance controls, freeze behavior, and operational failure modes. - [Voting Power](/docs/architects/components/token-features/voting-power): Delegated, checkpointed voting weight for DALPAsset tokens, enabling governance contracts to read current or historical votes without moving the asset. - [Historical Balances](/docs/architects/components/token-features/historical-balances): Timestamp checkpoints written after every token operation let reporting, yield, and snapshot logic read point-in-time balances and total supply without changing transfer amounts. - [Permit](/docs/architects/components/token-features/permit): EIP-2612 gasless approvals for DALPAsset tokens. Holders sign approval messages off-chain, while a relayer submits the permit on-chain without changing transfer compliance. - [Maturity Redemption](/docs/architects/components/token-features/maturity-redemption): How DALP handles bond maturity redemption: operator maturity actions, treasury funding and allowance readiness, indexed solvency signals, and holder redemption after maturity. - [Fixed Treasury Yield](/docs/architects/components/token-features/fixed-treasury-yield): Fixed-rate yield paid to token holders at periodic intervals from a treasury. Holders claim completed-period yield, and Historical Balances supplies the snapshot data used for entitlement calculation. - [Dividend Yield](/docs/architects/components/token-features/dividend-yield): Declared cash dividends with a record-date snapshot, Merkle entitlements, and holder claims paid in the denomination asset from a treasury. - [Interest Yield](/docs/architects/components/token-features/interest-yield): Continuous interest accrual at an annual rate, claimed in the denomination asset from a treasury, with accrued interest that a conversion can consume instead of paying in cash. - [Conversion](/docs/architects/components/token-features/conversion): How DALP models convertible instruments with a loan-side Conversion feature and target-side Conversion Minter feature, including how accrued interest settles on a full conversion. - Capabilities - [Overview](/docs/architects/components/capabilities): Capabilities are optional system addons for asset operations. They add focused workflows for orderbook trading, atomic settlement, and issuer-signed market data without putting every workflow into an asset contract. - [Trading Venue](/docs/architects/components/capabilities/trading-venue): The Trading Venue capability provides a permissioned central limit orderbook per deployment: identity-registered participants trade listed platform token pairs with non-custodial reservation, deterministic matching, and failure-isolated on-chain settlement. - [XvP Settlement](/docs/architects/components/capabilities/xvp-settlement): The XvP Settlement capability provides atomic cross-party token exchanges with all-or-nothing local execution, per-sender approvals, expiration controls, and optional hashlock coordination for referenced external legs. - [Token Sale](/docs/architects/components/capabilities/token-sale): The Token Sale capability provides compliant primary distribution infrastructure for Digital Asset Initial Offerings (DAIOs), with multi-currency payment support, optional presale, optional vesting, a seven-phase lifecycle, soft cap protection, and identity-gated buyer eligibility. - [Issuer-signed scalar feed](/docs/architects/components/capabilities/issuer-signed-scalar-feed): Issuer-signed scalar feeds let trusted issuers publish signed integer values for a subject and topic, then expose the latest value through a Chainlink-compatible read interface. - Flows - [Overview](/docs/architects/flows): Explanation of the main DALP operational flows, how platform flows support capability-specific workflows, and which flow page to read for signing, issuance, identity recovery, compliance transfers, data feeds, distributions, XvP settlement, and trading venue orders. - [Signing Flow](/docs/architects/flows/signing-flow): How DALP moves an EVM transaction from a verified user or API request through compliance simulation, custody signing, provider policy review, and broadcast. - [Asset issuance](/docs/architects/flows/asset-issuance): The two-layer flow that takes an instrument configuration through platform setup, factory deployment, role grants, identity claims, and initial operations. - [Compliance Transfer](/docs/architects/flows/compliance-transfer): Step-by-step sequence for how DALP validates token transfers through recipient identity checks, token-specific compliance modules, global compliance policy, and post-transfer state hooks. - [Identity recovery](/docs/architects/flows/identity-recovery): How DALP replaces a holder's wallet on the identity registry while keeping their OnchainID, claims, and token balances intact. - [Feeds update flow](/docs/architects/flows/feeds-update-flow): How DALP accepts issuer-signed feed updates, validates them on chain, indexes accepted rounds, and exposes current values to contracts, APIs, and the Console. - [Treasury Distribution](/docs/architects/flows/treasury-distribution): How DALP fixed treasury yield uses a configured treasury address to fund holder-initiated claims for completed yield periods. - [PvP and DvP settlement hub](/docs/architects/flows/xvp-settlement): When to use local PvP, local DvP, or hashlock coordinated settlement, and how DALP runs approvals and atomic execution for each pattern. - [Trading venue order lifecycle](/docs/architects/flows/trading-venue-order): How a signed order moves through intake checks, reservation, the orderbook, matching, and on-chain settlement, how a stop order arms and triggers, how a preopen auction opens the session, and how the venue recovers when a fill fails or a compliance change invalidates resting orders. - [Token Sale Flow](/docs/architects/flows/token-sale): How the DALP Token Sale flow manages primary distribution of digital assets -- from sale creation and configuration through purchase execution, presale-to-public transition, vesting withdrawal, and soft-cap-failure refunds. - Integrations - [Integration overview](/docs/architects/integrations): Overview of DALP's integration architecture covering documented provider surfaces and configurable project-specific integrations across custody, compliance, networks, market data, storage, secrets, payments, wallets, ERP, and security controls. - [Custody providers](/docs/architects/integrations/custody-providers): Custody provider integration for digital asset platforms covers per-organization provider selection at onboarding, the provider lock, credential rotation, browser-wallet verification, DFNS MPC signing, Fireblocks MPC signing, Luna HSM partition signing, provider approval policy, configuration inputs, and the signer model that keeps EVM transaction workflows consistent while custody control stays with the provider. - [Compliance Providers](/docs/architects/integrations/compliance-providers): Architecture reference for compliance-provider intake across identity, business, AML, and wallet-monitoring providers, covering how provider events become tenant-scoped on-chain claims and where per-transfer decisions belong instead. - [Supported networks](/docs/architects/integrations/supported-networks): Reference for DALP network configuration across built-in viem chains, custom EVM-compatible networks, RPC transport settings, finality controls, and monitoring behaviour for test and production environments. - Data availability - [Overview](/docs/architects/data-availability): How DALP turns EVM events into queryable platform state, where indexed reads can lag on-chain finality, and which monitoring pages operators use during indexing incidents. - [Ledger Index](/docs/architects/data-availability/chain-indexer): The Ledger Index reads EVM logs, decodes DALP events, and writes queryable read models. It explains how checkpoints, finality, reorg handling, and reindexing affect the state shown by APIs and dashboards. - Operability - [Overview](/docs/architects/operability): Overview map for operating DALP deployments: telemetry, PostgreSQL persistence, workflow durability, high availability handoffs, and failure behavior. - [Observability](/docs/architects/operability/observability): The observability stack provides platform visibility through metrics collection, log aggregation, distributed tracing, and a connected Grafana dashboard system with a single-glance platform health view, for deployments that enable the observability chart. - [Database](/docs/architects/operability/database): PostgreSQL is the authoritative store for DALP application data, with validated connection settings, TLS modes, pooling, UTC sessions, health checks, and operator-owned HA and backup planning. - [Failure Modes](/docs/architects/operability/failure-modes): Architecture-level failure-mode reference for DALP deployments, covering how platform components degrade, what operators can detect, and which recovery path applies when dependencies are unavailable. - Self-Hosting - [Self-hosting overview](/docs/architects/self-hosting): Deploy the Digital Asset Lifecycle Platform in your own Kubernetes or OpenShift infrastructure. Covers operating responsibilities, required platform services, installation planning, and high availability choices for enterprise deployments. - [Prerequisites](/docs/architects/self-hosting/prerequisites): Infrastructure, service, network, and credential checklist for teams preparing a self-hosted DALP installation on Kubernetes or OpenShift. - [Installation process](/docs/architects/self-hosting/installation-process): What SettleMint does during a self-hosted DALP deployment: four phases from environment verification through blockchain wiring to handoff, with clear owner assignments at each stage. - [OpenShift installation](/docs/architects/self-hosting/openshift-installation): OpenShift deployment guidance for self-hosted DALP environments that use restricted SCCs, Routes, and OpenShift Data Foundation or another CSI-backed storage class. - High Availability - [High availability](/docs/architects/self-hosting/high-availability): How self-hosted DALP operators choose a high availability and disaster recovery pattern, with recovery metrics, recovery ownership, and links to the supported deployment scenarios. - [Cloud-native high availability](/docs/architects/self-hosting/high-availability/cloud-native): Use managed Kubernetes, managed data services, multi-zone placement, health probes, and backup tooling as the default high availability pattern for self-hosted DALP deployments. - [Hot-warm active-standby](/docs/architects/self-hosting/high-availability/hot-warm): Geographic recovery pattern that keeps a second DALP cluster ready for promotion, with RTO of 30 to 180 minutes and a manual operator-driven failover sequence. - [Hot-cold backup recovery](/docs/architects/self-hosting/high-availability/hot-cold): Use hot-cold disaster recovery when a self-hosted DALP deployment can accept restore-based recovery, backup-dependent RPO, and multi-hour RTO in exchange for a lower standby cost. - [Hot-hot active-active HA](/docs/architects/self-hosting/high-availability/hot-hot): Compare DALP hot-hot and hybrid multi-region deployment patterns for consortium and public EVM networks, including provider patterns, outage behaviour, recovery targets, and when to choose this model. - [Backup and recovery](/docs/architects/self-hosting/high-availability/backup-recovery): Backup scope, recovery dependencies, PostgreSQL point-in-time recovery, namespace snapshots, monitoring signals, and disaster recovery drills for self-hosted DALP deployments. - [Glossary](/docs/architects/glossary): Definitions of key DALP architecture terms, token standards, identity concepts, operating components, and settlement primitives. - Developers - [Developer documentation](/docs/developers): Choose the right DALP developer guide for API integration, CLI automation, platform setup, compliance configuration, asset operations, data feeds, and operator runbooks. - CLI - [Overview](/docs/developers/cli/overview): Choose the right DALP CLI guide for installation, command lookup, scripting, CI automation, and AI agent workflows. - [Getting started](/docs/developers/cli/getting-started): Install the DALP CLI, connect it to a DALP instance, and verify your first authenticated command. - [Command reference](/docs/developers/cli/command-reference): All DALP CLI commands grouped by function, with authentication scope, global options, output formats, and exit codes. - [Scripting and automation](/docs/developers/cli/scripting): Automate DALP CLI commands safely with JSON output, project configuration, CI runners, and error handling. - [AI agent integration](/docs/developers/cli/ai-agents): Set up the DALP CLI for shell-based agents, MCP tool calls, and generated skill files. - Platform setup - [Platform setup overview](/docs/developers/platform-setup/platform-overview): Choose the setup path for organisation deployment, administrator roles, shared services, API automation, and the handoff to asset creation. - [Local chain endpoints](/docs/developers/platform-setup/local-dev-chain): Understand the local EVM endpoint names used when connecting DALP services to a local development network. - [Organisation deployment API](/docs/developers/platform-setup/organization-deployment-api): Start organisation deployment, read the deployment tree, track account-abstraction setup, and separate organisation deployment from system creation for API-based platform setup. - [Invitation onboarding API](/docs/developers/platform-setup/invitation-onboarding-api): Accept an organisation invitation through the API, run the invitee onboarding workflow, poll typed deployment status without SSE, and retry a failed onboarding from a clean slate. - [Admin operating model](/docs/developers/platform-setup/admin-operating-model): Covers both control planes: the organisation layer (users, API keys, webhooks, providers) and the system layer (on-chain roles, minting, compliance, and operator wallets). - [Configure RPC upstream pools](/docs/developers/platform-setup/rpc-upstream-pools): Configure each network's RPC upstream pool from the Console: add providers and nodes, set failover order and weights, store provider credentials, and read the health view that shows which upstream is serving traffic. - [First administrator setup](/docs/developers/platform-setup/first-admin-setup): Create the first administrator, organisation, wallet security, identity, system, currency, and token factories by API. - [Add administrators](/docs/developers/platform-setup/add-admins): Grant DALP platform administrator roles through the API when provisioning operators, compliance teams, auditors, or automation accounts. - [Change admin roles](/docs/developers/platform-setup/change-admin-roles): Update platform administrator role assignments through the API when operating responsibilities, least-privilege reviews, or provisioning workflows change. - SSO sign-in (OIDC) - [SSO sign-in (OIDC)](/docs/developers/sso-oidc): Configure an external OpenID Connect identity provider as the sign-in method for a DALP deployment, with FusionAuth as the worked example. - [Configure an OIDC provider](/docs/developers/sso-oidc/configure-provider): Reference for every auth.oidcProviders field, its environment variable, default, and the claim contract any OIDC identity provider must satisfy for DALP sign-in. - [FusionAuth setup](/docs/developers/sso-oidc/fusionauth-setup): End-to-end FusionAuth configuration for DALP OIDC sign-in: the full-name claim and id-token roles requirements the standard setup misses, plus every step to wire it in. - [Deploy OIDC in production](/docs/developers/sso-oidc/deploy-production): Roll out OIDC sign-in through the DALP Helm chart, inject the client secret safely, keep issuer validation fail-safe, and recover from a lockout. - [Troubleshooting OIDC sign-in](/docs/developers/sso-oidc/troubleshooting): Map each OIDC sign-in failure (invalid redirect, missing issuer, missing name, unverified email, member-not-admin, and lockout) to its cause and fix. - User management - [Create users](/docs/developers/user-management/create-users): Create DALP users through the API with wallet and identity setup, then verify the account before using it in platform workflows. - [Register user](/docs/developers/user-management/register-user): Register a user's wallet and OnchainID in the identity registry via API for compliance tracking and token eligibility. - Compliance - [Choose a KYC issuance path](/docs/developers/compliance/choose-kyc-issuance-path): Decision guide for choosing manual DALP KYC claim issuance or provider-driven ClaimSource intake through a compliance-provider integration. - [Configure trusted issuers](/docs/developers/compliance/configure-trusted-issuers): Add, scope, and remove trusted issuer entries in system and token registries so on-chain claim verification resolves the correct identity addresses. - [Verify KYC](/docs/developers/compliance/verify-kyc): Issue KYC verifications to registered users via API - [Identity verification](/docs/developers/compliance/smart-identity-verification): Configure the identity verification compliance module to require verified OnchainID claims for all asset transfers. Build logical expressions combining multiple claim requirements. - [Onboard a compliance provider](/docs/developers/compliance/onboarding-a-provider): Connect a KYC, KYB, AML, or KYT provider to DALP, configure its webhook and claim topics, and confirm the resulting on-chain verifications through the Console. - [Map provider subjects](/docs/developers/compliance/compliance-provider-subjects): Developer guide for creating DALP subject mappings with provider IDs so compliance-provider webhooks can issue or revoke claims for known identities. - [Provider API reference](/docs/developers/compliance/compliance-provider-api-reference): Reference for DALP compliance-provider endpoints, subject mapping endpoints, webhook headers, statuses, and monitoring fields. - [Rotate a webhook signing secret](/docs/developers/compliance/rotate-webhook-secret): Rotate a compliance-provider webhook signing secret through the Platform API without losing inbound provider events, using the staged rotate, promote, and cancel sequence and a configurable grace window. - [Collateral requirement](/docs/developers/compliance/collateral): Configure collateral ratios, issue collateral claims, and read collateral ratio stats via API. The collateral compliance module uses trusted identity claims to gate minting. - Asset creation - [Create an asset with the API](/docs/developers/asset-creation/create-asset): Deploy a digital asset from an instrument template with the Platform API. - Asset servicing - [Change asset admin roles](/docs/developers/asset-servicing/change-asset-admin-roles): Grant or revoke token-level administrator roles for specific assets via API. - [Mint assets with the API](/docs/developers/asset-servicing/mint-assets): Issue new asset units to eligible wallet addresses with the Platform API. - [Forced transfer](/docs/developers/asset-servicing/forced-transfer): Execute governed exception transfers through the custodian-only forced-transfer API. - [Freeze controls](/docs/developers/asset-servicing/freeze-controls): Hold a holder address or lock a specific token amount through the custodian-only address-freeze and partial-freeze API. - [Recover assets](/docs/developers/asset-servicing/recover-assets): Move an asset balance out of a lost or compromised wallet, or return a stray ERC-20, through the governed recovery API. - [Pause and unpause assets](/docs/developers/asset-servicing/pause-unpause-asset): Enable or disable all transfers for an asset via API. - Corporate actions - [Corporate actions](/docs/developers/corporate-actions): Run dividends, coupons, bonus issues, splits, rights issues, spin-offs, and capital decreases with the Platform API primitives available today. - [Cash dividend](/docs/developers/corporate-actions/cash-dividend): Pay holders a cash dividend through the Corporate Actions catalog and dividend-yield. - [Bonus issue](/docs/developers/corporate-actions/bonus-issue): Distribute free shares pro-rata to existing holders with a record-date snapshot and a batch mint. - [Bond coupon](/docs/developers/corporate-actions/bond-coupon): Pay periodic bond coupons through the fixed-treasury-yield feature, from funding the treasury to holder claims and maturity. - [Stock split and reverse split](/docs/developers/corporate-actions/stock-split): Change the share count for every holder at a fixed ratio through the Corporate Actions catalog. - [Rights issue](/docs/developers/corporate-actions/rights-issue): Offer new shares to existing holders pro-rata, either as a subscription offering through a token sale or as a direct allotment mint. - [Spin-off](/docs/developers/corporate-actions/spin-off): Distribute a new instrument pro-rata to the holders of an existing one by creating the new asset and batch minting against a record-date snapshot. - [Decrease of capital](/docs/developers/corporate-actions/capital-decrease): Reduce issued capital with batch burns, an optional supply-cap reduction, and an optional cash return to holders. - Feeds - [Feeds overview](/docs/developers/feeds/overview): On-chain data feeds registered in a system-level FeedsDirectory. Use feeds for price reporting, NAV tracking, interest rates, and custom oracle data. - [Create feeds](/docs/developers/feeds/create-feeds): Deploy issuer-signed scalar feeds via the factory, create aggregator adapters for stable consumer addresses, and register external feeds in the directory. - [Submit updates](/docs/developers/feeds/submit-updates): Submit issuer-signed feed updates through DALP. Resolve issuer identity, check nonces, send values, and verify freshness before consuming a feed. - [Read data](/docs/developers/feeds/read-data): Query feed data: latest values, historical rounds, resolve feeds by subject and topic, list feeds with filtering, and check staleness. - Trading venue - [Place and cancel orders](/docs/developers/trading-venue/place-and-cancel-orders): Sign an EIP-712 order intent, submit it to the Trading Venue, poll the reserved-balance transaction to completion, and cancel a working order on-chain. - [Trade through sessions and auctions](/docs/developers/trading-venue/sessions-and-auctions): Read a market's session state and calendar, collect orders during preopen, follow the live indicative auction price, and handle the uncross and the official close from an integration. - [Place stop orders and use time in force](/docs/developers/trading-venue/stop-orders-and-time-in-force): Arm a stop order that reserves nothing while dormant, understand what triggers it and what can invalidate it, and choose between GTC, GTD, and IOC time in force. - [Quote in bulk](/docs/developers/trading-venue/bulk-quoting): Place, replace, and cancel signed orders in one batch with per-order failure isolation and net-delta reservations, so a flat two-sided re-quote emits no chain transactions. - [Read market data and streams](/docs/developers/trading-venue/market-data-and-streams): Read venue markets, depth, trades, candles, and the ticker through the v2 API, and consume the live market-data stream with sequence-gap resynchronization. - Operations - [Transaction tracking](/docs/developers/operations/transaction-tracking): Understand DALP transaction finality, indexer visibility, and safe retry behavior. - [Funding wallets for gas](/docs/developers/operations/funding-wallets-for-gas): Keep transactions from stalling on networks where gas is not free. Check gas readiness before you submit, fund the right wallet, and resolve a GAS_REQUIRED failure. - [Testnet to mainnet](/docs/developers/operations/testnet-mainnet-promotion): Move a validated DALP environment from a test EVM network to a production EVM network without treating testnet chain state as production state. - [System upgrades](/docs/developers/operations/system-upgrades): Compare system contract versions and run the guided upgrade workflow from the Console. - [Blockchain monitoring](/docs/developers/operations/blockchain-monitoring): Monitor platform status from the Console and API, and inspect chain RPC and indexer health from the API or CLI. - [Workflow engine recovery](/docs/developers/operations/workflow-engine-recovery): Diagnose and recover durable work in the merged DALP backend without clearing workflow history or creating duplicate chain operations. - [Reconcile balances](/docs/developers/operations/reconciliate-balances): Compare indexed token balances and token events with your own ledger before investigating a mismatch. - Runbooks - [Digital equity issuance (API)](/docs/developers/runbooks/equity-tokenization): Step-by-step API guide covering platform setup, user onboarding, trusted issuer configuration, token deployment, and shareholder supply for an equity issuance. - [Deploy and mint a bond](/docs/developers/runbooks/create-mint-bonds): Step-by-step guide for creating and minting bond tokens using the DALP TypeScript client. - [Deploy and mint a deposit](/docs/developers/runbooks/create-mint-deposits): Create a deposit token, handle queued creation responses, grant token roles, unpause it, and mint deposit certificates with the DALP TypeScript SDK. - [Deploy and mint equity](/docs/developers/runbooks/create-mint-equities): Create an equity token with the DALP TypeScript client, set the required roles, unpause the token, and mint verified shareholder supply. - [Create and mint a fund token](/docs/developers/runbooks/create-mint-funds): Use the DALP TypeScript client to create a fund token, assign the roles needed for supply operations, unpause the token, and mint units to a registered holder. - [Deploy and mint a stablecoin](/docs/developers/runbooks/create-mint-stablecoins): Create a stablecoin token with the DALP TypeScript client, configure the required roles and collateral issuer, add collateral, and mint supply. - [Configure equity collateral](/docs/developers/runbooks/configure-equity-collateral): Configure collateral backing requirements for equity tokens with the Collateral Compliance Module. Install the module, issue a token-identity collateral claim, verify collateral stats, and mint only when backing is sufficient. - Operators - [Operator documentation](/docs/operators): Choose the right DALP operator guide for platform setup, user management, compliance evidence, asset creation and servicing, data feeds, system add-ons, AI assistants, and runbooks. - [User guides](/docs/operators/introduction): Console-led operating guides for administrators and operations teams running regulated digital asset workflows on DALP. - Platform setup - [Platform setup overview](/docs/operators/platform-setup/platform-overview): Understand the platform setup model, ownership responsibilities, administrator roles, and next setup guide to read. - [First administrator setup](/docs/operators/platform-setup/first-admin-setup): Create the first administrator account, deploy the organisation, recover from interruption, and choose the next setup step. - [Add administrators](/docs/operators/platform-setup/add-admins): Grant platform administrator roles to an existing participant or wallet from Organisation settings. - [Evaluation users](/docs/operators/platform-setup/evaluation-environment-users): Create the minimum user set needed to run a controlled DALP demo or evaluation environment. - [Change admin roles](/docs/operators/platform-setup/change-admin-roles): Update platform administrator roles from Organisation settings when operating responsibilities, least-privilege reviews, or wallet assignments change. - [Switch the participant you act as](/docs/operators/platform-setup/acting-as-switcher): Use the Acting as switcher in the Console header to move between your own person participant and any organization you administer, so operations run under the right identity. - [Advanced accounts](/docs/operators/platform-setup/advanced-accounts): What advanced accounts gives your organisation, the difference between transaction funding and gasless transactions, and when to enable them. - [Advanced accounts control center](/docs/operators/platform-setup/advanced-accounts-control-center): Review and fund the gas reserves behind advanced accounts from Organisation settings, including the submission reserve, sponsorship reserve, signer key, and recent on-chain activity. - [Complete token role migration](/docs/operators/platform-setup/complete-token-role-migration): Finish migrating a token's participant roles to smart accounts when advanced accounts skipped that token, using the token-page warning and the pending-tokens list. - [Gas reserves](/docs/operators/platform-setup/gas-reserves): Understand how DALP's two gas reserves serve distinct roles in advanced-account transaction processing, and what each reserve's depletion means for platform operations. - [Operator wallets](/docs/operators/platform-setup/operator-wallets): Check configured operator wallet balances from the Admin area before low native token balances interrupt gas-funded platform operations. - [Console color palette](/docs/operators/platform-setup/console-color-palette): How administrators edit the light and dark color tokens for the Console, with inline validation that blocks invalid values before they are saved. - [Global search](/docs/operators/platform-setup/global-search): Use the DALP Console global search palette to find assets, users, contacts, and system contracts, then open a record or copy its address. - [Manage a webhook endpoint](/docs/operators/platform-setup/webhook-endpoint-settings): Rotate the signing secret, change the delivery URL, switch payload shape, or delete a webhook endpoint from the DALP Console settings page. - User management - [Administration operating model](/docs/operators/user-management/admin-operating-model): Understand how DALP separates organisation administration, invitations, platform permissions, API keys, webhooks, providers, data feeds, security settings, and operator wallets. - [Invite users](/docs/operators/user-management/invite-users): Send invitations for team members and external partners to join your platform from the Users page, optionally pre-assigning their platform roles, and understand what the recipient completes after accepting. - [Create users](/docs/operators/user-management/create-users): Create or invite users from the Users workspace, and know when to choose direct creation instead of an invitation. - [Participants hub](/docs/operators/user-management/participants-hub): Review users, entities, identity registration status, KYC evidence, holdings, activity, and security signals for every participant on the platform. - [Manage address book contacts](/docs/operators/user-management/manage-address-book-contacts): Review, edit, and delete address book contacts in the DALP Console so transfer and operator workflows use the intended wallet address. - [Review address book contacts](/docs/operators/user-management/review-address-book-contact): Open a saved contact in DALP, confirm its wallet address and timestamps, then edit or delete the contact when the local address book entry is wrong. - [Open private files](/docs/operators/user-management/open-private-files): Open /dalp/private/ file links from DALP workflows and respond when authentication, ownership, organisation, or administrator checks fail. - [Account security](/docs/operators/user-management/account-security): Manage password, two-factor authentication, passkeys, active sessions, PIN, and recovery codes, including resetting a forgotten PIN, from the DALP account security page. - [Your account wallet](/docs/operators/user-management/account-wallet): Read the Wallet card on your DALP account page. Understand the wallet address that holds your assets, the on-chain status badge, and the managed signing key behind the Show control. - [Your onchain identity](/docs/operators/user-management/account-onchain-identity): Read the Onchain identity page on your DALP account. Understand your onchain identity address, your on-chain registration status, and the verifications that let you transact under a compliance policy. - [User onboarding](/docs/operators/user-management/user-onboarding): Understand how invited users, admin-created users, administrators, and investors complete DALP onboarding. - [Recover a user's identity](/docs/operators/user-management/recover-user-identity): Recover a user who lost wallet access, review the console preview, confirm recovery, and re-issue claims on the replacement identity. - [Provide KYC data](/docs/operators/user-management/provide-kyc-data): Complete a versioned KYC profile with identity details and supporting documents so an Identity Manager can review it. - [Register user](/docs/operators/user-management/register-user): Complete identity registration so a user becomes eligible for regulated asset checks, with wallet, OnchainID, and jurisdiction linked in the registry. - Compliance - [Compliance overview](/docs/operators/compliance/overview): Understand how DALP enforces digital asset compliance controls across identity, eligibility, transfer approvals, supply limits, capital raise limits, issuance volume, collateral checks, and trusted verification issuers. - [Policy templates](/docs/operators/compliance/templates): Create, publish, delete, and reuse policy templates that group DALP compliance modules for asset creation. - [Global controls](/docs/operators/compliance/global-controls): Configure global compliance controls in DALP so a single rule applies across every token in the system, and use scope to narrow which tokens and transfers a rule covers. - [Add a verification topic](/docs/operators/compliance/verification-topics): Add, edit, and delete verification topics in DALP organisation settings so trusted issuers can sign identity claims your compliance policy accepts. - [Configure trusted issuers](/docs/operators/compliance/configure-trusted-issuers): Configure the identity contracts that can issue verification claims for the topics your DALP compliance policy accepts. - [Manage token claim topics](/docs/operators/compliance/manage-token-claim-topics): View the resolved claim topic scheme chain for a token in the DALP Console and add or remove token-specific schemes from the claim-topics tab. - [Manage token trusted issuers](/docs/operators/compliance/manage-token-trusted-issuers): Review the resolved trusted-issuer chain for a token and add or remove token-level issuers from the Console verifications area. - [Manage KYC data](/docs/operators/compliance/manage-kyc-data): Review KYC submissions, inspect version history, and approve, reject, or request updates as an Identity Manager. - [Verify KYC](/docs/operators/compliance/verify-kyc): Issue on-chain KYC verifications for users, with the approved-KYC-profile prerequisite and a fix for the "No approved KYC profile" block. - [Require identity verification](/docs/operators/compliance/identity-verification): Set up the identity-verification module so every holder must carry a valid claim from a trusted issuer before transacting on a regulated asset. - [Country restrictions](/docs/operators/compliance/country): Configure DALP country allow-list and block-list compliance modules so an asset accepts holders only from approved jurisdictions or rejects sanctioned ones. - [Identity allow-list](/docs/operators/compliance/identity-allow-list): Restrict an asset to a specific set of approved OnchainIDs so only explicitly authorised identities can hold or receive units. - [Identity block-list](/docs/operators/compliance/identity-block-list): Prevent specific OnchainID holders from sending or receiving an asset without touching the asset's broader eligibility policy. - [Address block-list](/docs/operators/compliance/address-block-list): Configure the DALP address block-list module so an asset rejects specific wallet addresses regardless of registered identity status. - [Token supply limit](/docs/operators/compliance/token-supply-limit): Set a hard ceiling on how many tokens can ever be minted for an asset, protecting a fixed share count or placement quota. - [Capital raise limit](/docs/operators/compliance/capital-raise-limit): Enforce a regulatory fundraising ceiling by rejecting mints whose cumulative fiat value would exceed the configured cap in a fixed or rolling window. - [Issuance volume limit](/docs/operators/compliance/issuance-volume-limit): Configure the DALP issuance-volume-limit compliance module so minting stays within a fixed or rolling token-unit quota. - [Investor count limit](/docs/operators/compliance/investor-count): Cap the number of unique holder identities on an asset, set per-country sub-limits, and track holders issuer-wide so private placements and jurisdictional investor caps are enforced on-chain. - [Time lock](/docs/operators/compliance/timelock): Enforce a minimum holding period on received units so asset positions cannot be transferred until the configured lock duration has elapsed. - [Transfer approval](/docs/operators/compliance/transfer-approval): Require explicit authoriser sign-off on every regulated transfer before it settles on chain. - [Collateral requirement](/docs/operators/compliance/collateral): Configure the collateral compliance module so DALP checks the asset identity for a valid collateral claim before minting more supply. - Asset creation - [Asset Designer](/docs/operators/asset-creation/create-asset): Use the DALP Asset Designer wizard to choose an instrument template, configure compliance controls, set initial roles, and deploy a digital asset. - [Instrument templates](/docs/operators/asset-creation/instrument-templates): Create, reuse, and publish instrument templates for the Asset Designer. - [System templates](/docs/operators/asset-creation/system-templates): Reference for the 27 seeded templates in the Asset Designer, showing which asset class and required token features each template attaches when you create an asset. - [Custom template authoring](/docs/operators/asset-creation/custom-template): Walk an operator through creating a custom DALP instrument template, from choosing an asset class to publishing the template for the Asset Designer. - Token features - [Token features](/docs/operators/token-features): Operator how-to pages for the thirteen DALP token features, including which instrument templates attach each feature and how to configure their parameters. - [Historical balances](/docs/operators/token-features/historical-balances): How the historical-balances token feature records timestamped holder and supply checkpoints, and how operators read holders as of a past date for reporting, voting, and audit. - [Operate Voting Power](/docs/operators/token-features/voting-power): Attach Voting Power so token holders can delegate weight and vote in native DALP governance, with each holder's weight fixed at the vote's record date. - [Permit](/docs/operators/token-features/permit): Operate the permit token feature in the Console. Create custodial EIP-2612 approvals for a spender, set a deadline, and relay stored permits on-chain. - [Maturity redemption](/docs/operators/token-features/maturity-redemption): How operators configure the maturity-redemption token feature, complete issuance before maturity, and trigger holder redemption when a fixed-income asset reaches its maturity date. - [Fixed treasury yield](/docs/operators/token-features/fixed-treasury-yield): Steps to set the yield rate, fund the treasury, monitor coverage, and settle holder claims using the fixed-treasury-yield token feature. - [Dividend yield](/docs/operators/token-features/dividend-yield): Steps to declare a dividend, record the record-date snapshot, fund the treasury, settle holder claims, and reclaim unclaimed value with the dividend-yield token feature. - [Interest yield](/docs/operators/token-features/interest-yield): Steps to set the annual rate, fund the treasury, settle holder claims, and pair interest accrual with conversion using the interest-yield token feature. - [AUM Fee operator guide](/docs/operators/token-features/aum-fee): How operators configure, monitor, collect, and freeze AUM Fee on DALP tokens without duplicating the architecture reference. - [Transaction fee](/docs/operators/token-features/transaction-fee): How operators configure the transaction-fee token feature for on-chain fee collection on mint, burn, and transfer operations. - [Transaction fee accounting how-to](/docs/operators/token-features/transaction-fee-accounting): How operators configure the transaction-fee-accounting token feature for off-chain settlement of mint, burn, and transfer fees. - [External transaction fee](/docs/operators/token-features/external-transaction-fee): How operators use external-transaction-fee to keep fee costs in a separate ERC-20 asset, so the operated asset's balance is never reduced by the fee collection. - [Conversion](/docs/operators/token-features/conversion): How operators configure the conversion token feature for convertible instruments that exchange holdings into a target equity or settlement token. - [Conversion minter](/docs/operators/token-features/conversion-minter): How the conversion-minter token feature mints target-side tokens during a conversion exchange, paired with the conversion feature on the source asset. - Asset servicing - [Asset detail workspace](/docs/operators/asset-servicing/asset-detail-workspace): Review an issued asset, inspect token tabs, and understand which operator workflows are available for the current token. - [Register external tokens](/docs/operators/asset-servicing/register-external-token): Add an existing EVM token to DALP from the External Tokens workspace so operators can track it beside assets created in DALP. - [Change asset admin roles](/docs/operators/asset-servicing/change-asset-admin-roles): Grant, revoke, and review token-level administrator roles for one asset in the DALP web interface. - [Stablecoin operations](/docs/operators/asset-servicing/stablecoin-operations-lifecycle): Run the post-issuance stablecoin lifecycle across holder eligibility, reserve and collateral updates, controlled minting, transfers, burns, and reconciliation. - [Exit control portability](/docs/operators/asset-servicing/exit-control-portability): Keep issuer authority, investor eligibility, lifecycle governance, and audit evidence portable during an asset servicing exit. - [Mint assets in the console](/docs/operators/asset-servicing/mint-assets): Issue new units of a security to investor accounts from the web console, with eligibility checks and safe retry guidance. - [Transfer assets in the console](/docs/operators/asset-servicing/transfer-assets): Send tokens you hold to one or more recipients from the DALP console, with per-recipient amounts, a live compliance verdict, and a balance preview before you submit. - [Set a token price](/docs/operators/asset-servicing/set-token-price): Record a fiat base price on a deployed token so valuations, NAV reporting, and portfolio views can resolve a value for the asset. - [Burn assets](/docs/operators/asset-servicing/burn-assets): Permanently remove units of a security from circulation. - [Freeze and unfreeze balances](/docs/operators/asset-servicing/freeze-unfreeze-balances): Restrict or release a holder address or part of a holder balance for approved custodian cases. - [Forced transfer](/docs/operators/asset-servicing/forced-transfer): A custodian-authorised on-chain transaction that debits one holder and credits another, bypassing normal approval and freeze controls for governed exception cases. - [Compliance pre-check console](/docs/operators/asset-servicing/compliance-precheck-console): Simulate a token transfer in the Console before anyone submits it, read the will-clear or will-revert verdict, and act on each blocker by who can resolve it. - [Forced conversion](/docs/operators/asset-servicing/forced-conversion): Run a custodian-initiated conversion that bypasses the holder consent path, used for mandatory convertible instruments and institution-approved exception cases. - [Authorized converters](/docs/operators/asset-servicing/authorized-converters): Add or remove converter addresses for conversion-minter assets before running governed conversion workflows. - [Manage on-chain token metadata](/docs/operators/asset-servicing/manage-token-metadata): Add, update, or remove on-chain metadata entries on a deployed asset from the Console after issuance. - [Manage asset documents](/docs/operators/asset-servicing/manage-asset-documents): Review, preview, verify, download, and manage the files attached to a live asset from the Documents tab in the Console. - [Pause and unpause assets](/docs/operators/asset-servicing/pause-unpause-asset): Pause or reactivate one asset after launch checks, maintenance, or an incident response hold. - Data feeds - [Data feeds overview](/docs/operators/data-feeds/overview): Understand issuer-signed scalar data feeds, their architecture, required permissions, and configuration properties. - [Create a topic](/docs/operators/data-feeds/create-topic): Register a scalar feed verification topic to define the data schema for your data feeds. - [Create a feed](/docs/operators/data-feeds/create-feed): Deploy an issuer-signed scalar feed or register a Chainlink-compatible feed for a global, asset, or identity subject. - [Publish a feed update](/docs/operators/data-feeds/publish-feed-update): Keep NAV, price, and metric data current by writing a trusted issuer's EIP-712 signed value to an on-chain scalar feed. - [Replace or remove a feed](/docs/operators/data-feeds/replace-or-remove-feed): Change the feed address for an existing subject and topic, or remove a feed registration from the Feeds Directory. - [Add a reporting currency](/docs/operators/data-feeds/add-reporting-currency): Add a currency to your organization's exchange-rate feeds, read the latest rate snapshot, and troubleshoot a failed Save additions from the Currencies & exchange rates settings page. - System addons - [System addons overview](/docs/operators/system-addons/introduction): Understand how DALP system addons are discovered, installed, and operated across settlement, distribution, yield, fee, feed, conversion, and infrastructure workflows. - [Install addons](/docs/operators/system-addons/install-addons): Addons are installed by converging your system to the on-chain Directory. Onboarding installs every available component, and System updates installs anything added to the Directory later. - [Review addon workspaces](/docs/operators/system-addons/review-addon-workspaces): Open an installed addon workspace, confirm the selected factory, and continue into XvP settlement, token sale, or token governance instance pages from the DALP Console. - [Review token sale offerings](/docs/operators/system-addons/review-token-sale-offerings): Open a token sale offering in the Console, check sale status, funding, purchases, payment currencies, whitelist entries, and vesting settings before taking the next operator step. - XvP settlement - [Overview](/docs/operators/system-addons/xvp-settlement/overview): XvP Settlement coordinates multi-party asset exchanges for DALP assets. Local settlements execute all local flows in one transaction; external-flow settlements use hashlocks and secrets to coordinate with a leg that stays outside the local execution. - [Choose a settlement type](/docs/operators/system-addons/xvp-settlement/choose-settlement-type): Choose between local XvP settlement and HTLC settlement before you configure flows, approvals, cancellation, or expiry recovery. - [XvP execution models](/docs/operators/system-addons/xvp-settlement/execution-boundaries): Clarify what DALP executes for local XvP settlement, what it records for external-flow settlement, and which off-chain checks remain outside the settlement contract. - Local settlements - [Overview](/docs/operators/system-addons/xvp-settlement/local/overview): Local settlements execute all asset transfers atomically on a single blockchain. Learn when to use local settlements and how the approval workflow operates. - [Walkthrough](/docs/operators/system-addons/xvp-settlement/local/walkthrough): Follow a complete example of a local settlement where a Builder sells property tokens to a Buyer, with a Notary receiving a fee. - HTLC settlements - [HTLC settlements](/docs/operators/system-addons/xvp-settlement/htlc/overview): Use HTLC settlements to coordinate EVM asset exchanges across chains with a shared hashlock, local settlement controls, and party-managed secret reveal before each cutoff date. - [HTLC explained](/docs/operators/system-addons/xvp-settlement/htlc/htlc-explained): Understand how Hash Time-Locked Contracts coordinate XvP settlement legs with a shared secret and cutoff dates. - [Walkthrough](/docs/operators/system-addons/xvp-settlement/htlc/walkthrough): Follow a multi-party HTLC settlement where two DALP settlements use the same hashlock to coordinate token and USDC flows across Ethereum and Polygon. - [Verify external flows](/docs/operators/system-addons/xvp-settlement/htlc/verify-external-flows): Confirm the cross-chain asset details, hashlock, and cutoff timing in an HTLC settlement so both sides match before any sender approves or the secret is revealed. - [Cancel or recover a settlement](/docs/operators/system-addons/xvp-settlement/cancel-or-recover): Choose the correct XvP cancellation or expiry recovery path for local and HTLC settlement modes. - Settlement action reference - [Create](/docs/operators/system-addons/xvp-settlement/actions/create): Create an XvP settlement from an XvP add-on factory, add local and external flows, configure cutoff and HTLC details, then submit the reviewed settlement. - [Approve](/docs/operators/system-addons/xvp-settlement/actions/approve): Learn how the local sender approves an XvP settlement, what DALP checks before approval, and how the settlement moves toward execution after approval. - [Revoke approval](/docs/operators/system-addons/xvp-settlement/actions/revoke-approval): Revoke your approval from an XvP settlement. The platform returns your locked assets to your wallet. - [Reveal secret](/docs/operators/system-addons/xvp-settlement/actions/reveal-secret): Reveal the hashlock preimage for an external-flow HTLC settlement, queue the on-chain reveal transaction, and optionally notify counterparties by email. - [Execute](/docs/operators/system-addons/xvp-settlement/actions/execute): Manually execute an XvP settlement after approvals and any HTLC secret reveal are complete. Use this action when auto-execute is disabled and the settlement is ready to commit on-chain. - Cancel - [Cancel](/docs/operators/system-addons/xvp-settlement/actions/cancel): Stop an open XvP settlement and return locked assets to their original senders. Learn when the cancel endpoint cancels immediately, when it records an HTLC cancel vote, and when expired-withdrawal is the correct recovery path. - [Local settlements](/docs/operators/system-addons/xvp-settlement/actions/cancel/local-settlements): Cancel a local XvP settlement before execution and return locked assets to the senders. - [HTLC settlements](/docs/operators/system-addons/xvp-settlement/actions/cancel/htlc-settlements): Cancel an HTLC settlement before it is armed, or coordinate the local participants who must vote when the settlement already has all local approvals. - [Withdraw expired](/docs/operators/system-addons/xvp-settlement/actions/withdraw-expired): Withdraw assets from an expired XvP settlement after the cutoff date passes and the settlement has not executed or been cancelled. - Trading venue - [Overview](/docs/operators/system-addons/trading-venue/overview): What the venue-operations surface covers, who can use it, and where to find the markets table, listing ceremony, market controls, fee schedules, desk administration, and venue health. - [List a market](/docs/operators/system-addons/trading-venue/list-a-market): Request a new market with the new-market wizard, then complete the listing ceremony: custodian-role grants from each issuer, feed-writer registration, and fee-account eligibility. - [Configure trading calendars](/docs/operators/system-addons/trading-venue/trading-calendars): Give a market an IANA timezone, a weekly session template, and dated exceptions so it opens through a preopen auction and closes on schedule, and override the calendar when a session must move. - [Run private markets](/docs/operators/system-addons/trading-venue/private-markets): Create an auction-only private market, administer its approved-participant list, and understand what non-members can and cannot see, including the market's intentionally public on-chain footprint. - [Set price bands and thresholds](/docs/operators/system-addons/trading-venue/price-bands-and-thresholds): Configure the static and dynamic price bands and the maximum order quantity and notional per market, preview how many resting orders a tighter setting would strand, and prune them as an explicit separate action. - [Halt, resume, and delist a market](/docs/operators/system-addons/trading-venue/halt-resume-delist): Stop matching with a market halt, reopen with resume, and permanently close a market with the typed delisting confirmation, including what happens to resting orders and reserved balances in each case. - [Set fee schedules](/docs/operators/system-addons/trading-venue/fee-schedules): Set a market's maker and taker fees in basis points, understand how fees are charged on the quote leg, and see which resting orders a fee raise prunes before you apply it. - [Administer desks](/docs/operators/system-addons/trading-venue/desk-administration): Propose trading authorizations and desk limits for institutional desks, and approve them with a distinct approver so limits take effect at order intake. - [Bust an erroneous trade](/docs/operators/system-addons/trading-venue/trade-busting): Propose a trade bust inside the bust window, have a distinct approver decide it, and let the platform execute the compensating reversal that returns both legs, refunds the fee, and corrects statistics and published prices. - [Monitor venue health](/docs/operators/system-addons/trading-venue/monitor-venue-health): Read the venue health panel: settlement failures, reconciliation state, feed publishing, and the settlement submitter's gas budget, with the response each severity asks for. - Token Sale - [Overview](/docs/operators/system-addons/token-sale/overview): Token Sale enables compliant primary distribution of digital assets to investors. Learn about sale phases, payment currencies, optional presale, vesting schedules, and soft cap protection. - Presale - [Presale Overview](/docs/operators/system-addons/token-sale/presale/overview): Learn how the Token Sale presale phase works, including whitelist management, discount pricing, per-address caps, and transition to public sale. - Vesting - [Vesting Overview](/docs/operators/system-addons/token-sale/vesting/overview): Learn how vesting schedules work in a token sale. Understand cliff periods, linear token release, and how to withdraw your vested tokens. - Actions - [Create](/docs/operators/system-addons/token-sale/actions/create): Learn how to create a new token sale using the wizard. Configure payment currencies, timing, optional presale, optional vesting, and caps. - [Activate](/docs/operators/system-addons/token-sale/actions/activate): Learn how to activate a token sale, opening it to investors. Activation requires the sale to be funded with tokens and the SALE_ADMIN_ROLE. - [Buy](/docs/operators/system-addons/token-sale/actions/buy): Learn how to purchase tokens during an active token sale. Select a payment currency, specify an amount, accept terms if required, and submit the transaction. - [Acknowledge Terms](/docs/operators/system-addons/token-sale/actions/acknowledge-terms): Learn how to accept the terms and conditions for a token sale. If a terms hash is set, acknowledgment is required before you can purchase tokens. - [Manage Permissions](/docs/operators/system-addons/token-sale/actions/manage-permissions): Assign and revoke the Sale Admin and Funds Manager roles on a token sale from the Permissions tab, granting each role to a participant without handing over full token administration. - [Pause and Resume](/docs/operators/system-addons/token-sale/actions/pause-unpause): Learn how to temporarily pause a token sale to halt purchases, and how to resume it. Use pause for emergency response or compliance holds. - [End and Finalize](/docs/operators/system-addons/token-sale/actions/end-finalize): Learn how to end a token sale before its scheduled close and how to finalize it after it ends to determine SUCCESS or FAILED status. - [Withdraw Funds](/docs/operators/system-addons/token-sale/actions/withdraw-funds): Learn how to withdraw sale proceeds after a successful token sale. Requires FUNDS_MANAGER_ROLE and a SUCCESS finalization status. - [Withdraw Tokens](/docs/operators/system-addons/token-sale/actions/withdraw-tokens): Learn how to withdraw your vested tokens after purchasing in a token sale with vesting enabled. Tokens are released linearly after the cliff period. - [Claim Refund](/docs/operators/system-addons/token-sale/actions/claim-refund): Learn how to claim a refund of your contributions when a token sale fails to meet its soft cap. Refunds return the payment currencies you contributed. - [Yield schedule](/docs/operators/system-addons/yield-schedule): Configure fixed yield periods for token holders. The schedule records period timing, rates, denomination asset balances, and holder claims. - [Bond lifecycle prerequisites](/docs/operators/system-addons/bond-lifecycle-prerequisites): Prepare bond funding, yield claims, maturity, and redemption in DALP by checking the required features, treasuries, allowances, and indexed status values before each phase. - AI assistants - [AI assistants for operators](/docs/operators/ai-agents/overview): Understand how AI assistants use the DALP CLI, MCP tools, and generated skills while staying inside the operator account, organisation, role, and approval boundaries. - Runbooks - [Runbooks](/docs/operators/runbooks): Find the right DALP runbook for controlled platform, compliance, asset, and recovery operations. - [Digital equity issuance](/docs/operators/runbooks/equity-tokenization): Set up actors, verify compliance, mint 100,000 ACME shares, and distribute tokens to issuer and exchange through the DALP console. - [User onboarding](/docs/operators/runbooks/onboard-user-im): Register an onboarded wallet in the identity registry, issue KYC verification, and confirm the user is ready for asset rules that require identity claims. - [Actions work queue](/docs/operators/runbooks/actions-work-queue): Review upcoming, pending, completed, and expired DALP actions from the operator queue. - [Governance votes](/docs/operators/runbooks/governance-votes): Create token governance votes, manage record dates and delegation, collect ballots, and execute approved proposals through the timelock. - [Monitor platform status](/docs/operators/runbooks/monitor-platform-status): Read the Platform status page to check overall health, then drill into a degraded service to inspect indexing, transactions, API requests, and workflows. - [Rotate claim signer key](/docs/operators/runbooks/rotate-provider-claim-signer-key): Operational runbook for rotating the autonomous EOA that signs claims on a compliance provider's claim-issuer identity. Rotation happens via addKey / removeKey on the identity and does not require any trusted issuers registry mutation. - [Gas reserves operations](/docs/operators/runbooks/gas-reserves-operations): Fund, configure, and troubleshoot the Submission reserve and Sponsorship reserve for advanced accounts in DALP. - Core concepts - [Asset policy](/docs/architecture/concepts/asset-policy): Understand how DALP combines identity records, compliance modules, lifecycle hooks, and governance controls to decide whether regulated token operations can execute. - [Account abstraction](/docs/architecture/concepts/account-abstraction): What account abstraction is in plain terms, how DALP chooses the smart account or EOA route, and why execution stays separate from identity and policy. - [Claims and identity](/docs/architecture/concepts/claims-and-identity): Understand how participants, wallet registration, OnchainID claims, trusted issuers, claim topics, and token compliance expressions work together in DALP. - Compliance and security - [Compliance and security](/docs/compliance-security): Choose the right DALP compliance and security guide for public-chain privacy, pre-launch review, source verification, the layered security model, and the per-asset compliance modules that enforce regulated operations. - Privacy - [Public chain privacy](/docs/compliance-security/privacy/overview): The compliance and security entry point for deciding whether a regulated asset can use a public EVM network. - [Public EVM visibility model](/docs/compliance-security/privacy/public-evm-visibility-model): How to identify which DALP asset data becomes discoverable on public EVM networks and which evidence must stay in controlled off-chain systems. - [Transaction ordering privacy](/docs/compliance-security/privacy/transaction-ordering-privacy): What can leak from pending transactions on public EVM networks and which routing controls reduce that exposure before finality. - [Privacy architecture patterns](/docs/compliance-security/privacy/architecture-patterns): Compare public eligibility, private evidence, permissioned EVM networks, privacy layers, and metadata minimisation patterns for regulated DALP assets. - [Pre-launch privacy review](/docs/compliance-security/privacy/pre-launch-review): Operator checklist for reviewing on-chain fields, evidence storage, transaction routing, and legal approval before a regulated asset uses a public EVM network. - [Private mempool routing](/docs/compliance-security/privacy/private-mempool-routing): How to route DALP transaction submission through a private or encrypted mempool service by replacing the public RPC endpoint, what the service protects against, and what remains an operator responsibility. - Source verification - [Source verification](/docs/compliance-security/source-verification/overview): How DALP makes deployed EVM contracts reviewable through deployment records, bytecode checks, upgrade history, and audit evidence, with links to the detail pages for each evidence surface. - [Deployment evidence](/docs/compliance-security/source-verification/deployment-evidence): How DALP makes the contract-deployment step reviewable through the deployment record, address manifest, bytecode presence checks, and the change controls operators preserve for the environment evidence pack. - [Bytecode verification](/docs/compliance-security/source-verification/bytecode-verification): How auditors check that deployed EVM bytecode matches the accepted source package, and what the operator shares about DALP-managed proprietary contract source versus customer-controlled source. - [Upgrade history](/docs/compliance-security/source-verification/upgrade-history): How auditors trace DALP contract provenance, upgrade authorisation, proxy patterns, directory pointers, and timelock or cancellation controls for the deployed environment. - [Audit evidence](/docs/compliance-security/source-verification/audit-evidence): How to answer vulnerability-control, formal-verification, and smart-contract audit evidence requests with DALP's deployed-scope evidence pack. - Security - [Security overview](/docs/compliance-security/security): DALP security separates identity, access, wallet verification, on-chain compliance, and custody controls so reviewers can see which gate owns each asset-operation decision. - [Authentication](/docs/compliance-security/security/authentication): DALP authenticates browser operators and API integrations before authorization and wallet verification decide what each request may do. - [Authorization](/docs/compliance-security/security/authorization): DALP authorizes asset operations through platform RBAC, organisation context, wallet verification for browser-session writes, and on-chain roles for the contract operation being requested. - [Identity and compliance](/docs/compliance-security/security/identity-compliance): How DALP links participants, wallets, and OnchainID identities, keeps evidence off chain, trusts claim issuers by topic, and evaluates claims before regulated token operations execute. - [Compliance and custody split](/docs/compliance-security/security/compliance-custody-boundary): Understand how DALP separates identity and compliance decisions from custody approvals and signing policies when token operations are executed. - [Trading venue compliance model](/docs/compliance-security/security/trading-venue): What the Trading Venue can and cannot do with the custodian role it holds, why the token remains the final compliance judge at fill, how private-market visibility and trade busting are bounded, and what audit evidence the venue produces. - [Mint replay and idempotency](/docs/compliance-security/security/replay-idempotency-mint-controls): How DALP keeps EVM mint retries tied to one queued transaction while preserving nonce ordering, signer approval, and per-asset supply controls. - [Vendor governance](/docs/compliance-security/security/vendor-governance): DALP separates platform controls from the third-party services, operating procedures, and regulatory evidence that a financial institution owns when it assesses outsourcing, DORA, and vendor governance obligations. - [Wallet Verification](/docs/compliance-security/security/wallet-verification): Wallet verification gates blockchain write operations as a second security layer beyond session authentication, using PIN, TOTP, or backup-code checks. - [Bridge and cross-chain](/docs/compliance-security/security/bridge-cross-chain): Understand where DALP controls end in bridge, wrapper, redemption, and XvP designs, and which external-route evidence an operator must own before production. - [Stablecoin responsibilities](/docs/compliance-security/security/stablecoin-architecture-trust-boundaries): Understand the DALP stablecoin issuance architecture, including mint, burn, reserve, compliance, governance, and operator-owned responsibilities. - [Advanced accounts security](/docs/compliance-security/security/advanced-accounts-security): How DALP bounds the authority of the advanced accounts execution layer: sponsorship ticket constraints, signer key controls, account-management safety rails, and the separation between execution and identity. - Compliance modules - [Compliance module index](/docs/compliance-security/compliance): Choose the DALP compliance module that matches each asset policy rule, including identity, geography, supply, approvals, collateral, and holding-period controls. - [Asset policy](/docs/compliance-security/compliance/asset-policy): Reference page for DALP asset policy compliance configuration, module categories, configuration scope, and the pages to use when reviewing per-asset rules. - [Country Restrictions](/docs/compliance-security/compliance/country): Choose CountryAllowList or CountryBlockList to permit or exclude token recipients by ISO 3166-1 country code, covering MiCA jurisdiction selection, OFAC sanctions screening, and similar regulatory requirements. - [Identity lists](/docs/compliance-security/compliance/identity-lists): IdentityAllowList, IdentityBlockList, and AddressBlockList compliance modules for investor-level and wallet-level access control. - [Address Block List](/docs/compliance-security/compliance/address-block-list): Block specific EVM wallet addresses from sending or receiving a regulated token, without requiring an OnchainID identity. - [Identity verification reference](/docs/compliance-security/compliance/identity-verification): Configure postfix claim expressions that gate token recipients on KYC, AML, accreditation, or any trusted issuer claim before a transfer executes. - [Policy-based transfer controls](/docs/compliance-security/compliance/policy-based-transfer-controls): Understand how DALP combines identity, eligibility, asset policy, transfer approvals, and settlement conditions before regulated token transfers execute. - [Supply & Investor Limits](/docs/compliance-security/compliance/supply-investor-limits): TokenSupplyLimit and InvestorCount modules for time-based and rolling supply caps with currency conversion, plus unique holder limits with per-country granularity. - [Capital Raise Limit](/docs/compliance-security/compliance/capital-raise-limit): CapitalRaiseLimit enforcement for fiat-denominated gross fundraising caps during minting, including price resolver requirements and fixed or rolling windows. - [Transfer approval](/docs/compliance-security/compliance/transfer-approval): How the TransferApproval module gates regulated transfers with identity-bound approvals, expiry, consumption modes, and fee-feature exemptions. - [Supply cap and collateral](/docs/compliance-security/compliance/supply-cap-collateral): How DALP combines circulating supply caps with collateral claims to control minting for reserve-backed assets. - [TimeLock](/docs/compliance-security/compliance/timelock): TimeLock enforces minimum holding periods with FIFO batch tracking, hold-period configuration, and address-level transfer checks. - API reference - [API reference](/docs/api-reference): Choose the right DALP API page for authentication, OpenAPI client generation, request headers, errors, webhooks, EVM token lifecycle, token data, durable workflow recovery, smart wallets, and XvP settlement. - Reference - [Getting started with the DALP Platform API](/docs/api-reference/reference/getting-started): Create an API key, configure the DALP TypeScript SDK, and choose the right API, CLI, or OpenAPI path for authenticated integration. - [TypeScript SDK](/docs/api-reference/reference/sdk): Install and use the promise-based @settlemint/dalp-sdk client generated from the v2 OpenAPI document. - [Migrate to the reset v2 API](/docs/api-reference/reference/v2-migration): Update DALP v2 clients for the new REST hierarchy, native SDK, strict decoding, bundler resources, and live API reference. - [V2 migration operation appendix](/docs/api-reference/reference/v2-operation-appendix): Public route-by-route mapping for the coordinated DALP API v2 reset. - [API changes](/docs/api-reference/reference/api-changes): What changed on /api/v1 and /api/v2 relative to the previous release, and why. - [DALP OpenAPI specification and typed client generation](/docs/api-reference/reference/openapi): Access the OpenAPI specification and generate type-safe clients for integrating with the DALP platform programmatically. - [Request headers](/docs/api-reference/reference/request-headers): Select participant, executor, network, transaction speed, retry-safety, and response-timing headers for DALP API requests. - [System directory API for contract catalog reads](/docs/api-reference/reference/directory): Read the Directory-backed system contract catalog for the active network or a specific Directory contract. - [Directory trusted issuers API reference](/docs/api-reference/reference/directory-trusted-issuers): Read the platform-wide directory of trusted claim issuers and the claim topics each one is authorised to verify, through the DALP Platform API. - [System trusted issuers API reference](/docs/api-reference/reference/system-trusted-issuers): Read the trusted claim issuers that apply to one system, and the claim topics each one is authorised to verify, through the DALP Platform API. - [Directory topic schemes API reference](/docs/api-reference/reference/directory-topic-schemes): Read the platform-wide directory of claim topic schemes, including the claim data shape each one defines, through the DALP Platform API. - [System claim topics API reference](/docs/api-reference/reference/system-claim-topics): Read the claim topics registered for the active system, including each topic's claim data shape and its authorised trusted issuers, through the DALP Platform API. - [Organisation and system scope in the DALP API](/docs/api-reference/reference/organization-system-scope): Understand how DALP API requests are bounded by organisation membership, API key scope, active system context, and resource visibility. - [System value and transaction stats API reference](/docs/api-reference/reference/system-value-and-transaction-stats): Read the organization-wide total value of indexed assets and the transfer activity for your wallet set through the DALP Platform API, including trailing-window and custom-range time series. - [System identity and compliance stats API reference](/docs/api-reference/reference/system-identity-compliance-stats): Read organization-wide identity, claim, trusted-issuer, and topic-scheme statistics through the DALP Platform API, including current snapshots, trailing-window series, and claim coverage gaps. - [Operational integration patterns for the DALP API](/docs/api-reference/reference/operational-integration-patterns): Answer common integration questions about DALP event access, token discovery, upgrade operations, operational monitoring, and self-hosted deployment responsibilities. - [System upgrade comparison API](/docs/api-reference/reference/system-upgrade-comparison): Read your system's upgrade readiness through the DALP Platform API. Compare every deployed component against the network directory, see which differ, and confirm what an upgrade will change before you run it. - [Token factory registry API](/docs/api-reference/reference/token-factories): Read the token factories deployed on your system through the DALP Platform API. List every factory and its asset type, read one by address, and check whether an address is available before you deploy. - [Webhook delivery receipts API](/docs/api-reference/reference/webhook-receipts): Read and submit counter-signed webhook delivery receipts through the DALP Platform API for non-repudiation proof that a consumer received and verified each event. - [Participant directory API reference](/docs/api-reference/reference/participant-directory): List an organization's participants for a given address purpose and classify their wallet addresses as externally owned or smart wallets through the DALP Platform API. - [Participant assumption API reference](/docs/api-reference/reference/participant-assumption): List the participants a user may act as and learn how the Platform API authorizes acting as an organization participant through the X-Participant header. - [User lookup API reference](/docs/api-reference/reference/user-lookup): Look up a single platform user by their approved national ID, wallet address, email address, or internal user ID through the DALP Platform API, with exact-match semantics and clear not-found behaviour. - [User security administration API reference](/docs/api-reference/reference/user-security-administration): Read a member's MFA status and active sessions, revoke sessions, reset multi-factor authentication, trigger a password reset, and handle the permission, not-found, and validation errors these operator endpoints return. - [Organization admins API reference](/docs/api-reference/reference/organization-admins): List the admin users of an organization through the DALP Platform API, with filtering, sorting, and global search over the on-chain role holders mapped to their platform profiles. - [Participant role assignments API](/docs/api-reference/reference/participant-role-assignments): Read participant role assignments across signing and operations addresses through the DALP Platform API, including the drift signal that flags when on-chain roles do not match. - [Organization settings API reference](/docs/api-reference/reference/organization-settings): Read, list, create, update, and delete an organization's key-value settings through the DALP Platform API, including the base currency, system address, target currencies, and account abstraction toggle. - [Organization membership API reference](/docs/api-reference/reference/organization-membership): Add a user to the active organization with a member or owner role through the DALP Platform API, including the permission, onboarding, and owner-grant rules and the exact error codes. - [System account roles API reference](/docs/api-reference/reference/system-account-roles): Read the system access-control register through the DALP Platform API, listing every account and the roles it holds and reading the roles for a single account address. - [Participant activity API reference](/docs/api-reference/reference/participant-activity): Read a participant's on-chain activity feed and activity time series across every wallet they own, EOA and smart wallet, through the DALP Platform API. - [Account activity API reference](/docs/api-reference/reference/account-activity): Read the on-chain activity feed and activity time series for a single account address through the DALP Platform API, including meta-transaction attribution. - [User statistics API reference](/docs/api-reference/reference/user-statistics): Read organization user statistics through the DALP Platform API, including total members, recently active members, and a cumulative member growth series for dashboards. - [Identity registration status](/docs/api-reference/reference/identity-registration-status): Check whether a wallet holds a registered, active on-chain identity in a DALP system before you transact, through the Platform API registration status endpoint. - [Actions API](/docs/api-reference/reference/actions): List or live-stream the pending and historical operational actions across an organization or one token through the DALP Platform API, with status, type, and per-action metadata for review and execution. - [Global search API reference](/docs/api-reference/reference/global-search): Run one permission-aware query across contacts, tokens, users, and system contracts in the active system through the DALP Platform API, with results grouped by section. - [Metadata resolver API](/docs/api-reference/reference/metadata-resolver): Resolve a content-addressed metadata hash into its payload through the DALP Platform API, with the bytes32 hash parameter, the resolved content type, the base64 payload, and the not-found error. - [Contract inspector API reference](/docs/api-reference/reference/contract-inspector): Inspect any on-chain address through the DALP Platform API to read its token metadata, detect a SMART (ERC-3643) interface, see how the active organization already knows it, and check external-token registration eligibility. - [System addon factory registry API reference](/docs/api-reference/reference/addon-factories): List and read the system addon factories registered on the active DALP system through the Platform API, including type, kind, deployment, and implementation fields. - [Asset class definitions API, CLI, and SDK reference](/docs/api-reference/reference/asset-class-definitions): List, create, read, update, and delete organisation asset class definitions through the DALP Platform API, CLI, and SDK, hide or unhide classes through the API and SDK, and understand how class names behave across locales. - [Instrument templates API](/docs/api-reference/reference/instrument-templates): List, read, create, update, publish, and delete instrument templates through the DALP Platform API and SDK, and hide or show templates per organisation with the isHidden filter and toggle. - [Asset decimals and precise amount handling in the DALP API](/docs/api-reference/reference/asset-decimals): Send and read DALP asset amounts without losing precision. - [Feature inventory API for token-feature rollups](/docs/api-reference/reference/feature-inventory): Read the active system's per-feature attachment rollup through the DALP Platform API. See which token-feature capabilities are live, how many tokens carry each, and when each was last attached. - Tokens - [Token lifecycle](/docs/api-reference/tokens/token-lifecycle): How to sequence API calls for token creation, minting, transfers, burns, feature detach, and event reconciliation with safe idempotent retries. - [Corporate actions](/docs/api-reference/tokens/corporate-actions): Named catalog for cash dividends, bond coupons, bonus issues, rights issues, capital decreases, splits, and spin-offs. - [Token creation progress stream](/docs/api-reference/tokens/token-create-progress-stream): Subscribe to a server-sent events stream that reports token-creation deployment progress for one async create request, then handle each phase event until the deployment completes or fails. - [Token holders and transfers](/docs/api-reference/tokens/token-holders-transfers): Query token holders, inspect balances, execute transfers, and understand the controls around standard, allowance-based, forced, and pre-approved transfer workflows. - [Recipient eligibility check](/docs/api-reference/tokens/recipient-eligibility): Check whether one address can receive a token for a mint, transfer, or burn before you submit the on-chain transaction. - [Transfer simulation](/docs/api-reference/tokens/transfer-simulate): Simulate a token transfer before you submit it, and get an authoritative will-clear or will-revert verdict plus a classified list of compliance blockers. - [Inherited global controls](/docs/api-reference/tokens/inherited-global-controls): Read which global compliance controls actually run for one token, after scope and disabled bindings are applied. - [Tokens pending role migration](/docs/api-reference/tokens/aa-role-migration-pending): List the tokens whose access-control roles still need to be mirrored onto participants' smart accounts after the advanced-accounts migration, so each token's admin can finish the job. - [Token events](/docs/api-reference/tokens/token-events): Use the token events endpoint to read indexed on-chain events for one token, with collection pagination, filters, facets, and Console table behaviour. - [Token metadata](/docs/api-reference/tokens/token-metadata): Set and remove mutable token metadata entries for DALP asset tokens using the token metadata API. - [Token document uploads](/docs/api-reference/tokens/token-documents): Upload, confirm, list, download, and delete token or asset documents through the DALP API, SDK, and CLI. - [Token topic schemes](/docs/api-reference/tokens/token-topic-schemes): Read inherited claim topic schemes for a token and register token-specific schemes through the DALP API. - [Token permits](/docs/api-reference/tokens/token-permits): Let a custodian relay a holder's EIP-2612 signature to set an allowance without requiring the holder to send an on-chain approval transaction. - [Managed permits](/docs/api-reference/tokens/managed-permits): Sign an EIP-2612 permit with a holder's managed key, store it as a pending signed permit, list stored permits, and relay one later as the token custodian. - [Token conversion records](/docs/api-reference/tokens/token-conversion-records): Reconcile accepted conversion requests with target-side issuance by reading indexed conversion lifecycle records, status, converted amounts, and replay identifiers. - [Token conversion triggers](/docs/api-reference/tokens/token-conversion-triggers): Read the conversion triggers on a DALP token, including the effective price after discount and cap, and the published, disabled, and republished lifecycle of each trigger. - [Token conversion holder state](/docs/api-reference/tokens/token-conversion-holder-state): Read a single holder's available principal and total converted on a DALP token straight from the attached conversion feature, so you can show an accurate current position. - [Token conversion authorizations](/docs/api-reference/tokens/token-conversion-authorizations): Read which target tokens a DALP token can convert into, and which source tokens can convert into it, through two paginated conversion authorization endpoints. - [Tokens pending role migration API](/docs/api-reference/tokens/tokens-pending-role-migration): List the tokens whose participant roles still need migrating onto smart accounts after advanced accounts was enabled, so each token admin knows what to finish. - [Token price resolution](/docs/api-reference/tokens/token-price-resolution): Read token prices through indexed base-price feeds and FX conversion feeds. - [Token treasury health](/docs/api-reference/tokens/token-treasury-health): Read treasury funding readiness for maturity-redemption and fixed-treasury-yield features. - [Wallet distribution statistics](/docs/api-reference/tokens/wallet-distribution-statistics): Read indexed holder concentration buckets for a token through the DALP API. - [Token supply statistics](/docs/api-reference/tokens/token-supply-statistics): Read indexed total supply and mint/burn history for a token through the DALP API. - [Token volume statistics](/docs/api-reference/tokens/token-volume-statistics): Read indexed transfer-volume history for a token through the DALP API. - [Token collateral statistics](/docs/api-reference/tokens/token-collateral-statistics): Verify that a reserve-backed token holds sufficient collateral before approving a mint or preparing a reconciliation pack. - [Yield coverage statistics](/docs/api-reference/tokens/yield-coverage-statistics): Monitor funding gaps for fixed-treasury-yield tokens before they affect payouts, with schedule status, consumed interest, and allowance coverage in one call. - [Portfolio statistics](/docs/api-reference/tokens/portfolio-statistics): Query a participant's portfolio value time series and breakdowns, aggregated across their linked wallets, for the active DALP system. - [Realized P&L statistics](/docs/api-reference/tokens/realized-pnl-statistics): Read a participant's realized profit and loss as a paginated disposal list and as a bucketed time series, scoped to their own linked wallets in the active DALP system. - [Unrealized P&L over time](/docs/api-reference/tokens/unrealized-pnl-statistics): Read a participant's unrealized profit and loss for one token as a bucketed time series through the DALP API, scoped to their own linked wallets in the active system. - [System value and transaction statistics](/docs/api-reference/tokens/system-value-transaction-statistics): Read the total value of issued assets and transaction activity for a DALP system, as current figures or as time series for dashboards and reporting. - [System asset statistics](/docs/api-reference/tokens/system-asset-statistics): Read the asset count, value breakdown, and creation and activity trends for a DALP system through the Platform API, as current figures or as time series for dashboards and reporting. - [User asset balances](/docs/api-reference/tokens/user-asset-balances): List the authenticated participant's token holdings through the DALP API, aggregated across their linked wallets, with balances, base-currency value, cost basis, and unrealized profit and loss. - Token features - [Token features API](/docs/api-reference/token-features): Reference index for the thirteen DALP token features and the Platform API endpoints that configure and operate them during asset creation and servicing. - [Historical balances API](/docs/api-reference/token-features/historical-balances): API reference for reading DALP historical-balances checkpoints, including the timestamp timepoint model and the holder-history endpoints used by integrations. - [Balance snapshot at a block](/docs/api-reference/token-features/historical-balances-at-block): Reconstruct holder and total-supply balances as of a specific block across one or more tokens in the active DALP system, for audit and point-in-time reporting. - [Voting Power](/docs/api-reference/token-features/voting-power): API reference for the DALP Voting Power token feature, including delegation mutations, delegation history, current distribution, and per-account snapshot weights at a block. - [permit](/docs/api-reference/token-features/permit): API reference for the DALP permit token feature, which enables EIP-2612 signature-based approvals on the asset. - [Maturity redemption API](/docs/api-reference/token-features/maturity-redemption): Reference the endpoints that manage a fixed-income token's full payout lifecycle: attach the feature, mature the token, fund the treasury, and redeem holder positions. - [Fixed treasury yield API](/docs/api-reference/token-features/fixed-treasury-yield): Endpoint reference for fixed-treasury-yield, covering creation-time parameters, coverage reads, holder claim-period history, treasury funding and allowance approval, and submitting holder claims. - [Fixed yield schedule read API](/docs/api-reference/token-features/fixed-yield-schedule): Read a fixed yield schedule by contract address, including its rate, interval, denomination asset, claimed and unclaimed totals, and every accrual period. - [Dividend yield API](/docs/api-reference/token-features/dividend-yield): Endpoint reference for dividend-yield, covering creation-time parameters, declaring a dividend, the snapshot preview and confirm step, holder proofs and claims, treasury funding, deadline extension, and reclaim. - [Interest yield API](/docs/api-reference/token-features/interest-yield): Endpoint reference for interest-yield, covering creation-time parameters, rate updates, holder claims, treasury funding, rate history, and holder and issuer position reads. - [AUM Fee API reference](/docs/api-reference/token-features/aum-fee): Endpoints to configure AUM Fee on a token, read time-weighted accrued estimates, collect fees into a recipient wallet, freeze the rate, and page through collection history. - [Transaction fee API](/docs/api-reference/token-features/transaction-fee): Update rates, change the fee recipient, freeze future rate changes, and read collection history for tokens with the transaction-fee feature attached. - [Transaction fee accounting API reference](/docs/api-reference/token-features/transaction-fee-accounting): Configure rates, manage recipients, submit reconciliations, manage exemptions, and read accrual state for tokens with the transaction-fee-accounting feature. - [External transaction fee API](/docs/api-reference/token-features/external-transaction-fee): Endpoint reference for the external-transaction-fee feature, covering creation-time parameters and the mutation routes for updating fee amounts, recipient, fee token, and freeze state. - [conversion](/docs/api-reference/token-features/conversion): API reference for the conversion token feature: configuration, publishing and disabling priced triggers, setting the conversion window, the holder conversion request, and staged interest settlement. - [Conversion minter API](/docs/api-reference/token-features/conversion-minter): How to grant mint authority and configure the conversion-minter feature on the target asset so it mints to holders when the paired source asset burns their position. - Wallets - [Smart wallet API overview](/docs/api-reference/wallets/smart-wallets): Use the DALP smart wallet API to list account-abstraction wallets, inspect gas readiness, manage signers and modules, and coordinate multisig approvals. - [Integration walkthrough](/docs/api-reference/wallets/smart-wallet-integration-walkthrough): A step-by-step tutorial that takes you from confirming advanced accounts is active to submitting your first transaction through a participant's smart wallet. - [Multisig approvals](/docs/api-reference/wallets/smart-wallet-approvals): Create, inspect, and sign weighted multisig approvals for smart wallet user operations that need more signer weight before submission. - [Multisig thresholds](/docs/api-reference/wallets/smart-wallet-thresholds): Update and validate the approval threshold for a DALP smart wallet that uses weighted multisig signing. - [Account native balances](/docs/api-reference/wallets/account-native-balances): Read indexed native balances and history for accounts, plus the live custody wallet gas balance, in the active DALP system. - [Bundler REST API](/docs/api-reference/wallets/bundler): Submit and track ERC-4337 UserOperations, request ERC-7677 sponsorship, and discover the active EntryPoint through typed REST resources. - [Bundler wallet status and balance](/docs/api-reference/wallets/bundler-wallet-status): Read the active system's bundler wallet address and its native token balance through the DALP API to monitor sponsored-gas funding. - [Gas sponsorship paymasters](/docs/api-reference/wallets/system-paymasters): List system paymasters, check EntryPoint deposit balances, manage sponsorship configuration, and rotate signer keys through the DALP API. - [Gas treasury runway and fee split](/docs/api-reference/wallets/gas-treasury-runway): Read gas treasury balances, runway days, and burn rate, set the fee-split allocation, manage runway warning thresholds, and recover stranded balances through the DALP API. - Blockchain RPC - [JSON-RPC endpoint](/docs/api-reference/blockchain-rpc/json-rpc-endpoint): Send authenticated JSON-RPC read calls to any configured network through DALP's managed RPC endpoint, with a read-only method allowlist, per-key rate limits, and automatic failover across upstream providers. - [RPC API keys](/docs/api-reference/blockchain-rpc/rpc-api-keys): Issue, list, rotate, and revoke the API keys that authenticate JSON-RPC calls to your DALP networks. Each key carries its own name, expiry, rate limit, and documented error responses. - Compliance - [Compliance API route map for eligibility, templates, and recovery](/docs/api-reference/compliance): Choose the right DALP compliance API page for participant eligibility, policy templates, module bindings, identity recovery, and the KYC review lifecycle from version submission to reviewer decisions. - [Registered identities API reference](/docs/api-reference/compliance/registered-identities): List the on-chain registered contract identities in your system's identity registry, with filtering, search, sorting, and claim counts, through the DALP Platform API. - [Identity claim events API reference](/docs/api-reference/compliance/identity-claim-events): List the chronological claim lifecycle events for a registered identity, including added, changed, removed, and revoked claims, with filtering, sorting, and faceted counts through the DALP Platform API. - [Identity keys API reference](/docs/api-reference/compliance/identity-keys): List the ERC-734 keys registered on an identity contract, with each key's purpose, key type, and the block and transaction that added it, through the DALP Platform API. - [Participant eligibility](/docs/api-reference/compliance/participant-compliance-eligibility): Evaluate a participant against system-level compliance modules and read the verdict, reason codes, source, and per-wallet breakdown. - [Compliance module registry and token-binding API reference](/docs/api-reference/compliance/compliance-modules): List, register, install, configure, scope, and uninstall compliance modules through the API, on one token or globally across every bound token. - [Reusable compliance template API reference](/docs/api-reference/compliance/compliance-templates): Create, list, search, filter, publish, and delete reusable compliance templates through the DALP API. - [Token compliance expression](/docs/api-reference/compliance/token-compliance-expression): Read and replace a token's on-chain compliance expression, the postfix rule that gates holder verification, through the DALP Platform API, SDK, and CLI. - [Wallet and identity recovery API reference](/docs/api-reference/compliance/identity-recovery): Preview, start, and monitor identity recovery workflows for users who lost access to a wallet. - [KYC version submission](/docs/api-reference/compliance/kyc-version-submission): Create, edit, submit, and read back a versioned KYC profile, including the review-outcome trail, through the DALP Platform API, SDK, and CLI. - [KYC document uploads](/docs/api-reference/compliance/kyc-document-uploads): Upload, confirm, list, download, and delete KYC documents through the DALP API, SDK, and CLI, with auth-gated download URLs that re-check access on every request. - [KYC reviewer version actions](/docs/api-reference/compliance/kyc-reviewer-version-actions): Approve, reject, or request changes on a KYC profile version under review through the DALP Platform API, SDK, and CLI. - [KYC action request fulfillment](/docs/api-reference/compliance/kyc-action-request-fulfillment): Mark a reviewer's KYC change request as fulfilled once the user resubmits the requested data through the DALP Platform API, SDK, and CLI. - [KYC profile deletion](/docs/api-reference/compliance/kyc-profile-deletion): Delete a user's KYC profile record through the DALP Platform API, including who may call it, the request and response shape, and the idempotent already-removed response. - Files - [Private file access](/docs/api-reference/files/private-file-access): How DALP restricts KYC, organisation, and admin files to authenticated Console sessions and validates each request against the caller's object-key scope. - Feeds - [Exchange rates](/docs/api-reference/feeds/exchange-rates): Read current and historical fiat currency pair rates, discover supported currencies, and understand how DALP selects one feed per pair and resolves inverse pairs. - [Price feeds](/docs/api-reference/feeds/price-feeds): Read the on-chain price-feed registry through DALP. List registered feeds, read one feed, resolve a feed for a subject and topic, and inspect latest value, historical rounds, and staleness. - [Feed value submission](/docs/api-reference/feeds/feed-value-submission): Submit a signed value to an issuer-signed price feed through DALP. Read the issuer nonce, post a new value, and track the on-chain update. - Offerings - [Token sale offering flows](/docs/api-reference/offerings/token-sale-offering-flows): Create, configure, activate, buy, finalize, and settle a token sale offering through DALP APIs, SDK methods, and CLI commands. - Settlement - [XvP settlement flows](/docs/api-reference/settlement/xvp-settlement-flows): Create, approve, execute, and monitor XvP settlement flows through DALP APIs, SDKs, CLI commands, and polling. - Trading venue - [Trading venue flows](/docs/api-reference/trading-venue/trading-venue-flows): Read venue markets, calendars, and market data, place signed orders and quoting batches, manage watchlists, stream live depth, and administer markets, bands, participants, busts, and desk limits through the DALP v2 API. - Airdrops - [Airdrop distribution reads](/docs/api-reference/airdrops/airdrop-distribution-reads): List and read deployed airdrop distributions through the DALP Platform API, SDK, and CLI, with filtering, pagination, recipient counts, and error codes. - Governance - [Governance proposals and polls](/docs/api-reference/governance/governance-proposals-and-polls): Create proposals, run record-date votes, cast ballots, execute approved actions through the timelock, and run off-chain polls with DALP APIs, SDKs, and CLI commands. - Actions - [Actions feed and live updates](/docs/api-reference/actions/actions-feed): Reference for the DALP actions feed API: list pending, upcoming, executed, and expired actions with filters, facets, and pagination, then subscribe to the live server-sent events stream for real-time updates. - Observability - [API monitoring endpoints](/docs/api-reference/observability/api-monitoring): Query API traffic, latency, errors, request logs, and real-time API activity from the DALP monitoring API. - [Blockchain monitoring endpoints](/docs/api-reference/observability/blockchain-monitoring): Read per-chain indexer and chain-RPC health, sync lag, finality lag, block age, reindex progress, and raw health snapshots from the DALP blockchain monitoring API. - [Platform status endpoints](/docs/api-reference/observability/platform-status): Read DALP platform-status panels, stat cards, history, and transaction and workflow detail lists from the current API. - [Debug information export](/docs/api-reference/observability/debug-information-export): Export a point-in-time, redacted debug bundle from DALP so support can diagnose a restricted deployment without cluster or shell access. - [Transaction queue lifecycle and recovery](/docs/api-reference/observability/transaction-queue-lifecycle): Reference for the DALP transaction queue API: list and filter queued requests, read lifecycle status, cancel pending transactions with replace-by-fee, and run operator recovery for stuck or dead-lettered work. - [Reporting and audit access](/docs/api-reference/observability/reporting-audit-access): Use DALP's indexed read APIs, dashboard exports, transaction references, webhook delivery records, and audit-access responsibilities for reporting and data retrieval. - Administration - [Organizations administration API](/docs/api-reference/administration/organizations): List every organization on a DALP platform from one cross-tenant endpoint built for platform administrators. - [Invitations with roles API](/docs/api-reference/administration/role-invitations): Invite a user to an organization and pre-assign their on-chain roles in one call through the DALP Platform API, behind a wallet verification gate. - [Platform setup API](/docs/api-reference/administration/platform-setup): Read and finish the first-install platform setup flow on a DALP platform from two administration endpoints. - [Custody credentials API](/docs/api-reference/administration/custody-credentials): Read, probe, and rotate an organization's custody provider credentials through the DALP Platform API without ever exposing secret material. - Webhooks - [Webhook endpoints](/docs/api-reference/webhooks/webhook-endpoints): Configure DALP webhook endpoints, delivery privacy, idempotent mutations, signed receiver handling, retries, replay, and chain-of-custody proofs. - Events - [Webhook events](/docs/api-reference/events): Subscribe to DALP lifecycle events with AsyncAPI, signed webhooks, idempotent delivery, and typed SDK verification. - [Idempotency and outcomes](/docs/api-reference/events/idempotency-and-on-chain-outcome): Reconcile cached DAPI mutation responses with webhook-only on-chain outcomes, including final, retracted, and recalled events. - [access-control.role-granted.provisional](/docs/api-reference/events/access-control-role-granted-provisional): A role was granted on the access-control manager; the grant is provisional until the indexer reaches the configured reorg depth. - [access-control.role-granted.retracted](/docs/api-reference/events/access-control-role-granted-retracted): A role grant was retracted because a reorg invalidated the source log. - [access-control.role-revoked.provisional](/docs/api-reference/events/access-control-role-revoked-provisional): A role was revoked on the access-control manager; the revocation is provisional until the indexer reaches the configured reorg depth. - [access-control.role-revoked.retracted](/docs/api-reference/events/access-control-role-revoked-retracted): A role revocation was retracted because a reorg invalidated the source log. - [asset.issuance.provisional](/docs/api-reference/events/asset-issuance-provisional): An asset issuance transaction entered the reorg window and is provisionally visible. - [asset.issuance.retracted](/docs/api-reference/events/asset-issuance-retracted): An asset issuance event was retracted because a reorg invalidated the source log. - [compliance.freeze.recalled](/docs/api-reference/events/compliance-freeze-recalled): A compliance officer recalled an earlier compliance freeze event. - [identity.registration.provisional](/docs/api-reference/events/identity-registration-provisional): An identity was joined to an identity registry; the linkage is provisional until the indexer reaches the configured reorg depth. - [identity.registration.retracted](/docs/api-reference/events/identity-registration-retracted): An identity registration was retracted because a reorg invalidated the source log. - [settlement.transfer.retracted](/docs/api-reference/events/settlement-transfer-retracted): Reference for the DALP settlement.transfer.retracted webhook event that invalidates an earlier settlement transfer event after a chain reorg. - [token.transfer.final](/docs/api-reference/events/token-transfer-final): Reference for the DALP token.transfer.final webhook event that reports an indexed token transfer, final unless a chain reorg retracts it. - [token.transfer.pending](/docs/api-reference/events/token-transfer-pending): A token transfer was observed before block inclusion and may later finalize or retract. - [token.transfer.retracted](/docs/api-reference/events/token-transfer-retracted): A token transfer event was retracted because a reorg invalidated its pending or final source. - Contacts - [Contacts API](/docs/api-reference/contacts/address-book-contacts): Store named EVM wallet contacts, reuse them in DALP operations, and keep address-book convenience separate from compliance controls. - External tokens - [External tokens](/docs/api-reference/external-tokens/external-tokens): Register and list existing EVM token contracts that were not deployed through DALP factories, including inspection, collection semantics, verification requirements, and error handling. - Workflow - [workflow engine operator API](/docs/api-reference/workflow/workflow-engine-operator-api): Operator API routes for workflow engine health checks, service re-registration, stale deployment cleanup, preparing stuck workflows for retry, and resuming paused invocations. - Errors - [Errors overview](/docs/api-reference/errors/overview): Index of DALP's error catalogs and handling guidance. Map an error you encountered to the right reference page, find the domain the error covers, and choose the next action for your integration. - [DALP error index](/docs/api-reference/errors): Look up any error your integration can receive and jump to the reference page that explains its cause and its fix. - [Error handling](/docs/api-reference/errors/error-handling): Handle DALP API failures with stable error identifiers, retry decisions, and support-ready diagnostics. - [Platform API Error Reference](/docs/api-reference/errors/platform-api-error-reference): Complete reference of all Platform API error codes returned by the DALP API, with HTTP status, retryability, and remediation guidance. - [Error code reference](/docs/api-reference/errors/error-code-reference): Find the cause and the fix for every on-chain revert your contracts can return, with retryability for each. - Changelog - [Changelog](/docs/changelog): Find every user-visible capability, API change, and operator workflow update shipped in the 3.x line, with context for what to act on. - DALP 3.1 - [DALP 3.1: run the platform as your own](/docs/changelog/dalp-3-1): Each organization brings its own custody provider, contracts deploy inside air-gapped clusters with customer-held keys, admins run the platform with first-class, audited tools, and each deployment can run its own trading venue. - [Trade it where you issued it](/docs/changelog/dalp-3-1/trading-venue): Every DALP deployment can now run its own permissioned orderbook. Identity-registered participants trade listed token pairs with funds that never leave their wallets, and every fill passes the token's own compliance checks. - [Run it like an exchange](/docs/changelog/dalp-3-1/trading-venue-market-structure): The Trading Venue gains trading calendars with opening auctions and official closes, auction-only private markets, stop orders, price bands, bulk quoting for market makers, and an audited trade-bust remedy. - [Bring your own custody, per organization](/docs/changelog/dalp-3-1/org-custody): Each organization on a DALP deployment now configures its own custody provider, tests the credentials before adopting them, and rotates them from the Console, with secrets masked and never returned. - [Deploy where no one else can reach](/docs/changelog/dalp-3-1/air-gapped-deployment): DALP deploys its contracts inside an air-gapped cluster, signing with a key only the customer holds, pulling images from a mirrored registry, and trusting object storage behind a private CA. - [Run and support the platform](/docs/changelog/dalp-3-1/platform-operations): Archive and restore organizations with an audit trail, reset a user's onboarding, invite people with their on-chain roles pre-assigned, and tighten KYC search and uniqueness. - DALP 3.0 - [DALP 3.0: design your own digital asset](/docs/changelog/dalp-3-0): Reusable instrument and compliance templates let regulated teams move from policy definition to live instrument without rebuilding from scratch on every launch. - [Design your own assets from templates](/docs/changelog/dalp-3-0/asset-templates): Turn a proven asset setup into a reusable template, so the next instrument starts from a standard instead of a blank form. Your institution's configuration knowledge travels with it. - [Write your compliance policy once](/docs/changelog/dalp-3-0/compliance-templates): Package an entire compliance policy (identity, jurisdictions, supply caps, approvals) once and apply it to every asset in a program, so the chain enforces the same rules at every transfer. - [Keep signing inside your own custody](/docs/changelog/dalp-3-0/custody): Sign through your own custody provider while DALP prepares, broadcasts, and tracks every transaction to confirmation, with keys that never leave the vault. - [Operators act, the platform sponsors gas](/docs/changelog/dalp-3-0/advanced-accounts): ERC-4337 smart wallets and a system paymaster eliminate the native-token balance requirement, so on-chain work runs under enforced role boundaries without a gas custody problem. - [Transactions that recover themselves](/docs/changelog/dalp-3-0/durable-transactions): Every transaction carries explicit state across preparation, approval, broadcast, and confirmation, so a stuck step recovers instead of going dark, and a retry can never duplicate an in-flight send. - [A blockchain index, built into the platform](/docs/changelog/dalp-3-0/ledger-index): A live, multi-chain index that decodes every on-chain event the moment a block is final, reorg-safe and queryable as plain business data, with balances at any past block. - [Signed prices, on-chain](/docs/changelog/dalp-3-0/data-feeds): Push off-chain prices and values into assets through issuer-signed, per-token feeds. An asset only acts on a figure a named party has cryptographically vouched for. - [One identity surface per participant](/docs/changelog/dalp-3-0/identity): Verified KYC claims live on-chain; the asset checks the claim at transfer time and never sees the documents. In 3.0 the full lifecycle (provider intake, versioned history, recovery, and the participant view) lives on one surface. - [Token features that behave like instruments](/docs/changelog/dalp-3-0/token-features): Fees, yield, redemption, and conversion now carry the controls a real financial instrument needs. - [Lower gas on every on-chain operation](/docs/changelog/dalp-3-0/gas-optimization): DALP 3.0 optimizes the hot path across every digital asset: identity verification is up to 40% cheaper, a supply-cap mint saves roughly 146,000 gas, and compliance checks now run in constant time regardless of list length. - [Push signed events, stop polling](/docs/changelog/dalp-3-0/webhooks): HMAC-signed delivery with exponential retries and counter-signed receipts means every settlement, approval, and deployment reaches your systems the moment it happens, with no polling loop to maintain. - [Platform health in one view](/docs/changelog/dalp-3-0/monitoring): One verdict tells you whether the platform can proceed, without leaving the product to stitch together three separate infrastructure views. - [Upgrade your platform from the on-chain directory](/docs/changelog/dalp-3-0/self-managed-upgrade): System updates compares your deployed components against the on-chain directory and upgrades every out-of-date implementation in one guided run, with addresses and balances preserved. - [Drive all of it from the SDK, CLI, and MCP](/docs/changelog/dalp-3-0/cli-api): Every console action is available through the SDK, an AI-native CLI, and an MCP server that agents drive. Same permissions, same controls, whether a human or an agent is behind the wheel. The REST surface has its own entry. - [A typed v2 API built for real integrations](/docs/changelog/dalp-3-0/v2-api): The v2 REST API at /api/v2 adds JSON:API filtering and sorting, offset pagination, idempotency keys for safe retries, and headers that control identity, wallet routing, and response timing. - [Hardened for enterprise security review](/docs/changelog/dalp-3-0/security): Authentication, key material, roles, and deployment, hardened and documented for an enterprise security review in DALP 3.0. - [Documentation rebuilt around the reader](/docs/changelog/dalp-3-0/documentation): DALP 3.0 splits docs into six audience tracks so each role reads pages written for their job, not a shared feature dump. ## Agent endpoints - [Full corpus](/docs/llms-full.txt): every documentation page concatenated as markdown - Search: GET /docs/api/search?query= matches page titles, descriptions, headings, and body text, returned as JSON. Four page groups are not in this index: /docs/api-reference/errors, /docs/api-reference/errors/error-code-reference, /docs/api-reference/reference/api-changes, and the webhook event pages under /docs/api-reference/events/. Find them through /docs/llms.txt, which lists every page including them. Add &tag= to hold the search to one section. It takes one value, never a list: operators, api-reference, architects, developers, compliance-security, changelog, business, architecture, overview. Every page carries exactly one section, so &tag=a,b matches no page at all and returns an empty array. Add &limit= to change the result cap. The cap counts records, not pages: each matched page contributes one record for the page itself plus up to 8 text fragments from that same page, so the default of 60 records can be as few as 7 pages. An empty, fractional, zero, or negative value falls back to 60, and anything above 200 is capped at 200. Every response reports the cap it applied in the X-Docs-Search-Limit header, and says in X-Docs-Search-Truncated whether more records were available: true means raise &limit= or narrow the query, false means the array is the complete result set.