ARIN and the economics of liquidity discount

Summary

• ARIN-region IPv4 liquidity is not the same as headline price, escrow safety or title confidence; it is the practical ability to convert a block into cash, completed transfer, usable capacity or financeable value.
• Time-to-transfer, recipient eligibility, block size, fragmentation, inter-RIR compatibility, agreement status, dispute status and operational cleanup can make two nominally similar blocks trade at different values.
• ARIN should be read as a registry ledger, not a market maker: its public materials are factual exhibits on where liquidity is made or lost, not conclusions about commercial value.
• The policy objective is not to abolish all discounts, but to ensure that discounts reflect real risk, buyer depth and cleanup cost rather than avoidable opacity in the transfer path.

Two similar blocks, two different economic objects

A CFO presenting two IPv4 blocks to a board can be forgiven for asking why the market does not treat them alike. Each block may contain the same number of addresses. Each may be capable of announcement on the global Internet if routing arrangements are made correctly. On a spreadsheet prepared for an acquisition committee, they may sit in adjacent rows: one /20 here, another /20 there, both part of the same problem of keeping products, customers and legacy systems online while IPv6 remains a slow transition rather than a clean substitution.

The first block is registered to a current operating company. Its points of contact are alive and responsive. The holder has a current agreement with the registry, a clean board authority file, no known dispute, no awkward prior transfer restriction, no obvious route-security residue, and a buyer pool that includes in-region operators as well as some inter-regional candidates. The seller can move quickly. The buyer can qualify without heroic documentation. Reverse DNS and routing records are easy to clear. The block can become cash for the seller, usable capacity for the buyer, or collateral support for a lender in a reasonably short period.

The second block is not broken in the engineering sense. It is still numerically valid. It may even be routed today. But its registered organization has changed names twice and one predecessor was dissolved. A former business unit used part of the block, but no one is certain whether the relevant asset sale included it. The contacts include a retired engineer and a shared mailbox that only partly works. The holder is not sure which agreement, if any, covers the resource. A lawyer wants old corporate filings. A prospective buyer asks whether the block can move under current policy and whether the requested size is eligible. Another buyer would be in a different registry region, so compatibility and receiving-side validation become relevant. Network staff find stale route objects, old reverse DNS delegations and a reputation trail that may make hosting platforms cautious. A bank asks how long liquidation would take if the borrower defaults.

Both blocks are technically usable. The market will not price them the same. The discount on the second block is not mainly a mystery of price transparency, although weak comparables can widen the bargaining range. It is not mainly a title-insurance problem, although chain defects can matter. It is not mainly an escrow problem, although closing is not instantaneous. It is a liquidity problem. Liquidity is the ability to convert a resource into cash, a completed transfer, productive capacity or financeable value with speed, certainty, low transaction cost and a deep set of willing counterparties. A block with a broad buyer universe, predictable registry path and low cleanup burden is more liquid than a block whose conversion path is narrow, slow and uncertain. The value difference is a liquidity discount.

That discount is central to the economics of ARIN-region IPv4. ARIN is not a market maker and should not become one. It should not tell parties what a block is worth, guarantee every buyer's use case, or insure private bargains. But ARIN's registry function affects liquidity because the market cannot convert a private bargain into a durable network fact without registry recognition and a coherent record. The public ledger is the bridge between an engineering identifier and an economic asset. When the bridge is predictable, the market prices scarcity, quality and risk. When the bridge becomes uncertain, the market prices time, delay, adverse selection and optionality loss.

Liquidity is not the same as price

The usual conversation about IPv4 scarcity begins with price per address. That is natural because scarcity needs a number. Boards, auditors, sellers, buyers and lenders want a benchmark, and public transfer logs do not show the consideration paid. But a price is only the result of a transaction that managed to clear. Liquidity asks a prior question: how hard was it to clear at all?

A liquid asset can be sold quickly into a broad market without taking a large discount. A less liquid asset may have real value but require time, specialist search, concessions, evidence work, legal review or technical remediation before a buyer will close. A house in a functioning market is more liquid than an otherwise similar house with unresolved boundary claims. A bond traded by many dealers is more liquid than a bespoke loan that must be negotiated creditor by creditor. A data-centre cabinet with standard power, access and contract terms is more liquid than one that can be used only after landlord approvals and rewiring. IPv4 blocks follow the same economic logic, even though the underlying resource is a coordination identifier rather than ordinary property.

The elements of IPv4 liquidity are easy to list and difficult to maintain. First is speed: how long from decision to sale, transfer or productive deployment? Second is certainty: how likely is the transfer to complete without a late evidence problem, policy mismatch or dispute freeze? Third is buyer depth: how many qualified buyers can realistically use and receive the block? Fourth is transaction cost: how much legal, registry, technical and intermediary work is needed? Fifth is financeability: can a lender, auditor or board treat the resource as recoverable value if plans change? Sixth is operational convertibility: can the new holder route, secure, delegate and reputationally clean the block quickly enough that the registry record becomes useful service capacity?

The market's discount attaches to the weak answers. A seller may say that its /20 is numerically identical to another seller's /20. A buyer will answer that it is not identical if the purchase requires three months of corporate reconstruction, a narrower recipient universe, old route cleanup and uncertainty about whether a cross-region recipient can qualify. A lender will answer that it is not identical if forced-sale timing could vary from weeks to many months. A board will answer that it is not identical if the resource cannot be financed, disposed of or integrated with predictable risk.

This is why price opacity cannot be the whole story. A buyer might lack perfect comparables but still know that a messy block should be cheaper than a clean one. Conversely, perfect publication of past prices would not make an encumbered block liquid. It would only help the parties estimate how much of a discount the market has previously applied to comparable friction. The friction itself remains.

