The committee paper does not begin as a debate about Internet governance. It begins as a lending problem. A regional hosting and connectivity group wants to finance a data-centre expansion. It has customers, contracts, racks, routers, cross-connects and a block of public IPv4 addresses that its engineers regard as ordinary capacity. The addresses are announced. They carry traffic. Reverse DNS can be maintained. Abuse contacts can be updated. Customers can be placed on them without changing the product plan. Inside the network team, the block is useful. Inside the credit room, it is not quite the same asset.
The lender's analyst separates the block from the rest of the collateral package. Not excluded, exactly; discounted. The note says the addresses may have meaningful economic value, but the bank will not give them full credit because registry recognition, future transferability, dispute status, audit timing and enforcement against the economic position cannot be treated as routine. Counsel wants more authority evidence. The technical team wants assurance that a registry review will not become a service problem. The finance director wants to know why a block that works on the network is being valued as if something is wrong with it. Nobody has found a routing failure. The concern is that the block may not be liquid enough for capital to trust it at full face value.
That is the liquidity discount. It is the gap between technical usability and realizable economic value. A public IPv4 block can be routeable, scarce and commercially important while still being discounted by buyers, banks, boards and operators because the path from use to sale, financing, recognized transfer, recovery or strategic redeployment is uncertain. Liquidity is not the same as quoted price, closing mechanics, title diligence or lease risk, although each can influence it. Liquidity is the probability that a holder can convert a recognized operating position into another trusted position at the moment it matters, with tolerable cost, bounded delay and a counterparty pool large enough to make the choice real.
AFRINIC makes this discount visible because its registry layer has been publicly tested. The African Network Information Centre administers Internet number resources for Africa and parts of the Indian Ocean and supports services such as Whois, RDAP, reverse DNS, routing registry functions and RPKI. Those functions are normally background utilities. They become economic infrastructure when IPv4 scarcity turns registry recognition into a balance-sheet fact. Address-theft reporting in 2019 showed how dormant or weakly monitored records could become valuable targets. The Cloud Innovation dispute showed how disagreement over use, registry authority and commercial address activity could reach courts and affect the institution itself. Receivership, board discontinuity and contested elections showed that the authority path of the registry can become part of the market's diligence file. Later restoration efforts may reduce some risk, but they do not erase the lesson: the bookkeeper is part of the asset's liquidity surface.
The thesis is narrow. AFRINIC-administered IPv4 does not become worthless because AFRINIC has experienced strain. A clean block can still support customers, routes and contracts. Nor does every discount imply a proved defect, a bad seller, a failed transfer or a broken service. The point is subtler. When registry friction, legal uncertainty, governance discontinuity, adverse-claim risk, audit delay, transfer execution risk, reputational uncertainty and future optionality constraints accumulate around a scarce resource, counterparties do not wait for final proof. A bank prices uncertainty through a haircut. A buyer prices it through a lower bid or narrower conditions. A board prices it through reserve language. An operator prices it through backup plans. A seller prices it through delay, legal spend or a smaller pool of willing counterparties.
The economic question is therefore not whether AFRINIC can say that basic services continue, nor whether a given prefix can be routed today. It is what rational counterparties do when the same technically usable block must also become capital, security, acquisition value, customer assurance or future mobility under a registry system whose discretion and continuity are no longer invisible. Liquidity discount is the market's quiet way of saying that the ledger is not boring enough.
The discount is an option problem, not a price complaint
Liquidity discount is often mistaken for a lower price. That is only its most visible expression. The discount starts earlier, before the bid and sometimes before the holder has decided whether to transact. It appears when an executive hesitates to classify addresses as available inventory. It appears when a lender refuses to treat address-supported revenue as fully financeable. It appears when a buyer asks for longer exclusivity, broader conditions or more extensive authority evidence. It appears when a broker says the block is useful but will require patience.
The timing matters because liquidity is an option. A holder does not merely possess an address block for today's routes. It possesses, or believes it possesses, a set of possible future choices: keep the resource for operations, sell it, split it, move it inside a corporate group, use it as part of a merger package, support customer acquisition, preserve it for disaster recovery, or indirectly support financing through address-dependent cash flow. The value of the block is the value of those choices under uncertainty. If the choices can be exercised quickly and predictably, the option is worth more. If exercising them requires registry discretion, legal interpretation, reconstruction of old corporate files, account-authority clarification or an unpredictable review, the option is worth less.
This is why a liquidity discount can exist even without a current sale. A company may carry addresses in internal planning at one value while a buyer, lender or auditor applies another. The disagreement may have nothing to do with IPv4 scarcity. Everyone may agree that public IPv4 addresses remain scarce and useful. The disagreement concerns realizability. Can the company get the value out when it needs to? Can a buyer obtain recognized control? Can a bank enforce against the economic position if the borrower fails? Can an acquirer move the block without inheriting a dispute flag, a frozen update or an institutional delay?
That makes liquidity distinct from price transparency. A thin market may lack reliable comparable transactions. That problem is real, but it is not the centre of this article. Liquidity discount asks a different question: even if market participants knew the approximate value of an uncomplicated block, how much less would they pay for a block whose conversion into recognized, usable and financeable control is slower or riskier? Published prices can reveal a discount. They do not create the underlying friction.
The same distinction separates liquidity from transaction protection. Escrow, release conditions and handover sequencing matter because they bridge the gap between commercial agreement and completion. But an elegant closing structure cannot remove every liquidity discount if the registry path is uncertain, if future transfers may be hard, if claims can cloud the file or if a later buyer will inherit the same questions. A closing protects one transaction. Liquidity measures whether the asset can keep moving across transactions and strategic uses.
Nor is liquidity identical to title assurance. A strong authority file reduces uncertainty over who may act for the holder and what old claims might exist. But a block with a good authority chain can still suffer a discount if the registry is slow, policy treatment is narrow, the institution is in litigation, the counterparty pool is small or future mobility depends on uncertain discretion. Title confidence is an input into liquidity. It is not the whole asset.
The first discipline is therefore to name the discount without exaggerating it. A discount is not proof that AFRINIC resources are impaired. It is a market response to risk. It may be too large in some cases and too small in others. It may shrink after credible governance repair or widen after new litigation. It may vary by block history, holder type, route reputation, documentation strength, buyer urgency and the intended use. But it exists as soon as rational counterparties ask for compensation for not knowing how smoothly a recognized operating position can be converted into cash, credit, control or future use.
Technical use can survive financial impairment
Engineers can be forgiven for finding the finance discussion odd. A prefix that can be announced is useful. Servers can answer on it. Firewalls can be configured around it. Customers can be migrated onto it. Reverse DNS can support operational identity. Abuse contacts can be maintained. RPKI, where the relevant controls are available, can support route-origin confidence. From an operations desk, a block either helps deliver the product or it does not.
Markets ask a wider question. They want to know whether today's operating usefulness will survive tomorrow's transaction, default, acquisition or dispute. A hosting provider may use a block for years, yet if it cannot transfer it, reassure an acquirer, pledge address-dependent revenue, respond to a claim or move the block during restructuring, its economic value is lower than its engineering value. The resource is still useful. It is less liquid.
The distinction is familiar in other asset classes. A factory may produce goods but be hard to sell because land records are unclear or a permit is not transferable. A ship may sail but be discounted because liens complicate financing. A receivable may be collectible but excluded from a borrowing base because the debtor has offset rights. The operating asset and the financeable asset are not always the same thing. IPv4 now sits in that category.
For IPv4 the split is especially important because the asset is not a physical object. Its value comes from uniqueness, registry recognition, route acceptance, customer dependence, reputation, security publication, DNS support and the ability to alter or transfer the record when business requires. If one of those layers is uncertain, the block may remain useful but become harder to sell, finance or redeploy.
AFRINIC's role makes the split visible. The institution does not forward packets, but it supports the public facts that make packets commercially legible. Whois and RDAP records tell outsiders whom to contact and whom to diligence. Reverse DNS supports operating identity. RPKI and routing registry functions can affect confidence in origin authorization and route hygiene. Holder-change and transfer processes determine whether a buyer can move from private agreement to recognized control. Member standing and account authority determine who may ask for changes. When those systems are predictable, technical usability and liquidity sit close together. When they are uncertain, a gap opens.
That gap is where capital becomes cautious. A buyer may be willing to operate the block but unwilling to pay as if future resale will be easy. A lender may value the business's customers while excluding part of the address inventory from collateral analysis. An acquirer may require recognized registry changes before closing. A board may keep addresses for operational safety but refuse to count them as liquid reserves. These choices do not mean the block fails technically. They mean the market refuses to equate routeability with financial mobility.
This distinction also prevents overstatement. Registry friction does not always destroy value. Often it redistributes value across time and counterparties. A discounted seller loses value, while a buyer with patience and specialist counsel may gain. A large operator can absorb process risk that a small operator cannot. A broker with registry experience earns fees because direct exchange is difficult. A registry delay may be unintended, yet it still shifts bargaining power toward the party with the lower cost of waiting.
Liquidity therefore depends on the full conversion chain. Can the holder prove control? Can the buyer underwrite the record? Can the registry process the change without turning a narrow file into a broad policy confrontation? Can the block remain operational while questions are resolved? Can public services be maintained? Can future owners rely on the result? The more "yes" answers the file can produce, the smaller the discount. The more "maybe" answers it produces, the larger the gap between use and value becomes.
AFRINIC makes institutional confidence a value variable
All regional Internet registries convert institutional confidence into market value, but most do so quietly. A buyer discounts less when it assumes the registry can process records predictably, separate fraud control from commercial judgment, maintain service continuity and survive internal disputes without contaminating individual files. The registry is not setting prices. It is lowering uncertainty around recognized use.
AFRINIC has made that background assumption more fragile. Its service surface is broad enough to explain the dependence: Internet number-resource administration, membership operations, resource records, Whois, RDAP, reverse DNS, routing registry functions and RPKI. Its exhaustion materials record the move from ordinary availability toward scarcity-era rules. Those are factual exhibits. They are not a conclusion about value. The value issue is that the body maintaining the scarce-resource ledger has itself been the subject of litigation, governance interruption, receivership and election controversy.
The 2019 address-theft reporting matters for liquidity because it linked scarcity to record integrity. Public accounts described allegations that valuable African IPv4 space associated with dormant or weakly monitored organizations had been commandeered and sold, with Ron Guilmette's investigation becoming part of the public record. The relevance is not scandal as theatre. Once old records can be monetized, buyers ask whether record integrity is strong enough. Sellers with clean files may still be asked to prove cleanliness because the regional market memory includes an address-theft story.
The Cloud Innovation dispute created another value variable. AFRINIC challenged the use and status of a large holder's resources. Cloud Innovation contested the interpretation and treated threatened termination or reclamation as existential. Litigation followed, including proceedings that affected AFRINIC's finances and capacity. One need not decide the merits to see the liquidity lesson. A registry action over address use can become a dispute large enough to affect the registry itself. When an enforcement dispute becomes a continuity dispute, counterparties widen their risk model.
Receivership widened it again. Public reporting described periods without ordinary board and chief-executive stability, with a Mauritian court-appointed receiver asked to preserve operations and arrange elections. The Number Resource Organization described the appointment of an official receiver as a continuity event for the registry system; that statement is useful as background, not as a market verdict. Later election attempts reportedly raised concerns over voter documentation, powers of attorney, potential interference, annulment and further litigation. These facts matter because a counterparty asks not only what the record says, but which institutional authority will stand behind future changes.
The result is a market in which AFRINIC's institutional condition becomes a quality adjustment. Not every block receives the same adjustment. A maintained holder record with current corporate authority, clean route history and no dispute should not be treated like a dormant block with weak documents. But the regional registry context changes the questions. What if a dispute arises? What if board authority affects policy interpretation? What if processing slows during litigation? What if a future transfer depends on a rule adopted or applied during contested governance? What if counterparties cannot tell whether delay reflects normal review or institutional stress?
This is not a choice between official reassurance and hostile criticism. A registry can truthfully say that services are operating and still face a market discount if counterparties think future recognition is uncertain. Critics can identify structural flaws and still overstate the immediate impairment of individual resources. The market is not required to accept either broad story. It prices the uncertainty left after both are heard.
Institutional confidence becomes a value variable because liquidity is forward-looking. A buyer does not pay only for today's working route. It pays for the ability to use, explain, finance, transfer and defend the resource over time. AFRINIC's public history makes that confidence harder to assume. The discount is not a verdict on every file. It is the price of doing extra diligence where the bookkeeper has become part of the risk.
Registry friction is a cost of capital
Registry friction is often described in moral terms. One side says friction protects the community from speculation, hoarding, fraud or extraction. Another says friction protects institutional power at the expense of holders that built networks and carried costs. Both claims may contain truth in particular cases. Neither is enough for valuation. On a balance sheet, friction is a cost.
The cost has several components. Documentation friction forces a holder to reconstruct corporate history, authority, allocation facts, route use and registry correspondence. Review friction adds waiting time and uncertainty over whether a file will be accepted, narrowed, challenged or expanded into a broader inquiry. Policy friction limits the forms in which a resource can move, or the counterparties willing to take it. Communication friction leaves outsiders guessing whether the issue is evidence, payment, member standing, legal order, staff capacity or institutional caution. Each component reduces the number of counterparties willing to pay full value.
Some friction is valuable. A registry that never tests authority invites fraud. A registry that allows forged documents to move scarce addresses destroys confidence. A registry that ignores adverse claims or court orders will create more expensive disputes later. The liquidity problem is not the existence of checks. It is the absence of predictable boundaries. A known evidence standard can improve liquidity by making clean files more credible. An open-ended review can reduce liquidity by making every file look contingent.
This difference is crucial for AFRINIC. The address-theft reporting made weak record control unacceptable. But the cure for weak record control cannot be a general assumption that registry discretion should expand until every commercial use is reviewable on uncertain terms. If the remedy for fraud is broad discretionary review, the market pays twice: first for the original record weakness and again for the uncertainty of the cure. Liquidity improves when anti-fraud controls become specific, auditable and proportional. It worsens when the institution retains the power to ask open-ended questions after capital has been committed.
The cost appears as time. A seller with an underused block may be willing to sell, but not if the process consumes management attention for months and exposes the company to public dispute. A buyer may need addresses for a launch window, not for vindication next year. A lender may include address-supported revenue only if the recognition path can be written into a covenant. If the file cannot produce a credible timeline, the counterparty applies a discount or chooses another resource.
It appears as legal expense. Counsel must review registry rules, contracts, corporate authority, local law, sanctions exposure, transfer conditions, litigation risk and service continuity. In a low-friction environment, much of this work is standardized. In a high-friction environment, every file becomes bespoke. Bespoke work is expensive. Expensive work eats value. The burden is heavier for smaller operators and one-time sellers because they cannot spread legal learning across many transactions.
Friction also affects internal governance. A board may conclude that monetizing a block is rational on paper but not worth the organizational burden if registry interaction may become slow, public or politically charged. The block remains idle. The market loses supply. Scarcity persists. A control regime designed to prevent misuse may inadvertently preserve underuse by making legitimate movement too costly.
The moral vocabulary therefore has to be translated into economic vocabulary. If a registry wants a control, what risk does it reduce? How often does that risk occur? What cost does the control impose? Who bears the cost? Can the same risk be reduced with a narrower instrument? Does the control improve the liquidity of clean resources by separating them from suspect files, or impose a general cloud? A serious liquidity analysis does not ask whether friction sounds virtuous. It asks whether friction creates more confidence than it destroys.
Legal uncertainty changes the buyer's opportunity cost
A buyer of IPv4 addresses does not buy certainty. It buys a level of uncertainty it can tolerate. Legal uncertainty becomes a liquidity discount when the buyer cannot estimate the probability, timing or consequence of a registry-related challenge. The buyer may still want the block, but it will compare the AFRINIC file with alternatives: provider addresses, another regional registry path, a smaller block with stronger documentation, temporary delegated use, NAT expansion, customer renumbering, IPv6 migration where feasible, or waiting. Each alternative has a cost. The discount is the amount required to make the uncertain path worth choosing.
The Cloud Innovation dispute illustrates why buyers think this way. Public accounts describe AFRINIC's concerns over use, geography and the purposes for which resources were justified; Cloud Innovation's objection to that interpretation; threatened termination or reclamation; interim court relief; frozen funds; and a legal conflict that became part of AFRINIC's broader crisis. The valuation issue does not require a final view on who was right. If a registry can treat a resource-use dispute as a high-consequence compliance matter, and if the holder's remedy is prolonged court action, legal uncertainty becomes part of the asset's carrying cost.
Legal uncertainty is not limited to active litigation. It includes ambiguity about future interpretation. What happens if a block is transferred and a previous use pattern is later questioned? What happens if a resource has been used outside the region under facts that are neither clearly forbidden nor clearly accepted? What happens if a court order affects one holder but counterparties fear wider implications? What happens if bylaws, member status or authority documents become relevant to the validity of an action? These questions may be remote in a given file. Liquidity prices remoteness as well as present danger.
Opportunity cost is harshest for growth businesses. A data-centre operator waiting for addresses loses revenue from racks that cannot be sold as planned. A cloud platform paying for provider space while a transfer is pending carries higher operating costs. A mobile network stretching CGNAT ratios may save addresses but incur support, logging and customer-experience costs. A buyer with a product launch cannot wait indefinitely for legal clarity. If AFRINIC-administered space carries a longer uncertainty tail, the buyer demands compensation or chooses a substitute.
The discount also includes legal asymmetry. A large holder may litigate. A small buyer may not. A bank may require formal opinions. A local ISP may rely on a shorter counsel memo. A multinational can model registry risk across regions. A regional operator may have fewer alternatives. The same uncertainty therefore produces different discounts for different counterparties. Liquidity is not one number; it is a distribution of willingness to transact.
Legal uncertainty changes seller behaviour too. A seller facing ambiguous registry treatment may prefer a buyer with stronger counsel, a longer timeline and a higher tolerance for dispute, even at a lower price. That shrinks the counterparty pool. The seller may also demand that the buyer assume more risk, but private risk allocation cannot fully bridge the registry layer. If future recognition is uncertain, contractual promises only partly address the problem.
The answer is not to pretend legal risk can disappear. Scarce resources create conflicts. Courts will remain necessary for fraud, corporate authority, insolvency, damages and binding orders. The liquidity question is whether legal uncertainty is classified early and narrowly enough for counterparties to price it. A buyer can tolerate a known exception. It struggles with a file in which any policy disagreement might become a high-consequence enforcement dispute. The clearer the boundary between registry administration and legal war, the smaller the opportunity-cost discount.
Governance discontinuity narrows the market
Liquidity depends on the number of serious counterparties. A resource is more liquid when many buyers, lenders, operators and intermediaries can underwrite it without unusual expertise. It is less liquid when only specialists, insiders or unusually risk-tolerant actors will touch it. Governance discontinuity narrows the market because it adds a question many counterparties do not want to answer: who can act for the registry, under what authority, and with what continuity if the file becomes non-routine?
AFRINIC's recent history brought that question into the open. Public reporting described periods without a functioning board or chief executive. A receiver was appointed under Mauritian court supervision to preserve operations and arrange elections. Later election efforts drew concerns over voting authority, credential security, powers of attorney and possible interference. One election was reportedly suspended and annulled; further legal challenges followed. The exact legal implications belong to the relevant proceedings. The market implication is simpler: ordinary governance could not be assumed.
For some counterparties, that is enough to step back. A public company may have internal rules that discourage acquisition of assets whose recognition path depends on contested institutional authority. A government buyer may avoid a transaction if procurement reviewers cannot understand the registry risk. A lender may decide the asset is too specialized for collateral treatment. A conservative enterprise may prefer provider addresses despite higher recurring costs because institutional uncertainty is harder to explain to its board than a monthly invoice. Liquidity falls not only when everyone walks away, but when mainstream counterparties do.
The pool also shrinks because governance discontinuity increases due-diligence specialization. A buyer must understand AFRINIC's service region, corporate status, member standing, resource policy, litigation history, public registry services, court-supervised events and the difference between individual file risk and institutional continuity risk. That is too much for occasional participants. They may still transact through brokers or specialist counsel, but intermediation becomes more valuable precisely because direct confidence has weakened. Any asset that requires specialist navigation has a narrower market.
Governance discontinuity changes expectations about the future. A buyer asks not only whether today's record is valid, but whether future policy, bylaws, service access or transfer treatment may change under a newly restored or contested board. It asks whether a repair programme might affect existing reliance. It asks whether peer-registry or Internet-governance statements would protect the ledger, the organization or neither in the particular way a buyer needs. These are not everyday technical questions. They are institutional-risk questions, and each reduces the number of parties willing to pay as if the resource were ordinary.
The discount can be rational even when services continue. A factory can keep producing during a corporate-control dispute; buyers still price the dispute. A bank can keep taking deposits while regulators review governance; investors still price the review. A registry can keep RDAP, Whois, reverse DNS and RPKI services running while counterparties discount future non-routine actions. Continuity of basic service is necessary. It is not sufficient for full liquidity.
Governance repair should therefore be judged by its effect on the counterparty pool. If a board, clearer bylaws, audited authority processes and narrow service-state communications make ordinary buyers and lenders comfortable again, the discount should shrink. If repair is presented mainly as institutional victory without reducing the cost of underwriting future files, the market will remain cautious. Liquidity does not return because an institution announces stability. It returns when fewer counterparties need a specialist memo.
Adverse claims and audit delay convert risk into carrying cost
An adverse claim is often most expensive before it is decided. Once a claim is proven, rejected, cured or settled, the market can price the outcome. While the claim is possible but unclassified, counterparties widen the discount. That is not unfairness; it is how capital handles uncertainty. Credit committees, boards and acquisition teams are paid to avoid surprises, not to assume that untested claims will fail.
AFRINIC-related resources carry several forms of adverse-claim concern. One is historical record risk. The address-theft reporting described valuable African IPv4 blocks linked to dormant or defunct organizations and alleged manipulation of registry records. A buyer looking at an old block asks whether a prior entity, successor, creditor, former operator or affected party could later appear. That does not mean the block is defective. It means the absence of a visible claim is not the same as proof that no claim can arise.
Another concern is policy or contract challenge. A holder may have used a resource in a way the registry later questions. The holder may describe the use as ordinary network evolution, customer service or global routing. The registry may view it as inconsistent with justified need, membership category, regional-use expectations or contractual undertakings. The conflict may be highly fact-specific. Liquidity suffers because future buyers are not sure whether the risk travels with the block, stays with the holder or can be isolated by representation and registry recognition.
A third concern is corporate authority. Companies merge, dissolve, revive, rebrand, sell divisions or lose records. Technical contacts outlast employment. Consultants hold credentials. Powers of attorney become contentious. Representative authority became visible in AFRINIC governance disputes, but similar questions can arise in resource files. A buyer does not need proof that a signature is bad to ask for a discount if the authority chain is hard to verify.
Audit delay is the time version of the same problem. A registry may need evidence because records are old, authority is unclear, holder standing is uncertain or fraud controls require confirmation. That can improve confidence if bounded. But an audit that expands without clear stopping rules turns a scarce asset into a queue. The holder cannot plan. The buyer cannot close. The bank cannot value. The board cannot decide. Every day in the queue becomes a small tax on liquidity.
Scarcity magnifies the tax. When IPv4 was abundant, waiting for a registry action might have been irritating. In a scarcity market, delay can move revenue, financing, product schedules and bargaining power. A buyer may have funds committed but not yet productive. A seller may be unable to recognize proceeds. Counsel and technical teams remain engaged. If the block is part of an acquisition, the entire deal may carry a condition tied to registry recognition. The cost of capital during the interval becomes part of the discount.
Delay also changes bargaining power. A buyer that can wait may demand a lower price from a seller under time pressure. A seller that can wait may demand stronger terms from a buyer whose launch depends on the block. A broker with knowledge of likely timing can shape expectations. A lender may use uncertainty to require more collateral. The registry may not intend any of these effects, but its process becomes the clock around which parties negotiate.
The liquidity-preserving answer is classified, limited, reviewable claim handling. No active claim. Claim received but unsupported. Transfer paused for a specific action. Court order restrains a defined change. Fraud review under stated evidence categories. Corporate authority unclear. Policy review pending. Claim resolved and corrective entry made. Each state allows the market to price risk more narrowly. Fog produces the broadest discount. Over-marking can destroy liquidity without proving a claim; silence can make buyers fear hidden defects. Precision is the middle course.
Reputation follows both the block and the registry
IPv4 reputation is usually discussed in operational terms: spam history, blocklists, geolocation errors, route leaks, abuse complaints, previous hosting use and the quality of prior network hygiene. Those factors affect value. A clean block is easier to onboard. A block with poor reputation requires remediation and may face customer resistance. In AFRINIC's case, however, reputation has a second layer. The registry environment itself can carry reputation risk.
That does not mean AFRINIC-administered space is tainted as a category. Such a claim would be too broad. The careful point is that market participants may ask extra questions because AFRINIC has been associated in public reporting with address theft allegations, major resource litigation, receivership and contested governance. Those questions travel into diligence even when the individual block is technically clean.
Reputational uncertainty affects boards first. A board approving the purchase of a block from a controversial registry environment may want to know why the risk is acceptable. The answer may be strong: current holder record, clean route history, no dispute, clear corporate authority, predictable registry path and business necessity. But the fact that the answer must be prepared is itself a cost. A transaction from a quieter registry environment may require less explanation.
It affects customers as well. Large enterprise customers increasingly ask suppliers about operational resilience, cyber exposure, IP reputation, geographic routing, sanctions exposure, legal continuity and service-dependency risk. A hosting or cloud provider using addresses connected to a controversial registry environment may be asked for assurance that service will continue if registry disputes arise. The customer may not understand regional registry governance. It understands contractual risk. If the provider cannot explain the registry layer simply, the customer asks for migration rights, stronger service terms or price concessions.
It affects banks and insurers. A bank may worry that public controversy around address resources complicates collateral recovery or borrower valuation. An insurer may worry that operational disruption from registry action falls outside ordinary coverage or creates ambiguous claims. Cyber insurers may focus on abuse history and reputation cleanup. Directors and officers insurers may care whether management has adequately disclosed risks around a material intangible asset. These concerns may be remote, but underwriting is built from remote concerns.
Registry reputation also shapes expectations of future optionality. If a market believes a registry may apply broad discretion, face further litigation, change transfer treatment under pressure or require emergency intervention, then even a clean resource is viewed through that possibility. The discount is not that today's record is bad. It is that tomorrow's institutional context may be harder to predict.
The reputational layer can be unfair to individual holders. A clean seller may pay for a general narrative it did not create. That is why registries should treat institutional reputation as an economic asset, not a communications accessory. Good governance lowers transaction costs for members. When a registry communicates precisely, classifies disputes, repairs records additively, publishes credible process data and avoids broad discretionary rhetoric, it reduces the reputation discount carried by members' resources.
Critics and large holders have duties too. Broad claims that imply all resources are trapped, all registry acts are suspect or all official processes are illegitimate can widen discounts if they replace evidence with atmosphere. Market discipline requires specificity on all sides. Which resource? Which claim? Which service? Which action? Which remedy? A serious market discounts facts, not slogans. When everyone speaks in broad narratives, counterparties protect themselves by applying a broader haircut.
Future optionality is the asset being discounted
The buyer of an IPv4 block is not only buying addresses for today's use. It is buying future optionality. It may later need to split the block, merge it with other holdings, transfer it to an affiliate, support a customer carve-out, bring it into a cloud BYOIP arrangement, preserve it for disaster recovery, finance address-dependent revenue, lease unused portions or sell after a business pivot. Each future choice depends on the ability to rely on registry recognition and operational controls.
Liquidity discount is therefore an option-pricing problem in institutional form. The more future choices remain open, the more valuable the block. The more choices depend on uncertain approval, legal interpretation, policy change, old-file disputes or institutional continuity, the lower the value. This is why buyers care about more than immediate routeability. A routeable block with constrained mobility is less valuable than a routeable block with durable, transferable and financeable recognition.
AFRINIC's scarcity context intensifies the issue. Its exhaustion materials describe a move into scarcity-era allocation, including soft-landing logic and justified-need limits. That is background, not a value guarantee. Scarcity raises the value of existing space because future demand cannot simply be met from a deep free pool. But if policy treatment, registry discretion or institutional uncertainty constrains how existing space can move, scarcity raises the value of the option while registry risk lowers its exercisability. The tension creates the discount.
Optionality constraints can be formal or informal. A formal constraint is a published rule: transfer limits, need requirements, regional conditions, holding periods or service conditions. An informal constraint is market belief that certain uses will attract scrutiny, certain counterparties will face delay or certain transaction structures will be viewed unfavourably. Informal constraints can be just as costly as formal ones because counterparties structure around perceived risk. If a buyer believes a future sale may be hard, it pays less today even if no rule explicitly blocks the sale.
Future optionality is also why legal language that rejects ordinary property analogies does not end the economic question. A resource may not be property in a registry's vocabulary and still carry option value because it supports operations, revenue, customer continuity and market transactions. If institutional language makes transfer, enforcement or reliance less predictable, the market does not abandon the asset model. It discounts the option.
Boards understand this intuitively. A board may approve a purchase only at a lower price if future exit is uncertain. It may keep a larger reserve of addresses because sale would sacrifice resilience. It may prefer internal retention because the organization values future flexibility more than near-term cash. It may require stronger governance before treating the block as strategic collateral. Each decision reflects optionality. The block's value is not only what it can do this year. It is what management can do with it under future stress.
The distributional effects are important. Large operators with multiple address pools, legal teams and alternatives can manage constraints better. Small operators with one critical block cannot. A large buyer can purchase a discounted block and wait for reform. A small buyer needs immediate confidence. A multinational can absorb policy risk across a portfolio. A regional ISP may have no hedge. Liquidity discount can therefore transfer value from smaller, more constrained holders to better-capitalized counterparties.
The cure is not unlimited mobility. Fraud, duplicate claims, court orders and narrow policy requirements must still matter. The cure is to make the conditions on future optionality explicit, prospective and reviewable. A buyer can pay fairly for an option whose exercise conditions are known. It discounts harshly when those conditions are hidden inside institutional discretion.
The discount is paid by sellers, operators and customers
Liquidity discount is often described as a seller's problem. The seller receives less or waits longer. That is true, but incomplete. The discount is paid twice, and then passed on. Sellers pay through lower realizable value. Operators pay through higher operating costs, weaker financing and reduced strategic flexibility. Customers eventually see the effects through prices, contract terms or delayed service.
The seller's discount is direct. A holder with a clean, mobile block can attract more buyers and stronger bids. A holder with uncertain records, adverse-claim risk, registry delay or future mobility limits faces fewer buyers and more conditions. It may accept a lower price, provide broader representations, wait longer or choose not to transact. In each case, liquidity is lower than scarcity alone would imply.
The operator's discount is less visible. A data-centre company may hold AFRINIC-administered space that it uses for customers and never intends to sell. Even then, uncertainty around registry recognition can affect financing. A bank may apply a lower multiple to address-dependent revenue. An acquirer may adjust enterprise value. A customer may demand continuity terms. An insurer may ask more questions. The operator pays through cost of capital, contract complexity and management attention.
Liquidity discount also shapes technology choices. If buying confidently recognized space is hard, operators rely more on provider addresses, CGNAT, NAT-heavy architectures, smaller public pools, renumbering, cloud public IPv4 charges or temporary delegated use. Some choices are rational. Many are costly. They can increase support burden, reduce customer portability, weaken bargaining power with upstreams or cloud platforms, and complicate security operations. Registry friction can become an engineering cost downstream.
Small operators are exposed most sharply. A large cloud provider can negotiate, buy elsewhere, structure around risk or absorb delay. A small African ISP may need a modest block, a predictable update and a bank that understands its business. If registry uncertainty causes lenders or sellers to demand stronger protections, the small operator may be pushed toward provider dependence, short-term arrangements or delayed expansion. The market discount then becomes an entry barrier.
Public-sector and enterprise users pay indirectly. Government services, universities, hospitals, banks, retailers and industrial companies may not follow AFRINIC disputes, but they depend on providers whose address strategy is affected by registry liquidity. If providers carry higher address costs or weaker financing, customers eventually see it in pricing, resilience, migration rights or slower service. The discount travels down the value chain.
The regional development argument therefore cuts both ways. A registry may justify friction as protecting regional resources. But if friction makes clean resources harder to mobilize, it can hurt regional operators by keeping supply idle, raising financing costs and narrowing counterparty access. Conversely, a market with weak record controls can invite theft, abuse and extraction, also hurting regional operators. The relevant question is not "market" or "community." It is which institutional design moves usable resources toward productive use while preserving record integrity and operational continuity.
AFRINIC's case shows why this balance matters. The region needs address liquidity because growth continues while IPv4 scarcity persists. It also needs confidence that old records cannot be stolen, that large holders cannot exploit legal asymmetry, and that registry services will not be used as arbitrary leverage. A liquidity discount is the market's measurement of how far the present balance falls short. When the discount is high, both sellers and operators pay for institutional ambiguity.
Leasing is a symptom, not the theory
Leasing appears whenever ownership-like transfer is slow, risky, restricted or strategically undesirable. It lets holders monetize unused capacity without surrendering long-term control. It lets operators obtain addresses without full purchase. It can match short-term demand to idle supply. In an IPv4 scarcity market, some form of delegated use is inevitable. But here leasing is not the main subject. It is a symptom of impaired liquidity.
When sale liquidity weakens, leasing becomes more attractive. A holder may hesitate to transfer a block because registry review is uncertain, future optionality is valuable or the board does not want to lose control. A buyer may hesitate to purchase because registry risk is too hard to underwrite. Leasing offers a middle path: operating use without full transfer. That path can be useful, but it also shows that the market is substituting private contract for confident public recognition.
The substitution can reduce or increase risk. A careful lease can define routing, abuse handling, reverse DNS, RPKI status, permitted use, termination, reputation monitoring and customer continuity. A vague lease can create abuse spillover, hidden sub-delegation, uncertain operating control and later disputes over responsibility. Those are contract issues. They matter, but they are not the centre of the liquidity argument.
AFRINIC's history makes leasing politically sensitive because the Cloud Innovation dispute and surrounding debate involved commercial use and out-of-region leasing arguments. The liquidity point is narrower. If registry friction makes sale hard, demand does not disappear. It moves into contracts, intermediaries and operating delegation. The registry may see less transparent control, not more. Suppressing delegated use without improving transfer liquidity can therefore make the market less legible.
Leasing also shows why liquidity is not only about sale price. A holder chooses among sale, lease, reserve and internal use. Sale produces cash but sacrifices optionality. Leasing produces yield but adds contract risk. Reserve preserves flexibility but produces no cash. Internal use supports operations but may hide market value. Registry uncertainty changes the relative attractiveness of each. A high transfer-risk discount pushes holders toward leasing or reserve. A low discount allows clean sale or financing.
The goal should not be to force every resource into sale or to condemn every lease. It should be to make each choice explicit and priced. If AFRINIC's registry environment gives holders confidence that legitimate transfers, responsible delegation and future changes will be handled predictably, the market can choose among them on economic grounds. If not, leasing remains a workaround for institutional uncertainty, and the discount survives.
How the discount shrinks
Liquidity returns when counterparties can rely on the conversion chain. For AFRINIC-administered IPv4, that means reducing the number of questions that require special interpretation. The goal is not a frictionless market without fraud controls. It is a predictable market in which clean resources can move, finance can underwrite risk, and disputes are isolated rather than allowed to cloud the whole registry environment.
The first requirement is precise record status. AFRINIC should distinguish current recognition, pending update, incomplete documentation, transfer pause, court restraint, fraud review, policy review, member-standing issue, operational-service issue and resolved dispute. A vague cloud produces a broad discount. A precise state produces a narrower one. The market can price a known exception. It struggles with institutional fog.
The second requirement is predictable authority verification. Resource holders should know what evidence proves corporate authority, representative capacity and account control. Buyers and lenders should know when that evidence has been accepted and what it does not prove. Old records, mergers, liquidations, powers of attorney and changes of control will remain difficult. Difficulty becomes less costly when the standard is known. A standard that catches false authority improves liquidity. A standard that expands unpredictably reduces it.
The third requirement is bounded audit. AFRINIC must be able to review records, especially after public reporting on address theft and dormant-resource weakness. But audit should have scope, timing, evidence relevance, notice, cure and review. A bounded audit separates suspicious files from clean ones. An unbounded audit makes all resources feel contingent. Liquidity depends on that distinction.
The fourth requirement is continuity of public services during dispute. RDAP, Whois, reverse DNS, RPKI and related publication services should not become ordinary leverage in commercial or policy conflict. Severe impairment may be necessary in narrow cases of fraud, duplicate recognition, clear legal order or security emergency. The default should preserve the last verified operational state while the disputed action is examined. Buyers and customers discount less when they know running networks will not become collateral damage.
The fifth requirement is transparent timing. Processing states and aggregate timelines matter. How long do routine changes take? How long do incomplete files remain open? What causes escalation? How often are transfers paused? How often are disputes resolved? Such data need not expose confidential documents. It would let boards, lenders and buyers model delay rather than fear it. Unknown time is expensive time.
The sixth requirement is governance repair that reduces, rather than raises, the prize value of institutional control. Elections, bylaws, budgets and legal strategy matter because board authority can affect resource policy, litigation posture and registry discretion. The way to lower the liquidity discount is not merely to restore a board. It is to narrow the board's ability to turn registry control into market control. A ledger-first registry is easier to trust because capturing it yields less private advantage.
The seventh requirement is legal-continuity architecture. Courts will remain backstops. Receivership or emergency intervention may be necessary under institutional stress. Resource holders and counterparties should know how data custody, service continuity, pending transfers, dispute flags, RPKI, reverse DNS and member communications survive such events. A continuity protocol lowers the fear that corporate stress at the registry will impair otherwise usable resources.
The eighth requirement is disciplined public communication. AFRINIC, critics and large holders all have incentives to frame disputes broadly. Broad framing increases discounts. A registry rebuilding liquidity should speak in narrow market-useful categories: what is alleged, what is decided, which resources or services are affected, which functions continue, what review exists and what action is not being taken. Critics and large holders should be held to the same standard. Markets can absorb hard facts. They discount rhetorical fog.
None of these reforms requires AFRINIC to become a price regulator, insurer, commercial judge or owner of the economic value created by networks. The opposite is true. Liquidity improves when the registry is narrower, more auditable and more boring. It should maintain the ledger, protect uniqueness, prevent fraud, preserve publication and security-adjacent services, record disputes precisely, process authorized changes and respect lawful orders. The market can then decide price, financing, delegated use, reserve value and commercial strategy.
The committee paper would change if that architecture were credible. The analyst would still consider IPv4 scarcity, route history, reputation, block size and business use. Counsel would still review authority. Engineers would still test operational controls. But the special AFRINIC haircut would shrink because the questions would be answered by a predictable system rather than by a bespoke institutional-risk file. The block would not become risk-free. Mature assets are not risk-free. It would become liquid enough for risk to be priced normally.
That is the economics of liquidity discount. It is not a campaign slogan against AFRINIC and not a defence of every commercial address strategy. It is a measurement of institutional trust. The same technically useful IPv4 block can support a network and still be discounted if the market doubts its mobility, recognition, financeability or future optionality. AFRINIC is the test case because scarcity, litigation, address-record history and governance discontinuity have made the hidden registry layer visible. The way to reduce the discount is not to ask markets for faith. It is to make the ledger narrow, durable and reviewable enough that faith is no longer part of the price.