Summary

  • No public global tape links every IPv4 transfer to its counterparty, fees, block quality and contractual terms. RIR transfer records are authoritative for specified administrative events, but their published fields do not provide transaction prices.
  • Public price series are largely compiled by market actors. IPv4.Global publishes marketplace sales reports and a price history based on its own activity; IPv4 Market Group publishes a chart and the prices it says it has observed; IPXO publishes average lease prices on its own platform and reproduces the sales history identified as coming from IPv4.Global; Prefixx publishes market factors and current context rather than a single universal price.
  • These sources are valuable precisely because they observe transactions that third parties cannot see. Their limitation is coverage. Each platform sees its own clients, block sizes, regions, negotiation styles and disclosure choices, while private direct transactions and unsuccessful negotiations generally remain invisible.
  • Sample construction can move a benchmark without any underlying market-wide change. Weighting by transaction and by address answers different questions; listings, offers, signed deals and completed RIR transfers are different events; a bulk sale, a distressed sale and a clean /24 cannot be treated as interchangeable observations.
  • A contract-ready benchmark requires a defined interest, eligible input data, block and region categories, a minimum number of observations, a weighting rule, treatment of fees and currency, error and revision policies, coverage statistics, conflict disclosures, oversight, complaints and a contingency plan for cessation.
  • Illiquid markets do not make benchmark construction impossible. IOSCO's Principles for Financial Benchmarks explicitly provide for low-liquidity markets, but require that users understand when transactions are limited public evidence and when firm bids, offers or expert judgement enter the calculation. These principles serve here as an analytical model, not as a statement that an IPv4 chart is a regulated financial benchmark.
  • The Number Resource Society can make the market more legible by maintaining an open register of methodologies, a common transaction vocabulary and compliance reviews that preserve evidence. It must not set an official price, mandate private disclosure, approve transactions or turn a voluntary standard into a barrier to market access.

The figure appears more authoritative than the market it underpins

An IPv4 price is typically expressed with misleading simplicity: a currency amount per address. This presentation invites the reader to imagine a homogenous commodity, a common unit and a deep market in which many comparable transactions establish a single clearing value. The real market is more fragmented.

A /24 and a /16 differ not only in quantity. They attract different buyers, involve different total funding needs and may face different routing, reputation and transfer considerations. A prefix registered in one RIR service region may only be transferable to another under compatible policies and procedures. A clean aggregate may be immediately usable operationally; a block with a tarnished reputation, contested authority, fragmented use or difficult geolocation may require time and cost before deployment. A buyer needing a contiguous block is not in the same position as a buyer able to combine several smaller prefixes.

The transaction itself also varies. Some addresses are sold via an online marketplace at a listed price. Some are auctioned. Some are placed by a broker after bilateral negotiation. Some are transferred as part of a wider corporate acquisition. Some are transferred between related parties. Some are leased, temporarily transferred or used as part of a service agreement rather than sold. Some public registry changes reflect mergers or internal reorganisations without a market sale.

Compressing these differences into a single line can nevertheless be useful. The airline, metals, real estate and credit sectors all use indices that simplify diverse activity. Simplification becomes legitimate when the method tells users what has been included, what has been excluded and how dissimilar observations were made comparable. Without such a method, a chart is not necessarily wrong. It is simply easy to ask it a question it was never designed to answer.

The governance problem begins when a descriptive chart becomes prescriptive. A broker may publish its recent experience to help a seller set expectations. An analyst may reproduce that chart to describe scarcity. An investor may then use it to value a portfolio. A lender may include it in a contractual clause. A lease may revise its rent by reference to it. At each step, the apparent authority increases, even though the underlying sample has not changed.

The first discipline is therefore linguistic. A platform average is a platform average. A broker-observed range is a broker-observed range. A count of registry transfers is a count of registry transfers. None becomes a global benchmark simply because it is widely reproduced.

The visible compilers are market actors, not a consolidated exchange

The longest-running public sales price history is associated withIPv4.Global, a marketplace and brokerage of Hilco Global. It publishes monthly reports on its own marketplace, historical sales and commentary by block-size group. These reports are direct evidence of the activity the company observes. They may reveal changes within a significant trading venue, including differences between small, medium and large blocks.

The reports also make the platform's perspective visible through phrases such as 'we had' a certain number of transactions or 'our monthly average'. This is helpful disclosure. It tells the careful reader that the count refers to the publisher's activity, not to every transfer that occurred worldwide. The public pages do not present a comprehensive benchmark manual explaining every eligibility decision, rule for including private sales, weighting choice, fee adjustment, correction threshold and historical restatement.