Nor is liquidity the same as legal confidence in the narrow sense. A strong chain of authority improves liquidity because more buyers are willing to participate and fewer conditions are needed. Yet an immaculate authority file is not enough if the block is fragmented into sizes the buyer does not want, trapped by recipient-size policy, burdened by reputation residue, or hard to move across registries. Liquidity is broader than confidence in who may sign. It includes the size and shape of demand, the public rules for transfer, the operational afterlife of the numbers and the time value of waiting.

Nor is liquidity the same as settlement safety. Escrow can protect money while a transfer is pending, and staged conditions can reduce bilateral risk. But escrow does not create buyer depth. It does not make a /23 attractive to a buyer that needs a contiguous /20. It does not remove a dispute flag. It does not make ARIN and another registry share compatible policies. It does not clean reverse DNS or reputation records. Settlement helps a deal close. Liquidity determines how many plausible deals exist and how costly it is to reach the closing point.

The discount is therefore not irrational. It is the market's shorthand for a bundle of delays and uncertainties. The more friction between "I have addresses" and "I can turn them into cash or usable capacity," the larger the discount. The market may express that discount as a lower price, a longer option period, a larger holdback, more warranties, narrower buyer interest, tougher financing terms or an outright refusal to bid. Each expression says the same thing: nominally usable IPv4 is not automatically liquid capital.

ARIN's ledger converts private scarcity into public usability

ARIN's public materials provide the factual background. Its Number Resource Policy Manual states that number resources are not transferable unless ARIN has expressly and in writing approved a transfer request, and that resources are administered through published policies rather than treated as ordinary sold goods. Its transfer guidance distinguishes merger, acquisition and reorganization transfers from specified-recipient transfers within the ARIN region and inter-RIR transfers to or from other regions with compatible needs-based policies. Its public transfer page describes separate source and recipient requests, agreements, fees and completion steps. These details are not the conclusion of the economic analysis; they are exhibits showing where liquidity is made or lost.

The institutional point is that ARIN operates the ledger on which the private market depends. A private contract can allocate risk between buyer and seller. It can say what price is payable, who signs, what happens if approval fails, who removes old records and who bears cleanup costs. But the contract cannot by itself make the registry record move. The market's conversion event is public recognition in the registry, followed by operational controls that allow the new holder to use the resource. Without that public state, the buyer has a promise, not the full object of the bargain.

This does not make ARIN a market supervisor. The distinction between ledger and gatekeeper matters. A ledger keeps public uniqueness coordinated, records recognized holders, supports contactability, enables reverse DNS and routing-security services, and makes changes auditable. A gatekeeper, in the stronger sense, decides which commercial uses deserve approval, which buyers should be favored, or what economic outcome is socially preferred. ARIN necessarily performs some approval functions because false, disputed or policy-ineligible transfers would damage the ledger. But the more scarce and valuable IPv4 becomes, the more costly it is if approval logic drifts from necessary ledger protection into avoidable market friction.

Liquidity improves when the registry's role is predictable and bounded. Predictable means parties can know early which evidence matters, which policy path applies, which agreements are needed, which services follow the resource, and which conditions will stop a transfer. Bounded means the registry does not turn every private risk into a reason for discretionary control. It checks holder status, authority, dispute status, recipient eligibility, agreement status and policy compatibility because those are registry facts. It does not become a price referee, a lender, a reputation court or a broker of last resort.

This boundary is not merely philosophical. It affects capital value. If parties believe that a clean file will be processed under known standards, they will price the block according to scarcity, size, quality and ordinary execution time. If parties believe that approval may depend on shifting interpretations, opaque institutional preference or an uncertain view of the buyer's business model, they will price an additional risk premium. That premium is a tax on liquidity.

ARIN's own sequence illustrates the difference. The public guidance says that once ARIN receives a signed Registration Services Agreement and all applicable fees, resources will be transferred within two business days. That statement is useful because it identifies a late-stage timing expectation after the file has cleared prior requirements. But the market's liquidity problem often occurs before that point: obtaining authority evidence, satisfying recipient qualification, resolving old contacts, determining whether the source is restricted, aligning two parties' tickets, and handling inter-regional compatibility. The final two-business-day step is not the whole transfer. The liquidity discount is priced over the entire path from potential sale to durable use.

The same is true of transfer pre-approval. ARIN offers recipient pre-approval based on projected 24-month need, with approval valid for two years and not subject to re-verification for a qualifying transfer submitted within that period. This can deepen the buyer pool because a pre-approved buyer is less risky for a seller. It reduces one uncertainty but does not eliminate all others. The seller still must be eligible. The block still must be transfer-ready. The technical and reputation tail still must be managed. Liquidity is improved by modular certainty: the more each part of the sequence can be known in advance, the smaller the discount.

Time-to-transfer is an asset characteristic

Markets often treat time as an inconvenience rather than a value driver. For IPv4, time is part of the asset. A block that can move in a month and become usable shortly afterward is not the same economic object as a block that may take a quarter to prepare, another quarter to approve and an uncertain period to clean operationally. The addresses are identical on a binary level. The option they give the buyer is not.

Time-to-transfer affects the seller first. If the seller wants cash to fund a restructuring, return capital, simplify a divestiture or close a fiscal-year transaction, each month of delay has a cost. The seller may pay that cost through a lower price, a larger exclusivity concession, a longer period during which the buyer can walk away, or the lost opportunity to sell to a different buyer. The seller may also face internal fatigue. A sale that requires legal, finance, network and executive attention for months can lose sponsorship. A resource that looked like trapped capital can become a nuisance that management would rather discount than manage.

