Bubblemaps Under the Lens
Following 12 million BMT from the published team wallet toward Gate, and a separate vesting recipient that sold nearly four million tokens.
Evidence through November 9, 2026 UTC

At 16:09:51 UTC on November 9, 2026, 2.5 million BMT left a wallet that Bubblemaps publicly identifies as its team claim address. Less than two hours later, after three intermediary wallets, 2.5 million BMT arrived at Gate 1, the exchange address labelled by BscScan.
The movement was part of a larger pattern. Five identified departures from that team wallet totalled 12 million BMT between November 3 and November 9. Separately, a Solana vesting recipient sold almost 3.97 million BMT across 95 transactions, receiving 91,051.12 USDC net.
These are transactions that holders can inspect for themselves. They put specific questions on the table: what were the team-origin transfers for, who controlled the receiving exchange account, and which allocation funded the Solana seller?
The records establish movement and selling within those two distinct histories. They do not establish insider trading or show that the Solana recipient belongs to the team. That boundary matters throughout this review.
Five transfers and one published team address
The team attribution is unusually straightforward. Bubblemaps names 0x44C9...C4b3 as Team (claim) in its own tokenomics documentation. The five departures reviewed here concern BMT on BNB Chain, contract 0x7d814b9eD370Ec0a502EdC3267393bF62d891B62.

| Date and time UTC | BMT sent | Receipt |
|---|---|---|
| Nov 03 13:25:36 | 2,000,000 | View transaction |
| Nov 04 08:31:38 | 3,500,000 | View transaction |
| Nov 05 08:24:46 | 2,000,000 | View transaction |
| Nov 08 10:11:42 | 2,000,000 | View transaction |
| Nov 09 16:09:51 | 2,500,000 | View transaction |
The total equals 1.2% of BMT's published one-billion-token maximum supply. Each departure is counted once. Counting the same tokens again at every intermediate address would inflate the number without adding any new supply.
Bubblemaps also publicly discloses a 90 million BMT team allocation, with a 12-month cliff and a 36-month vesting period. Those disclosures deserve to be acknowledged. This review did not audit the underlying locks or establish that any transfer breached the vesting schedule.
The November 9 route ends at Gate custody

The first receiving address, 0x3A64...E98D, forwarded 2.5 million BMT at 16:11:23 UTC to 0xa474...7FA9. A third transfer at 16:13:30 moved the same amount to 0x58dE...e74f. At 18:06:57, the tokens reached 0x0D07...92Fe, labelled Gate 1 by BscScan.
The other reviewed dates follow the same observed route. There are small downstream differences in the displayed amounts: the November 3 sweep shows 1,999,999.98 BMT and November 4 shows 3,500,000.01. Because balances mix at intermediary addresses, the precise finding is 12 million BMT leaving the team wallet, with approximately that amount moving onward through the route.
The public trail stops short of the exchange account. It does not identify the beneficiary or reveal an executed trade. Custody, market-making inventory, beneficiary payments and sales are possible explanations; none was established here. Several hops are also insufficient to prove concealment when control of the intermediary wallets remains unknown.
A separate wallet shows actual sales
On Solana, the evidence is different. Wallet FLNrnojn...Kpaswdx4zrh received BMT through the documented vesting system and exchanged tokens for USDC. Across the reviewed history from August 10 through November 9, ten claims delivered 3,965,288.39 BMT. Ninety-five sales disposed of that same total.

The sales produced 91,051.12 USDC net, measured from the wallet's token-balance changes. The checked BMT token account ended at zero after the latest sale. Proceeds are not profit: this review does not establish the recipient's acquisition cost or other economic arrangements.
The source of the tokens is supported by matching balance changes at the project's documented vesting operator and use of its vesting program. The recipient's identity and allocation category are still unproven. There is no established ownership link to the BNB Chain team wallet, so the two totals cannot be combined into a claim that the team sold 15.97 million BMT.
Seventeen seconds from claim to sale
On November 9, the Solana recipient claimed 48,844.52 BMT at 18:16:39 UTC. It sold that same amount at 18:16:56, 17 seconds later, receiving 1,128.56 USDC net. Two other paired transactions show similarly short intervals.

| Date in 2026 | BMT claimed and sold | Delay | Receipts |
|---|---|---|---|
| Oct 28 | 55,614.71 | 14 seconds | Claim / Sale |
| Nov 04 | 62,413.73 | 28 seconds | Claim / Sale |
| Nov 09 | 48,844.52 | 17 seconds | Claim / Sale |
The wider history is important. Seventy-five of the 95 sales happened on August 10, disposing of 2.3 million BMT. Another seven sales over the next two days disposed of the remaining 821,455.12 BMT from the initial claim. The first sale occurred 38 seconds after that claim, but it sold only 10,000 BMT, not the entire 3.12 million.
September claims were handled differently. Receipts on September 9 and 30 accumulated to 277,270.66 BMT before further activity in October. The chart preserves that holding period. Ninety-five transactions also means repeated selling by one address; it does not establish 95 sellers or a coordinated group.
The large holder that needs context
The Rug.Tools scan also surfaced an approximately 42.82% holding at 0xeaed...6b8d. UNCX's own contract list identifies the full address as its legacy BSC vesting contract. That holding should be understood as contract custody, not automatically as one insider's freely spendable balance. Identifying the contract does not verify every beneficiary or lock.
BMT exists on both BNB Chain and Solana, which creates another trap: a holder percentage on one chain is not automatically a share of the global maximum supply. The same attribution and denominator checks should apply to Rug.Tools' own scan before it is used to support an allegation.
What holders still need explained
For the team-origin transfers, the missing information is their purpose and beneficiary. Were the tokens delivered to a market maker, paid to allocation recipients, retained in custody or sold? If a market maker received them, a reconciliation of supplied, returned and remaining inventory would help holders understand the arrangement.
For the Solana recipient, the useful questions are its allocation category, any applicable sale restrictions and whether it was acting for itself or another party. The public receipts cannot answer those questions.
The transactions are enough to justify asking. They are not enough to attribute BMT's price decline to these wallets or to establish misuse of inside information. A substantive explanation would connect the recorded transfers to named allocation purposes and relevant records. Holders already have the transaction trail. What remains missing from this review is the account of why the tokens moved.
How the records were checked
Bubblemaps and the recipient are welcome to provide records or a response at hello@rug.tools. Substantive corrections or responses will be identified as updates.
Token contracts reviewed
Open a current token scan. The article above describes evidence through November 9, 2026 UTC.
0x7d814b9ed370ec0a502edc3267393bf62d891b62FQgtfugBdpFN7PZ6NdPrZpVLDBrPGxXesi4gVu3vErhY