IPv4 Market Grouppublishes another long-running view. It describes its own transaction experience, gives self-reported totals for transactions and addresses transferred, and presents a price chart and current prices by prefix-size group. This is valuable first-hand evidence from a broker that has participated in the market since its early days. It is not an independent census of competitors' transactions.

IPXOpublishes average IPv4 lease prices on IPXO platform transactions, with filters by period, RIR and mask. This is a more explicit product and population: leasing activity on a single platform. Its separateprice history analysisidentifies the historical sales data it uses as IPv4.Global data and warns that the information comes from a single independent broker and may not reveal administrative fees. Attribution matters. Two websites displaying the history do not necessarily create two independent samples.

Prefixxtakes a different public approach. It states that there is no single fixed IPv4 price and identifies block size, RIR region, reputation, transfer type, timing and contiguity as pricing factors. It offers current market context and transaction support rather than presenting its page as a universal daily fix.

The RIPE NCC's2025 State of IPv4 Reportadds institutional analysis based on registry data and interviews conducted by an external consultancy. It discusses indicative prices and states that a series of estimated market values used publicly available information from various sources involved in transfers. The report is informative, but its public explanation does not transform those sources into a complete transaction tape or a reproducible transaction-level benchmark.

These compilers are not interchangeable and should not be ranked by claiming one holds the 'true' price. They observe different slices. Governance begins by naming the slice.

RIR logs answer who and when, not how much

The Regional Internet Registries hold the strongest public evidence that certain administrative transfers took place. Their records are indispensable for market analysis. They do not, however, operate a price reporting system.

TheNRO transfer log formatprovides a common structure by which RIRs publish resource transfers. APNIC'searlier transfer log specificationillustrates the relevant fields clearly: resource type and prefix, source and destination organisations and economies, source and destination RIR, delegation date and transfer date. There is no price, currency, commission, tax, payment date, assignment-lease, warranty, escrow condition or block condition.

TheRIPE NCC transfer statisticspublish source and transferred blocks, parties, country codes, transfer type and date. They distinguish policy transfers from company structure changes. Again, no consideration field appears. ARIN makes cumulative transfer data available through its public statistics directory, but the common log is designed to record resource movements, not market economics.

This separation is sensible. An RIR must maintain accurate registration and process transfers in accordance with applicable policies. Asking it to determine the economic price, classify every ancillary arrangement or publish confidential consideration would expand its role and might discourage accurate registration. The absence of a price field is not a failure of the registry. It is a limitation on what analysts can infer from registry data.

A transfer log can provide a denominator for some questions: how many listed records match a defined transfer type, how many prefixes were moved, or what address space those records contain. It cannot provide the denominator for arm's-length paid sales unless the analyst can distinguish sales from reorganisations, related-party movements, donations and other changes. Nor can it reveal how many private leases occurred without a transfer entry.

Joining a broker's prices with the RIR log does not automatically solve the problem. A marketplace transaction may involve multiple prefixes, be finalised on a different date from the commercial agreement, or be recorded by entries that do not match the invoice one-to-one. A prefix may be split before transfer. A corporate package may include addresses alongside other assets. Matching by date and size can create confident but incorrect associations.

Public evidence therefore has two complementary layers. RIR records offer broad administrative visibility without prices. Market actors offer narrower economic visibility with prices. A defensible benchmark must state how, if at all, it links them.

Define the interest before collecting observations

The first page of a benchmark methodology should define the economic interest it seeks to measure. 'The IPv4 price' is not sufficient.

One possible interest is the cash consideration per address for completed arm's-length permanent transfers of specified prefix sizes in a given RIR region, excluding transaction fees and taxes, measured at the date of the commercial agreement. Another is the total acquisition cost to the buyer at RIR completion. A third is the midpoint of executable firm offers for clean, transfer-ready blocks. A fourth is the recurring monthly rent for identified prefixes with a defined set of routing and operational services.

These interests may move differently. A sales series is not a lease series multiplied by an assumed yield. A listing series measures seller aspiration or immediate availability, not necessarily execution. A completed transfer series measures transactions that survived due diligence and registry processing, but may be offset by weeks or months from negotiation. A total cost to buyer includes items that a net-to-seller series excludes.

Timestamps also need definition. The agreement date captures the market at the time the price was negotiated. The deposit date captures commitment. Registry completion captures administrative finality. The invoice or cash settlement date captures payment. A volatile period may place a transaction in different months depending on which event is used.

