Four Bottles. One Year. No Onchain Record.
The LVMH-owned Champagne house is launching what amounts to a multi-disciplinary event: four new vintages released simultaneously, making it one of the most expansive launches in the house’s recent history. The four releases are Dom Pérignon Vintage 2017, Dom Pérignon Vintage 2008 – Plénitude 2, Dom Pérignon Rosé Vintage 2010, and Dom Pérignon Vintage 2018. The Vintage 2018 will be available starting in October 2026. The house said each one reflects a different expression of its idea of harmony, from balancing difficult harvest conditions to extending the structure of rosé or showing the effect of aging on a classic vintage.
To understand why this is unusual, consider the house’s own architecture. According to Dom Pérignon’s own framework, the wine expresses its first Plénitude after seven years in the cellar, with a second Plénitude twelve to fifteen years after the vintage, and a third Plénitude after thirty to forty years. Around 2016, the producer stopped using the Œnothèque designation and started labeling new Plénitude releases as P2 or P3, providing more clarity to the disgorgement date. What that means in practice is that each bottle in this simultaneous release occupies a fundamentally different position in its maturation arc. The Vintage 2017 is a first-Plénitude expression — fresh, early, structurally primary. The Vintage 2008 Plénitude 2 is, by the house’s own definition, a wine that has undergone nearly two decades of transformation. The 2008 is widely considered one of the greatest Dom Pérignon vintages of the 21st century and was released out of sequence after the 2009, because the house believed it deserved more time in the cellar. These are not four versions of the same thing. They are, structurally, different products — with different aging durations, different Plénitude tiers, and presumably different recommended service windows and pricing.
The unveiling is being supported by a schedule of global dinners taking place in May and again in November, with events planned across Italy, Spain, Germany, Japan, France, Hong Kong, South Korea, Britain, Belgium, Dubai, and Thailand. Albert Adrià will host one of the May dinners at Enigma in Barcelona, following an earlier event at Casa Balañà where he created dishes matched to the Vintage 2017, the Vintage 2008 Plénitude 2, and the Rosé Vintage 2010. In November, participating chefs will include Giancarlo Perbellini at Casa Perbellini 12 Apostoli, Clare Smyth at Core, and Amaury Bouhours at Le Meurice Alain Ducasse. The dinners are clearly part of a coordinated global brand event, not isolated market introductions. That matters for the information environment the house is creating — and for what is absent from it.
What Exists Onchain for .dompérignon — And What Does Not
A search across Freename, Unstoppable Domains, and ENS surfaces no registered or minted TLD matching .dompérignon or any close transliteration owned and controlled by the house. There is no .domperignon, no .dompérignon, no sub-namespace under any verified brand-controlled onchain identity. Dom Pérignon’s parent entity, LVMH, has not publicly announced any onchain TLD strategy for its prestige cuvée brands. The house’s prior engagement with blockchain has been in a different register entirely. Dom Pérignon partnered with a digital agency to build an exclusive Web3 marketplace inspired by their collaboration with Lady Gaga, furnishing it with 100 NFTs that represented the Dom Pérignon Vintage 2010 and Dom Pérignon Rosé Vintage 2006 collections, with every NFT purchase bundled with a purchase of the bottle depicted. By linking the NFT purchase to the physical bottle, Dom Pérignon created an additional revenue stream while giving consumers digital collectibles that grew their value by nearly 1,500% on the secondary market.
That was a campaign. An onchain TLD is infrastructure. The distinction is not cosmetic. A campaign mints assets under a third-party platform’s namespace. A TLD gives the brand sovereign control over its own onchain namespace — the ability to issue, revoke, and sign second-level domains (SLDs) under a string it owns outright. Blockchain technology in Web3 ensures that once a brand owns its TLD, it stays on the decentralized ledger. There is no central registrar enforcing terms. Ownership is documented on a public blockchain, providing visible and verifiable control. Without .dompérignon as a controlled TLD, any SLD issued under that namespace by a third party carries no authority. A releases.dompérignon that the house does not own is either nonexistent or someone else’s. Neither outcome is neutral for a brand managing four simultaneous releases across three Plénitude tiers in twelve countries.
The secondary market context amplifies this. Historical data shows consistent appreciation for top Dom Pérignon vintages. The 1993 P2 Plénitude Brut appreciated 1,308% between November 2021 and April 2023. The 1990 Œnothèque Rosé gained 41% in a single year from 2023 to 2024, and even current vintages like the 2010 Brut have shown meaningful gains. The house knows its bottles trade at material valuations long after release. It knows collectors are not casual buyers. Yet the information environment those collectors operate in — which release, which disgorgement window, which Plénitude, which market availability — remains entirely mediated by the house’s own PR apparatus, by trade publications, by secondary market platforms that aggregate what they can find. None of it is signed. None of it is machine-readable. None of it is anchored onchain by the issuing house.
The Use Case the House Cannot Execute Without Onchain Identity
Consider what a releases.dompérignon SLD would make possible, stated plainly. The house controls the TLD. It publishes a machine-readable release registry as a signed record at releases.dompérignon. Each entry in that registry specifies: vintage year, Plénitude tier, disgorgement window, recommended service window, RSP by territory, and market availability by date. Every entry is cryptographically signed by a wallet address the house has publicly associated with the TLD. Any agent, any collector tool, any trade buyer system can query that record and receive a response they can verify independently — without calling a PR representative, without parsing a press release published in three languages across twelve markets, without reconciling contradictory secondary market listings.
This is not a speculative future capability. The infrastructure to support it exists now. The x402 protocol, developed by Coinbase, revives HTTP’s long-dormant 402 Payment Required status code and transforms it into a programmable payment rail for autonomous AI systems. x402 natively makes payments possible between clients and servers. When an agent requests a resource or service, the server responds with a status 402 response and a payment specification. The agent evaluates the cost, executes a USDC micropayment on-chain, and resubmits the request with a payment receipt — all within a single automated exchange, with sub-2-second settlement. A releases.dompérignon endpoint that gates premium data — RSP by market, disgorgement lot codes, allocation windows — could expose that data to collector agents through x402 on a per-query basis, at a cost the house sets. No subscriptions. No account relationships. No reseller intermediation.
ERC-8004 and x402 form a complete autonomous transaction loop. ERC-8004 answers “who you are” and “how trustworthy you are” through on-chain identity and reputation, while x402 handles “how agents pay each other” via HTTP-native micropayments. The workflow: an agent discovers another via ERC-8004 and verifies its reputation, requests a service, receives an HTTP 402 with payment requirements, pays via USDC, and the service is delivered. Apply that loop to a verified releases.dompérignon endpoint: a collector’s AI agent queries for current P2 availability in Japan, receives a 402 response from the house’s signed endpoint, pays a micropayment, and gets a machine-readable JSON response specifying allocation status, RSP range, and disgorgement window — data the house signed, timestamped, and can update in real time. In January 2026, three foundational layers converged — x402 payments, onchain identity, and autonomous agents — making this architecture not theoretical but deployable today.
The information asymmetry in the current release is substantial. The house announces four vintages simultaneously. Each occupies a different tier, a different aging duration, a different price band. Prices vary significantly depending on the expression and vintage. The current Vintage Brut 2015 starts at around $290 to $320. The Vintage 2008 Plénitude 2, by contrast, is positioned as a collector asset — a wine for buyers who already know what a P2 means and why the 2008 in particular commands a premium. The RSP differential between a P1 standard release and a P2 from a generational vintage can be measured in multiples, not percentages. The P2 releases are generally considered the most compelling expressions of the house, offering the perfect balance between evolved complexity and remaining vitality. A trade buyer placing an allocation across four simultaneous releases needs to know exactly what they are acquiring — not approximately, not by inference from press copy, but with a level of specificity that a signed, queryable, onchain record can provide and a PDF press release cannot. Without a canonical onchain record, every piece of information about these releases is derivative. It passes through intermediaries. It gets summarized, paraphrased, sometimes misattributed. The house’s own press team becomes the only source of ground truth, and ground truth that lives only in press releases is not machine-accessible. It cannot be queried by an autonomous collector agent. It cannot be embedded in a trade AI tool that a buyer runs before placing an order. It cannot be verified by a secondary market platform trying to confirm disgorgement dates for provenance purposes.
If HTTP connected the world’s computers into an information network, the combination of x402 and ERC-8004 aims to connect billions of agents into an open marketplace for services and data — no accounts, no approvals needed, just a request, a payment, and a result. The fine wine secondary market is already operating with AI-assisted tools for pricing, provenance tracking, and allocation monitoring. Dom Pérignon is one of the most actively traded wines in the world. Its universal brand recognition means there are buyers across every major market, from New York and London to Hong Kong and Tokyo — a global demand base that provides liquidity that more obscure investment wines cannot match. The buyer infrastructure is sophisticated. The data infrastructure the house provides to support it is not.
The Gap, Stated Without Ceremony
Dom Pérignon has just released four vintages simultaneously — across three Plénitude tiers, across twelve countries, supported by Michelin-starred chef dinners on two continents, with a fourth release arriving in October. The event is real. The appetite is real. The secondary market is watching. The collector agents being built right now — tools that query availability, cross-reference RSPs, flag disgorgement windows, and route allocation decisions — have no canonical signed source to query. They are scraping press releases from wine publications. They are reading secondary market aggregators. They are guessing. The house has not given them anything better, because the house does not have a releases.dompérignon that it signs, controls, and makes queryable. The harmony the house speaks about — the precise calibration between terroir, time, and expression — is entirely absent from its own information architecture.
That gap is not permanent. It is a choice, for now.
The author holds onchain positions related to this topic. This post reflects independent editorial judgment.