Time affects the buyer differently. A buyer acquiring addresses for a service launch, migration, customer expansion or data-centre build cares about the date at which the block becomes productive. A delayed transfer can force temporary leasing, more network translation, renumbering, customer deferral or capacity constraints. The buyer may pay a premium for speed because the cost of waiting exceeds the price premium. Conversely, it may demand a discount for a slow block because the addresses do not solve the immediate problem. Liquidity is therefore use-case specific: the same delayed block may be acceptable to a patient consolidator and unattractive to an urgent operator.

Time also affects financing. A lender does not ask only whether the collateral can eventually be sold. It asks how long enforcement would take. If a borrower defaults, the lender may not have the operating staff, historical knowledge or registry account access that the borrower had. It may need a receiver, corporate authorizations, account recovery, transfer preparation and buyer search before any cash is realized. A block with uncertain transfer timing receives a haircut because the lender must fund the waiting period and bear execution risk. A clean block shortens the recovery period and supports a higher valuation.

The same logic applies to internal capital allocation. A board comparing IPv4 purchase, IPv6 acceleration, network translation, cloud redesign and customer segmentation is not choosing between static costs. It is choosing between dated options. IPv4 acquired quickly may preserve revenue or defer a more disruptive migration. IPv4 acquired slowly may arrive after the relevant business need has changed. A block that is cheap but slow can be more expensive than a block that is costly but immediately convertible.

This is why a transfer-ready file has value before the first buyer appears. Current contacts, documented authority, known agreement status, clean route-security state, reverse-DNS control, reputation notes and clarity about recipient eligibility reduce the variance of closing time. They are not merely compliance artifacts. They are investments in liquidity. The market rewards them because they make the resource closer to cash and closer to usable capacity.

Time-to-transfer also disciplines policy. If a rule prevents a bad transfer, its timing cost may be justified. If a rule only creates serial uncertainty, late questions or avoidable repetition, it becomes a liquidity tax. The distinction should be explicit. A registry can impose evidence requirements while still caring about predictable sequencing. Parties can accept a demanding standard if they know the order in which it will be applied. They price the standard harshly when the order is uncertain.

Eligibility filters shrink the buyer universe

The most direct way registry policy affects liquidity is by determining who can receive a block, when, and in what size. A resource with many qualified buyers is more liquid than a resource that can be sold only to a narrow set of recipients. In thin markets, the difference can be large. Buyer depth is not a moral judgment; it is an asset-pricing variable.

ARIN's specified-recipient framework includes several filters. For transfers within the ARIN region, the source must be the current registered holder, must not be involved in a dispute over the resources, must satisfy timing and reserved-pool restrictions, and must accept wait-list consequences after transferring IPv4 resources. The recipient must meet the transfer requirements in Section 8.5, and the transferred resources become subject to current ARIN policies. The minimum IPv4 transfer size is a /24. For larger blocks, recipient qualification turns on projected operational use, efficient utilization and other size limits. A recipient without an IPv4 allocation qualifies for the minimum size; a recipient seeking more must document use of at least half the requested addresses within 24 months, and holders seeking additional space must satisfy efficient-utilization criteria or an alternative 80% utilization path capped by policy.

These filters may have defensible purposes. They reduce warehousing, maintain the needs-based tradition, preserve registry discipline and prevent transfer rules from becoming a pure auction for any speculative buyer. But every filter also has a liquidity cost. A seller of a large block cannot treat every interested party as an executable buyer. Some buyers may want the space but fail projected-need documentation. Some may be too new to satisfy internal or registry requirements beyond the minimum. Some may prefer to acquire for future optionality rather than near-term operational use. Some may be outside the region and subject to another registry's policy. Some may be on the wait list and face consequences. The seller's theoretical market is larger than the executable market.

The liquidity effect is strongest for unusual sizes and urgent schedules. A seller with a clean /24 may find a larger universe because the minimum-size path is more accessible. A seller with a /16 equivalent faces a smaller universe because buyers must justify a much larger operational need or fit the alternative criteria. Large buyers exist, but they are fewer, more sophisticated and more able to bargain. They also know that the seller cannot simply sell the whole block to every potential participant. The seller's headline value may be large while its buyer universe is narrow. That is classic illiquidity.

Fragmentation adds another layer. A seller may split a larger block into smaller pieces to reach more buyers, reduce qualification burden or accelerate sales. But splitting has costs. Smaller pieces can lose aggregation value. More transfers mean more tickets, fees, documents, coordination and operational cleanup. Buyers may discount fragments if they increase routing table entries, complicate internal addressing, or fail to match planned deployment sizes. Conversely, a contiguous large block may command strategic value to a buyer that can qualify, while carrying a discount because the number of qualifying buyers is small. There is no single liquidity rule; the market prices the interaction between size, buyer depth and transaction cost.

Transfer restrictions on recent receipt also affect liquidity. If a source has received a transfer, allocation or assignment within the relevant prior period, it may be restricted from transferring under specified paths, subject to exceptions. Such rules limit flipping and protect policy integrity. They also reduce optionality. A holder who cannot resell immediately holds a less liquid asset during the restriction window. A buyer acquiring space today must consider whether future resale would be constrained. A lender must consider whether enforcement after default could be delayed by such restrictions. The value of an address block includes not only current use but exit optionality.

The needs-based system also creates a distributional effect. Sophisticated buyers can prepare documentation, model 24-month demand, maintain utilization records and obtain pre-approval. Smaller operators may have real need but fewer administrative resources. A small buyer facing the same fixed diligence cost as a larger buyer has a higher cost per address. That cost does not always appear as a lower nominal price; it can appear as not bidding, buying a smaller block, accepting inferior terms or relying on costly assistance. Liquidity is thinner where compliance cost is high relative to deal size.

