Summary

  • The existing RIR transfer logs are valuable records of custody. Their common JSON publication format can identify transferred IPv4, IPv6, or AS number ranges, source and destination organisations, the registry pair, the transfer date, and the general transaction type. They support provenance checks and research on post-transfer routing. However, they are not a complete market record.
  • A completed line contains no contract price, no currency, no fees, no contract date, no application date, no time spent with each registry, no rejected or withdrawn cases, no ageing of pending cases, no reason for failure, no broker coverage, and no transactions that changed operational control without a recognised transfer. Successful transfers are therefore a selective numerator without a stable denominator.
  • Price confidentiality does not require price blindness. Registries, brokers, and escrow services could report quarterly medians, quartiles, volume-weighted averages, block size bands, interquartile ranges, and coverage rates, but only once a minimum cell count is reached. The publication should be delayed and separated from named transaction lines, so that an aggregate cannot be traced back to a party's contract.
  • Delay must be broken down by stage and controller. The calendar time from complete request to record change, the days controlled by the registry, the days of party response, the bilateral handover time, the fee and contract time, and the ageing of pending cases answer different questions. A single average processing time allows an institution to attribute the rest to everyone else.
  • Rejection reporting requires an explicit case count and a reconciliation: Pending cases at the start plus new complete applications should equal approvals, rejections, withdrawals, and pending cases at the end, after accounting for reopened or merged cases. Standardised rejection reasons and appeal outcomes can be published without disclosing application documents.
  • The Number Resource Society can provide the missing public interest layer as a minimal ledger and independent aggregation service. It can publish definitions, collect signed but confidential price observations, reconcile RIR performance, preserve revision history, and make datasets portable, while refusing to broker deals, set prices, or turn its own certificate into a new barrier.

The Line for the Winner Is an Attractive Illusion

A transfer log creates the satisfying impression of a fully observed market. There is a date, a block, a source, a destination, and perhaps two registries. The resource was moved. The public record changed. An analyst can count lines, sum addresses, and draw a line through time.

Everything difficult happened outside the line.

The seller may have marketed the block for months. Multiple buyers may have withdrawn after learning their registry path was unavailable. The final buyer may have sought pre-approval, renegotiated the price when reputation checks revealed a history of abuse, waited for corporate documents, paid a broker and escrow agent, and then watched the two registries coordinate. A rejected applicant leaves no completed line. A buyer who could not meet a needs assessment may never file an application. A seller who leased operational control without changing the recognised holder may never appear.

The final transfer date is therefore a publication event in a selected population. It proves that a record changed. It does not prove that the process was fast, open, competitive, or consistent. It does not show whether the same block sold for USD 10 or USD 50 per address, whether a small buyer paid a premium, or whether a regional incompatibility narrowed the bidder pool.

This distinction matters because a registry does not just observe the market. Its decision is part of the close. Buyers and sellers can agree on price, but closing often depends on updating the authoritative record. A log of approvals is partly a log of the institution's own exercise of power. Members cannot evaluate that power when they only see cases that survived.

The absence is most severe in thin markets. Ten successful transfers may look like steady activity. If they come from eleven complete applications, the department appears predictable. If they come from a hundred applications, with long delays and unexplained withdrawals, the same ten lines describe a restrictive system. If brokers have screened out hundreds more because a path was known to be closed, even the registry denominator is incomplete.

This does not make the completed log misleading. It makes its purpose narrower than its visual authority. A custody log answers: Which recognised record changed, from whom to whom, for which resource, and when? A market transparency statement answers: Who could participate, what did they pay, how long did cases take, which cases failed, why did they fail, and how much of the market do the data cover?

Both are needed. Combining them in a public line would disclose contracts and create security risks. Treating the first as a substitute for the second protects the institution from scrutiny. The correct design keeps transaction identity and market accountability in separate, reconcilable publications.

What the Usual RIR Logs Actually Record

