Open app

HostDeFi › Deployers › G4ME…fzcp

Deployer G4ME…fzcp

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

G4MEMC4G23QhXcaTM5yAqzAtTWDwFd9sLFvG7XDEfzcp

Launches on ledger
568
First seen
2026-08-31
Last seen
2026-09-20
Biggest capture mcap
$6.80K

Venue split on the ledger: unstamped ×563 · pump ×5.

The deployer record

Deployer G4MEMC4G23QhXcaTM5yAqzAtTWDwFd9sLFvG7XDEfzcp minted 263 tokens across five isolated days of the window — four firings with silence between each. August 31 produced 43; September 5 produced 100; a lone 7 on the 7th; then September 11–12 closed with 42 and 71.

Every working day is separated from the next by at least a day of silence — the wallet never ran on consecutive days at scale until the 11–12 pair at the end. The September 5 firing is the largest single day at 100, but the closing pair minted more combined.

None of the 263 launches reached the bounded candidate pool; the isolated-firings pattern is the record.

For a reader, the practical fact is the count and its spacing. Any token whose deployer field shows this address is one of roughly two hundred sixty-five siblings minted in four separated pushes. The dev-wallet guide puts cadence first among its checks, and the launch statistics place an isolated-firing profile against the feed. Tallies are dated to the August 31–September 12 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