None of this proves that eligibility filters should be abolished. A registry that ignores eligibility can damage the trust that makes transfers possible. The point is more precise: every eligibility rule should be understood as both a policy control and a market-depth variable. If the control is necessary, the liquidity cost may be justified. If the control is unclear, duplicative or poorly signaled, the discount is unnecessary. The goal should be to reduce avoidable illiquidity while preserving the rules that protect the ledger.

Agreement status and legacy boundaries as liquidity variables

ARIN's legacy-resource framework is a particularly clear example of how service boundaries become market variables. Legacy resources have a long institutional history. ARIN's public legacy page describes early allocations that predate modern registry agreements and the formation of ARIN in 1997. It also states that legacy holders not under an ARIN agreement can maintain unique registration in Whois/RDAP, update public data, manage reverse DNS delegations, maintain registry records through ARIN Online, and access DNSSEC; but RPKI and IRR access require an ARIN agreement. The legacy fee cap for older Legacy Registration Services Agreements expired on December 31 2023, with fee treatment changing for later-covered resources.

This is not just account administration. It affects liquidity. A buyer or lender does not look only at whether a legacy block can be routed today. It asks what services are available now, what services become available after an agreement, what fees apply, what obligations follow the resource, and whether the transfer itself will require the recipient to sign or update an agreement. A block under a current agreement with clean service access is easier to evaluate than a block outside agreement boundaries where the buyer must price legal and operational changes after closing.

RPKI and IRR access matter because operational acceptance increasingly depends on machine-readable routing confidence. ARIN's RPKI material explains that resource certificates allow holders to make cryptographically signed statements about which ASNs should originate prefixes, and that network operators can compare BGP announcements with RPKI validity data. ARIN's IRR material explains that routing registries publish routing policy information used by networks and aggregators. These services are not mere ornaments. They reduce downstream uncertainty. A block whose holder cannot use them until agreement status changes carries an integration cost for a buyer planning to secure and announce the space.

Reverse DNS matters too. ARIN's reverse DNS page describes the use of PTR records and the need for holders to maintain them. It also explains management of delegations and the role of shared authority in some reassignment settings. A buyer acquiring a block with clear reverse DNS control faces less operational residue than one inheriting old delegations, shared authority, stale customer reassignments or unclear nameserver control. Again, the addresses may be technically valid. The liquidity question is how quickly the buyer can turn validity into dependable service.

Agreement status also affects the seller's internal preparation. A holder that has kept records current, validated contacts, maintained a clear officer file and understood its service perimeter can market the resource as lower friction. A holder that discovers during sale preparation that contacts are stale, the relevant organization must be recovered, or agreement coverage is unclear will either delay the transaction or accept a discount. The discount compensates the buyer for uncertainty and the seller for time lost only if the seller can wait. If the seller is distressed, the discount can be severe.

The legacy boundary also shows why liquidity cannot be reduced to title chain alone. A legacy holder may have strong historical continuity and still face lower liquidity because certain services require an agreement and the buyer must model the transition. Conversely, a holder may have current agreement coverage but a messy corporate history. Both conditions can produce discounts through different channels. One concerns service convertibility; the other concerns authority confidence. Liquidity bundles them.

Boards and lenders translate these distinctions into haircuts. If the block is under current agreement, records are current, RPKI and IRR state can be cleaned, and reverse DNS is controlled, a lender may assume a shorter enforcement sale. If the block sits outside current service boundaries, the lender will ask whether a receiver, buyer or secured party can obtain the necessary registry cooperation quickly. Even if the legal answer is favorable, uncertainty in timing reduces advance value. A credit committee does not need to decide the philosophical character of number resources. It only needs to decide how much cash it could recover and how fast.

The efficient policy response is clarity, not market planning. ARIN should describe service boundaries, agreement effects and transfer consequences in language that a non-specialist board can understand without turning the registry into a financial adviser. The market can then price real differences rather than fear unknown ones. A predictable agreement boundary may still produce different values, but it will produce smaller unnecessary discounts.

Inter-RIR compatibility and cross-border friction

Liquidity changes again when the buyer or seller sits outside the ARIN region. ARIN's policy allows inter-regional transfers only through RIRs that agree to the transfer and share reciprocal, compatible needs-based policies. ARIN's current public transfer guidance identifies APNIC, LACNIC and RIPE NCC as approved for compatible transfers and AFRINIC as not approved for transfers with ARIN under that compatibility table. It also notes that inter-RIR transfers cannot include IPv6 addresses in ARIN's process and that timing can vary because multiple RIRs and organizations are involved.

The economic implication is simple: an ARIN-administered block that can be sold to in-region buyers and to compatible-region buyers has a deeper market than a block whose likely buyer pool is in a region not compatible for transfer, or whose intended transfer direction requires additional validation. Cross-region demand can support price by increasing buyer depth. Cross-region complexity can reduce liquidity by adding time, documentation and failure risk. Both effects operate at once.

Compatibility rules matter because they define executable demand. A foreign buyer may value a block highly for its network, customers or market position. If the receiving registry cannot participate under compatible policy, that demand is not executable as a clean registry transfer. The seller can still look for other buyers, leasing structures or corporate alternatives, but the straightforward sale path narrows. A buyer that cannot receive the block under its registry's rules is not part of the same liquid buyer universe as a buyer with a pre-approved, compatible path.

Even where compatibility exists, institutional distance imposes cost. The source side must satisfy its registry's conditions. The recipient side must satisfy the receiving registry's conditions. ARIN may require certification or validation that compatible needs-based policy has been met. Records may move out of ARIN's Whois service and be replaced by a placeholder pointing to the new RIR. The receiving registry's publication, agreement, routing-security and reverse-DNS arrangements may differ. A transaction that looks bilateral becomes a coordinated change across two ledgers.

