We are waiting for the response from @theEXOgirl

$BOB On-chain Analysis
Let's start from the initial deployer's address (which is not Binance), this one here (`0x9c3326bB220d4C195144A440D5161209908896B0`) of the **Build On BNB (BOB)** token:

📌 Initial Distribution and Key Movements

1. Initial allocation (420.69 trillion BOB):
- At the time of the smart contract deployment (2023), the entire total supply of **420,690,000,000,000 BOB** was transferred to the deployer's wallet (`msg.sender`).
- Constructor code:
```solidity
constructor() {
_balances[_msgSender()] = _tTotal; // 420.690.000.000.000 BOB
}
```

2. **Transfer to the liquidity pool (LP)**:
- The deployer transferred **~269.996 trillion BOB** (64.18% of the supply) to the address `0x73d8bd54f7cf5fab43fe4ef40a62d390644946db`, identified as the liquidity pool on PancakeSwap.
- This transfer occurred shortly after the launch, to bootstrap liquidity on DEX.

3. Ownership renouncement and abandonment of the project:
- The deployer made the `renounceOwnership()` call, resetting the owner to `address(0)` and renouncing administrative privileges:
```solidity
function renounceOwnership() public virtual onlyOwner {
_owner = address(0);
}
```
- Last known transaction: 275 days ago (December 2024), after which the wallet is inactive.

4. Current balance:
- The deployer's current balance is 0 BOB.
- The remaining tokens were transferred to exchanges or other smaller wallets before the renouncement.

What is the risk in this context?
- Concentration in the LP: 64.18% of the BOB is locked in the liquidity pool, stabilizing the market but exposing it to "rug pull" risks if the LP were removed, no Bob LP token appears to have ever been locked or burned.
But it is equally interesting to note how around these aggregation pools rotate addresses from which, from behavioral patterns, it is possible to deduce suspicious activity.
The rest in the next post...