Legacy-equivalent presets

Legacy-equivalent presets are prepared DALPAsset configurations for familiar instrument categories. Each preset selects token features, compliance modules, and deployment parameters for one common asset pattern.

The preset is a starting point for configuration. The deployed token is still a DALPAsset. The issuer remains responsible for choosing the legal terms, compliance policy, trusted issuers, and operating process that fit the asset.

Identity, claim topics, and trusted issuers are defined in the claims and identity model. If you need fixed bytecode for a specialised contract family instead of configurable DALPAsset composition, read Legacy Types.

Choose a preset

How presets compose a DALPAsset

A preset does not create a new contract family. It prepares a DALPAsset configuration by combining three layers:

• Token features add asset behavior such as yield claims, maturity redemption, voting power, management fees, and historical balance snapshots.
• Compliance modules enforce transfer and minting rules such as identity verification, jurisdiction rules, supply caps, investor limits, or collateral attestations.
• Instrument parameters set the values that make the asset specific, such as face value, maturity date, denomination asset, fee rate, supply cap, or metadata schema.

Because those layers are configurable, the seven presets below are common baselines rather than the full product boundary.

Presets

Each preset mirrors a legacy type's embedded behavior using DALPAsset features and compliance modules. Add, remove, or combine features only when the selected asset terms and compliance policy support that composition.

Bond

• Use case: Fixed-income instruments with face value, coupon or fixed yield terms, and maturity redemption.
• Token features:
  • Fixed Treasury Yield - periodic yield schedule paid in the denomination asset; holders claim completed-period entitlements
  • Maturity Redemption - maturity date and face value redemption in the denomination asset
  • Historical Balances - balance snapshots for entitlement calculations and audit views
• Compliance modules:
  • CappedComplianceModule - enforces the maximum issuance cap
  • Additional jurisdiction modules from Regulatory templates
• Key deployment parameters: face value, maturity date, denomination asset, yield schedule, supply cap, trusted issuers, and claim topics
• Legacy equivalent: DALPBond embeds redeemable, yield, cap, and historical-balance behavior at compile time. The DALPAsset preset recreates the pattern through attached features and modules.

Equity

• Use case: Shares with governance voting rights and balance snapshots for shareholder records.
• Token features:
  • Voting Power - ERC20Votes delegation where voting weight follows token balance at snapshot
  • Historical Balances - balance checkpoints for snapshot-based governance and records
• Compliance modules: jurisdiction-specific identity, country, and investor-count rules from Regulatory templates
• Key deployment parameters: standard token parameters, trusted issuers, claim topics, and any investor-limit or jurisdiction settings
• Legacy equivalent: DALPEquity embeds voting and historical-balance behavior at compile time.

Fund

• Use case: Managed investment vehicles with AUM-based management fees and optional governance.
• Token features:
  • AUM Fee - time-weighted management fee calculated from AUM, fee basis points, and elapsed time, then minted to the configured fee recipient
  • Voting Power - investor governance where required
  • Historical Balances - snapshots for records and calculations
• Compliance modules: jurisdiction-specific identity and country rules from Regulatory templates
• Key deployment parameters: fee rate in basis points, fee recipient, trusted issuers, and claim topics
• Legacy equivalent: DALPFund embeds management-fee, voting, and historical-balance behavior at compile time.

StableCoin

• Use case: Fiat-pegged or asset-backed stable value tokens where minting depends on collateral attestations.
• Token features:
  • Historical Balances - balance snapshots for reporting and audit views
• Compliance modules:
  • CollateralComplianceModule - gates minting against configured collateral-ratio requirements using identity claims and trusted issuers
  • Additional jurisdiction modules from Regulatory templates
• Key deployment parameters: collateral proof topic, collateral ratio in basis points, trusted issuers, claim expiry policy, and any jurisdiction rules
• Legacy equivalent: DALPStableCoin embeds collateral and historical-balance behavior at compile time. The DALPAsset preset uses the plug-in collateral module instead.

Deposit

• Use case: Deposit-like tokens with minimal on-chain constraints and optional jurisdiction policy.
• Token features:
  • Historical Balances - balance snapshots for records and audit views
• Compliance modules: jurisdiction-specific modules from Regulatory templates; collateral-backed deposits can add CollateralComplianceModule
• Key deployment parameters: standard token parameters, trusted issuers, claim topics, and any collateral settings if collateral is used
• Legacy equivalent: DALPDeposit embeds historical-balance behavior at compile time.

RealEstate

• Use case: Fractional real estate representation where a fixed supply maps to the chosen property or portfolio model.
• Token features:
  • Historical Balances - ownership snapshots for records and downstream reporting
• Compliance modules:
  • CappedComplianceModule - enforces the configured supply cap
  • Additional jurisdiction modules from Regulatory templates
• Key deployment parameters: supply cap, metadata fields, trusted issuers, claim topics, and jurisdiction settings
• Legacy equivalent: DALPRealEstate embeds cap and historical-balance behavior at compile time.

PreciousMetal

• Use case: Tokenized precious metals with a pooled backing model where supply changes as recognised backing changes.
• Token features:
  • Historical Balances - balance snapshots for records and custody reporting
• Compliance modules: jurisdiction-specific modules from Regulatory templates; no supply cap is part of the baseline preset
• Key deployment parameters: standard token parameters, metadata fields, trusted issuers, and claim topics
• Legacy equivalent: DALPPreciousMetal embeds historical-balance behavior at compile time.

Production checks before deployment

• Confirm the asset's legal and economic terms before selecting the preset. DALP composes token behavior; it does not define the legal instrument.
• Choose the claim topics, trusted issuers, and compliance modules before minting. Transfer and minting rules depend on those settings.
• Store collateral and reserve evidence outside token metadata unless the collateral workflow records evidence as a claim. DALP can gate minting from trusted attestations. DALP does not independently prove off-chain reserves.
• Verify treasury funding, wallet allowance, and maturity settings before issuing yield or redemption-bearing instruments.
• Use RBAC to separate issuer, admin, supply, compliance, and feature-management duties.

See also

• DALPAsset - recommended configurable contract type
• Asset Contracts - decision framework and common foundation
• Token Features - full runtime-pluggable feature catalog
• Compliance Modules - transfer and supply rule engine
• Legacy Types - compile-time types, decision checklists, coexistence guidance
• RBAC - per-asset role model and separation-of-duties invariants