Archalis Radar

Check BNB Chain token risks, trace connected creators and monitor changes. On-chain evidence behind every finding. 5 free token checks/day with an account.

[Archalis Radar @ArchalisRadar]

Checking a BNB Chain token?

Archalis shows trading restrictions, creator connections and changes in risk—with the evidence behind them.

Explore the public radar. Get 5 fresh checks/day with a free account.

Start here: https://t.co/eyaGB8wchH

[Archalis Radar @ArchalisRadar]

@leksa12345678 Which contract is 天文 here? A chart alone leaves the exit question open: liquidity, sell restrictions and creator history. Those are the checks we focus on at Archalis for BNB Chain. Happy to look at the exact address here rather than guess from the ticker.

[Archalis Radar @ArchalisRadar]

Do you have the BSC contract address for wormbrain? We build Archalis to check token risks and creator connections on BNB Chain. The address would let us examine the BSC side of this claim. Linking it to the ARC launch would need separate evidence; similar names alone would not establish that.

[Archalis Radar @ArchalisRadar]

@BenTodar Was it liquidity being pulled, blocked sells, or large wallets dumping? Those need different checks. We build Archalis for BNB Chain. Share one contract address and we can look at the available evidence here, including what remains unknown.

[Archalis Radar @ArchalisRadar]

#ARK’s token governance is zero. But who still controls the contracts allowed to mint?

We followed the permission chain. Our manual investigation found an owner-controlled, upgradeable contract that still holds minting permission.

Here is the evidence:

• ARK’s governance() returned the zero address.
• Its separate ARKMinter contract was unpaused and pointed to this exact ARK token.
• Contract 0xbc9e4BC9f839cE93Aba50b9315F31A9A2CBF7E08 held MINTER_ROLE in ARKMinter.
• That contract’s owner was 0xD02ce7A31a1737b1289A961A2c770946555f1d82.

We then tested the owner’s upgrade authority.

At BSC block 128991299 - 21 October 2026, 19:07:56 UTC - an eth_call simulation adding a function through diamondCut succeeded from the owner on two independent RPC providers. The same call from an unrelated address reverted.

No transaction was signed or broadcast.

Why this matters: checking whether mint() exists is only the first step. You also need to trace who can invoke it—and who can change those callers’ logic.

For this ARK contract, zero token governance does not mean all mint-related control has been relinquished.

This is evidence of remaining authority, not evidence of abuse or a verdict that the token is safe.

Sources:
ARK token:
https://t.co/Cce7Xl7nIK

Verified ARKMinter implementation:
https://t.co/503OBOPG2q

Mint-authorized contract:
https://t.co/eX0Jj8AHgM

The last contract’s source is unverified; its upgrade authority was checked through bytecode, on-chain reads and simulations.

[Archalis Radar @ArchalisRadar]

@stitchdegen @tradyxyz The “what changed since my last check?” part matters too. We’re building Archalis for BNB Chain to compare token checks and trace creator connections. Which changes would you most want surfaced: sell restrictions, liquidity or creator activity?

[Archalis Radar @ArchalisRadar]

@WestallDylan @crawlhivexyz 把开发者过去的发币记录和后续结果放在一起，确实能省去很多来回查证的时间。我们在做 BNB Chain 的 Archalis，也在研究这个问题。你更想先看到同一创建者的历史，还是有资金关联的钱包的历史？资金关联本身不等于同一人控制。

[Archalis Radar @ArchalisRadar]

@crawlhivexyz @WestallDylan One approach: separate token deployer, launchpad/factory and pool creator, then show each past launch with its evidence and observation time. Shared funding should be labelled as a connection, not proof of common control. That would make the history easier to interpret.

[Archalis Radar @ArchalisRadar]

https://t.co/owfZqnhRev

[Archalis Radar @ArchalisRadar]

Simulated liquidity, drained with a hidden function. A case file, with every transaction.

The #AXIS scam contract (7777 vanilla wallet) has an owner-only function that rewrites any balance. It emits no event and leaves totalSupply unchanged.

On 21 Oct at 06:12:56 UTC the owner used it on itself: 730M tokens became 1.46 quadrillion (x2,000,000). Declared supply: 1B.

https://t.co/vOQSifhNsC

[Archalis Radar @ArchalisRadar]

@BNBCHAIN just burned $1.2B of BNB.

Also on BNB Chain, in the last 24h:
2,828 new pools analyzed.
1,778 ended in a rug pull (63%): 1,544 liquidity pulled, 180 insider sells, 54 liquidity exhausted.
Median time to rug: 12 minutes.

The chain is healthy. The launches are not.
Evidence for any token: https://t.co/Se5Tlrg6SR

[BNB Chain @BNBCHAIN]

The 37th quarterly $BNB token burn has been completed directly on BNB Smart Chain (BSC).

~1.64M $BNB has been burned, worth approximately $1.197B USD 🔥

View the details of the burn below 👇
https://t.co/sIm4wp4R1Y

[Archalis Radar @ArchalisRadar]

https://t.co/Tc2L5drmI6

[Archalis Radar @ArchalisRadar]

Two tokens. #黑马 #币安队长 Two funders. One shared funding wallet.

Today, we traced two BNB Chain launches:
• 18,000 and 20,000 USDT sent to their creators.
• Each funder also sent 250 USDT to 20 wallets before launch.
Who was funding the apparent demand? The same wallets funding the creators.

#BNBChain #OnChain

[Archalis Radar @ArchalisRadar]

In BOTH tokens, 9 of the top 10 holders appeared in those funding batches.

We verified one recipient in each group buying its respective token.

After liquidity was pulled, both creators sent funds back to their funders-in the same block, 10 seconds later.

[Archalis Radar @ArchalisRadar]

https://t.co/C27CQGeHMj

[Archalis Radar @ArchalisRadar]

#SUPERMAMA: why did we give a D to a contract that references Binance? We followed the code and the transactions. This case concerns only 0x5269cac4279825917c07761c8e162f9bfc79734f, not every token with this name. Here's what happened. 🧵 #BNBChain #DYOR

[Archalis Radar @ArchalisRadar]

The lesson for our radar: check effective powers even after ownership is renounced; don't confuse airdrops with insiders; reserve D for verified events. And always identify the contract: the same name can belong to many tokens.

[Archalis Radar @ArchalisRadar]

Sources:
@BinanceArg post: https://t.co/c6YWySaxkQ
Pool pull: https://t.co/FH2RuZz6nh
Sync: https://t.co/rtfPIsc2JR
Sale: https://t.co/de6pLVQTvZ
Contract source: https://t.co/5IMq0qa5iv
#BNBChain #BSC #RugPull

[Binance Argentina @BinanceArg]

SUPERMAMA