The five registries have done important technical work towards comparable publication. ARIN'sNRO Transfer Log Format Descriptionstates that the common JSON design covers IP address and AS number transfers within and between RIRs. Each registry publishes a cumulativetransfers_latest.jsonfile and dated archives. This is a stronger foundation than isolated web tables, because researchers can keep versions and review changes over time.

The live feeds are available fromARIN,APNIC,RIPE NCC,LACNICandAFRINIC. A field check on 14 July 2026 revealed a recognisable common core: original and transferred resource sets, source and destination organisations, source and destination RIRs, transfer date, and transaction type. The resource set may contain IPv4 networks, IPv6 networks, or AS numbers. Organisation entries may include name and country code.

The feeds are not identical. ARIN and LACNIC include a source registration date on some records; the other current feeds do not expose this field. Current files use broad labels such as Resource Transfer and Merger or Acquisition. The latest transfer dates visible in the files also differ significantly, so a user cannot assume that downloading five files at one point yields five equally current populations.

The common core is well suited for documenting provenance. A network operator can ask whether a block was moved after a historical allocation. A researcher can measure address volume by destination region, compare block sizes, or examine routing after the transfer date. The 2017 studyOn IPv4 Transfer Markets: Analyzing Reported Transfers and Inferring Transfers in the Wildcombined published RIR transfers with routing and other data to examine whether transferred space was used and to infer unreported movements. This is evidence of the logs' research value.

However, the common fields describe the completed resource state, not the economic or administrative path of the transaction. They contain no contract price, no currency, no broker, no escrow date, no request timestamp, no completeness date, no approval timestamp, no rejection status, no withdrawal status, no pending status, no review reason, or appeal. A merger and an arm's-length sale can both move a resource but reflect different markets. A resource transfer label does not prove that money changed hands.

Even the date requires care. It is the recorded transfer date, not necessarily the contract signing, price agreement, payment, routing change, or first use. Treating it as a sale date can place an observation in the wrong market period. Considering every transferred address as sold can turn restructurings or donations into fabricated revenue.

Thus the current logs are a public skeleton: unusually useful, cumulative, and machine-readable, but built for custody. A transparent market analysis must add a second layer whose definitions do not spoil this purpose.

The Observation Unit Is Not Yet Stable

Before adding fields, the registries must define what a case is. This is harder than it sounds.

A commercial agreement may contain multiple prefixes. A prefix may be split across multiple transfer records. A single corporate transaction may move IPv4, IPv6, and AS numbers. ARIN's transfer policy explains that source and destination submit separate tickets which staff link. An inter-RIR case may have a ticket in each registry and one for each party. A later correction may update the same resource. A merger may move many records without an address market negotiation.

Counting lines therefore does not necessarily count deals. Counting tickets does not necessarily count applications. Counting addresses gives volume but lets one large block dominate. Counting organisations may aggregate repeated purchases by one large platform while splitting subsidiaries of a group. Each denominator answers a different question.

ARIN'sstatistics pageprovides an instructive example. It reports transfer requests and processed transfer tickets, and explicitly states that a processed ticket is a submitted ticket that was closed regardless of final status. It reports separately on completed address volume within region and between RIRs. This is better than equating every closed ticket with an approval, but the public chart does not by itself turn closed tickets into a results table with rejection and withdrawal reasons.

A minimal market statement should use a case identifier within the involved registries and publish aggregates at four levels. Thecommercial caseis a buyer-seller agreement, if the parties report it. Theregistry caseis a requested change to recognised custody for a defined resource set. Theparty ticketis an interaction of a source or destination with a registry. Theresource recordis each changed prefix or ASN entry.

These levels should be reconciled and not added. One commercial case may produce one registry case, four party tickets, and twenty resource lines. The public statement can report all four counts with an explanation. It should never call their sum market volume.

Inter-RIR cases also need a common case reference. The reference can remain hidden from the transaction log if its linkage would reveal confidential phases, but both registries need it for aggregate reconciliation. Otherwise, each may report its half as a separate request, or one may exclude the case while the other includes it. A bilateral close must not become two global closes.

