1. Dividend Tax Handoff

The dividend tax is collected in the token’s base/pair asset:

Native launches use WETH.
stock pair launches use that manager’s configured pair token.
The authoritative asset for a launch is rewardToken in the dividend controller’s TokenRegistered event.

The tax is pushed, not pulled:

manager or hook -> dividend controller -> active dividend processor

Production currently uses a shared dividend processor, not a MemeDex-provided per-token vault:

Dividend controller: 0xa8F6Cb031C5f0f923909842D4435687e250559bC
Dividend processor:  0x69AeE265043ab8Fa5AcEB721537bb9aED5B4b7A9

The processor receives and accounts for 100% of the dividend tax for eligible holders.

2. Launch Trigger

The current launch flow does not call an external factory.

The common token-registration event is:

event TokenRegistered(
    uint256 indexed tokenId,
    address indexed launchToken,
    address indexed rewardToken,
    address registrar
);

Its canonical signature is:

TokenRegistered(uint256,address,address,address)

It is emitted by the production dividend controller:

0xa8F6Cb031C5f0f923909842D4435687e250559bC

registrar is the manager that launched the token. This event is emitted for every RH V2 token registration. Whether dividends are enabled and the configured percentage are stored in that manager’s tokenParams(tokenId).

3. Bonding Curve, Pool and Dividend Exclusions

Current production launches use:

75% of the token supply sold through the bonding curve.
25% of the token supply added to liquidity upon graduation.
A Uniswap V4 pool after graduation.

There is no separate bonding-curve address per token. The registrar/manager is the bonding-curve contract.

At graduation, the dividend controller emits:

event PoolRegistered(
    uint256 indexed tokenId,
    bytes32 indexed poolId
);

The pool can also be retrieved from:

tokenDividendState(tokenId)

Uniswap V4 does not deploy a per-pool contract. Liquidity accounting resides in the PoolManager singleton:

0x8366a39CC670B4001A1121B8F6A443A643e40951

The LP position is a Uniswap V4 position NFT owned by the timelocked LP vault:

0x7d4A72C6EF99E935c1e723b8eD6e38Ac51C8190b

The current dividend exclusions are:

The launch token contract.
The manager/bonding-curve contract.
The dividend controller.
The active dividend processor.
The Uniswap V4 PoolManager.
The pool deployer.
The timelocked LP vault.
The Uniswap V4 hook after graduation.

Exclusion changes are emitted through:

event DividendExcludedSet(
    uint256 indexed tokenId,
    address indexed account,
    bool excluded
);

There is no separate launch-token allocation for a treasury or vesting contract. Creator, protocol and creation-fee wallets receive the base asset, not launch-token supply, and are not automatically excluded if they independently hold or buy the token.

4. Basket Choice

There is no basket selection in RH V2 today.

Each launch distributes one reward asset: its base/pair token. The current launch UI, manager ABI and dividend controller do not accept a default or custom basket configuration, and Arena does not write to a MemeDex basket registry.

5. Node Access

use alchemy?

6. Fees

A MemeDex 15% cut is not implemented today.

Currently, 100% of the collected dividend tax is deposited into the active dividend processor and accounted for eligible holders. Creator and protocol fees are separate.

Current fee caps are:

Dividend fee: maximum 5%.
Creator fee: maximum 1%.
Fee-helper aggregate cap: 7%.
Hook hard safety cap: 9.9%.

Taking 15% from the dividend tax would require a change to the current processing/distribution path. Discuess with Jason if he agrees with this change.

Pls refer to : https://github.com/starsarenaorg/ArenaRhInfo if you want more technical info.

untitled