SettleMint vs Kresus KITE
Use DALP to operate regulated assets after a Kresus KITE launch.
Operating a regulated asset starts the day after issuance, when coupons, redemptions, and corporate actions begin moving against a live holder register. Kresus KITE positions itself as full-stack orchestration for launching tokenized investment products, naming embedded compliance, role governance, and T+0 settlement on its product page. DALP's ERC-3643/SMART implementation checks holder eligibility inside the transfer call itself: if a token is sent to a wallet that fails its KYC or jurisdiction attribute, the transaction reverts and never settles, so there is no failed trade to unwind across a custodian and a transfer agent the next morning. Every coupon and redemption runs the same eligibility check and writes the approving signer to chain, so a servicing team reads one ledger instead of matching a payment file against a spreadsheet.
Feature Comparison
SettleMint DALP vs Kresus KITE: what matters for regulated institutions
| Decision area | SettleMint DALP | Kresus KITE |
|---|---|---|
| Primary job | Runs regulated digital assets after issuance on an ERC-3643/SMART implementation, where transfer rules and eligibility live in the token contract: issuance, compliance, settlement and servicing. | KITE's product page describes full-stack orchestration for tokenized investment products from issuance to settlement, naming T+0 settlement, embedded compliance, collateral mobility, programmable compliance and role governance. DALP runs the operating layer for actions that follow issuance. |
| Best fit | Institutions that run an asset in production after launch, with approval gates and an audit record across its lifecycle. | KITE's public positioning centres on white-label tokenization and investor workflows. DALP covers the lifecycle that continues once the asset is issued. |
| Operations after launch | After issuance, DALP routes each action through a defined approval, checks eligibility in the token contract before a transfer executes, and writes the result to an audit record. Custody orchestration, settlement and event servicing run in the same workflow on EVM infrastructure. | KITE's product page lists T+0 settlement and investor workflows. DALP covers post-issuance servicing, exceptions and recorded approvals. |
| Compliance | Eligibility and transfer rules are evaluated by the token contract before a regulated movement executes. A transfer to a wallet that fails the eligibility check reverts in the same transaction, so there is no settled position to claw back. See DALP compliance documentation. | DALP lets the institution define the eligibility and transfer rules enforced on chain. KITE's product page lists programmable compliance and transfer restrictions in its own model. |
| Settlement and servicing | A bond coupon or fund redemption runs as an approved step in DALP and is written to the audit record at execution, with the paying party, amount and timestamp captured on chain. The servicing team reads that record rather than rebuilding the event from custodian statements and spreadsheets after the fact. See settlement and servicing requirements. | DALP handles servicing and settlement events after issuance inside its workflow. KITE's product page names embedded compliance and role governance in its issuance-to-settlement scope. |
| Institutional requirements | Regulated institutions usually test three things. First, whether the platform covers the lifecycle from onboarding and issuance through servicing, transfer control, redemption and reconciliation. Second, whether it can run in production with a security review and support path. Third, whether compliance controls, eligibility rules and maker-checker approvals run before execution and leave an audit record. | DALP enforces eligibility in the token contract and records approvals across issuance and post-issuance. KITE's product page names embedded compliance, role governance and enterprise integrations in its own scope. |
| Distribution and access | DALP holds issuance terms, approvals and servicing inside the institution; distribution and venue connectivity attach around that core without moving lifecycle control outside it. | KITE's product page names collateral mobility and enterprise integrations. DALP keeps issuance terms, approvals and servicing under the institution's control alongside that reach. |
| Approvals and segregation of duties | DALP assigns each team a defined role, so authority to approve, sign or act on an asset is set in advance and recorded each time it is used. | KITE's product page lists role governance and key-management options. DALP records the named approver and timestamp against each action. |
| Network and chain support | DALP runs on EVM, using the same wallet, contracts and workflows across permissioned and public EVM deployments. No native Canton, Solana or Fabric support is implied. | KITE's product page names enterprise integrations across its stack. DALP gives the institution one EVM operating model across permissioned and public deployments. |
Why Choose DALP
Why regulated institutions choose DALP
KITE speaks the executive language of compliant issuance and settlement. The harder work begins once the product is live: a quarterly coupon on a private credit note, a partial redemption, a register update after a corporate action, each one has to confirm the recipient is still an eligible holder before value moves, and each has to name the signer who released it. DALP routes these post-issuance events through the same on-chain transfer rules that governed the initial allocation, so a redemption that would breach a holding limit reverts at execution instead of surfacing as a break a reconciliation analyst chases down weeks later.
Branded portals and issuance flows get a programme started, but the harder work is governing how a tokenized bond or fund unit moves once it is live. When a transfer hits an investor who has fallen out of an eligibility window, DALP rejects it at execution against the ERC-3643 identity registry, so it never reaches settlement and there is nothing to unwind. Kresus KITE's product page positions KITE as a Kresus Institutional Tokenization Engine for white-label tokenization and investor workflows, which suits programmes where the investor experience is the priority.
Take a tokenized money market fund that limits holders to verified institutional investors. When a transfer is submitted to an address outside that registry, DALP rejects the transaction at execution rather than booking it and reversing it the next day. The check reads the same ERC-3643/SMART identity and compliance modules used to issue the fund, so eligibility and transfer restrictions are evaluated by the token contract itself. For a servicing desk, that means no after-the-fact cancel-and-rebook and no investor who briefly held units they were never allowed to hold.
After issuance, the events that keep a security alive run on the contracts that created it. A semi-annual coupon pays only the holders in the current eligible set, and a redemption settles against that same registry, with each action carrying the on-chain record of who approved it. The alternative is a servicing analyst exporting a holder file to a spreadsheet, matching it against payment runs by hand, and catching a stale eligibility flag only after a coupon has already paid an investor who should have been excluded. Keeping the event on the governed contract removes that off-platform step and the wrong payment it can produce.
Key Differentiators
What DALP runs across the regulated asset lifecycle
When a bond coupon or a fund redemption comes due, the payment runs through the same governed workflow that issued the asset on an ERC-3643 token contract. The eligibility list, the role approvals and the settlement step are the same ones used at issuance. A servicing team does not rekey the event into a separate ledger after the fact, which is where date errors and missed holders tend to enter the process.
An ERC-3643 token contract checks the recipient against its on-chain eligibility registry as a precondition of any transfer. Send 10,000 units to a wallet that is not on that registry and the contract reverts the transaction; the trade never reaches a holder who cannot lawfully receive it. There is no failed settlement to reverse the next day and no off-ledger correction to file.
Approval, signing and action rights map to named roles before the asset launches, and every use writes to the on-chain record. When an auditor asks who authorized a specific redemption on a specific date, the answer is the signing address and timestamp on the transaction, not a reconstructed email trail.
A redemption clears against the same eligibility registry and role approvals that governed issuance. The institution does not run a second manual process for life after issuance, so the rules a regulator reviewed at launch are the rules still running when the asset pays out.
The same wallet, token contracts and approval workflows run whether you deploy to a permissioned network or a public EVM chain. Moving an asset from one to the other does not mean rewriting the operating model, retraining the servicing team or re-certifying the compliance logic.
DALP runs on EVM networks. It does not support Canton, Solana or Fabric.
Frequently Asked Questions
DALP is SettleMint's platform for regulated digital assets, built on the ERC-3643/SMART standard for permissioned transfer control. Kresus KITE's product page describes white-label tokenization and investor workflows covering issuance through settlement. DALP carries the same transfer rules from issuance into servicing, and every approval is written to the platform record against the person who authorized it.
DALP and KITE both address compliant tokenized products. The difference in scope: KITE's public positioning names full-stack orchestration from issuance to settlement, while DALP keeps the eligibility and transfer rules attached to the asset through coupons, redemptions, and corporate actions, so a structured product or money market fund stays under one rule set after launch.
DALP runs the regulated asset lifecycle on EVM chains. KITE's product page positions investor-facing distribution and front-end workflows. In a deployment that combines them, DALP holds the transfer rules and approval record for the asset on-chain, and KITE handles the buyer-facing experience it is built around.
DALP is EVM-compatible. It operates on EVM chains and uses the ERC-3643/SMART standard for permissioned transfer control.
DALP routes approvals, settles movements, and processes coupons and redemptions, writing the authorizing identity to the record for each event. For a tokenized bond, a compliance team can reconstruct who approved a given coupon payment from the platform log instead of tracing it across email and spreadsheets.
DALP checks holder eligibility and transfer rules in the contract before a regulated movement executes. If a tokenized security is sent to an address that has not cleared eligibility, the contract rejects the transfer at execution, so there is no settled trade to claw back later. The institution defines which addresses can hold and transfer the asset.
DALP runs settlement, coupons, redemptions, and corporate actions through the same rule set that issued the asset. A semiannual coupon on a tokenized bond carries the eligibility check and the approval record at execution, so it posts as one auditable on-chain event rather than a line item a servicing team re-keys and matches by hand.
Build regulated digital assets on a lifecycle platform.
Run a worked example against your own asset: pick a coupon date and a holder register, and see where an ineligible transfer reverts and where the approval record lands. Talk to a product specialist about operating an ERC-3643/SMART asset through its full lifecycle.