Most digital assets platform shortlists place two different purchases against a single RFP. Architecture assesses nodes, middleware and, at times, a first-party custody product. Ops, Compliance, Settlement, Risk and Audit assess whether a regulated instrument can be issued, governed correctly, dual-controlled, serviced and reconstructed for Audit within one operating model.
Those purchases are distinct product categories. One is a blockchain stack. The other is a digital asset lifecycle platform.
SettleMint DALP is the entirely composable Digital Asset Lifecycle Platform. Enterprise stack vendors package networks, middleware and a custody product with supporting workflows. DALP provides regulated issuance, compliance-gated transfer and settlement-tracked operations on the custodians and EVM networks the institution already runs.
This article is an evaluation brief for committees that need stack demonstrations to answer infrastructure questions, and lifecycle demonstrations to answer programme questions, each on its own terms.
Public materials for enterprise blockchain vendors, including platforms such as Kaleido that organise Digital Assets, Web3 Middleware (including FireFly) and Chain Infrastructure as product lines, help the market evaluate breadth of stack. That substance earns its place: multiparty networks and orchestration are demanding work.
Regulated programmes also surface Board-level operating questions:
Those questions sit on the lifecycle side of the evaluation. Additional chain capacity alone addresses a different set of needs.
A stack fits when the programme focuses on the network laboratory, the multiparty mesh or the integration fabric. Vendors with stronger stack portfolios, including Kaleido, typically emphasise the following concerns.
| Stack concern | Typical owner | Evidence to request |
|---|---|---|
| Public and permissioned nodes, gas and explorer operations | Architecture / SRE | Deploy path, SLAs, multi-cloud posture |
| Middleware and transaction orchestration (for example FireFly-class products) | Integration PMO | Exactly-once delivery, connectors, event reliability |
| First-party platform custody product | Risk / Ops (joint) | Key control model, HSM options, policy at signing |
| Multi-protocol range | Architecture | Protocols in production use, with documented support |
| CBDC, FMI or digital cash infrastructure narratives | Programme office | Scope that sits under funded programme ownership |
Review stack vendors against these rows when infrastructure and multiparty connectivity are the funded agenda.
A lifecycle platform fits when the programme is the regulated instrument after rails exist, or when rails will be selected independently of the asset application.
| Lifecycle concern | Typical owner | Evidence to request |
|---|---|---|
| Instrument issuance through servicing | Product / Ops | Asset classes and operator actions after go-live |
| Eligibility and identity in the transfer path | Compliance | Live deny path, claims, freezes, recovery |
| Durable transaction states and dual control | Ops / Settlement | Named states, PENDING_APPROVAL, rescue routes |
| Terminal settlement verdict | Settlement / Audit | Completed, failed, dead-letter or cancelled as explicit outcomes |
| Provider-routed custody | Risk | Named vault adapters; keys remain with the approved vault |
| Queryable history | Audit / Ops | Balances and events as business data, including as-of queries |
For how SettleMint maps those systems, see the DALP platform overview and Getting Started with SettleMint DALP.
Ops needs an instruction that remains visible while custody is waiting, a clear state when a broadcast requires intervention, and day-two servicing (freeze, force transfer, maturity, distribution) on the same control surface as issuance.
In a controlled demonstration, request one dual-control transfer, one managed failure and one operator recovery. A platform that returns only a hash leaves Ops without an operating model.
Compliance requires transfer gates tied to identity claims and modular rules, with screening evidence that names vendors the institution already accepts.
On SettleMint DALP, regulated transfers are designed to check eligibility off chain and again on chain. The configuration matrix includes:
Adapters orchestrate evidence. Legal policy remains the institution’s. Related: compliance templates and identity and KYC for digital assets.
Settlement requires unambiguous outcomes. A request reaches a terminal verdict, or it remains in a named intermediate state. DALP’s transaction lifecycle uses durable named states from receipt through preparing, signing, broadcast and confirmation, with custodian approval when dual control applies, and recovery paths when runs fail or enter dead-letter.
Atomic DvP and multiparty XvP cover on-ledger legs the settlement contract can move. Cash settles on-platform when tokenized. Detail: durable transactions and ledger history.
Audit needs history as a first-class product surface. Balances, transfers, fees, redemptions and operator actions should be queryable as business data across reporting cycles.
Lifecycle platforms sit within an architecture the institution already governs. They bound the domain model; they leave network design and deployment posture with Architecture.
SettleMint DALP’s production asset and compliance track is EVM. Where Fabric, Corda or multi-protocol BaaS is the funded scope, stack vendors such as Kaleido belong on that shortlist on their merits. Where EVM is accepted and the vault is already chosen, Architecture’s work becomes RPC topology, deployment posture (on-prem, institution cloud, dedicated SaaS) and clean seams to middleware, with custody remaining under Risk’s mandate.
These patterns recur in institutional evaluations when lifecycle gaps remain:
Each pattern points to a lifecycle requirement. Stack investment can still be the right infrastructure decision, and the asset programme may still need a dedicated lifecycle product beside it.
Many institutions retain the infrastructure vendor and add a lifecycle layer. A coherent multi-vendor design:
A practical proof of concept: retain the network and the vault, and demonstrate the lifecycle under Ops, Compliance and Settlement.
Weight columns according to the funded programme:
| Criterion | Relevance when buying a stack | Relevance when buying a lifecycle platform | Evidence to request in demonstrations |
|---|---|---|---|
| Multi-protocol nodes | High | Lower for EVM-scoped programmes | Deploy time, operational path |
| FireFly / middleware | High | Medium (coexistence often preferred) | Message reliability together with domain state |
| Platform custody product | High when first-party custody is desired | Depends on Risk mandate | Key control model versus required MPC or HSM |
| ERC-3643 / identity gates | Medium | High | Live compliance deny path |
| External custody adapters | Medium | High | Dual control with a named vault |
| Terminal settlement verdict | Medium | High | Failure and recovery walkthrough |
| Bond, fund or deposit servicing | Varies by SKU | High | Maturity, freeze, distribution operations |
| CBDC / cash-rail programmes | High when funded as infrastructure | Programme-specific | Documented programme ownership |
DALP is the Digital Asset Lifecycle Platform, entirely composable. Composability means named adapters and contract seams for custody, screening, secrets, storage and chain configuration.
DALP is designed for Ops, Compliance, Settlement, Risk and Audit running regulated programmes on EVM rails and institutional vaults.
Hyperledger Fabric or Corda farms, FireFly product stewardship, SWIFT or RTGS cash rails, and CBDC infrastructure programmes remain the domain of dedicated stack and market-infrastructure offerings. On those agendas, vendors such as Kaleido should be evaluated on the strength of their stack proposition.
When Kaleido or another stack vendor owns the infrastructure shortlist, evaluate that vendor on stack merit with full respect for that craft. When the evaluation committee is the asset programme, evaluate a lifecycle platform on lifecycle merit.
Educational material around Kaleido digital assets and FireFly tokenization remains valuable for understanding stack layers. Use that material to inform architecture, then apply the criteria above so Ops, Compliance, Settlement, Risk and Audit receive a dedicated hearing on lifecycle requirements.
Supporting pages on settlemint.com:
For product shape and systems view, continue with the platform overview or request an architecture review for Ops, Compliance and Settlement.
If the funded problem is networks, middleware and multiparty infrastructure, select a stack and evaluate it as a stack. If the funded problem is a regulated instrument Ops, Compliance, Settlement, Risk and Audit must run for years, select a lifecycle platform and evaluate it as a lifecycle platform.
SettleMint DALP exists for the second purchase: the entirely composable Digital Asset Lifecycle Platform, on the custodians and EVM networks the institution already runs.
Map stack scope and lifecycle scope against your custody model and first instrument.
Architecture review for Ops, Compliance and Settlement ↗ · Secondary path: DALP on your Fireblocks or DFNS deployment, on the chain you already operate.
SettleMint, headquartered in Leuven, Belgium, with offices in UAE, Singapore and Japan, is the company behind DALP, the entirely composable Digital Asset Lifecycle Platform. DALP enables financial institutions, market infrastructure operators and governments to build, deploy and manage digital assets and blockchain applications at scale.
A blockchain stack focuses on networks, middleware and, in many cases, a first-party custody product. A digital asset lifecycle platform focuses on regulated issuance, eligibility, custody-routed execution, servicing and queryable history for Ops, Compliance, Settlement, Risk and Audit.
How does SettleMint DALP relate to Kaleido?Kaleido is a strong option when the programme centres on enterprise chain infrastructure, Web3 middleware and related stack capabilities. SettleMint DALP addresses regulated digital asset programmes where Ops, Compliance, Settlement, Risk and Audit need lifecycle control on institutional custody and EVM networks the organisation already runs. The two products answer different primary questions and can also operate together in a multi-vendor design.
Can stack infrastructure and DALP run together?Yes. Architecture can retain network connectivity and middleware. DALP provides the asset registry, compliance claims path, durable transactions and settlement semantics, while signing remains with DFNS, Fireblocks, Ripple Custody as shipped, Thales Luna or the vault Risk has already approved.
Does DALP replace FireFly?FireFly remains enterprise Web3 orchestration. DALP is a regulated asset lifecycle product. Each serves a distinct role; together they can form a coherent architecture.
Which custody and screening providers does DALP integrate?Custody and HSM: DFNS, Fireblocks, Ripple Custody (partial relative to full DFNS and Fireblocks parity), Thales Luna. KYC: Jumio, Onfido, Persona, Sumsub, Trulioo (DataVerify), Veriff. KYB: Onfido, Persona, Middesk. AML and analytics: ComplyAdvantage, Elliptic. KYT: Sumsub.
What should Settlement request in a platform demonstration?A named state for every on-chain write, dual-control paths when custody requires approval, recovery or dead-letter handling, and a terminal settlement verdict. Completion should rest on a terminal state, with asynchronous handles kept distinct from confirmation.
What should Compliance request?Eligibility that fails closed on transfer, identity claims tied to trusted issuers, and screening and KYC or KYB providers the institution can name in policy and contracts.