The discount here is not merely legal. It is also time value. A seller with several possible buyers will prefer a buyer whose transfer path is more predictable, unless the less predictable buyer pays enough to compensate. A buyer that expects a long cross-registry sequence may insist on exclusivity, a lower deposit, a longer outside date or a price discount. A lender financing the buyer may require a larger reserve because the block cannot be treated as usable until both registry states and operational services align. The same numerical addresses therefore have different economic value depending on the path they must travel.

Cross-border corporate and payment friction compounds the registry problem. A buyer or seller may face beneficial-ownership review, sanctions screening, tax analysis, currency movement, payment custody questions or local corporate approvals. These are not ARIN policy questions in the narrow sense. Yet they affect liquidity because they add counterparties, documents and failure points. A seller can prefer a domestic or in-region buyer not because the block is more useful there, but because the conversion into cash is more certain.

This is where registry predictability has its highest leverage. ARIN need not solve every cross-border private-law problem. It can, however, make clear which RIRs are compatible, what validation is required, what record changes occur when resources move, and which services will or will not follow. A seller can then separate registry uncertainty from banking uncertainty, and a buyer can price each layer. Illiquidity grows when those layers are confused. If a delay might be due to ARIN, another RIR, escrow, banking review, corporate evidence or technical cleanup, every participant demands a wider cushion.

Inter-RIR compatibility also creates option value. A holder of a clean ARIN block with broad cross-region eligibility owns a more valuable option than a holder of a similar block whose plausible demand is trapped in fewer regions. The option may never be exercised, but it supports bargaining power. A buyer knows the seller has alternatives. A lender knows sale recovery could reach more markets. A board knows waiting may reveal more bidders. Conversely, a block with limited compatible demand is less liquid even if it can be routed anywhere after deployment.

Operational cleanup is part of convertibility

The most common mistake in valuing IPv4 liquidity is to stop at the registry record. A completed registry transfer is central, but it is not the end of convertibility. The buyer still must turn the record into reliable operation. That means RPKI state, IRR objects, reverse DNS, provider filters, geolocation systems, abuse contacts, customer allowlists, email reputation, platform onboarding and internal addressing plans. Some of these are under ARIN's services. Some are controlled by other networks or private databases. All can affect value.

ARIN's transfer guidance includes a source pre-transfer checklist for specified-recipient and inter-RIR transfers: edit or delete transferring prefixes from source ROAs, review maxLength values, update or remove IRR objects that no longer apply, coordinate reverse DNS delegation, and make sure the recipient understands its responsibility for creating its own RPKI objects, IRR records and reverse-DNS state after transfer. This is an operational guide, but it has asset-pricing consequences. A block requiring little cleanup is more liquid than a block whose buyer must spend weeks proving to upstreams, validators, mail systems and customers that the holder has changed.

RPKI can create a very concrete form of friction. If a seller's old ROA authorizes a different origin ASN, the buyer's announcement may be invalid under route-origin validation until the old state is corrected and new authorizations are created. If maxLength values were set for a prior routing plan, the buyer may need to adjust its planned announcements. If the buyer is acquiring only part of a larger block, route-security design can become more complex. These facts do not make the addresses unusable. They make usability slower and riskier.

IRR residue is similar. Many networks and filtering systems still use routing registry data. Old route objects can point to the wrong origin or confuse automated filters. Some objects may sit in ARIN's IRR; others may sit in third-party registries. A buyer may not control all stale objects. The more cleanup requires cooperation by a seller, predecessor, provider or third party, the less immediate the block's operational liquidity. A seller that prepares by removing or updating stale objects before marketing the block reduces the discount.

Reverse DNS can be deceptively sticky. Old delegations may point to nameservers controlled by the source, predecessor, customer or provider. Shared-authority arrangements can leave delegated parties with control that must be removed when customers disconnect or assignments change. Mail platforms and security systems often look at reverse DNS as one indicator of legitimacy. A buyer using the block for hosting, mail-related infrastructure, access networks or customer services may care deeply about the transition. A buyer using the block in a narrower internal context may care less. The same block's liquidity can therefore vary by buyer use case.

Reputation residue is harder to observe and harder to cure. A block may have appeared on blocklists, been used by compromised hosts, been associated with spam, hosted abusive services, carried suspicious proxy traffic, or simply been geolocated incorrectly for years. Some reputation memories are public. Some are private. Some update quickly. Some lag long after registry records change. ARIN cannot and should not certify that every private reputation system will treat a transferred block kindly. But market participants price the risk because the buyer's intended use depends on external acceptance.

This creates a useful incentive. Sellers can increase liquidity by cleaning before sale: update contacts, remove stale ROAs, audit IRR objects, plan reverse DNS, document prior announcements, check public reputation lists, disclose known issues and separate the parts they control from the parts the buyer must handle. Buyers can reduce surprises by checking intended upstreams, platforms, mail systems and customer dependencies before closing. The registry can support this by educating parties and keeping its own services clear. It need not guarantee downstream acceptance.

Operational cleanup is where running networks provide evidence but not complete comfort. If a block is being routed today by the current holder, that proves practical control and use. It does not prove that the buyer's new origin will be accepted, that old ROAs are harmless, that third-party IRR objects are correct, or that reputation will transfer cleanly. Conversely, a dormant block with no current traffic may avoid some reputation risk but require more onboarding work. Liquidity depends on the intended conversion path, not only on current routeability.

The broader institutional lesson is that public uniqueness coordination does not end at a line in Whois/RDAP. RDAP tells the world who the recognized holder is and how to find relevant information. RPKI, IRR and reverse DNS connect that recognition to routing and service practice. Reputation systems and provider filters add private acceptance layers. The more smoothly those layers can be aligned, the smaller the liquidity discount. The addresses are the same; the conversion cost is not.

Disputes, adverse claims and freezes

