HostDeFi › Deployers › 512u…umih

Deployer 512u…umih

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

512uQVCiYc1PkhuoBaK4XRh4Sjp75rPjqWwe1RD9umih

Launches on ledger

623

First seen

2026-09-01

Last seen

2026-09-19

Biggest capture mcap

$3.18K

Venue split on the ledger: unstamped ×365 · pump ×258.

The deployer record

Deployer 512uQVCiYc1PkhuoBaK4XRh4Sjp75rPjqWwe1RD9umih minted 516 tokens across three days two weeks apart — 312 on September 1, 160 on September 2, then silence for twelve days, and 44 on September 15, 2026.

The shape is two separated events: an opening burst of nearly five hundred launches over two days, a long idle stretch, and a modest return on the window's last day. The September 15 activity suggests the operator was back — whether for another batch or a test is not in the ledger yet.

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

For a reader, the practical fact is the count and the gap. Any token whose deployer field shows this address is one of roughly five hundred siblings across two bursts a fortnight apart. The dev-wallet guide explains why cadence leads its checks, and the launch statistics place a two-event profile against the feed. Tallies are dated to the September 1–15 window; the ledger keeps counting.

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