Algorand birthday site pins 8th anniversary to June 12, 2027 — dug from block records

A countdown with a contested date

Every June, one question quietly divides the Algorand community: on what day, exactly, was the network born? isitalgorandsbirthday.com¹ exists to answer it, and right now its answer is a countdown — 21 days to Saturday, June 12, 2027 at midnight UTC, labeled the '8th² Birthday Countdown.' When the clock hits zero, the site promises a 'Free NFT drop on June 12 at midnight UTC exactly,' and visitors present at the moment receive a browser code entitling them to a free copy. The page offers a Google Calendar reminder, an archive of five past birthday editions, and wallet connection for Pera, Defly and Lute to check eligibility.

The date on that countdown is the real story, because 'Algorand's birthday' has never been settled. The genesis file — Algorand's 'block zero' is not a block but the configuration file the network launched with — carries a timestamp of June 11, 2019, 00:00 UTC. The Algorand Foundation³ has itself marked two different dates: its May 2026 report noted that 'June 11 marks seven years since Block 0,' while the same report wrote that 'On June 19, Algorand celebrates seven years since the network launched' — June 19 being the day ALGO first reached the public through a Dutch auction. D13, the pseudonymous researcher who runs the countdown site, now argues a third date, and this time he has built his case out of the ledger itself.

When a genesis timestamp becomes a red herring

D13 first built the countdown for MainNet's third anniversary in June 2022, picking June 11 straight off the genesis timestamp — the domain was registered on June 1, 2022, the same day his D13.co⁴ announcement went up. A 2026 update appended to that post now reads: 'We picked wrong — turns out MainNet's birthday is June 12.' The correction is argued at length in D13's 'MainNet Archaeology' series, which reconstructs the launch time from block timestamps rather than from marketing calendars.

The technique starts with how Algorand timestamps blocks. Each block's proposer chooses that block's timestamp, subject to a consensus rule that the gap between consecutive blocks — the 'round time' — must fall between 0 and 25 seconds. MainNet's first 6,637⁵ rounds all recorded the maximum 25⁶-second gap. Since the genesis timestamp pins the earliest legal block time, a long run of max-gap blocks is exactly what you would expect from nodes that considered their local clocks to be running 'way ahead' of the ledger's recorded time — the signature of a network that actually started later than its own configuration file suggests. Anchoring at round 6,638⁷, the first block stamped 22:05:29 UTC on June 12 (the moment round times settled to roughly 4.25⁸ seconds), and averaging backward, yields an estimated launch of about 14:15 UTC on June 12, 2019 — 10:15 AM in Boston, a saner moment to switch on a network than 8 PM on a Monday. Round-to-date lookups confirm both anchor points: round 1 is stamped June 11, 2019 at 00:00:25 UTC, and round 6,638⁹ at June 12, 2019, 22:05:29 UTC.

The reconstruction leaves four candidate dates on the table, each with a distinct meaning:

Source: 10 d13.co

D13 frames the whole dispute in deliberately satirical terms — 'Genesarians' hold June 11, 'Duodecimalists' June 12, 'First Transactionists' June 15, 'Dutchaversarists' June 19 — and puts the question to an on-chain vote. Voting costs nothing: send a 0-ALGO payment to a vanity address (777WHEN777IS777MY777BIRTHDAY777HELP...) with a note in the standardized ARC-2 format, such as 'd13bday:u12,' and the most recent vote per wallet wins. Ten wallets have voted; 7 chose June 12, 2 chose June 11 and 1 chose June 15. One of the June 12 votes comes from the operator's own d13.algo account — a useful reminder that the countdown's keeper is also its advocate.

Five birthdays, five editions, and a standing burn policy

Each June the site mints a commemorative 'fractional NFT': a single Algorand Standard Asset (ASA), the base-layer token type that lets anyone issue a token without a smart contract, split here into hundreds of identical video collectibles. All five editions were minted from one vanity address whose name spells JUNEII..CAME, and each edition's video is stored on IPFS, encoded for display inside Pera Wallet's collectible view. Every edition carries no freeze or clawback roles — the issuer cannot freeze or seize the tokens — and every edition has honored the standing 2022 promise that unsold copies would be 'verifiably burned,' locked away forever in a burn address.

Take-up has been thin, and the ledger shows exactly how thin. The 2022 drop sold 50 of its 1,096¹¹ copies; 2023 moved 110 of the 200 on offer; 2024 sold 141 of 260. From 2025 the drop went free — 520 units, then 777¹² — open to midnight attendees and anyone who had ever bought or claimed before. The chart below shows the share of each edition's supply now sitting in a burn address, the visible residue of that policy, from 95.4% of the 2022 run to 43.3% of the 2023 edition. One wrinkle: the 2025 availability page still reads '141/260' — a counter evidently copied from the 2024 edition, against an on-chain supply of 520 units — a small instance of the site's pages lagging the ledger.

What the burn data does not capture is how each edition was designed and offered — the per-year details differ in ways worth separating out:

Sources: 13 d13.co, 14 isitalgorandsbirthday.com

None of the five editions was found listed on Downbad, Statto, Rand Gallery or Exa Market at the time of research, so whatever aftermarket exists runs outside the major Algorand NFT venues.

What the next drop will take

For a reader who wants the 2027 edition, the mechanics are straightforward and entirely on mainnet — these are real ASAs with real, if nominal, economic stakes, not a testnet demo. Show up at the site around midnight UTC on June 12, 2027 with a Pera, Defly or Lute wallet connected; if the countdown's promise holds, being present at the stroke of zero issues a browser code that makes you eligible for a free copy. Eligibility for the 2025 and 2026 drops remains checkable through published spreadsheets linked from each edition's page, and past claimants got a head start for the 2026 round. The operator has run this loop five times without missing a year.

The operator, and what to read carefully

D13 is an active and productive builder, not a hobbyist. His GitHub organization spans 59 public repositories — 38 stars across all of them — with several pushed within days of this writing: an app-address registry, algo.surf¹⁵ (his own chain explorer, which the birthday pages and the archaeology post link to), an Algorand metrics SDK, and 'The Reti' consensus-incentive contracts. Our prior coverage of D13.co documents his fee-sustainability proposals and his disclosures of vulnerabilities in several high-profile Algorand smart contracts. The archaeology post itself carries a disclaimer that its views 'are personal, not representing my employer.'

Read the countdown with its incentives in view. D13 is not a neutral historian: the birthday site is a promotional engine for that broader ecosystem work, and the paid editions raised real money at 3, 40 and 50 ALGO a copy. The 2025–2026 shift to free, past-buyer-only drops functions as a loyalty loop for precisely the audience his other projects target. Two claims warrant scrutiny rather than repetition. The 2024 pledge noted above cannot be verified on-chain: no recipient addresses are published, so there is no way to confirm the EFF or COOP DAO donations were made. And free-drop eligibility is administered through browser codes and spreadsheets rather than enforced by a smart contract — participation rests on the operator's good faith, the same good faith the assets' 'no freeze, no clawback' settings advertise. Those settings cover the tokens themselves; they say nothing about the off-chain mechanics around them.

For all the caveats, the project does what it says: five editions minted on schedule, every one burned down to its sold or claimed remainder. And its central factual claim is falsifiable — anyone running a node can replay the early block timestamps and judge for themselves whether June 12 holds.