Quality is part of the definition. If the benchmark claims to measure 'clean /24s', clean must have an observable meaning: specified reputation checks, no unresolved registration disputes, transfer eligibility, routing tests and disclosed geolocation status. A marketing label without testing makes inclusion discretionary.

The rights included in the sale must also be defined. Does the consideration cover only the transfer of the recognised registry position? Are RPKI administration, reverse DNS, route objects, transition services, customer leases, receivables or warranties included? A higher package price may reflect services rather than higher address value.

The methodology should state what it does not measure. It may exclude legacy resource disputes, corporate mergers, bankruptcy packages, related-party transfers, temporary transfers and leases. Exclusion does not prove those activities are unimportant. It protects the consistency of the chosen interest.

Without a stable definition, composition changes masquerade as price changes. A series may rise because it included more small clean blocks this month, not because comparable blocks became more expensive. The methodology must make this distinction accessible to the user.

Platform bias is the first unavoidable bias

Every voluntary platform attracts a non-random user group. A marketplace designed for smaller standardised blocks may see more /24 and /22 transactions than a private broker serving very large block holders. A leasing platform may attract operators who value quick recurring access and holders willing to delegate operational use. A restructuring adviser may see distressed or strategic portfolio sales that never appear on a public listing page.

Geography compounds the effect. Brokers have different registrations, languages, client networks, banking relationships and familiarity with RIR procedures. A platform strong in ARIN and RIPE NCC transactions may not represent conditions in APNIC or LACNIC regions. Cross-RIR compatibility may widen the pool for some resources but does not erase regional documentation, demand or operational preferences.

Client selection matters. A provider known for tailored due diligence may observe cleaner blocks and clients willing to pay for certainty. A low-fee listing platform may attract more price-sensitive entities. A firm with a relationship with a large institutional seller may produce a temporary supply concentration. None of these samples is false; each depends on how the platform acquired its flow.

Publication adds another layer. A broker may know the consideration for every completed transaction but only publish standard marketplace sales. Large private deals may be omitted for confidentiality. Unusual prices may be withheld because they could identify a party. Failed negotiations, withdrawn listings and offers that never reached a reserve price may not appear in a sales table. The visible sample may therefore differ from the provider's full book.

This bias cannot be cured by calling the provider experienced. Experience may improve execution and interpretation but it does not make one firm's clientele equal to the global market. Nor can one simply average several series if their observations overlap. A secondary analyst must check whether one site republishes another's data, whether brokers co-brokered the same transaction, and whether a registry entry represents the same deal counted by two intermediaries.

The correct response is disclosure, not dismissal. The publisher should describe the platform, eligible transaction channels, geographic coverage, share of observations from its own platform, treatment of co-brokered deals and any significant concentration by client or seller. If it cannot disclose identities, it can still disclose concentration in bands.

The user then knows what the benchmark represents: not 'all IPv4' but a defined window on IPv4 trade.

Realisation bias hides negotiations that did not close

A series of completed sales observes success. It does not observe every price at which buyers declined, sellers walked away or registry conditions prevented closing.

This can create an optimistic or pessimistic picture depending on the market. If sellers anchor above available bids, only competitively priced stock sells; realised deals may appear lower than listings. If urgent buyers pay premiums while patient buyers wait, realisations may appear higher than broader willingness to pay. If difficult blocks fail due diligence, the observed sample becomes cleaner than the offered stock.

Time to realisation changes the sample again. Transactions requiring complex corporate authority, cross-RIR coordination, legacy documentation or remediation may close later than straightforward transfers. A monthly series based on realisation may over-represent easy deals during a period of congestion. Missing transactions are not random; difficulty is related to value.

Cancelled deals are informative even when their prices remain private. A methodology can publish aggregate counts of eligible observations, withdrawals, due diligence failures and incomplete registry processing without naming parties. It can state whether the calculated point uses only settled transactions or includes signed agreements pending administrative completion. It can publish the median lag between price agreement and the retained timestamp if data permit.

Firm offers can help in low-liquidity periods, but only if they are genuinely executable for a defined block and duration. An indicative email, an expired listing and a funded bid are not equivalent data. The methodology should describe verification, validity windows, deduplication and whether the submitter had authority to trade.

This is where a benchmark can become vulnerable to strategic behaviour. An entity with inventory benefits from higher published indications. A buyer benefits from lower indications. If non-transactional submissions enter the calculation, the administrator needs controls against selective submissions, fictitious indications, coordination between related parties and repeated quotes unsupported by capacity.