Reopened and amended cases require rules. If a buyer changes the block size after review, is that one case or a withdrawal and a new application? If a seller replaces a corporate document, the case remains one. If the parties replace the counterparty after a price failure, the commercial case has changed even if the source block was not changed. Definitions should be set before outcomes are known, with disclosed revisions.

Transparency begins here because institutions can improve apparent performance by changing units. Fewer, larger cases can lower case counts while address volume rises. Splitting a difficult case can inflate closings. A stable observation unit prevents publication from becoming a producer-selected story.

Price Blindness Leaves Buyers Dependent on Private Storytellers

Regional Internet registries often say that commercial terms are a matter for the parties. ARIN states that negotiations and financial terms can be resolved directly or through an intermediary. LACNIC says it does not participate in commercial transactions between parties using its listing service. This restraint is appropriate: maintaining an authoritative address record does not give a registry a mandate to set the sale price.

Non-participation is not the same as public ignorance. The IPv4 price is already discussed through brokers, auctions, court documents, and selected transactions. The problem is coverage and comparability. A broker knows its own deals, not necessarily the entire market. Its published series may be honest and still shaped by client mix, block size, region, reputation, and won transactions.

Market significance is visible in APNIC Chief Scientist Geoff Huston's reviewof IP addresses through 2025. Using transaction data from Hilco Streambank's IPv4.Global, the analysis reports that prices rose strongly to 2021, declined later, and in 2025 included a low of USD 9 per address for a /14 and a mean of USD 22 per address over the last 40 days to 10 January 2026. The article carefully identifies the private data provider. It is a price series, not a census of all transfers.

IPv4.Global'smonthly reportsprovide current observations and commentary on block size. They also come from a market intermediary with an interest in transactions. Another broker may see a different population. Public RIR logs can provide the denominator of completed resources, but since they omit price and broker, they cannot show what proportion of logged volume underlies a private series.

This asymmetry advantages large repeat buyers and established brokers. They observe bids, failed offers, time to close, and discounts for constrained routes. A newcomer sees offer prices and selected averages. The information gap can become part of the spread. It also weakens member oversight: if policy delays impose costs, no public series connects price or discount to the registry path.

Requiring every exact contract price in the named log would cause serious problems. Consideration may include services, liabilities, tax allocation, clean-up obligations, or a portfolio price. Publishing exact terms could expose strategy, invite collusion, or enable a competitor to identify a party by block and date. A registry may lack legal authority to demand the contract and should not pretend that a declared number is an audited fair value.

The alternative is aggregate price reporting with coverage. Brokers, escrow services, and voluntary parties submit a standard observation: gross monetary consideration, currency, address count, block size class, registry pair, contract period, whether fees are included, whether the deal is bundled, and whether it is an arm's-length permanent sale. An independent collector validates arithmetic errors and duplicates, converts currency by a published method, and releases only sufficiently populated cells.

The public learns the distribution and the sample proportion without learning the price of any named party. Registries remain record keepers. Market entities no longer must accept a private storyteller's sample as the entire market.

Privacy Can Be Protected with Separation, Delay, and Thresholds

The usual choice between precise disclosure and secrecy is false. Statistical systems regularly publish useful distributions without releasing individual records. The IPv4 market is thin enough to require a stricter design, but not so thin that every aggregate is impossible.

The first protection isseparation. The named custody log should contain no aggregate cell identifier. The price publication should use quarter, broad block size class, intra- or inter-RIR path class, and possibly status class. It should not repeat the exact prefix, organisation, transfer timestamp, or broker. A reader should not be able to join one table with the other and isolate a contract.

The second isminimum cell size. No price distribution should be published with fewer than five independent commercial cases, and thin directed pairs may require ten. Independence matters: ten prefixes from one portfolio purchase are one case. If the threshold is not met, combine adjacent periods or block classes. The publication should say data were suppressed, not replace the cell with zero.

The third isdelay. Quarterly figures can be published after sufficient time so that current negotiation strategy is not disclosed. A six-month delay may be justified for very large or unique blocks. The delay should be set in advance, not invoked selectively when prices are politically uncomfortable.

