A scarce address becomes working capital
IPv4 scarcity in Latin America and the Caribbean is often described as a technical hangover: an old addressing system ran out, IPv6 is the answer, and the remaining problem is persuasion. That account is true enough to be dull, and too thin to explain the economics now surrounding LACNIC. In practice a scarce IPv4 block behaves like working capital. It is not property in the ordinary sense, and the regional internet registry does not sell it like land. But a network that cannot obtain enough usable IPv4 space must finance the shortage somehow. It can buy addresses, lease them, stretch old pools through carrier-grade NAT, slow a product launch, change the terms of an acquisition, depend more heavily on an upstream, or keep customers on legacy arrangements while it waits for IPv6 economics to catch up with IPv6 architecture.
Those choices appear in balance sheets before they appear in policy debates. A small access provider may need addresses to sign a business customer that still requires IPv4 reachability. A hosting firm may need clean space to add a rack, migrate a customer or avoid an overconcentrated NAT design. A regional carrier may value a target partly because its address records are cleaner than its fibre routes. A public university may not trade addresses at all, yet still discover that stale records complicate a procurement, a security response or a move to a new operating entity. A Caribbean operator with limited correspondent-banking options may find that an invoice, a transfer fee or a broker's escrow deadline is as consequential as a router upgrade. Scarcity turns a numbering resource into a financial constraint.
The registry is not responsible for creating that scarcity. IPv4 was small by design; internet demand grew beyond it; IPv6 is the durable route out. LACNIC's formal role remains narrower than the economic consequences now attached to it. It records number-resource holders, implements policy, supports reverse DNS and RPKI, handles transfers, manages member relationships and keeps the regional record coherent. It is not a bank, a securities exchange, a telecommunications regulator or a court. Yet in a scarce market a narrow registry decision can have a wide economic effect. Recognition, documentation, timing, account standing, legacy regularisation, transfer eligibility, certification continuity and reverse DNS delegation all influence whether an address block can be converted into revenue, financing comfort or saleable capacity.
That is the central point of this article. LACNIC's post-exhaustion importance is not merely institutional legitimacy, and not merely the choice between ledger and gatekeeper. Those questions matter, but this case is sharper. The issue is how scarcity is priced. A block that can be transferred with predictable evidence, paid for through ordinary channels, kept certified, delegated in reverse DNS, documented through a clean corporate chain and integrated into an operating network is worth more than the same number of addresses trapped behind a founder's estate, a public-sector reorganisation, a currency-control delay, an opaque lease, a suspended account or a disputed legacy record. The registry does not need to publish a price list to shape prices. It needs only to decide what counts as final.
This is why a policy that looks neutral on paper can redistribute value in practice. The same request for documents can be a routine anti-fraud measure for a multinational, a costly legal exercise for a family-owned ISP and an administrative ordeal for a public body whose history is scattered across ministries. The same payment deadline can be easy in a dollarised treasury and difficult in a jurisdiction with capital controls or fragile bank links. The same transfer rule can be an understandable safeguard for the community and a discount applied by a buyer to every small seller that has never navigated the process before. Scarcity magnifies fixed costs.
The registry's proper task is therefore not to suppress the market and not to indulge it. It is to make scarcity legible. LACNIC should be strict where strictness protects the record: identity, authority, provenance, dispute status, resource eligibility, operational responsibility and fraud prevention. It should be cautious where strictness becomes economic permission: judging whether a seller ought to monetise, whether a lessee is admirable, whether a price is too high, whether an operator deserves to acquire more IPv4, or whether IPv4 dependence is morally obsolete because IPv6 exists. The line is not always easy. But after exhaustion, it is the line that determines whether the regional scarcity premium reflects genuine shortage or avoidable institutional friction.
When waiting lists price the alternative
The most important economic fact about LACNIC's IPv4 pool is not the romance of the final allocation. It is the absence of a practical alternative for many operators. In June 2014 the Number Resource Organization reported that LACNIC had reached the phase in which one remaining /10 block was left and IPv4 could be considered exhausted in the region. The remaining addresses were rationed under community policy. In August 2020 LACNIC created its IPv4 waitlist after assigning the last available IPv4 block. LACNIC's own description of the waitlist is sobering: the last approved request faces an estimated wait of at least 18 years and may receive at most 1,024 IPv4 addresses, subject to uncertainty because future recovered space cannot be predicted.
That waiting list is not a supply plan. It is a price signal. It tells a new entrant, an expanding ISP, a data-centre operator, a managed-services provider and a carrier consolidator that ordinary fresh supply from the registry cannot be the basis of an IPv4-dependent business plan. A /22 after a very long wait might help a small transition need, a starter network or a tightly rationed service. It cannot support the ordinary growth of access, hosting, cloud, enterprise migration or regional platform capacity. Operators that still need IPv4 must turn to conservation, purchase, lease, acquisitions, internal renumbering, more aggressive NAT or customer restrictions.
That changes the meaning of paperwork. In a world of abundant supply, documentation is a compliance burden. In a world of scarcity, documentation is part of price discovery. If a buyer expects a transfer to require translations, legal opinions, historic corporate certificates, proof of authority, policy justification, account cure and possible registry questions about a predecessor entity, it will discount the address block before it signs. If a seller can show that its records are current, its account is clean, its directors are authorised, its resource history is unchallenged and its operational delegations can move smoothly, it can bargain from a stronger position. The same address count can carry different market values because the administrative path differs.
The waitlist also exposes the distinction between nominal addresses and usable addresses. LACNIC has described recovered blocks assigned in this late phase as having been quarantined for at least six months, while also making clear that recipients may still face blacklisting or filtering issues and must handle rehabilitation themselves. That is not a minor caveat. A block with a poor reputation, uncertain route acceptance or broken reverse DNS does not have the same financial quality as a clean block. The asset-like thing is not a row of numbers. It is reachable, recognised, routable address capacity with tolerable reputation risk and operational continuity.
Timing then becomes money. A delay that would be irritating in a mature credit market can be material in a country with inflation, exchange controls or scarce dollars. A buyer may have committed to a customer deadline. A seller may need proceeds before a debt payment or equipment order. A merger may depend on whether addresses can be integrated before closing. A public body may have a budget window. A leased block may be a bridge while an operator completes IPv6 deployment or customer renumbering. A registry file in review is not merely waiting in a queue; it is inventory that cannot be financed, sold or fully deployed.
This does not mean every attempt to monetise IPv4 deserves approval. Scarcity attracts fraud. Prices create incentives for forged documents, account compromise, shell companies, old contact abuse, speculative warehousing and opportunistic claims over defunct organisations. LACNIC has to protect the record precisely because market value now attaches to it. But anti-fraud discipline should be distinguishable from an allocation-era instinct to ask whether the proposed use is worthy. Once addresses are already issued and the market is the practical path to reallocation, liquidity is not the enemy of stewardship. It is the mechanism by which resources move to networks that can put them to work without forcing the registry to pretend that it still has abundant stock.
The rhetoric of exhaustion often ends with IPv6. The economics do not. IPv6 deployment reduces future scarcity, but many customers, platforms, enterprise systems, security tools, procurement assumptions and legacy applications still require IPv4 reachability. Operators have to finance the transition while supporting today's revenue. If the cost of obtaining or regularising IPv4 capacity becomes too unpredictable, the result may not be faster IPv6. It may be postponed growth, more complex NAT, weaker resilience, thinner margins and less cash for network modernisation. A serious scarcity regime should help the old system settle cleanly while the new one grows.
Liquidity across unequal balance sheets
LACNIC serves a region, not a single balance sheet. The phrase "Latin America and the Caribbean" hides vast differences in scale, credit access, legal administration, language, exchange-rate risk, storm exposure, market concentration and technical staffing. Brazil and Mexico have large markets, deep communities and national institutional channels that shape parts of the number-resource relationship. Argentina brings recurring currency and inflation complications. Chile, Colombia, Peru and other substantial markets may have sophisticated operators but uneven access to capital. Central American networks may face cross-border service dependencies. The Caribbean contains small-island economies where undersea capacity, correspondent banking, storm resilience and limited specialist staffing are persistent realities.
An IPv4 block is not financed in the abstract. It is financed through a local treasury and a local legal structure. Revenue may arrive in pesos, reais, soles, dollars or Caribbean currencies. Registry invoices and transfer settlements may require hard currency. Banks may ask for unfamiliar documentation before sending funds. A public-sector network may depend on procurement approval. A small private ISP may rely on the owner-manager's relationship with one bank. A cooperative or family operator may have legally valid records that look untidy to a buyer accustomed to large-company formalities. A multinational carrier can centralise all of this in a legal department. A local network may have one person handling routing, customer escalations, accounting and registry tickets.
Scarcity punishes fixed costs. A notarised translation, board resolution, legal opinion, foreign wire shortfall or document apostille does not scale down neatly for a /24. The minimum transfer size matters because a tiny block can still be economically vital to a small operator, but the cost of proving and moving it may resemble the cost for a much larger transaction. Large operators can amortise legal and registry experience across many addresses. They can hire brokers, maintain escrow relationships and learn which documents tend to satisfy reviewers. Small operators often encounter the process only once, under pressure, and pay a novice's discount.
This is one reason large-country gravity matters. Bigger markets concentrate demand, brokers, cloud investment, data-centre growth, policy participation and procedural knowledge. LACNIC's transfer information directs organisations based in Brazil or Mexico toward the relevant national channels for those countries, a practical reflection of the region's structure. The effect is not necessarily malign. Large markets can professionalise transfers, improve operational hygiene and supply experienced participants to policy discussions. But the same gravity can widen the gap between operators that understand the scarcity market and operators that discover it only when they are desperate.
Small-island dependence is different. The absolute address need may be modest, yet the marginal value can be high. A /24 may support services used by hotels, banks, schools, public offices, healthcare providers or emergency communications. Replacement options may be thin. An upstream may be powerful because there are few alternatives. A storm or cable fault may force operational changes on a timetable that does not respect registry queueing. If a network has to update contacts, preserve RPKI, change reverse DNS or regularise a predecessor entity during a service disruption, those tasks are not clerical. They are part of resilience.
Language is another balance-sheet item. Spanish, Portuguese and English all matter in the region. Formal translation of policy is useful, but practical knowledge is often conveyed through meetings, mailing lists, help desks, examples and informal memory. A small English-speaking Caribbean operator may face different participation costs from a Spanish-speaking continental carrier or a Portuguese-speaking Brazilian network. A global company can assign multilingual staff. A local ISP cannot always do so. If policy around transfers, legacy regularisation or payment cure is easier to understand in one language community than another, scarcity rules will not be equally cheap to use.
None of this implies that LACNIC should become a development bank or regional equalisation agency. It should not redistribute issued address space according to industrial preference, nor should it subsidise every operator that faces local constraints. The more modest duty is to avoid making neutral processes depend on hidden assumptions: fast dollar payments, large-company record-keeping, routine access to counsel, stable archives, multilingual policy labour and the ability to wait. Equal words do not produce equal liquidity if the cost of using them differs sharply across the region.
The best scarcity administration is therefore proportional. A routine contact correction should not resemble a contested succession. A simple intra-regional transfer should not carry the evidentiary fog of a decades-old legacy regularisation. A small block should not be priced out of usefulness by process designed for large consolidations. A high-risk case should still receive high scrutiny. Proportionality is not leniency. It is a way of directing verification to the risks that actually threaten the record, rather than allowing capital-rich operators to buy their way through avoidable complexity.
Transfers, discounts and the cost of uncertainty
Transferability is the central liquidity mechanism after exhaustion. LACNIC's policy framework, implemented for intra-regional and inter-regional IPv4 transfers under defined conditions, includes familiar safeguards. The minimum transfer size is /24. The recipient in the LACNIC region must justify its need under applicable policy. The relevant registry must verify the holder and check that the resources are not involved in a dispute. Legal documentation is required. Transfers are logged publicly. The originator is ineligible for new LACNIC allocations or assignments for a year, and transferred addresses face a one-year restriction on further transfer. Legacy resources transferred into the LACNIC region stop being legacy and become subject to current obligations.
These rules are not just technical. They constitute the settlement architecture for scarce capacity. A transfer is not economically finished when buyer and seller agree on a price. It is finished when the recognised record changes, when operational delegations can follow, when route-origin authorisations can be maintained or created, when reverse DNS can be aligned, when account standing no longer threatens the change, and when counterparties trust that the new holder is the recognised party. Registry finality is part of closing.
Uncertainty is discounted. A buyer pays less for a block if the seller's authority is unclear, if the block is legacy and unregularised, if the transfer path requires unfamiliar documents, if need justification is unpredictable, if payment standing may interrupt recognition, or if operational services might not move cleanly. A seller accepts less when it cannot prove a clean chain of control. A broker charges more when success depends on tacit knowledge. An escrow period lengthens when either side fears that the registry will ask for another document after commercial terms have already been fixed. These discounts are not always visible in public transfer logs, but they are part of the market.
Need justification is the most delicate part of this architecture. When a registry allocates scarce stock from a common pool, need review is rationing. When a buyer pays another holder for already-issued resources, need review changes character. It can still be required by adopted policy, and it can still help discourage pure speculation or hoarding. But its economic effect is closer to credit approval. The registry is not lending the capital, yet it may determine whether the recipient's plan is sufficiently legitimate to recognise the transaction. The more subjective that judgement becomes, the more LACNIC influences which business models can finance IPv4 continuity.
There are sound reasons not to make transfers frictionless. Fraud risk rises with market value. Address blocks can be laundered through shell entities, compromised accounts or paper transactions. A desperate seller may try to monetise resources it does not control. A buyer may be acquiring a dispute. A public-sector entity may lack authority to dispose of resources even if a contractor says otherwise. A registry that recognises every request at face value would lower short-term friction and raise long-term distrust. The result would be a dirtier market, not a freer one.
The design challenge is to tie friction to the right risk. Verification should ask whether the holder is genuine, the authority is real, the resource is eligible, policy conditions are met, account defects are material, disputes are known and operational responsibility will remain legible. It should not drift into broad judgement about whether the buyer is too large, the seller too mercenary, the price too financial, the use case insufficiently developmental or the transaction aesthetically inconsistent with address stewardship. Markets can price explicit policy rules. They struggle to price institutional hesitation.
Inter-regional transfers sharpen the issue because they connect LACNIC's scarcity to a wider market. A region without an effective inter-RIR transfer path may believe it is protecting local supply, but it also reduces the value of local holdings, narrows the buyer pool, makes sellers more dependent on local demand and encourages leasing or informal arrangements that may be less transparent than formal transfer. A region with an effective path must still prevent fraudulent export and ensure policy compatibility. The choice is not between purity and markets. It is between visible market design and informal leakage.
The one-year holding restrictions illustrate the balance. A cooling-off period can discourage rapid flipping and provide stability. It can also create costs when an operator faces a failed acquisition, an urgent refinancing, a restructuring or an unexpected change in customer demand. The rule is defensible if it is clear, narrow and consistently applied. It becomes damaging if it combines with vague suspicion, repeated document requests and long-tail review. Explicit rules can be modelled in a purchase price. Unclear process becomes a wider risk premium on the region.
Transfer policy also affects competition without becoming competition policy. Incumbents that already hold large address pools benefit when smaller challengers face high transfer costs. New entrants and consolidators need predictable access to addresses if they are to compete in IPv4-dependent services while deploying IPv6. LACNIC should not try to choose winners. But by making transfer recognition transparent and proportional, it can avoid letting registry friction become an incumbent advantage.
Leasing as finance, not a loophole
IPv4 leasing sits uneasily in registry politics because it exposes the gap between formal record holding and commercial use. Yet in a scarcity economy leasing is a normal financing response. Buying addresses turns shortage into capital expenditure. Leasing turns it into operating expense. For an operator facing uncertain demand, exchange controls, temporary customer growth, a migration project or limited financing, that distinction can decide whether a service launches. A hosting provider may need extra space for a six-month customer move. A cloud customer may need IPv4 during a staged deployment. A carrier may need a bridge while renumbering. A small ISP may be unable to purchase at market prices but able to rent enough space to keep legacy equipment and customers working.
The case for leasing is not a case for opacity. Leasing can separate economic control from registration. The registered holder may remain in the record while another party originates routes, serves customers, handles abuse, maintains reverse DNS or relies on the block for revenue. Responsibility can become muddy. The arrangement may resemble a transfer of control without being recorded as one. A lease can also become a way to avoid eligibility rules or hide a risky counterparty. These are serious record-integrity concerns.
But they are concerns about legibility, not proof that leasing is inherently suspect. The useful questions are practical. Who is the recognised holder? Who is authorised to create or maintain ROAs? Who controls reverse DNS? Who receives abuse reports? Are operational contacts accurate? Is the lessee visible enough for incident response? Does the arrangement cross the line into a transfer that policy requires to be recorded? Can the holder be reached if the lessee misuses the space or disappears? Does the routing state correspond to an authorised business relationship?
An unhelpful registry posture asks a broader set of questions. Is the lessor profiteering? Is the lease price too high? Should the lessee have deployed IPv6 faster? Is temporary use less virtuous than ownership? Is a foreign lessee insufficiently regional? Should address holders be discouraged from earning income on space they are not using fully? These questions may be framed as stewardship, but they move toward economic governance. If leasing is financially rational, moral suspicion will not abolish it. It will push it into weaker contracts, less visible operational delegation and more dependence on brokers.
Continuity is where lease quality becomes price. A leased block that comes with clear authorisation, reliable RPKI handling, stable reverse DNS, current abuse contacts and known reputation history is worth more than one that comes with vague promises. The lessee is not buying an address count; it is buying a period of usable reachability. The lessor is not merely renting numbers; it is lending operational credibility attached to its recognised record. If the registry's tools make responsibility visible without certifying every commercial term, the market can price leased capacity more accurately.
Leasing is especially relevant in countries where purchasing is difficult. A one-time dollar outlay may be impossible under exchange controls or hard-currency rationing, while smaller recurring payments can be managed. A seller may prefer lease income because a sale creates tax, regulatory or repatriation problems. A lender may treat a lease as an operating cost but hesitate to finance a purchase of resources whose legal character is not ordinary property. A public-sector network may lease capacity through a contractor because it cannot easily buy. None of these facts is exotic. They are ordinary corporate finance under scarcity.
The risk is that registry unease turns an economic adaptation into a hidden market. Hidden markets are worse for the record. They make abuse handling harder, weaken diligence, obscure responsibility and reduce the value of clean operators that are willing to document arrangements. A serious scarcity regime would not necessarily register every lease like a transfer, nor would it bless prices. But it would define when delegated use should be visible, which operational contacts should be accurate, how RPKI authority should be handled, and when a lease becomes a transfer of effective control. The aim should be a market in which temporary use can be made accountable, not a market in which everyone pretends temporary use is not happening.
The same logic applies to internal group use. Corporate groups, managed-service providers, outsourcing arrangements and infrastructure partnerships often place resource use somewhere other than the legal entity in the record. Scarcity makes those arrangements more valuable and more contested. A registry that insists on a simple property metaphor will misdescribe the market. A registry that ignores the gap between record and use will weaken trust. The better approach is to make authority and responsibility legible enough that counterparties can price the arrangement.
Payment friction is monetary policy by accident
Billing sounds remote from address scarcity until a payment problem freezes a scarce resource. LACNIC's public payment information states that payments should be made in US dollars, that wire-transfer fees must be taken into account, and that receipts are issued for the exact amount reaching its bank account. It also sets payment terms: full payment within 31 days after the invoice due date, surcharge and entry into recovery after 35 days, and revocation after 125 days. In one sense these are ordinary rules. A registry must be paid. In another sense they are a monetary interface between a regional institution and economies with very different access to dollars.
For a large operator with stable treasury access, the invoice is a service charge. For an operator in a country with exchange controls, inflation, bank scrutiny or hard-currency rationing, it can be a liquidity event. The company may have local revenue and good customers but limited access to foreign currency. It may need tax documentation, central-bank permission, procurement approval or a bank willing to send a small international transfer. A public-sector network may not control its payment calendar. A small island ISP may face expensive correspondent-banking routes or de-risking by banks that find telecom payments administratively unattractive. A wire fee deducted by an intermediary can create a shortfall even when the member intended to pay in full.
None of this makes nonpayment harmless. LACNIC cannot maintain a credible registry if members treat invoices as optional or abandon accounts while continuing to rely on recognition. Paying members should not subsidise chronic delinquency. The membership relationship matters because the record is not a free public noticeboard. But the remedy should fit the risk. A billing defect can be a collection problem, a currency problem, a documentation problem, an abandonment problem or evidence of bad faith. Treating all of these as the same can turn account standing into accidental monetary policy.
The principle should be separation. Billing enforcement should be clear, staged and predictable. Members should know which functions are affected at each stage and why. A curable wire shortfall should not be treated like abandonment. A documented currency-control delay should not automatically threaten operational continuity. Emergency contact correction, abuse-response updates, reverse DNS continuity and RPKI maintenance may deserve different treatment from new allocations, voting rights or the closing of a discretionary transaction. The registry's interest is not merely to collect. It is to collect while preserving a reliable record.
Payment friction has direct consequences for transfers. A seller in a currency-stressed economy may need to monetise underused IPv4 space to finance equipment, debt, succession or IPv6 migration. If its account has a curable defect, the block may be trapped just when liquidity matters most. A buyer discounts that risk. A broker asks for more. A larger counterparty uses the delay to renegotiate. The registry has not set the sale price, but it has changed the negotiating position.
The same applies to purchasers. A buyer may line up escrow, local approvals and foreign-exchange access around an expected registry timetable. If the review or account cure slips, the bank's approval may expire, the exchange rate may move, the board resolution may need renewal or the seller may walk. This is not the registry's fault in a narrow sense. But a registry that understands its role in settlement can reduce avoidable misalignment by publishing predictable stages, cure paths and service targets.
Leasing responds to the same monetary environment. A lessee may prefer monthly payments in a manageable currency over a large dollar closing. A lessor may prefer recurring income to a sale whose proceeds are hard to repatriate or politically conspicuous. A network may lease while waiting for a financing round, public procurement or IPv6 transition. If registry suspicion pushes leasing into informality, the financial choice does not disappear. It becomes less accountable.
Small operators suffer most from unclear payment consequences. They are less likely to have treasury staff, foreign accounts, counsel or repeated experience with LACNIC processes. A multinational can absorb surcharge and cure. A local ISP may discover the consequences only when a transfer, certification change or record update becomes urgent. Scarcity administration that assumes frictionless hard-currency settlement privileges the already liquid. Better billing design cannot fix exchange controls or bank de-risking, but it can avoid adding surprise to shortage.
Legacy title and the economics of old paper
Legacy IPv4 resources are where scarcity meets institutional memory. LACNIC defines legacy resources as IP addresses and ASNs assigned by InterNIC or IANA before the current regional registry system, specifically before 28 December 1997, and not later covered by a membership agreement with LACNIC. For years such records could look like residue from a less formal era. In a scarce market they are live financial facts. A legacy block may support customers, appear in acquisition diligence, interest brokers, or sit unused behind an entity that no longer resembles the organisation in the old record.
The hard question is not merely whether a legacy holder has property. The operational question is whether it can prove continuity well enough for the registry and the market to rely on it. The answer can be messy. A university may have changed legal status. A state telecom asset may have been privatised, split or merged. A public-sector network may have moved between ministries. A family-owned ISP may have passed through succession. A research network may have become a commercial provider. A cooperative may have old board records. A local company may have changed names several times without ever thinking of its address block as a capital item. Exhaustion makes old paper suddenly expensive.
In June 2026 LACNIC published a call to organisations holding legacy IPv4 resources, asking them to formalise the relationship, update associated information and justify the right to use the resources. The notice gave organisations six months from publication, until December 2026, to contact LACNIC. It also said that LACNIC would cease providing registration services to organisations that do not contact it or cannot justify the right to use the resources after review. The related guidance says legacy resources can be transferred once the right to use them is justified and legal documentation supports the change of holder; after transfer they are no longer legacy and become subject to current policies and obligations.
That is a major scarcity event. It can improve the market by cleaning contacts, reducing hijack risk, surfacing dormant records and giving counterparties more confidence. It can also impose heavy documentation costs on holders whose continuity is real but poorly archived. The market value of a block can fall sharply if a buyer fears that regularisation will become a forced legal reconstruction of the 1990s. Conversely, a block that emerges from regularisation with clear recognition and current operational services may rise in value because counterparties no longer have to price title ambiguity.
The danger is forced conversion without enough sensitivity to regional records. A public institution may need to search archives, obtain ministry confirmation or reconcile old administrative decrees. A founder's estate may require probate or corporate succession evidence. A small operator may have old invoices, routing history and customer continuity but not polished transaction documents. A government reorganisation may be legally obvious domestically and opaque to a regional reviewer. If modern transaction-quality evidence is demanded for every historical fact, legitimate continuity can become unaffordable to prove.
The opposite danger is stale recognition. A legacy record that remains untouched indefinitely can be exploited by anyone with old credentials, informal access or a plausible letterhead. A buyer may acquire a lawsuit rather than usable capacity. Abuse reports may go nowhere. RPKI may be unavailable or uncertain. Reverse DNS may remain under the wrong authority. A party that has no legitimate control may try to lease or sell a block because the real holder is inactive. Dirty legacy space damages confidence beyond the individual case because buyers and networks learn to distrust a class of resources.
The right posture is patient finality. Patient, because old records require routes that reflect public-sector history, family succession, local corporate law and imperfect archives. Final, because a valuable resource cannot remain in a fog forever. LACNIC should publish evidence categories, distinguish weak archives from bad faith, explain what fact is missing when a claim fails, and offer review paths that small holders can understand. A legacy process that produces clear outcomes will reduce the market's title discount. A process that looks like a cliff will cause panic, rumours and defensive leasing.
Legacy regularisation also changes bargaining power. A holder that regularises before negotiating can sell or lease from strength. A holder that enters negotiation with unresolved legacy status sells uncertainty. A buyer may demand warranties, escrow, a lower price or control over the registry process. A broker may become indispensable not because it found a buyer, but because it understands how to manage proof. If the registry wants a cleaner market, it should reduce the premium attached to private procedural knowledge.
Continuity premiums: RPKI, reverse DNS and reputation
IPv4 scarcity is not only a question of address count. It is a question of continuity. A block is more valuable if it can keep working through transfer, lease, merger, succession, account cure and operational restructuring. LACNIC's hosted RPKI service has been operational since January 2011, and its delegated RPKI service since December 2019. Its reverse DNS service supports reverse resolution for IP addresses assigned to ISPs and other organisations in the region, with infrastructure distributed across multiple continents. These services tie registry recognition to operational trust.
RPKI matters because route-origin authorisation translates recognised resource control into cryptographic assertions that relying parties can use. LACNIC is not a router and RPKI does not solve every routing problem. But the certification relationship affects whether a prefix can be originated with confidence. A transfer that leaves ROAs confused, a lease that leaves the lessee dependent on an inattentive holder, or a dispute that interrupts certification can reduce the value of a block. In an increasingly filtered routing environment, clean RPKI is not ornamental. It is part of liquidity.
Reverse DNS has a different but persistent importance. Mail systems, logging practices, security teams, enterprise customers and diligence processes may treat reverse resolution as evidence of operational hygiene. Some uses are old-fashioned; some are still practical. A transfer or lease that cannot maintain clean reverse DNS can create customer trouble, reputation risk and support cost. If reverse delegation lags behind commercial closing, the buyer has acquired addresses that are not yet fully integrated into its service promise.
Reputation is the third continuity premium. A quarantined recovered block, a block with spam history, a prefix associated with abuse, or space that has been routed through dubious arrangements may require rehabilitation. That work takes time and affects customer onboarding. It may require delisting requests, upstream coordination, mail-system changes, new abuse contacts and careful monitoring. The market price of IPv4 should therefore reflect not just scarcity but operational cleanliness. Registry records, transfer logs and contact accuracy cannot remove all reputation risk, but they can make responsibility clearer.
Continuity matters most when networks change hands. An acquirer of an ISP does not merely want to know that the target has addresses. It wants to know whether the addresses can remain routed, certified, delegated and supportable after closing. A public-sector reorganisation wants services to continue while the legal holder changes. A data-centre operator wants customer migrations to avoid reputation shocks. A small island network recovering from a disaster may need urgent contact and routing-security changes, not a general review of its development virtue. In these cases operational continuity is not a privilege; it is the substance of the resource's value.
The registry can reduce continuity discounts by coordinating record changes with operational services. A transfer that changes the holder but leaves certification or reverse DNS in limbo is only partially settled. A legacy regularisation that updates a name but leaves obsolete contacts in dependent systems has not fully cleaned risk. A payment hold that blocks an operational correction may damage the reliability of the record the registry is trying to protect. Scarcity administration should treat recognition, RPKI, reverse DNS, abuse contacts and reputation-sensitive transitions as one settlement package.
Leasing again tests the system. If the registered holder retains formal control while a lessee uses the space, the lessee's ability to maintain RPKI and reverse DNS depends on contract, trust and responsiveness. A high-quality lease will specify authority, contacts, abuse handling, ROA changes, reverse delegation and end-of-term transition. A poor lease will rely on email favours. LACNIC need not audit every contract, but it should define the operational facts that must remain visible. That is how leasing becomes finance rather than fog.
There is also a continuity premium for public and essential services. A hospital network, university, public utility, local government, electoral body or emergency-service provider may never sell addresses, but it still depends on recognition. If a ministry changes name or an outsourcing contract moves operations, the registry should help lawful continuity appear in the record without turning the case into a broad judgement about whether the institution's use of IPv4 is economically admirable. Scarcity affects non-traders too because operational trust follows the record.
Cross-border proof and the price of finality
The region is full of cross-border facts. Corporate groups hold subsidiaries across several countries. Carriers buy customer bases, towers, fibre, data-centre capacity and managed-service operations. Content networks serve one country from another. Cloud platforms centralise infrastructure. Governments contract with foreign vendors. Family-owned ISPs sell to regional consolidators. Banks finance local networks from outside the country. IPv4 addresses follow these transactions awkwardly because the registry must translate local legal reality into regional recognition.
Documentation is the point at which that translation becomes cost. A reviewer may need to understand corporate registries, public decrees, notarised powers, board authorities, merger certificates, translated contracts, insolvency papers, tax records and succession documents. A document that is authoritative in one country may not resemble the form expected by staff in another. A common-law island company, a civil-law public entity, a family firm, a state-linked carrier and a multinational subsidiary may all be legitimate while producing different proof. The registry has to verify without imposing one legal culture as the default.
Cross-border transfers also depend on compatibility among registries. In inter-RIR transfers the source and destination registries must align on eligibility, evidence, timing and conditions. Each registry applies its own criteria. The parties bear the capital cost while institutions coordinate. If either side moves slowly or asks for another document after the other has accepted a package, the commercial settlement can slip. A registry-to-registry process is therefore not merely administrative. It is part of the financial closing mechanics.
The market consequence is a documentation discount. Blocks held by modern companies with clean records are more liquid. Blocks tied to old public entities, complex mergers, family succession or cross-border group structures trade at a lower price unless the recognition path is well understood. Some holders may avoid formal transfer and prefer leasing or operational delegation because the documentation burden feels too high. That may preserve short-term cash flow while weakening the public record. The registry should want the formal path to be more attractive than the informal one.
Evidence tiers would help. A routine name change should not be treated like a contested sale. A small intra-regional transfer between current members should not require the same proof as a legacy regularisation after decades of stale records. A public-sector reorganisation should have a route that recognises official acts. A family succession should have a route that respects local probate or corporate law. A high-risk case should receive stricter review. The point is not to lower standards. It is to stop low-risk cases subsidising the caution required for high-risk ones.
Finality also requires reasons. In a scarce market, a refusal can destroy value or force a distressed settlement. If LACNIC says a document is insufficient, the holder should know which fact remains unproved. If staff suspect a dispute, the parties should know what would resolve it. If an account issue blocks recognition, the link between the account issue and record integrity should be explicit. Opaque refusal creates a private tax because future counterparties will price uncertainty even after the immediate case is cured.
Language again matters. A decision explained in legal or technical terms that a small operator cannot understand is not fully reviewable. Translation is not only customer service; it is settlement infrastructure. Scarcity turns explanations into economic instruments. A clear explanation lets a holder gather proof, a buyer price risk and a lender assess whether a problem is curable. A vague explanation transfers value to those with the best informal contacts.
Finality is not the same as speed. A registry should sometimes say no. It should sometimes pause a file, require stronger proof or wait for a court or public authority. But it should be possible to tell whether the problem is fraud risk, missing authority, conflicting claims, policy ineligibility, payment status, operational inconsistency or staff uncertainty. A market can tolerate discipline. It cannot efficiently price mystery.
Market design without pretending to be a market regulator
LACNIC cannot avoid market design. Exhaustion made that impossible. Every rule about transfers, legacy conversion, account standing, need justification, holding periods, leasing visibility and operational delegation changes the cost of IPv4. The question is whether the market design is explicit, reviewable and connected to the registry's mandate, or implicit inside support-ticket practice and institutional discomfort.
There is a temptation to deny the market by invoking stewardship. Address resources are not ordinary property; therefore, the argument goes, treating them as capital is vulgar or dangerous. The premise is right and the conclusion wrong. Scarce resources administered through policy can still have market value. Refusing to acknowledge that value does not make the market disappear. It makes the market less transparent and gives more power to those with private knowledge, legal budgets and existing holdings.
There is an opposite temptation to treat every market outcome as efficient. That is also wrong. IPv4 scarcity can reward hoarding, opaque leasing, dirty blocks, forged documents, market concentration and speculation. A registry that abandons verification would undermine the trust that gives addresses their usable value. The right approach is not laissez-faire. It is disciplined utility governance: protect the record, publish the rules, measure the process, make operational responsibility visible and leave commercial merit to parties better placed to bear it.
Need justification should be examined in that spirit. It may remain part of adopted policy, but the community should be honest about what it does in a transfer market. It is no longer merely conservation of a common pool. It is a filter on who may convert money into recognised capacity. If the community wants that filter, it should explain the economic trade-off: less speculation and perhaps more stewardship, but also less liquidity, higher diligence cost and a possible advantage for incumbents that can document demand more persuasively. Market design improves when the trade-offs are explicit.
Holding periods deserve the same candour. A one-year restriction can reduce flipping and create stability. It can also impede restructuring after a failed deal or business shock. That may be acceptable. But the reason should be stated as anti-speculation policy, not hidden as administrative inevitability. Operators can plan around clear restrictions. They cannot plan around a climate of suspicion.
Leasing visibility should be designed as an operational control, not as a morality test. If LACNIC worries that leases make contacts, RPKI and abuse responsibility unclear, it should specify the information and authorisation needed for those functions. If it worries that a lease is effectively a transfer, it should define the trigger. If it dislikes lease prices, it should resist the temptation to act on that dislike. Price is a market signal, however uncomfortable. Responsibility is the registry's concern.
Payment rules should be designed as collection and continuity tools, not as hidden asset-freezing powers. There should be consequences for nonpayment. But there should also be clean cure paths, proportional service impacts and special care where operational safety is at stake. The registry should know whether payment failures cluster around certain banking routes, wire-fee shortfalls or jurisdictions. If they do, the institution has learned something about liquidity rather than merely delinquency.
Legacy regularisation should be designed as title improvement, not confiscation by paperwork. Some claims will fail. Some resources may be abandoned or impossible to justify. But the process should visibly distinguish fraud, absence, weak archives, public-sector complexity and curable documentation gaps. The economic aim should be to reduce the title discount attached to old resources while protecting against false claims.
This is a narrow view of registry power, not a small one. It asks LACNIC to be more serious about the economic effects of technical administration, while being less tempted to become a shadow regulator of address use. That combination is difficult. It is also the best way to preserve both market confidence and the development mission. A registry that settles facts reliably is more useful to regional development than one that tries to correct every market outcome through hesitation.
What a serious scarcity regime would publish
A mature scarcity regime needs data because markets price what they can see. LACNIC already publishes useful factual background, including waitlist information, transfer materials and policy text. The next step is not more narrative authority. It is operational disclosure that helps members, buyers, lessors, lenders and public bodies understand the risk premium attached to scarcity.
Transfer timing should be the first measure. Average processing time is too blunt. The market needs medians, long-tail distributions and reasons for delay, separated by routine intra-regional transfer, inter-regional transfer, merger update, legacy regularisation, public-sector succession, account recovery, suspected fraud, disputed authority and applicant-caused incompleteness. Confidential details can remain private. Aggregate categories would still tell participants whether they are facing an ordinary queue, a high-risk review or an unusual bottleneck.
Documentation burden should be visible. LACNIC could publish evidence tiers and examples for common cases: contact update, name change, merger, intra-regional sale, inter-regional transfer, lease-related operational delegation, legacy holder regularisation, public-body reorganisation and disputed resource review. This would not require exposing member files. It would reduce the advantage of repeat players and brokers whose value comes partly from knowing what staff tend to ask for.
Payment friction should be measured. How many members enter surcharge or recovery? How many cure quickly? How often are shortfalls caused by intermediary fees? Do certain jurisdictions or payment routes recur? How many resource actions are delayed because of account standing? These facts would help separate strategic nonpayment from financial plumbing. They might also suggest better notices, payment alternatives or cure rules.
The waitlist should be treated as an economic indicator. Members need to understand not only their place in line but the pace of recovered-space flows, quarantine effects, assignment sizes and the practical value of waiting. A waiting time measured in decades tells operators that transfer and lease markets carry the real burden of IPv4 continuity. The registry should not pretend otherwise.
Legacy regularisation should be reported in aggregate. After the 2026 call, the region should know how many organisations respond, how many cases are resolved, how many require more documentation, how many involve public bodies, how many end with services withdrawn, and what recurring evidence problems appear. Without that visibility, a clean-up process can become a rumour machine. With it, counterparties can distinguish systemic risk from isolated difficulty.
Operational continuity should be measured alongside record changes. A transfer is not fully successful if RPKI, reverse DNS or contact data lags behind. A legacy update is incomplete if old operational contacts remain in dependent systems. A lease-related delegation is weak if responsibility cannot be found during an abuse incident. The scarcity market prices continuity whether or not the registry reports it. Better reporting would reduce the discount.
Participation cost is also relevant. LACNIC's policy process is community-based, but participation is not equally cheap. Meeting attendance, remote participation, language availability, election turnout and proposal engagement by country or member class would help show whether scarcity rules are being shaped by a narrow subset of operators. Perfect representation is impossible. Blindness to participation cost is optional.
The point of measurement is not to create another bureaucratic ceremony. It is to lower the risk premium. Strict rules are easier to accept when their operation is visible. Buyers can price evidence requirements. Sellers can prepare before negotiating. Small operators can decide when to seek help. Public bodies can plan archives and approvals. Banks can understand whether a problem is curable. Transparency is a liquidity tool.
The bargain after abundance
The post-abundance bargain for LACNIC is simple to state and difficult to administer. The registry should protect the truth of the record, and in return it should not use recognition as discretionary blessing over the economics of scarcity. It should verify identity, authority, provenance, dispute status, payment relationship and operational responsibility. It should support RPKI, reverse DNS and contact continuity. It should regularise legacy records with patience and finality. It should implement transfer rules clearly. It should collect fees without turning payment friction into unnecessary asset freezes. It should promote IPv6 without pretending that IPv4 working capital has lost its present value.
That bargain rejects two fantasies. The first is nostalgia for an allocation world that is gone. Waiting lists and tiny recovered blocks cannot supply the region's ordinary IPv4 needs. The second is market romanticism. An ungoverned market would dirty the record, reward fraud, obscure responsibility and raise the cost of every legitimate transaction. The useful middle is a registry that makes scarcity settleable.
Latin America and the Caribbean make the middle course especially important. In a single wealthy jurisdiction, participants might compensate for registry friction with courts, lawyers, lenders and specialised advisers. In this region, those substitutes are uneven. Some operators can absorb uncertainty; others cannot. Some can pay in dollars easily; others cannot. Some can produce corporate records at once; others must reconstruct a chain of public or family history. A predictable registry can stabilise transactions across those differences. An opaque registry can magnify them.
The economics of IPv4 scarcity will fade only when IPv6 deployment and service assumptions make IPv4 less central to revenue, reachability and customer expectation. That transition is under way, but it is incomplete. Until then, the registry's settlement role remains economically consequential. The question is not whether LACNIC influences the market. It does. The question is whether it does so by providing reliable finality, or by adding a regional scarcity premium through uncertainty.
A mature scarcity regime would be unsentimental. It would accept that addresses have market value without confusing them with ordinary property. It would accept that leasing can be useful without ignoring responsibility. It would accept that legacy holders may have legitimate continuity without allowing stale records to persist indefinitely. It would accept that payment discipline is necessary without ignoring exchange controls and banking friction. It would accept that development matters without converting the registry into a planner of address use.
It would also recognise the balance-sheet asymmetry between IPv4 and IPv6 during transition. IPv6 is an investment in future scale, better architecture and lower dependence on scarce IPv4. IPv4 continuity is often the condition that keeps present revenue available to finance that investment. If IPv4 liquidity is impaired, operators may not automatically accelerate IPv6. They may postpone both IPv6 work and customer growth because cash and management time are trapped in shortage management. The transition is helped not by pretending the old resource has no economic value, but by making it easier to settle, secure and retire from the centre of the business over time.
LACNIC's strongest role is therefore narrower than a development slogan and more important than a help desk. It is the institution that lets scarce-number claims settle across borders, languages, currencies, old corporate histories and uneven capital markets. That is a serious economic function. The less it resembles discretionary permission, the more it will support the regional internet economy that allocation alone can no longer supply.