TheIOSCO Principles for Financial Benchmarksrecognise that a low-liquidity market can still support a benchmark and that firm bids can supplement transactions. They also require transparency on hierarchy and expert judgement. Applied by analogy, the lesson for IPv4 is simple: missing transactions do not justify inventing certainty. The series should signal an limited public evidence period when its input data threshold is not met.

Weighting can flip the apparent direction

Suppose a period contains many small-block deals and one very large deal. A simple per-transaction average gives the large deal one vote. An address-weighted average lets it dominate because it contains many more units. A median transaction price may largely describe the small-block segment. Each measure can be correctly calculated and tell a different story.

For an operator buying a /24, a median on similar /24 deals may be more relevant than a global address-weighted figure dominated by a portfolio sale. For an investor valuing millions of addresses, the large-block market may be more relevant, but a single strategic disposal may not represent the price at which the entire portfolio could be liquidated. For a lender, a prudent executable value under time pressure matters more than a stated average.

Prefix splitting complicates counts. A single commercial transaction may result in multiple registry records. Counting records as deals inflates activity. Aggregating all transfers between the same parties on a given date may incorrectly merge separate deals. The benchmark needs a transaction identifier or a documented aggregation rule that does not expose confidential identity.

Bundled deals create another problem. A buyer may acquire multiple block sizes for a single total consideration. Spreading the bundle price equally per address assumes no size premia or discounts. Spreading according to an external curve uses the benchmark to create the observations that then support the benchmark. Circularity must be avoided or disclosed.

Outlier rules can also change direction. A fixed statistical clip may remove a genuine market break. A discretionary prune may remove an inconvenient transaction. The methodology should say whether it winsorises, excludes for quality reasons, flags a special situation or publishes the observation with a tag. It should record who made the decision and why.

No single weighting rule is universally correct. The answer is a family of measures linked to uses: median transaction by prefix category, address-weighted average within category, number of observations, address volume and dispersion. Publishing only one point conceals the composition needed to evaluate it.

Coverage should accompany each point. If a large-block category contains too few independent transactions, it should say so. Carrying forward the prior month's value without a staleness indicator turns absence into false stability.

A price per address is not a quality-adjusted price

Two prefixes of equal size may impose different costs from the first day of use. Reputation systems may associate addresses with spam, fraud, proxies or other prior activity. Geolocation providers may place the range in the wrong country. Reverse DNS may require delegation. Route objects and RPKI permissions may need changes. The block may have a history of fragmented announcements or operational claims requiring resolution.

Public market sources acknowledge several of these differences. Prefixx identifies reputation, RIR region, transfer type, timing and contiguity as pricing factors. IPv4.Global distinguishes block-size segments and offers due diligence and transition services. The existence of these services is itself evidence that the nominal address count does not describe the whole transaction.

A benchmark can address quality in three ways. It can restrict eligibility to a defined standard, stratify observations by quality attributes, or adjust the price with a model. The first is clearest but covers less market activity. The second requires enough observations in each category. The third achieves broader coverage but introduces judgement and model risk.

Whichever choice is made, the benchmark should not silently mix remediated and unremediated blocks. If the transaction price includes a warranty, indemnity, replacement promise or remediation service, the methodology should say whether the value of that protection is part of the measured interest. A lower bare price plus an expensive service package may cost more than a higher clean-block price.

Contiguity deserves attention. A buyer who needs a single aggregate may discount a collection of fragments because routing and management become more complex. Another buyer may prefer smaller units for deployment. 'Large blocks are cheaper' is not a law; it is an observed relationship that depends on funding, buyer population and available stock.

Maturity to transfer is another quality. A seller with complete authority documents and a block already eligible for the intended path presents lower execution risk than a seller still resolving a corporate succession. A completed-sales benchmark selects deals that ultimately closed, but the time and professional cost to reach completion may not appear in the stated price.

A credible series therefore publishes an attribute table alongside its price. It does not need to reveal the prefix or party. It only needs to reveal enough composition so that a user knows whether the sample resembles the resource being valued.

Region, currency, fees and taxes cannot remain footnotes

A price expressed in dollars per address may have been negotiated in euros, pounds or another currency. Converting at the agreement date, invoice date or publication date can produce different results. The benchmark must choose a source and timestamp for the exchange rate and retain the original currency for audit.

Fees also change the perspective. The seller may pay a brokerage commission on gross proceeds. The buyer may pay platform, escrow, legal, due diligence and RIR fees. A published transaction price may be gross consideration, net to seller or total cost to buyer. These are not interchangeable data.