The fourth isdistributioninstead of point disclosure. Publish the median, 25th and 75th percentile, the address-weighted average, minimum and maximum only where they cannot identify an outlier, and the number of cases and addresses represented. A median without sample size is weak. An address-weighted average without a case-weighted median lets a /8 or /12 dominate. Both belong together.

The fifth iscoverage. Report the number and address volume of priced cases as a proportion of recognised arm's-length sales in the same cell. If only 20% of logged addresses have reported prices, the public can see the limit. If brokers represent overlapping cases, deduplication rules and unresolved uncertainty must be disclosed.

The sixth iscontrolled access for audits. A trusted auditor can examine confidential submissions, escrow confirmations, and duplicate detection without publishing contracts. The auditor reports error rates, late corrections, provider concentration, and whether a contributor could dominate a cell. Contributors can challenge misclassifications.

No privacy design is perfect. A unique /8 sale will be visible in the custody log and discussed publicly; its price aggregate may need to remain suppressed. A court filing may disclose a price independently. The standard should protect information it controls, not promise anonymity that public facts contradict.

This approach is more respectful than the current imbalance. Public logs already name source and destination organisations for many completed transfers. It is hard to argue that even a delayed global median is categorically too private while exact counterparties and prefixes are public. The right question is what disclosure is necessary for custody and what aggregate is necessary for accountability.

Delay Needs a Clock for Every Controller

Price tells entities what scarcity costs. Delay tells them what institutional control costs. Existing transfer data only show the end.

A useful clock starts when the registry has a complete request, not when a user first opens an account or asks an informal question. But the period before completeness is also important, because unclear evidence requirements can take weeks. The publication should therefore include two starting points: the initial submission and the submission accepted as complete. The gap measures intake resistance.

From completeness, the case should record phase timestamps: source identity verified; resource eligibility verified; destination identity verified; need or destination eligibility determined; fees issued and paid; agreement issued and signed; counterparty registry notified; counterparty approval received; handover scheduled; record changed; technical condition verified. Not every registry uses the same order, but common milestones can be mapped.

Elapsed time then splits by controller.Registry-controlled timeruns while the department can act.Party-controlled timeruns while buyer or seller owes information, money, or signature.Counterparty-controlled timeruns after a complete bilateral handover.Joint scheduling timeruns while all parties choose a secure handover. A case may switch between states; sums should match calendar duration.

Medians in working days are limited public evidence. Publish calendar days, because deployment and financing continue on weekends. Show the 25th, 50th, 75th, and 90th percentiles and the oldest pending age. Report the fraction that meets a declared service target. Separate intra-RIR from inter-RIR, IPv4 from AS numbers, normal transfer from merger, and standard from enhanced due diligence.

Pending cases are essential. A registry can make completed cases look faster by processing easy requests while difficult cases remain open. At the end of each quarter, publish age bands of pending cases: under 15 days, 15 to 30, 31 to 60, 61 to 90, 91 to 180, and over 180, with protection for small cells. Identify the current controller and the general reason.

Time should also be linked to outcome. A rejection after two days and a withdrawal after six months are different burdens. An approval that takes 120 days can destroy a commercial agreement even if the log eventually shows success. Appeals should have their own clocks and should not prevent the original duration from being visible.

RIPE NCC openly admits that inter-RIR cases require more work and take longer because registries coordinate across time zones and synchronise updates. This is a plausible hypothesis. Stage-level data would show whether the extra time is in necessary handover, duplicate review, or unallocated handover. ARIN says duration can vary because multiple actors are involved. Controller clocks would identify which variation ARIN's members can demand improvement on.

Good time reporting does not punish careful review. It enables an institution to show that a long case waited 80 days on a disputed corporate succession, not in an analyst queue. It also prevents 'complexity' from becoming an explanation that cannot be tested.

Rejections and Withdrawals Are the Missing Denominator

A market cannot be transparent if it only records recognised transfers. Institutional accountability cannot be credible if it only records approvals.

The minimum quarterly reconciliation is simple in form:

