BKL-3, issued by Reental, is a tokenized real-estate investment that fractionalizes a single property vehicle onchain and tracks the value and rental performance of - BACALAR 3 [S1][S2].

The reference asset is - BACALAR 3 (BKL-3), and each token represents a proportional claim on that property held by its per-project vehicle [S1][S3]. This is a total-return instrument: tokenholders receive rental income distributed monthly in USDT, a stablecoin, in proportion to their holding, and may claim or reinvest distributions to compound [S1][S3][S2]. At the end of the property's cycle, holders recover their initial investment plus a share of any capital gain on sale; a 19% withholding applies in Spain [S4].

Reental operates from Spain and the United States, forming a dedicated per-project vehicle for each issuance rather than a single named parent issuer [S5][S1]. U.S. projects are private placements under the Securities Act of 1933, using Regulation D Rule 506(c) and Regulation S; Spanish projects are issued under Law 6/2023 on Securities Markets and Investment Services [S5][S2]. The token represents tokenized LLC shares in the United States, or a beneficiary interest in a participatory loan in Spain [S1][S5]. Investors complete KYC and AML checks, and U.S. tax residents must be accredited [S5][S4]. There is no issuer buyback; tokenholders sell to validated buyers [S6].

The property tokens are issued natively on the Polygon network and held in the investor's own offchain self-custodied wallet, such as MetaMask, Rabby, or HumanWallet [S5][S6]. To invest, a user registers, completes KYC and AML validation, purchases tokens with USDT or by bank transfer at a one-token minimum, and signs the investment agreement [S1][S5]. Distributions settle in USDT to the tokenholder's wallet [S1][S2].

<Sources
  retrievedAt="2026-06-19"
  items={[
    { id: "S1", url: "https://www.reental.co/en/blog/what-is-reental-and-why-we-tokenized-spanish-real-estate" },
    { id: "S2", url: "https://www.reental.co/en" },
    { id: "S3", url: "https://www.reental.co/en/properties" },
    { id: "S4", url: "https://www.reental.co/en/faqs" },
    { id: "S5", url: "https://www.reental.co/en/faqs" },
    { id: "S6", url: "https://www.reental.co/en/help" },
  ]}
/>


# 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

Reental tokenizes individual real estate properties on the Polygon blockchain, allowing investors to purchase fractional ownership through digital tokens. Each property is represented by a unique token with transparent rental income distribution and property management.

A real estate tokenization platform that enables fractional investment in rental properties worldwide through blockchain technology, providing accessible real estate investing with low minimums and automated income distribution.

Real estate investors seeking fractional ownership in tokenized property investments across global markets including Spain, Dubai, Mexico, and the United States.

website

twitter

docs

Real-world asset (RWA) issuers

Reental

REENTAL - BACALAR 3 (BKL-3) is a tokenized fund share issued by Reental through Reental BKL-3 LLC.

Each token is a direct claim on the issuer.

The fund is closed-ended and invests in real estate in Latin America.

Retail investors and accredited investors can subscribe and redeem in EUR, with a EUR 100 minimum after completing KYC.

Reental BKL-3 LLC is offered under an SEC Regulation D exemption, is offered under an SEC Regulation S exemption.

BKL-3 has been issued on Polygon as an ERC-20 token since March 2025.

REENTAL - BACALAR 3BKL-3