mMEV, issued by Midas Software GmbH, is a tokenized fund that gives investors onchain exposure to mMEV, expressed as a NAV per token that moves with the underlying portfolio's performance [S1].

The token tracks mMEV (mMEV) on a total-return basis, accruing value through changes in NAV rather than any peg or floor [S1]. Holders bear a management fee as a percentage of NAV and a performance fee on profits above a high-water mark, and instant redemption carries a fixed fee typically between twenty and one hundred basis points [S2].

Midas Software GmbH, a Berlin company incorporated under German law, issues each token as a Blockchain-based Certificate, a MiFID II debt instrument under a base prospectus approved by the Liechtenstein Financial Market Authority; the issuer is not itself licensed or regulated and approval is not an endorsement [S3][S4][S5]. Tokenholders hold a contractual claim against the issuer, not ownership of the underlying assets [S3]. Tokens are not offered to U.S. Persons, sanctioned parties, or restricted jurisdictions, and access requires KYC and AML verification, with some strategies limited to professional investors [S6]. Standard redemption settles after the next NAV update and instant redemption burns tokens for a stablecoin [S7].

The tokens are ERC-20 tokens issued natively across BNB Chain, Ethereum, Monad, Base, an Ethereum Layer 2, Plasma, Starknet, Katana Network, OP Mainnet, and Rootstock [S8][S9]. Deposits mint at current NAV instantly or at the next settlement [S7]. NAV equals total portfolio value divided by tokens outstanding and is published onchain through an Oracle Feed using Chainlink and Pyth [S1].

<Sources
  retrievedAt="2026-06-19"
  items={[
    { id: "S1", url: "https://docs.midas.app/llms-full.txt" },
    { id: "S2", url: "https://docs.midas.app/resources/investment-risks" },
    { id: "S3", url: "https://docs.midas.app/resources/legal-structure" },
    { id: "S4", url: "https://docs.midas.app/tokens/mtbill" },
    { id: "S5", url: "https://docs.midas.app/resources/legal-documents/investment-disclaimer" },
    { id: "S6", url: "https://docs.midas.app/resources/eligibility-and-compliance" },
    { id: "S7", url: "https://docs.midas.app/liquidity/open-liquidity-architecture" },
    { id: "S8", url: "https://docs.midas.app/developers/smart-contract-addresses" },
    { id: "S9", url: "https://docs.midas.app/tokens/mbasis" },
  ]}
/>


# Asset senders (daily) methodology

## 1. Overview

Asset senders (daily) is calculated as the number of unique addresses that initiate asset transfers within a fixed 24-hour window. Daily activity is measured from 00:00 UTC to 23:59 UTC for each tracked asset. Active transactors are isolated from passive recipients by identifying only the sending addresses of transactions. This metric is utilized to evaluate the daily active user base and transaction utility of tokenized assets across multiple blockchain networks.

## 2. Data sources

- **EVM chain events**: ERC-20 `Transfer` events, covering EVM-compatible chains (Ethereum, Arbitrum, Base, Polygon, Optimism, and others)
- **Solana instructions**: Token transfer instructions, covering Solana
- **Aptos, Cardano, Stellar Classic, and Sui events**: Token withdraw events, covering Aptos, Cardano, Stellar, and Sui
- **Near, Algorand, Injective, Ripple, and Stellar Soroban events**: Token transfer events, covering Near, Algorand, Injective, Ripple, and Stellar
- **Polkadot Asset Hub events**: `Transferred` events from the `assets` pallet, covering Polkadot Asset Hub
- **Asset metadata**: Token addresses and chain configurations

## 3. Step-by-step calculation

### Component A: Extract sender addresses

- **Purpose**: Identify and extract the unique sending addresses for each asset transfer across all supported chains.
- **Logic**: On EVM-compatible chains, sending addresses are extracted from the `from` field of ERC-20 `Transfer` events, excluding the zero address to filter out mint transactions. On Solana, sending addresses are extracted from the authority address field of token transfer instructions. On Aptos, Cardano, Stellar Classic, and Sui, sending addresses are identified from the account address field of token withdraw events. On Near, Algorand, Injective, and Stellar Soroban, sending addresses are extracted from the sender address field of token transfer events, with null addresses excluded. On Ripple, sending addresses are extracted from token transfer events where the transfer value is negative. On Polkadot Asset Hub, sending addresses are extracted from the event data of `Transferred` events emitted by the `assets` pallet.
- **Key fields**: `timestamp` (block timestamp truncated to daily grain), `token_address` (the contract or asset identifier), `sender_address` (the address initiating the transfer)

### Component B: Consolidate and deduplicate sender data

- **Purpose**: Aggregate sender addresses across all chains and prepare the dataset for daily unique counting.
- **Logic**: Sender records from all individual chains are consolidated into a unified dataset. For each asset on each chain, the sending addresses are grouped by day. To prevent double-counting, duplicate sender addresses for the same asset on the same chain within the same 24-hour window are removed.
- **Key fields**: `timestamp` (daily timestamp), `chain_id` (blockchain identifier), `token_address` (asset address), `sender_address` (unique sending address)

### Component C: Final aggregation

- **Purpose**: Calculate the final daily active sender count per asset and per chain.
- **Logic**: The consolidated dataset is aggregated to compute the daily active senders. Unique sending addresses are counted for each asset on a daily basis, both at the individual chain level and aggregated across all chains for multi-chain assets. If no transfer activity is recorded for a tracked asset on a given day, the daily sender count is filled with zero values.
- **Key fields**: `timestamp` (daily timestamp), `chain_id` (blockchain identifier), `token_address` (asset address), `asset_dau` (daily active senders count)

*This methodology was automatically generated by Token Terminal's methodology analyzer.*

Unique asset senders over a fixed 24-hour window.

Asset senders (daily)

Tokenized funds

website

twitter

discord

Real-world asset (RWA) issuers

Midas

Midas mMEV (mMEV) is a token providing exposure to a tokenized fund issued by Midas through Midas Software GmbH and managed by RockawayX.

Each token is a synthetic instrument that provides contractual exposure to the reference asset and has being wound down issuance.

The fund is open-ended, invests in crypto assets, locks up subscriptions for 0 months, and charges a 0% annual management fee.

Holders rank as unsecured creditors of the issuer in insolvency.

Retail investors, professional investors, and institutions can mint and redeem directly with Midas in USD, USDC, USDT, and EUR after completing KYC, and holders have a right to redeem at net asset value with monthly settlement.

Midas Software GmbH is incorporated in Germany and is offered under an EU-approved prospectus.

Holder terms are governed by the law of Germany.

mMEV has been issued on Ethereum as an ERC-20 token since February 2025.

Midas mMEVmMEV