pending cases at start + new complete applications + reopened cases = approvals + rejections + withdrawals + expiries + merged or replaced cases + pending cases at end

Each term needs a definition. A rejection is a registry decision that the application does not meet a specified requirement. A withdrawal is a party's decision to stop before a final decision. An expiry is a case administratively closed after notification and a set response period. A merged or replaced case is not a successful outcome; it is an accounting movement that must internally reference the successor case so it is not double-counted.

Reasons should be mutually exclusive at the primary level and allow secondary tags. Primary categories may include: holder identity not established, signing authority not established, active dispute, resource not eligible, holding period, destination identity, demonstrated need, regional connection, counterparty incompatibility, sanctions or legal order, fees or agreement incomplete, duplicate application, technical handover failure, and commercial party withdrawal. 'Other' should be rare, reviewed, and explained in aggregate.

The category describes the decision, not the applicant's character. A lack of need is not fraud. Missing documents are not evidence that the holder had no rights. A withdrawal after a price change is not a registry rejection. Maintaining these distinctions protects parties and improves analysis.

Withdrawals need a limited voluntary reason menu, because they often reveal the institutional impact before a decision. Parties may choose: commercial terms failed, financing failed, counterparty changed, timeline exceeded, policy suitability concerns, technical concerns, or reason withheld. Refusing to answer should remain available. The registry should not infer a reason from correspondence.

Attrition before submission belongs in a separate sample. Listing services, qualified intermediaries, and brokers can report how many inquiries were screened out for reasons of path incompatibility, needs assessment, block reputation, size, price, or seller eligibility. These numbers cannot be added to complete registry applications because the populations overlap. Publish them as surveyed funnel data with contributor count and coverage.

Appeals complete the picture. Report how many rejections were challenged, upheld, overturned, remanded for further review, or still pending, plus time to decision. Suppress thin categories where identity could be derived. A high overturn rate may indicate unclear standards; a zero appeal rate may mean predictable decisions or inaccessible review. The statistic requires context, not celebration.

ARIN's processed ticket chart already shows that institutions can count closings independently of final status. The next step is disclosing the distribution of those statuses in a case-consistent form. LACNIC's policy already requires a completed transfer log. Adding an aggregated decision table does not disclose the legal documents the parties submitted.

The denominator will not answer every fairness question. Brokers may deter weak cases, and sophisticated applicants may submit more complete evidence. It will end the current state where a registry can point to a clean list of successes while the public cannot see whom its rules excluded.

The Minimum Publication Needs Five Linked Panels

A workable standard should be small enough to be published every quarter and rich enough to resist institutional storytelling. Five panels meet this test.

Panel one: Completed custody changes.Retain the existing cumulative transaction log: resource set, source and destination organisations where lawful, source and destination registries, transfer date, general type, and corrections. Add a stable revision note and a data freshness timestamp. This remains the authoritative public history, not a price table.

Panel two: Case outcomes.For each registry, directed inter-RIR pair, resource class, and case type, publish opens at start, new completes, approved, rejected, withdrawn, expired, replaced, and open at end. Give address volume separately from case count. Reconcile the panel arithmetically.

Panel three: Elapsed time.Publish intake time from initial submission to completeness, time from completeness to decision, time from decision to handover, total calendar time, registry-controlled, party-controlled, counterparty-controlled, and jointly controlled days, percentiles, target compliance, and ageing bands of pending cases. Complex cases with enhanced review can be a separate class, but the rule for entering that class must be public.

Panel four: Reasons and review.Publish primary rejection, withdrawal, and pending reasons, categories of missing evidence, appeal filings, outcomes, and time. Link each decision category to the policy clause or operating rule it represents. Show corrections where a classification changed after review.

Panel five: Market aggregates.For permanent arm's-length sales of IPv4 with reportable consideration, publish case and address coverage; block size bands; intra- and inter-RIR classes; currency method; median; quartiles; case-weighted and address-weighted measures; dispersion; broker or direct proportion, where sufficiently populated; and the delay between contract and booking date. Suppress cells below the privacy threshold.