A disputed resource is the least liquid form of otherwise useful IPv4. ARIN policy and transfer guidance repeatedly make dispute status a stopping condition. For specified-recipient transfers within the region, the source must not be involved in a dispute as to the status of the resources. For inter-RIR transfers, the recognized source must likewise not be involved in a dispute over the status of the resources. For merger and reorganization transfers, the current registrant must not be involved in such a dispute. The rule is not decorative. It prevents the registry from turning an unresolved claim into a marketable fact.

From the market's perspective, a dispute flag is a liquidity freeze. It does not necessarily mean the resource has no value. It means the value cannot be converted predictably. A buyer does not want to pay for a block that may be claimed by another party. A seller cannot create cash value if it cannot deliver a clean transfer request. A lender cannot rely on forced sale if enforcement would first require resolving adverse claims. A board cannot treat the block as fully monetizable if a claim could interrupt disposition.

The discount can appear before a formal dispute. If a buyer's diligence uncovers a possible successor, a missing asset schedule, an old bankruptcy, a dissolved predecessor, a former affiliate still using the space, or a creditor claim, the buyer may treat the block as functionally less liquid. The seller may object that no formal challenge has been filed. The buyer will answer that the point is not adjudicated ownership but conversion risk. If the possible claim delays transfer, requires warranties, expands indemnities or scares away other buyers, it reduces liquidity.

Litigation risk has a time dimension. A court order, receivership, bankruptcy stay or corporate injunction can make a block temporarily unsaleable even if the eventual outcome is clear. A seller in a restructuring may have authority to sell only after a hearing. A secured creditor may need to release proceeds. A trustee may require notice. A counterparty may challenge a prior transfer. ARIN should not become the court for these private rights, but it cannot ignore them when asked to update the registry. The market prices that institutional pause.

There is also a behavioral effect. Buyers avoid blocks with public controversy because the cost is not limited to legal fees. A contested block can attract operational complaints, public relations risk, due-diligence delay and lender skepticism. Even if a buyer wins, the delay may miss a deployment window. In liquidity terms, the option to acquire that block is less valuable than the option to acquire a block that can close quietly. Time-to-cash matters as much as ultimate correctness.

This explains why dispute-containment design is so important. A registry should not move disputed resources as if no claim existed, because doing so would externalize risk onto future buyers and the routing community. But it should also avoid making every vague allegation an indefinite freeze. Market liquidity requires a path: identify the dispute category, preserve stable services where possible, require credible evidence, respect court processes, and restore transferability when the issue is resolved. The difference between a disciplined freeze and an open-ended freeze is economically large.

For sellers, the lesson is preparation. Clean corporate records, current contacts, clear succession files, documented authority and early resolution of old claims improve liquidity before the sale process begins. For buyers, the lesson is not to treat a discount as a bargain unless the reason is understood. A cheap disputed block may be cheap because the buyer's capital will be trapped. For lenders, the lesson is conservative: if enforcement requires first untangling adverse claims, the advance rate should fall. The resource may have high ultimate value and low immediate liquidity.

This is also where mandate expansion becomes tempting. Scarcity invites institutions to treat every dispute as proof that broader control is needed. That would be a mistake. The registry's legitimate role is to protect the ledger from unsupported change and preserve operational continuity, not to absorb every private contest into discretionary governance. Overreach creates its own liquidity discount because market participants fear that registry process itself will become an unpredictable claimant. The better rule is narrower: stop bad or contested changes, name the reason where possible, keep stable services coherent, and restore ordinary transferability when evidence or competent legal authority permits.

Financing haircuts and boardroom arithmetic

Liquidity discounts become most visible when IPv4 is treated as financeable value. A company may want to borrow against a portfolio of addresses, include address value in an acquisition model, support a purchase price allocation, reassure auditors, or satisfy a board that idle resources can be monetized. At that point the question is not only "What are addresses worth in today's market?" It is "How much of that value can be recovered under stress, on a timetable, by a party that may not be the current network operator?"

Lenders do not value collateral at best-case market price. They apply haircuts for volatility, legal uncertainty, enforcement cost, sale time, buyer depth and operational risk. An IPv4 block with clean records, current agreement status, no dispute, documented authority, low cleanup burden, broad transfer eligibility and a plausible pool of qualified buyers might support a higher advance rate. A block with stale contacts, uncertain chain, inter-RIR limits, reputation residue or size mismatch supports a lower one. The discount is not a statement that the block cannot be used. It is a statement that forced conversion is uncertain.

Boards perform a similar calculation, though often less formally. Suppose management proposes to hold unused IPv4 because prices may rise. Waiting has option value. The board must compare that option against the cost of carrying, record maintenance, security obligations, reputational exposure, possible fee changes, and the risk that future transferability will be harder than today's. A clean, liquid block makes waiting more attractive because the option can be exercised later. A messy block makes waiting riskier because liquidity may deteriorate or require cleanup at the worst time. If sale preparation takes six months, the option is not as valuable as it appears.

The option value of waiting also affects sellers' bargaining behavior. A large incumbent with a strong balance sheet can wait for a better buyer, invest in cleanup, split blocks intelligently and negotiate from strength. A small or distressed seller cannot. Its discount may reflect not only the block's objective quality but the seller's inability to wait through the registry and operational sequence. Liquidity therefore redistributes advantage toward holders with time, documentation and professional support.

Buyers face their own option arithmetic. A buyer that needs addresses for a specific launch date may pay a premium for a clean block because delay is costly. The same buyer may demand a discount for a messy block because the block's uncertainty threatens the launch. A buyer with flexible timing may accept a discount and do the cleanup. Thus, illiquidity does not always destroy value; it reallocates value to parties able to bear time and complexity. In economic terms, the discount rewards patient capital and specialist operational capacity.

