Torque Docs

Appearance

Service: RWA Tokenization Engine ​

The RWA Tokenization Engine configures an off-chain asset as a Fund and prepares its on-chain contract records. It manages fund terms, document associations, compliance parameters, share records, and deployment requests.

The engine provides:

  • Fund Validation: Checks required financial terms, legal documents, and compliance rules before a Fund advances.

  • Configuration Rules: Selects required fields and validation rules by asset, security, and regulation type.

  • On-Chain Integration: Prepares smart contract deployment parameters and requests creation of the on-chain asset.

  • Compliance Configuration: Stores investor eligibility and share-management rules with the Fund.

  • Document Association: Uses the Filer to upload and associate required legal and marketing documents.

  • Issuance Templates: Reuses configured terms and validation rules across compatible fund structures.

  • Contract Rules: Prepares contract parameters for compliance, distributions, and supported lifecycle events.

  • Asset Records: Links the off-chain Fund record, documents, share ledger, and on-chain contract record.

Core Technical Components & APIs ​

The engine creates and updates the Fund and its associated on-chain contract record through these components:

Primary Models:

Governing Logic:

  • Fund Status Lifecycle: The engine is responsible for a fund's progression through its initial states.

  • Global Business Rules: It enforces rules related to fund creation, such as share calculation and financial data integrity.

Primary APIs:

Process Lifecycle ​

The engine processes tokenization through the phases below.

Phase 1: Asset Structuring & Configuration ​

This phase records the asset, its terms, and its configured compliance rules.

  • Templatized Structuring: Provides flexible modules within the Issuer Portal to structure diverse asset classes (debt, equity, funds, real estate, etc.), including defining the legal vehicle and associated terms/covenants.

  • Financial Modeling: Provides the framework for defining and validating core financial terms (total shares, price per share, minimum investment), ensuring consistency.

  • Compliance Rule Configuration: Integrates with the Regulatory Compliance Engine to allow issuers to select and configure applicable compliance rules (residency, investor type, lockups, transfer restrictions) that will be embedded in the token.

  • Document Association: Integrates with the Filer to link all necessary legal agreements, disclosures (PPM/Offering Circular), and asset documentation to the fund record.

  • Ledger Initialization: The engine establishes the share ledger for the fund, setting the initial counters for subscribed shares and confirmed shares to zero.

  • Yield Mechanism Definition: Based on the fund's financial structure, the engine sets the economic_model (which will be stored on the EVM Contract record):

    • If PRICE_APPRECIATING (Growth Model): The engine configures the smart contract to function as an accrual token (e.g., like a cToken). The contract will be designed to automatically reinvest all generated yield, causing its internal exchange rate to rise.

    • If DIVIDEND_PAYING_BATCH (Periodic Income Model): The engine configures the contract as a standard, pegged-price token. This prepares it for the Smart Dividends Service, which must be used by an administrator to execute all periodic payouts.

    • If DIVIDEND_PAYING_STREAMING (Continuous Income Model): The engine configures a specialized "streaming" smart contract (e.g., a rebasing token). The contract is designed to receive yield and automatically distribute new tokens to holders in real-time.

Phase 2: Programmable Smart Contract Generation & Deployment ​

This phase prepares the configured fund for on-chain deployment.

  • Smart Contract Generation: Based on the configured terms and compliance rules, and selected economic_model, the engine automatically generates or parameterizes the appropriate smart contract code (e.g., EIP-3643 compliant). This includes embedding logic for distributions, potential vesting/amortization, and transfer controls.

    • If DIVIDEND_PAYING_BATCH, it deploys a standard token contract, awaiting calls from the Smart Dividends Service.

    • If DIVIDEND_PAYING_STREAMING, it deploys a contract with the real-time minting/distribution logic built-in.

    • If PRICE_APPRECIATING, it deploys a contract with the yield-reinvestment and exchangeRate logic built-in.

  • Deployment Orchestration: Upon final approval of the fund, the engine calls the evm-api via a simplified interface (potentially "no-code" in the Issuer Portal) to deploy the configured smart contract to the selected blockchain network.

  • Record Linking & Initialization: Creates the EVM Contract record, storing the contract's address and its economic_model, establishing the permanent one-to-one link back to the fund. It initializes the on-chain state (e.g., minting total supply to a treasury address).

Ongoing Capabilities ​

After tokenization, events from the Investment Process Management Service update the subscription ledger.

  • Subscription Logic:

  • Over-Subscription Prevention: The engine blocks the creation of new Investments if the requested number of shares would cause the total subscribed shares to exceed the total shares available for the fund.

  • Non-Investable Leftovers Rule: The engine enforces logic that dynamically adjusts the minimum investment amount when a fund is nearing full subscription, ensuring it can be completely sold out.

Exceptions and Recovery ​

The engine validates fund configuration and records deployment errors.

  • Configuration Validation: Before legal review, the engine blocks a Fund with inconsistent or missing required data.

  • Deployment Failures: If the evm-api call to deploy the smart contract fails, the engine will prevent the fund's status from advancing. It will log the error and keep the fund in a state where an administrator can retry the deployment.

  • Fund Updates: When an administrator edits a fund in the DRAFT status, the engine re-runs all validation checks upon saving to ensure its continued integrity.

  • Deployment Record: After deployment, preserves the parameters that link the Fund to its EVM Contract.

Associated End-to-End Workflows ​