Each panel needs metadata written for readers: reporting period, publisher, retrieval date, definitions, inclusions, exclusions, known gaps, revisions, and contact for corrections. A public cryptographic digest of each publication would make later changes visible. Dated snapshots should remain available.

The panels should not be combined into a composite score. A cheap market can be slow. A fast desk can reject many applicants. A high approval rate can reflect strict broker filters. A rising price can reflect scarcity, block mix, or changing demand, not registry performance. Keeping the dimensions separate forces the conclusion to match the evidence.

Nor should a global total erase pair differences. Inter-RIR friction is directional. Publish ARIN-to-APNIC separately from APNIC-to-ARIN where cell size allows. If privacy requires combination, show which routes were combined and why. A global median dominated by RIPE NCC internal transfers says little about a small operator trying to move space to LACNIC.

The minimum is not technically demanding. Registries already hold case states and data needed to manage requests. Brokers and escrow services already hold transaction amounts for their own cases. The challenge is institutional: agreeing on definitions, maintaining confidentiality, accepting reconciliation, and publishing the failures that make performance less flattering.

Data Quality Needs Revision History, Not Silent Correction

A cumulative file can improve when errors are found, but improvement without revision proof can rewrite the past. Transfer data are especially vulnerable because organisation names change, blocks are split, mergers are reclassified, and historical records are imported from older systems.

Each feed should identify production time, covered interval, and format version, as the NRO design already provides. It should also include a release count by resource and type, a digest of the previous release, and a correction file that indicates which records were added, changed, or removed and why. Personal or security-related reasons can be generic; the fact of the change should not disappear.

Timeliness is part of quality. A file named 'latest' encourages readers to assume current coverage. The five live RIR feeds examined did not have the same latest transfer date. This may reflect different market activity, production schedules, or stale publication. A timeliness panel should distinguish 'no new transfers' from 'file not regenerated' and 'generation failed'. A signed zero-activity statement is data.

Cross-RIR transfers should be reconciled on both sides. The source and destination feeds should match on resource set, transfer date, counterparty, and type. A public reconciliation report can list unmatched records after a grace period without disclosing internal tickets. Differences due to time zones, delayed publication, or format mapping should be classified and resolved.

Names require careful handling. The organisation named in a public registry may be a legal entity, a trading name, a parent, a subsidiary, or a historical holder. A name change should not look like a new sale. Stable public organisation identifiers would improve research, but they must not reveal private account identifiers. The identifier should survive spelling corrections and link to the public RDAP identity where lawful.

Price aggregates have their own revision risks. Late broker submissions can shift a median. Currency conversions can be corrected. A portfolio can be split after an audit. Each publication should preserve the originally published value, the revised value, the reason, the affected cell, and the date. Silent replacement would allow an institution or contributor to smooth an uncomfortable market movement.

Independent validation should sample from each panel. For custody, compare the feed with the public registry state and bilateral counterparties. For cases, reconcile opening and closing balances. For time, recompute sums from event timestamps. For price, verify a confidential sample against escrow or settlement evidence and test duplicate detection. The auditor reports method and error without publishing contracts.

Data quality also limits conclusions. A precisely looking mean from 30% coverage is not a market price. A rejection rate that excludes incomplete captures is not an application rate. A transfer count that mixes mergers and sales is not revenue. The publication should place these warnings next to the number, not in an obscure note.

Trust does not require error-free data. It requires that errors be detectable, correctable, and preserved as part of the record.

Brokers Can Contribute Evidence Without Owning the Market Narrative

Brokers are in an uncomfortable but necessary position. They see offers that never reach registries, negotiate prices, understand block reputation, and learn which institutional paths close reliably. They also compete for deals and can benefit from a particular depiction of supply, demand, and urgency.

Excluding them would discard the best available price and attrition observations. Leaving one broker's series to stand for the entire market would trade public opacity for private concentration. The standard should use multiple contributors and disclose concentration.