Tax treatment is jurisdiction-specific and often private. A benchmark does not need to estimate each party's tax. It should state that tax is excluded unless the measured interest explicitly includes it. It should not compare a public auction price including tax with a private sale excluding tax without adjustment.

Regional segmentation is not only about currency. RIR policies define available transfer paths, holding periods, agreements and conditions for the recipient. TheRIPE NCC reportnotes that regional policies can affect inter-RIR movement and that registry transfer counts include some company structure changes. A global series that treats every recorded movement as a sale will distort both volume and coverage.

Country codes in registry records also require caution. APNIC's analysis ofIP addresses through 2025explains that RIR country fields may refer to the holder's headquarters or intended use under different practices. They are not a reliable substitute for the commercial location of demand, transaction currency or deployment location.

A contract that refers to a 'global IPv4 price' should specify which regional category applies if policies or market conditions diverge. It should also specify the conversion rule, whether fees are included, and what happens when the relevant category has limited public evidence observations.

The benchmark administrator should publish both original and standardised values where confidentiality permits. Standardisation enables comparison; original terms make standardisation contestable. A single converted figure without its conventions creates an illusion of precision.

Commercial interest does not disqualify a compiler, but it must be visible

The companies with the best price information are often those that broker, list, lease, finance or advise on IPv4 transactions. Excluding every administrator with a commercial interest would remove a large share of the available evidence. Pretending that interest does not exist is worse.

A broker may earn more commission when a deal closes. A marketplace benefits from liquidity and being perceived as the go-to platform. A lessor benefits from confidence in the recurring rental value. A holder benefits from higher sale benchmarks. A consultant may publish a bullish view while seeking mandates from sellers. None of these facts proves manipulation. Each determines the controls a user should demand.

The publisher should identify its activities, how fees are generally calculated, whether employees or affiliates may hold relevant inventory, whether contributed data come from clients, and whether commercial staff can influence benchmark determinations. It should separate marketing commentary from the mechanical output.

Oversight should include people who do not report to the revenue line responsible for the observed transactions. Significant inclusion or exclusion decisions should leave a reasoned trail. Related-party transactions should be excluded, separately tagged or subjected to a defined arm's-length test. Co-brokered activity should not be double-counted.

The public output should disclose concentration without violating confidentiality. Examples include the share of address volume contributed by the largest contributor, the share of transactions from the administrator's own platform, and the number of independent buyers and sellers represented in bands. If a single portfolio sale drives a point, users should know that concentration occurred.

Forecasts require an even clearer boundary. A current benchmark should be based on defined current input data. An outlook is an analyst's judgement about the future. Publishing them on the same chart without distinction allows the forecast to borrow the benchmark's authority.

The IOSCO Principles place heavy emphasis on administrator governance, conflicts, submitter controls and accountability because a benchmark's integrity depends on more than arithmetic. An IPv4 methodology can adopt these disciplines voluntarily without claiming regulatory status. Commercial expertise and open governance can coexist.

The minimum methodology is longer than a chart legend

A contract-ready IPv4 benchmark should publish a methodology with at least four layers.

The first layer defines the scope. It names the administrator, the measured interest, eligible transaction types, prefix categories, regions, quality standard, currencies, fee treatment, timestamp, publication frequency and intended uses. It states whether the point measures listings, firm quotes, signed agreements, cash settlements or completed registration.

The second layer defines input data. It describes accepted sources, contributor eligibility, verification, deduplication checks, related-party handling, confidentiality, late data and the hierarchy between executed transactions, committed orders, firm bids and expert judgement. It states the minimum number of independent observations and any concentration limit required to publish.

The third layer defines calculation. It identifies weighting, aggregation, outlier treatment, bundle allocation, currency conversion, rounding, stale values, model use and quality adjustments. It gives examples with synthetic data so that users can replicate the calculation without exposing a real party.

The fourth layer defines governance. It establishes oversight, conflict controls, record retention, complaints, independent review, correction thresholds, revision windows, methodology consultation, emergency publication, cessation and contractual fallback.

Each published point should then be accompanied by a compact coverage statement: number of eligible transactions, independent buyers and sellers in non-identifiable bands, total addresses, prefix-size distribution, regional distribution, share of transactional versus non-transactional data, concentration, dispersion, staleness status and any expert adjustments.

Confidentiality is not a reason to omit all coverage. Small cells can be suppressed or grouped. Publication can be delayed. A trusted examiner can inspect protected evidence and publish an assurance conclusion. What cannot be done is to claim representativeness while refusing to describe the sample at any level.

