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

The token tracks mF-ONE (mF-ONE) 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 (monthly) methodology

## 1. Overview

Asset senders (monthly) is defined as the number of unique addresses from which asset transfers are initiated over a rolling 30-day period. For each tracked asset, outgoing transfer transactions are analyzed across supported blockchains to identify the sending addresses. These addresses are deduplicated over a 30-day window to represent the monthly active sender base. This metric is utilized to evaluate user adoption, transactional activity, and the overall utility of tokenized assets.

## 2. Data sources

- **EVM chain events**: Token transfer events, covering EVM-compatible chains (Ethereum, Arbitrum, Base, Polygon, Optimism, and others)
- **Solana instructions**: Token transfer instructions
- **Aptos, Sui, Cardano, and Stellar Classic data**: Token withdraw transactions
- **Stellar Soroban, Algorand, Near, Injective, and Ripple data**: Token transfer transactions
- **Polkadot Asset Hub events**: `Transferred` events from `assets` pallets
- **Asset metadata**: Token contract addresses and decimal precision

## 3. Step-by-step calculation

### Component A: Extract daily asset senders

- **Purpose**: Identify unique addresses initiating transfers on a daily basis
- **Logic**: On EVM-compatible chains, token transfer events are parsed to extract the sender address from the transaction, excluding the zero address. On Solana, token transfer instructions are parsed to identify the authority address. On Aptos, Sui, Cardano, and Stellar Classic, token withdraw transactions are parsed to extract the account address. On Stellar Soroban, Algorand, Near, and Injective, token transfer transactions are parsed to extract the sender address, excluding null addresses. On Ripple, token transfer transactions with negative values are parsed to identify the sending account address. On Polkadot Asset Hub, `Transferred` events from `assets` pallets are parsed to extract the sender address. For all chains, the extracted addresses are grouped by day and token address to produce a daily record of unique senders.
- **Key fields**: `timestamp` (block day), `token_address` (asset identifier), `sender_address` (initiating address)

### Component B: Aggregate rolling monthly senders

- **Purpose**: Calculate the unique sender count over a rolling 30-day window
- **Logic**: A daily datespine is generated to establish a continuous timeline. For each day in the timeline, a 30-day lookback window is constructed, encompassing the current day and the preceding 29 days. Daily sender addresses collected within this window are aggregated and deduplicated. The total number of unique, deduplicated addresses is then counted for each asset on each day.
- **Key fields**: `timestamp` (calculation day), `token_address` (asset identifier), `asset_senders` (unique monthly sender count)

### Component C: Final aggregation and zero-filling

- **Purpose**: Combine data across chains and fill missing activity days
- **Logic**: The deduplicated monthly sender counts are aggregated at both the individual chain level and the global asset level. For days where no transfer activity is recorded for a tracked asset, the metric is filled with zero values to maintain a continuous time series.
- **Key fields**: `timestamp` (reporting day), `chain_id` (blockchain identifier), `token_address` (asset identifier), `asset_senders` (final monthly unique sender count)

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

Unique asset senders over a rolling 30-day window.

Asset senders (monthly)

Tokenized funds

website

twitter

discord

Real-world asset (RWA) issuers

Midas

Midas mF-ONE (mF-ONE) is a tokenized fund share issued by Midas through Midas Software GmbH.

Each token is a direct claim on the issuer.

Qualified investors can mint and redeem directly with Midas after completing KYC, and holders have a right to redeem at net asset value with monthly settlement.

Midas Software GmbH is incorporated in Germany.

mF-ONE has been issued on Ethereum as an ERC-20 token since June 2025.

Midas mF-ONEmF-ONE