Each participating broker can quarterly send signed records to an independent collector. The record identifies a pseudonymous commercial case, block size band, address count, source and destination RIR, contract month, close month, currency, gross consideration, included services, broker fee treatment, escrow status, outcome, and reason if the deal failed. Exact party names and prefixes can be kept confidential for deduplication and audit and then excluded from public aggregates.

Direct deals also need a channel. Buyers, sellers, receivers, and escrow services can submit the same form. If two parties report the same case, the collector reconciles and resolves discrepancies instead of counting both. Contributors receive a receipt and can later correct a fact with an audit trail.

Coverage reporting should name provider concentration only on a safe aggregate. If one broker supplies 80% of priced cases, readers must know that the series largely represents one place. The broker need not disclose its client list. An independent auditor can confirm the proportion.

Listing data should remain separate from completed price. An asking price is not a sale. A bid is not a sale. A broker's valuation is not a sale. A court-approved amount may bundle assets. The public panel can show median ask and bid spreads as separate series if definitions and coverage are clear, but neither should be mixed into realised consideration.

Registries can help without requiring contracts. They can allow parties to opt in to a token to the collector, confirming that a recognised transfer occurred for a pseudonymous case and address count. The token need not contain a price. It allows the collector to distinguish completed recognised transfers from unrecorded operational leases or abandoned deals.

This division respects institutional roles. Brokers provide commercial observations. Escrow services confirm settlement where permitted. Registries confirm custody change. An auditor tests aggregation. Members and operators see coverage and method. No single actor can claim its partial view is the entire market.

The design also leaves room to examine unrecognised movements. Researchers can compare routing, RDAP, and named transfer records, as earlier academic work has done. These conclusions should be labelled as probable and never inserted into the authoritative custody log as proven sale. Market transparency improves when evidence classes remain separate.

NRS Should Publish the Comparison, Not Sell Permission

The Number Resource Society can make this architecture workable if it treats transparency as a ledger service. It need not become a broker, receive ownership documents for every transfer, or persuade registries to delegate approval powers.

Its first role is definitional. NRS can publish the case taxonomy, stage clocks, reason codes, privacy thresholds, currency method, revision rules, and coverage formula under open change control. Every definition should be usable by any RIR, broker, or researcher. Competing implementations should produce the same quarterly reconciliation from the same events.

Its second role is aggregation. NRS can receive signed statistical returns from registries, brokers, escrow services, and parties; deduplicate commercial cases under confidentiality; and publish the five panels. Raw identity evidence can remain with the submitting institution where possible. NRS only needs enough encrypted linkage to test duplicates and check coverage.

Its third role is portability. A buyer or seller should be able to export its own timestamps, submissions, decisions, and correction history in a standardised package. If a registry misclassifies a party delay or loses a document, the party has a verifiable record. Portability reduces dependence on a private ticket history and makes independent verification possible.

Its fourth role is comparative restraint. NRS can note that one registry reports the 90th percentile of processing time while another only publishes an average. It can identify missing rejection denominators and stale publications. It should not score institutions with a single value that rewards selective reporting. Comparison is strongest when it preserves gaps.

The boundary is as important as the service. NRS must not certify a 'fair price', require its report before a registry transfer, direct parties to a preferred broker, or sell faster recognition. It should not infer consent to public price disclosure from membership. Contributors choose defined confidential terms, and aggregates meet a public interest standard independent of sponsorship.

Funding must not determine the narrative. A large broker can pay for data development without controlling definitions or publication timing. A registry can correct an error without vetoing an unfavourable outcome. An operator can challenge its own classified delay without receiving another party's documents. Governance records should disclose funding and conflicts.

This is the positive NRS offer in concrete form: pay for a minimal, comparable ledger; make evidence portable; show where the public record ends; and refuse to turn the information service into a barrier rent. An institution demonstrates legitimacy not by knowing every contract, but by making the boundaries of its knowledge measurable.

If NRS could be replaced by another collector with the same open definitions and signed inputs, the design has succeeded. Transparency should not depend on a new monopoly.

Registries Could Publish the First Accountable Version Now