This can be efficient when cleanup is socially useful. A buyer or investor that can cure stale records, resolve old contacts and clean routing state may unlock capacity that would otherwise remain dormant. The discount then finances the work. But the same mechanism can entrench incumbents. If only large buyers can absorb fixed transaction costs, small operators face a higher effective price per usable address. If only repeat participants understand registry pathways, they capture surplus from occasional sellers. If financing is available only against the cleanest blocks, messy but usable resources stay trapped with holders who cannot fund cleanup. Liquidity discounts can therefore both discipline and concentrate the market.

Accounting treatment adds another practical layer. An auditor considering the value of acquired IPv4-related rights will want evidence that the resource can be controlled, used or sold. A valuation expert will adjust for transferability, market depth, size, timing and risk. A tax reviewer may care whether a transaction involved a separable asset price. A credit committee may ask what happens if the buyer no longer needs the addresses. None of these actors need ARIN to certify value. They need the registry record and policy environment to be stable enough that value can be defended.

This is why predictable ledger function is pro-market even when it is not price control. A registry that clearly states eligibility, preserves record history, identifies service boundaries, processes clean files predictably and handles disputes proportionately lowers financing haircuts. It does not make every block equally valuable. It reduces unnecessary uncertainty so private finance can distinguish real risk from procedural fog. The difference between those two forms of risk is capital.

Small participants face a fixed-cost trap

Liquidity discounts are not evenly distributed. Large buyers and sellers can spread legal review, registry preparation, technical cleanup and adviser costs across many addresses. Small participants cannot. A fixed cost of $20,000 in diligence, staff time and professional assistance is material for a /24 and minor for a large aggregate. A fixed delay of six weeks may be tolerable for a strategic acquisition and fatal for a small network needing capacity for customer growth. The smaller the participant, the more liquidity friction becomes a hidden tax.

The minimum transfer size of /24 establishes one floor, but it does not make small-block transfers cheap. A buyer seeking a /24 still needs to understand recipient eligibility, agreement requirements, routing security, reverse DNS, reputation, provider filters and the seller's authority. A seller of a /24 still must have current records and the ability to sign. If either side is unfamiliar with ARIN's transfer categories, it may seek a facilitator, broker, counsel or technical consultant. Those services can be valuable. They also increase the all-in cost per address.

Small buyers are more exposed to information asymmetry. They may not have repeat transaction experience or private market memory. They may not know which delays are normal and which signal a failing file. They may struggle to distinguish a legitimate discount for reputation risk from a negotiating tactic. They may accept blocks that larger buyers reject because they have fewer alternatives. They may overpay for speed or underinvest in cleanup. The result is a market in which nominal prices do not capture the full burden of liquidity friction.

Small sellers face a different trap. A university department, small enterprise, local network or acquired business may hold addresses that are valuable in aggregate but not enough to justify a long monetization project. If records are stale, internal authority unclear or operational dependencies messy, the seller may prefer not to sell at all. That keeps usable resources dormant. Or it may sell at a steep discount to a specialist buyer that can handle the file. The specialist's profit may reflect real work, but also the small seller's lack of market access.

Policy design can reduce the trap without turning ARIN into a market maker. Plain-language evidence expectations help occasional participants prepare. Clear pre-approval rules help small buyers prove eligibility before negotiating. Standard guidance on ROAs, IRR, reverse DNS and reputation checks reduces surprises. Public transfer statistics by size and type can help participants understand market depth, even without publishing prices. Optional qualified assistance can help, but the public process should remain intelligible without requiring a private intermediary for every routine transfer.

The fixed-cost trap also suggests caution about adding procedural burdens. A requirement that seems small to a repeat large buyer may be significant to a small operator. If every transfer must produce a thicker file, answer more questions or coordinate more manual steps, the effect may be regressive. The market may still function for large incumbents while small networks are pushed toward leasing, NAT workarounds, or delayed service. Liquidity policy is therefore entry policy.

This does not mean ARIN should ignore fraud or weak authority to help small participants. Weak files harm everyone, and small buyers are often the least able to absorb the consequences of a bad transfer. The better distinction is between necessary proof and avoidable complexity. Necessary proof verifies holder status, authority, eligibility and record integrity. Avoidable complexity arises when requirements are unclear, duplicative, late in the sequence or dependent on institutional discretion not visible to the parties. Removing avoidable complexity improves liquidity without weakening the ledger.

The broader market should also recognize that small-block liquidity is not simply a convenience issue. Small networks, local service providers, specialized hosting companies, public-sector systems and enterprises with legacy dependencies often need modest amounts of IPv4 to maintain service while transition continues. If liquidity is available only to large buyers with professionalized transfer desks, scarcity governance becomes less neutral than it appears. A public registry ledger should not guarantee cheap supply. It should avoid making usable supply needlessly hard to convert.

The cleanup incentive and the incumbent advantage

Liquidity discounts can be productive. They tell holders that a messy block is worth less and that preparation creates value. A seller that updates contacts, signs the necessary agreement, documents corporate succession, audits old reassignments, clears route objects, adjusts ROAs, plans reverse DNS, checks reputation and resolves internal authority before marketing the block can command a better price and faster closing. The discount becomes a market signal: invest in record quality before asking others to pay full value.

This incentive is healthy when cleanup is within the holder's control. It aligns private profit with public registry quality. Accurate contacts, current agreements, clean routing-security state and clear transfer files benefit not only the seller but future operators and the Internet's coordination layer. The market rewards maintenance that the registry also wants. In this sense, liquidity pricing can improve governance without new rules.

But the same discount can entrench incumbents when cleanup requires resources that only large holders possess. A large enterprise can hire counsel to reconstruct decades of acquisitions, use internal network teams to audit every route object, pay for reputation review, and negotiate patiently with buyers. A small holder may know that cleanup would create value but lack the budget, staff or certainty of sale to justify it. If the market then discounts the block heavily, the small holder may sell to an intermediary or larger buyer that captures the cleanup value. Over time, illiquidity can move resources toward those with the capacity to cure files, not necessarily those with the highest operational need.

