Open app

HostDeFi › Deployers › 3ZQs…t2QP

Deployer 3ZQs…t2QP

Tallied from HostDeFi's own launch captures · 2026-09-03 → 2026-09-15 · a ledger record, not an accusation or endorsement

3ZQs2pNRqSKupNh37EtHm4pMQkRzGnZiLvj1a44Yt2QP

Launches on ledger
566
First seen
2026-09-03
Last seen
2026-09-15
Biggest capture mcap
$21.01K

Venue split on the ledger: unstamped ×290 · pump ×276.

The deployer record

Deployer 3ZQs2pNRqSKupNh37EtHm4pMQkRzGnZiLvj1a44Yt2QP minted 548 tokens across nine days between September 6 and September 15, 2026 — a three-day open at ~70-100 a day, a single enormous spike of 251 on September 9, then a collapse: 1, 41, 4, 2 and 10.

The 251-day is the anomaly — more than three times the wallet's baseline, after which production fell to single digits and never recovered. A spike-then-silence that total usually means the run's purpose was that one day's batch, or the operator hit a limit — funding, rate caps, or attention.

None of its launches reached the bounded candidate pool; the cadence is the record.

For a reader, the practical fact is the count. Any token whose deployer field shows this address is one of roughly five hundred and fifty siblings, nearly half of them minted across two days. The dev-wallet guide explains why cadence leads its checks, and the launch statistics place a spike-then-silence profile against the feed. Tallies are dated to the September 6–15 window; the ledger keeps counting.

Share this deployer recordPost on XTelegram

HostDeFi is an educational risk tool, not financial advice. Deployer records tally our own dated launch captures; the ledger observes a sample, not the wallet's whole history, and presence here is neither listing nor accusation. How this page was made: the tallies are counted from HostDeFi's own launch captures at render time, and the written record is the HostDeFi desk's own write-up of this one wallet, dated to the window it describes. A HostDeFi product