The full standard requires coordination, but the lack of perfection is no reason to retain the current blind spot. Every RIR can publish a first quarterly statement from data it already controls.

Start with case reconciliation, outcome categories, elapsed time percentiles, and pending age. Do not wait for price. These fields test the transfer desk itself and do not require a registry to enter commercial negotiations. Publish definitions, exclusions, and a one-year lookback where reliable. Where historical event timestamps are incomplete, say so and start prospectively.

Next, reconcile directed inter-RIR cases. Each pair can reconcile completed and pending cases, handover time, and unmatched records. The institutions already communicate to change custody. A public aggregate reconciliation should be less sensitive than the documents exchanged in the case.

Third, add a voluntary confidential price pilot with at least three independent brokers, direct party access, and an auditor. Release only cells that reach the threshold, and publish coverage. A pilot result with 25% coverage is more useful than an unsupported claim of the global price, provided the limitation is clear.

Fourth, establish correction and appeal reporting. Each quarterly publication should list changes to earlier periods. Each decision reason should be mapped to a current policy clause. Members can then see whether a policy causes recurring confusion or reversals.

Fifth, commission an external data quality audit after four quarters. The auditor should test case counts, bilateral duplicates, pause attribution, privacy leaks, and price concentration. Recommendations and management responses should be public.

The first publication will look less polished than today's success log because it will include gaps, pending cases, and suppressed cells. That is a sign of improved honesty. A mature institution does not need every chart to flatter it.

Members should insist on publication because they fund the transfer desks and live under the rules. Buyers and sellers should support it because predictability reduces closing risk. Brokers should support it because a trusted aggregate can expand participation while distinguishing credible contributors from unsupported advertising. Operators should support it because accurate custody and timely technical handover affect routing security.

Price is not the only missing field, and it should not delay the rest. A market can become more accountable before it is fully priced. But the ultimate goal must include price coverage. Otherwise, institutions will know which resources moved while only private repeat players know what access cost.

The immediate test is modest: can each registry state for the last quarter how many complete cases it opened, approved, rejected, lost, carried forward, and how long each stage took? If the answer is no, a list of completed blocks cannot reasonably be called transparent market oversight.

A Transparent Market Records the Invisible Queue

The transfer log should be defended for what it does. It preserves a public history of recognised changes, supports routing and provenance research, and gives counterparties a way to verify that the ledger no longer names the old holder. Removing names or reducing file accessibility would not create privacy-respecting accountability. It would destroy useful evidence.

The reform is additive. Keep the custody record. Add a statistically protected report on the market and the institution.

This second report must include the invisible queue: complete requests waiting for processing, cases paused for parties, bilateral handovers, rejections, withdrawals, appeals, and inquiries screened out before submission. It must show the price sample and its limits. It must distinguish a commercial case from a ticket, a prefix line from a deal, a merger from a sale, and a transfer date from a contract date.

These distinctions prevent simple claims. A rising transfer count is not evidence of greater access. A high approval rate is not evidence of fairness if brokers prescreen most applicants. A low median is not evidence of speed if old cases are still pending. A private broker average is not the global price if coverage is unknown. A precise price is not comparable if it bundles services or comes from a different block class.

The minimal public fields are therefore not administrative decoration. They define what members can know about power exercised in their name. A registry that can reject a transfer, request more evidence, or coordinate a delayed handover should be able to report how often, why, and how long, even if individual documents remain confidential.

Price aggregation completes the accountability boundary. It does not ask the registry to endorse commodification or set a rate. It shows the economic environment in which registry decisions operate. If a policy closes a path, extends escrow, or favours buyers who can document conventional demand, price and delay data can reveal incidence. Without them, distributional effects remain anecdotal.

NRS points to a better institutional form because it can connect these observations without owning the underlying rights. A minimal ledger service authenticates records, preserves portability, and publishes comparable evidence. It does not decide whether an address is worth USD 20 or whether a buyer's business plan deserves approval. It makes these separate claims visible.

The public transfer line is the end of a story. Market transparency begins with recording all the cases that did not reach it.

Sources