The methodology must also have a version. If a publisher changes block categories, adds private sales, or moves from per-transaction to address-weighted, the historical series may break. Users need the effective date, rationale, impact analysis and whether history has been restated.

This is more work than plotting a line. It is precisely why a line should not govern cash flows until the work is done.

Revision policy is part of the price, not an editorial detail

IPv4 transactions may be reported after the period closes. A broker may discover that a bundle was misallocated. A registry transfer may complete after a signed agreement failed or changed size. Currency or fee treatment may be corrected. A benchmark that never revises may remain wrong; one that revises without rules may rewrite contractual history.

The administrator should distinguish routine late-data updates, error corrections and methodological restatements. Each needs a threshold and window. A small correction below publication precision can be recorded without changing the main figure. A significant error should trigger a revised point, a notice and a machine-readable record of old and new values.

Contracts must say which value prevails. If rent is revised on publication day, does a later correction change already-paid invoices? Does the corrected value apply prospectively? Can either party challenge a calculation? The benchmark administrator cannot answer every commercial question, but its revision policy gives the contract a stable input.

Historical comparability also matters. When methodology changes, the administrator may run old and new methods in parallel for a period, restate history where evidence permits, or mark a series break. It should not merge two methods into one continuous line without disclosure.

Cessation deserves advance planning. A broker may exit the market, stop publishing, be acquired, or lose enough observations to make the series unrepresentative. A website disappearing is not an acceptable definition of a contractual event. The administrator should publish a cessation policy and notice when possible.

Users need fallbacks that do not create circular discretion. A contract might switch to a second specified independent series, use a panel with documented quotes, obtain a qualified valuation, or carry forward the last value only for a short defined interval before renegotiation. 'A reasonable market price chosen by the lessor' is not a neutral fallback.

The IOSCO transition principle asks benchmark users to plan for material changes or cessation and to include robust fallback provisions. IPv4 contracts should do likewise even when the reference series is not subject to financial benchmarks regulation.

Revision governance protects both parties. It prevents an obvious error from becoming permanent and prevents a publisher or contracting party from changing history when the outcome becomes inconvenient.

Low-liquidity periods should produce less confidence, not more modelling

The temptation in an illiquid category is to fill the gap. The prior value may be carried forward, a neighbouring prefix size may be adjusted, a listing midpoint may substitute for a transaction, or an expert may estimate where a deal would land. Each technique can be reasonable if disclosed. None equals an executed observation.

The input data hierarchy should place verified arm's-length transactions at the top, closest to the measured interest. Executable firm bids may follow. Indicative quotes, comparable categories and models may sit below. The published result should state how far down the hierarchy it went.

Minimum data requirements should include independence, not just count. Ten prefixes sold in one lot to one buyer are not ten independent price discoveries. Five submissions from affiliates are not five market views. The administrator should test contributor concentration and common control.

Expert judgement needs boundaries. The decision-maker should record the observable facts, the adjustment and the rationale. Repeated judgement in the same direction should be reviewed. Commercial staff should not be able to informally adjust a point because they think the market feels stronger.

Some periods should not have a benchmark. 'Limited public evidence eligible data' is useful information. It warns a contracting party that the chosen index may not suit frequent revisions. Publishing a precise modelled point may encourage leverage and contractual reliance not supported by the market.

Dispersion matters alongside the central estimate. A wide range may reflect quality, region or genuinely uncertain clearing conditions. A narrow point derived from a model does not eliminate that uncertainty. Confidence indicators should respond to sample size, independence, concentration and input data type.

The benchmark may publish a hierarchy indicator, such as transaction-supported, quote-supported or model-supported, without claiming those categories have equal strength. Users can then define their own rules. A lender may accept only transaction-supported observations. A valuation may use model-supported points with a wider range. A lease may defer a revision when data are limited public evidence.

Market maturity shows itself in the ability to admit uncertainty. A benchmark's legitimacy should not depend on publishing every month at any cost.

Contracts must not outsource judgement to an undefined webpage

An IPv4 purchase agreement may use a benchmark to adjust the price between signing and completion. A lease may index the renewal rent. A financing agreement may test collateral coverage. A portfolio manager may value holdings. Each use requires different tailoring.

The contract should name the benchmark administrator, series, version, region, block category, currency, fee basis and observation date. It should archive or attach the applicable methodology. Referencing only the 'prevailing IPv4 price' or a homepage leaves the decisive term open.

The contract should state how the block in question maps to the series. A /19 should not automatically use a /24 point. A damaged block should not receive a clean-block benchmark without an agreed adjustment. A lot should not be split by unilateral judgement after signing.

