Open app

HostDeFi › Deployers › BVr1…NtDs

Deployer BVr1…NtDs

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

BVr1BGsT72PpSTbsyjB6KZhjRdJ2FzkBhg55nXsNtDs

Launches on ledger
654
First seen
2026-09-01
Last seen
2026-09-14
Biggest capture mcap
$11.57K

Venue split on the ledger: unstamped ×425 · pump ×229.

The deployer record

Deployer BVr1BGsT72PpSTbsyjB6KZhjRdJ2FzkBhg55nXsNtDs minted 647 tokens across nine days between September 2 and September 14, 2026 — a gappy run: 26 and 9 to open, a 145 pulse on the 4th, four days of silence, a 242 peak on the 9th, then 25, 19, 124, 4 and 53.

The four-day hole mid-window splits the run into two campaigns — an early-September batch and a second week that carried the wallet's largest single day. Intermittent production at this scale reads as an operator running discrete batches rather than a continuous process.

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 six hundred and fifty siblings across two separated campaigns. The dev-wallet guide explains why cadence leads its checks, and the launch statistics place a two-campaign run against the feed. Tallies are dated to the September 2–14 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