Incumbents also benefit from option value. A large holder with many blocks can sell the cleanest first and keep the messier ones for later. It can choose timing, buyer type and fragmentation strategy. It can wait for policy conditions or market demand. A small holder may have only one block and one opportunity. Its lack of optionality appears as a lower price. In a scarce market, patience is capital.

The policy challenge is to preserve the useful cleanup incentive while limiting unnecessary entry barriers. ARIN should not subsidize every holder's sale preparation or become a consultant. It can, however, reduce uncertainty about what cleanup matters. A public checklist tied to transfer readiness, service status, routing security and common legacy issues lowers the cost of preparation. Clear distinction between registry requirements and private best practices prevents parties from overbuilding files. Predictable handling of organization recovery and name changes reduces fear that old records will become traps.

Market participants can also improve practice. Buyers should explain discounts with specificity. "This block is illiquid" is not enough; the buyer should name whether the issue is recipient size, inter-RIR path, stale contacts, route-security residue, reputation, fragmentation, agreement status or dispute risk. Sellers can then decide whether to cure or accept the discount. Lenders should separate haircuts for policy transferability from haircuts for operational cleanup. Advisers should be paid for reducing uncertainty, not for mystifying it.

There is a subtle governance risk in using liquidity discounts as discipline. If the registry itself benefits from making agreement status or service access more complicated, market participants may perceive cleanup not as voluntary preparation but as compelled dependence. That is where narrow mandate discipline matters. The registry should protect public uniqueness and authorized change. It should not use scarcity to force commercial behavior unrelated to ledger integrity. When participants believe the registry is adding friction to preserve institutional relevance, they price that belief into every block. That is the avoidable part of the discount.

The most efficient market is not one in which all friction disappears. Some friction is the cost of preventing fraud, preserving accuracy and ensuring that recipients have real operational use under the governing policy. The efficient market is one in which friction is legible, proportionate and curable. Then discounts reflect real work rather than fear.

A predictable ledger reduces unnecessary illiquidity

The conclusion should be restrained. ARIN should not become a market maker for IPv4. It should not publish a recommended price, guarantee liquidity, certify that a block is reputationally clean, finance buyers, hold sale proceeds, or decide that one industry deserves priority because its story sounds better. Those roles would expand a registry into capital allocation and would likely create more uncertainty than they remove.

But ARIN also should not understate how much its ledger affects capital value. A registry record is not a mere administrative afterthought in a post-exhaustion transfer market. It is the public state that lets private contracts become recognized network facts. Its predictability shapes time-to-transfer. Its service boundaries shape operational convertibility. Its dispute handling shapes forced-sale value. Its transfer requirements shape buyer depth. Its inter-RIR compatibility rules shape the reach of demand. Its clarity or ambiguity becomes a discount or a premium.

The practical agenda is therefore about reducing unnecessary illiquidity. First, maintain clear public transfer categories and make the difference between 8.2 reorganizations, 8.3 specified-recipient transfers and 8.4 inter-RIR transfers understandable to finance and legal teams as well as network operators. Second, make recipient pre-approval and size qualification predictable enough that sellers can distinguish real buyers from speculative interest early. Third, present agreement and legacy service boundaries in market-relevant terms without turning them into sales pressure. Fourth, continue to emphasize source cleanup for ROAs, IRR and reverse DNS, while making clear what ARIN can and cannot control after transfer. Fifth, treat disputes with disciplined containment: no ordinary transfer while credible status disputes exist, but no indefinite freeze from vague claims. Sixth, publish enough non-price transfer statistics to help the community understand market depth, timing and fragmentation without exposing private bargains.

These measures do not require ARIN to choose winners. They require the registry to be a better ledger. The public good is uniqueness, accuracy, contactability, authorized change, operational continuity and historical intelligibility. The market good that follows is liquidity. When the ledger is reliable, private actors can price scarcity and quality. When the ledger is uncertain, they must also price institutional fog.

The CFO at the start of this article does not need a sermon about stewardship. The CFO needs to know how quickly the company can convert an address block into cash, capacity or collateral; what conditions might delay that conversion; how many buyers could realistically participate; which cleanup tasks are required; and whether a future board, lender or auditor can understand the record. If two blocks differ on those dimensions, their market values should differ.

The discount on the messy block is not proof that the market misunderstands IPv4. It is proof that IPv4 has become a capital asset whose value depends on institutional convertibility as much as technical usability. The policy question is not how to abolish the discount. Some discounts are deserved. A disputed, fragmented, poorly documented, reputation-tainted block should not trade as if it were clean. The policy question is how to ensure that discounts reflect real risk and real cleanup cost rather than avoidable registry opacity.

In the ARIN region, the strongest answer is disciplined ledger governance. Protect the public record. Verify authority. Preserve running networks where possible. Keep transfer paths predictable. Make service boundaries explicit. Do not launder broad market control through the language of coordination. Do not let private intermediaries become hidden gatekeepers. Do not pretend that a technically routeable block is automatically liquid. Scarce IPv4 will continue to trade, finance, fragment, consolidate and migrate for years. The least costly market will be the one in which the path from registered number to usable value is visible before the bargaining starts.

This analysis uses ARIN's public materials as factual background, including the Number Resource Policy Manual, Transferring IP Addresses & ASNs, Submitting a Transfer Pre-approval Request, Legacy Resources at ARIN, Using Whois, Resource Public Key Infrastructure, Internet Routing Registry, Reverse DNS, and the Qualified Facilitator Program. The institutional conclusions are the article's analysis, not ARIN's framing.