On buys · fees paid in $AI
Split · TBD$AI comes in
Route at the LP splitter
Route A
Community Vault
$AI held onchain under the published vault rules.
Route B
Original receiver
A disclosed receiver share, if the final design keeps one.
The proposed mechanics
The target is an $IA / $AI pool on LONG and Robinhood Chain. Final contracts, fee splits, and verified addresses will be published only after fork testing and review.
This is a meme-to-meme pool: $IA would trade directly against $AI. $AI's existing NVDA market sits one layer below; $IA would not trade directly against a stock token.
Where fees could go
In the proposed pair, the input asset changes with trade direction. That makes an $AI-denominated community vault possible without selling the parent asset to buy something else.
The canonical LP-beneficiary stream and the optional Rehype hook-fee stream are separate. These diagrams cover only a proposed LP-fee splitter; no extra hook fee is assumed.
On buys · fees paid in $AI
Split · TBD$AI comes in
Route at the LP splitter
Route A
$AI held onchain under the published vault rules.
Route B
A disclosed receiver share, if the final design keeps one.
On sells · fees paid in $IA
Split · TBD$IA comes in
Route at the LP splitter
Route A
A provable supply reduction, if the tested token supports it.
Route B
$IA retained by the vault and never actively sold by it.
These diagrams describe the architecture being tested. They are not active tokenomics, a promise of returns, or a deployed fee schedule. Any separate hook-fee route would require its own published, noncustodial receiver.
Community mode
The planned vault can hold $AI and community-contributed stock tokens. Anyone can add assets. A governor and timelock—not a marketing page—would define what the vault is allowed to do.

Contracts
No $IA token, pool, fee receiver, vault, or governor has been deployed. Any address claiming otherwise is not official.