Legacy-Equivalent Presets

Purpose: Pre-built DALPAsset configurations that replicate each legacy type's behavior — starting points for new projects, not limits on what DALPAsset can do.

• Doc type: Reference
• What you'll find here:
  • Token feature and compliance configuration per preset
  • Deployment parameters specific to each preset
  • Legacy type equivalents and their compile-time constraints
• Related:
  • Asset Contracts
  • Token Features
  • Compliance Modules
  • DALPAsset
  • Legacy Types
  • RBAC

---

Beyond the presets

DALPAsset supports any combination of token features and compliance modules — not just the seven below.

• These presets recreate legacy specialized contract behavior on DALPAsset — they are starting points, not limits
• Add features beyond the baseline: fees, governance, redemption, yield, permits, conversion
• Add compliance modules beyond the baseline: jurisdiction templates, investor count caps, collateral enforcement
• Regulation or legal constraints may require compile-time immutability — see Legacy Types
• Choose features and modules based on requirements; presets are not exhaustive

---

Presets

Each preset mirrors a legacy type's embedded behavior using DALPAsset's configurable features and modules.

Bond

• Use case: Fixed-income instruments with face value, coupon payments, and maturity date.
• Token features:
  • Fixed Treasury Yield — periodic yield schedule paid in denomination asset; pull-based (holders claim)
  • Maturity Redemption — maturity date, face value redemption in denomination asset
  • Historical Balances — balance snapshots for coupon accrual calculations
• Compliance modules:
  • CappedComplianceModule — enforces maximum issuance cap
  • Additional modules per jurisdiction (see Regulatory templates)
• Key parameters at deployment: face value, maturity date, denomination asset (e.g. USDC), coupon rate/schedule, supply cap
• Legacy equivalent: DALPBond — embeds SMARTRedeemableUpgradeable, SMARTYieldUpgradeable (legacy yield mechanism, deprecated in favor of Fixed Treasury Yield), SMARTCappedUpgradeable, SMARTHistoricalBalancesUpgradeable at compile time. Blocks transfers after maturity via isMatured state.

---

Equity

• Use case: Shares with governance voting rights and balance snapshots for shareholder records.
• Token features:
  • Voting Power — ERC20Votes delegation, voting weight equals token balance at snapshot
  • Historical Balances — balance checkpoints for snapshot-based governance
• Compliance modules:
  • Per jurisdiction — see Regulatory templates. Common: Identity Verification + Country Allow List + Investor Count.
• Key parameters at deployment: none specific beyond standard token parameters
• Legacy equivalent: DALPEquity — embeds ERC20VotesUpgradeable and SMARTHistoricalBalances at compile time.

---

Fund

• Use case: Managed investment vehicles with AUM-based management fees and governance.
• Token features:
  • AUM Fee — time-weighted management fee calculated as AUM x feeBps x elapsed / year, minted to configured feeRecipient
  • Voting Power — investor governance
  • Historical Balances — NAV and fee calculation snapshots
• Compliance modules:
  • Per jurisdiction — see Regulatory templates. Common: Identity Verification + Country Allow List.
• Key parameters at deployment: fee rate in basis points
• Legacy equivalent: DALPFund — embeds management fee logic, ERC20VotesUpgradeable, SMARTHistoricalBalancesUpgradeable at compile time. See Parity Notes for behavioral differences.

---

StableCoin

• Use case: Fiat-pegged or asset-backed stable value tokens with on-chain collateral enforcement.
• Token features:
  • Historical Balances — balance snapshots for reporting and audit
• Compliance modules:
  • CollateralComplianceModule — enforces that minting cannot exceed the on-chain collateral ratio (configured in basis points: 10,000 = 100%). Collateral proof verified via ERC-735 identity claims with expiry — claims must be renewed proactively or minting halts.
  • Additional modules per jurisdiction
• Key parameters at deployment: collateral proof topic (ERC-735 claim topic), collateral ratio (basis points), trusted issuers
• Legacy equivalent: DALPStableCoin — embeds SMARTCollateralUpgradeable (a separate compile-time collateral mechanism, distinct from the plug-in CollateralComplianceModule) and SMARTHistoricalBalancesUpgradeable at compile time. The collateral ratio is a required deployment parameter; 10,000 bps (100%) is the conventional starting point.

---

Deposit

• Use case: General-purpose deposit tokens (e.g. tokenized bank deposits) with minimal on-chain constraints.
• Token features:
  • Historical Balances — balance snapshots. Additional features as needed.
• Compliance modules:
  • Per jurisdiction — see Regulatory templates. For collateral-backed deposits, add CollateralComplianceModule.
• Key parameters at deployment: none specific beyond standard token parameters
• Legacy equivalent: DALPDeposit — embeds only SMARTHistoricalBalances at compile time. Minimal specialized logic.

---

RealEstate

• Use case: Fractional ownership of real estate with fixed supply representing the property valuation.
• Token features:
  • Historical Balances — ownership snapshots for dividend/rent distribution
• Compliance modules:
  • CappedComplianceModule — enforces fixed supply cap representing property valuation
  • Additional modules per jurisdiction
• Key parameters at deployment: supply cap (matching property valuation/fractionalization), property metadata
• Legacy equivalent: DALPRealEstate — embeds SMARTCapped and SMARTHistoricalBalances at compile time. Has a premint mechanism: factory mints the full supply to a recipient then pauses, locking the cap to the preminted amount.

---

PreciousMetal

• Use case: Tokenized precious metals (gold, silver) with pooled custody model — supply grows as vault deposits increase.
• Token features:
  • Historical Balances — balance snapshots for custody reporting
• Compliance modules:
  • Per jurisdiction — see Regulatory templates. No cap constraint (supply is dynamic based on vault backing).
• Key parameters at deployment: none specific beyond standard token parameters. No supply cap.
• Legacy equivalent: DALPPreciousMetal — embeds only SMARTHistoricalBalances at compile time. PAXG-style pooled model with no supply cap.

---

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