Publication timing matters. If the series appears after month-end, the contract should identify the first publication or the final revised value. It should handle holidays, delayed publication, limited public evidence data, a material methodology change and cessation. It should also state whether a correction reopens settled amounts.

Conflict protection is especially important when a party to the contract or its broker contributes data to the benchmark. The contract may exclude the parties' own transaction from a revision, require independent calculation, cap the effect of non-transactional data, or permit challenge based on evidence.

A benchmark should not be the sole evidence of fair value. The specific resource has its own reputation, authority, burden, services and timing. A benchmark provides context; due diligence provides deal-specific facts. The more unusual the block or lot, the less weight a broad series should carry.

Valuation users should also distinguish orderly exit value from forced-sale value and portfolio value from marginal deal value. Selling a /24 at the advertised market price does not prove that millions of addresses can be liquidated at the same point without moving the market.

The strongest contractual clause contains a fallback ladder and an obligation to exchange supporting evidence. It makes the benchmark useful without turning a publisher into an unappointed arbitrator.

Investors need coverage and liquidity, not a heroic line

An investor evaluating an IPv4 strategy asks more than whether the last point went up or down. It asks what volume could be traded near that point, how long execution takes, what costs sit outside the quote, how value differs by block and region, and what happens when IPv6 or policy changes alter demand.

A price history from a single platform can support scenario analysis if its limitations are preserved. It can show that the platform observed changing conditions. It cannot prove that an unobserved portfolio shared the same return. Backtests that apply a small-block series to every historical holding create artificial performance.

Liquidity should be measured separately from price. Registry logs can help describe administrative transfer activity but, as the RIPE NCC report warns, these logs may include company structure changes. Broker counts describe their own activity. Neither alone provides the total value of global arm's-length sales.

Bid-ask spreads, time on market, withdrawal rates and concentration would improve investment analysis, but public denominators are incomplete. The responsible conclusion is not that liquidity is high or low by a universal percentage. It is that users need platform-specific evidence and stress assumptions.

Valuation should use ranges and scenarios. A base scenario may use comparable executed observations. A downside scenario may account for time, fees, reputation remediation and market impact. An upside scenario may factor in scarcity and strategic demand without treating advocacy as an executed bid. Each scenario should identify the source and sensitivity.

The same discipline applies to collateral. A lender should not lend against a stated per-address price without testing enforceability, registry completion, buyer depth and selling costs. A benchmark may trigger a review, but it does not supply a buyer after default.

There is no public denominator for the share of all IPv4 transactions captured by a cited price publisher. There is no public global count of failed sales, private counterparties or lease terms. This analysis does not estimate those rates. It treats absence as a limitation on confidence, not a licence to fill the gap.

The Number Resource Society can govern method without governing price

The Number Resource Society has a credible positive role if it resists the appeal of an official figure. Its public materials advocate transparency, accountability and wider operator participation in numbering resource governance. These objectives support an open methodology layer for prices, but they do not establish that NRS currently operates an audited benchmark or that it possesses a comprehensive transaction dataset.

A first useful contribution would be a public vocabulary. It could define permanent transfer, temporary transfer, lease, listing, firm offer, signed deal, registry completion, gross consideration, net to seller, total cost to buyer, prefix category, quality attributes and related-party transaction. Common terms would allow publishers to disagree openly rather than present different measures under the same label.

A second contribution would be a register of methodologies. Any broker, platform, analyst or academic group could deposit a versioned methodology, coverage template, conflict statement and revision history. NRS could verify whether the publisher followed its own stated method and publish the review evidence. It would not decide whether the price is high or low.

A third contribution would be a confidential contribution protocol. Parties could submit protected transaction facts to independent depositories using a common format. Only coverage and non-identifying aggregated results would be public. Participation should remain voluntary unless a competent legal authority imposes a specific obligation. The absence of a dataset must not be treated as suspicious.

A fourth contribution would be interoperability. Multiple administrators could publish competing series using comparable coverage labels. Users could select the series fitting their contract and detect overlaps. A decentralised system is more resilient than a single official fix and enables methodological competition.

Safeguards are as important as the service. NRS should disclose funding and affiliations, separate advocacy from review, include perspectives of buyers, sellers, operators and independent metrics, publish complaints and corrections, and allow external audit. It should not require an NRS benchmark for an RIR transfer, certify a private transaction as morally acceptable, or require private contracts as the price of market participation.

This role is positive because it creates public infrastructure from facts the market already produces. It is limited by evidence because compliance with a method does not prove total coverage, fair value for every block, or legal status in every jurisdiction.

A practical assurance label would expose uncertainty rather than hide it

A useful compliance label could have five dimensions.

'Method disclosed' would mean that the measured interest, input data, calculation, quality rules and timestamp are public. 'Coverage disclosed' would mean that each point includes the number of observations, volume, independence, concentration and input data hierarchy in non-identifiable form. 'Revisions controlled' would mean that errors, late data, method changes and cessation follow published rules. 'Interests disclosed' would mean that the administrator and contributors identify commercial roles and relevant controls. 'Calculation examined' would mean that an independent examiner tested a sample against the stated method.

The label should not say 'correct price'. Two compliant benchmarks may differ because they measure different regions, block sizes or platforms. The point is to make the difference intelligible.

Assurance should be periodic and event-triggered. A material methodology change, new data source, administrator acquisition or abrupt concentration shift should trigger a review. The examiner should publish exceptions rather than negotiate them privately.

Open test files can improve reproducibility. The administrator can publish synthetic observations and expected calculations. Users can verify weighting, currency, outliers and revisions without accessing protected transactions. A cryptographic commitment to the protected dataset could later show that the dataset was not silently altered, though it does not prove the truthfulness of each submission.

Complaints should be accessible to contributors and users. A party may challenge double-counting, misclassification, an unannounced change or a calculation error. The process should publish outcomes while protecting transaction confidentiality.

Costs should be proportional. A small broker publishing occasional commentary should not need the same control environment as a series embedded in large contracts. The label can identify the intended use: commentary, valuation support or contractual reference. Accountability increases with reliance.

The market would then have a way to distinguish a useful opinion from a governed reference without suppressing either. That is better than declaring an official price and better than accepting every chart as equivalent.

What the evidence supports, and what remains unavailable

The evidence supports four strong conclusions.

First, market actors publish meaningful IPv4 price information. IPv4.Global, IPv4 Market Group, IPXO and Prefixx each provide direct evidence by virtue of their roles. Their observations should not be dismissed simply because they are commercial.

Second, their public samples and methods differ. IPXO explicitly identifies its platform population for lease averages and attributes the sales history data to IPv4.Global. IPv4.Global's reports speak to its marketplace activity. IPv4 Market Group describes its own experience. Prefixx emphasises deal-specific factors. Copying the same underlying data across multiple sites does not create independent confirmation.

Third, RIR transfer data cannot provide the missing prices. The published formats provide resource, party, region, type and date fields, not consideration. Transfer counts can contextualise activity only after analysts account for company structure changes, record splitting and other non-price events.

Fourth, established benchmark governance principles offer a practical design for methodology, input data quality, conflicts, revisions, complaints, review and transition. They can be adopted voluntarily and proportionally without claiming IPv4 is a regulated financial instrument.

Important denominators remain unavailable. No cited public source establishes the number or value of all global arm's-length IPv4 sales. No source establishes the share each broker or platform captures. No comprehensive public dataset links every transfer to price, fees, quality, negotiation date and contract type. No public evidence supports a universal error rate for current price charts or a prevalence rate for manipulation.

These gaps do not prevent price discovery. They prevent over-claiming. A transparent partial benchmark can be highly useful. An opaque claim to universality is brittle.

The benchmark earns its authority after reliance, not before

IPv4 commerce has developed enough public history to make prices discussable but not enough shared reporting to make a figure self-proving. Practical market experts see real transactions. Registries see real administrative changes. Analysts see public series and broader trends. Each holds part of the picture.

The next step is not a mandatory global price. It is a disciplined account of what each published price means. Method, coverage, revision and interest disclosure turn a figure from assertion into evidence. They allow competing series to coexist and users to choose the one fitting a particular block, region and contract.

Contracts should come last. Once a series automatically adjusts payments, its administrator exercises practical power over parties who may never have contributed data or consented to a later methodological change. That power needs rules, oversight and a fallback.

Investors should demand the same discipline. A line without address volume, independent observations and dispersion cannot alone carry a portfolio valuation. Registries should continue to publish accurate transfer facts without being converted into price authorities. Brokers should be able to publish their expertise while naming their sample. Analysts should preserve attribution and avoid counting republished data as independent.

The Number Resource Society can help make these roles legible. Its strongest contribution is not to announce what an address is worth. It is to make every claimed price reference answer four questions: how was it built, what did it cover, what changed after publication, and who had an interest in the outcome?

Until a series can answer these, it is market information, not market law.

Sources