The transaction that waits for a record
The scene is not a finance ministry, a central bank or a courtroom. It is a closing spread across email threads, bank portals, lawyers' marked documents, a broker's messages and a network operations channel. A Latin American or Caribbean network has found a counterparty for a block of IPv4 addresses. The seller may be a small access provider with more address space than it can now use, a carrier group tidying up after an acquisition, a hosting company trying to turn dormant inventory into cash, a public body whose old records have finally been regularised, or a firm that needs liquidity more than it needs unused numbering capacity. The buyer may be a regional cloud platform, a mobile group, a data-centre operator, an enterprise-services provider, a lender's borrower, or another network trying to keep customers reachable while the world moves toward IPv6 more slowly than commercial demand requires.
Everyone around the transaction has a different reason to care about the same record. Counsel wants signatories, succession documents, asset schedules, warranties and escrow triggers to match. A bank wants to know why money is moving across borders for an intangible network resource, whether the counterparty is acceptable, whether supporting papers explain the payment, and whether compliance questions sit behind either company. The buyer's upstreams want to know when they can accept route-origin data. The seller wants funds released. The buyer wants the block to become usable, not merely promised. Engineers want RPKI, reverse DNS, public registration data, abuse contacts and routing authority to line up before customers are moved onto the space.
At the end sits the registry. The private bargain may be signed. The funds may be ready. The network plan may be sound. Yet an IPv4 block acquires its full economic value only when the authoritative registry record recognises the movement. Until then the buyer owns a claim, an undertaking or a contractual expectation. It does not yet hold the settled position that banks, counterparties, route validators, anti-abuse teams, lenders, upstream networks and other regional registries can rely on. In this market, the last administrative act has the effect of settlement.
That is the sense in which LACNIC belongs in an economics of capital control. The phrase should not be misunderstood. LACNIC is not a state, does not run a foreign-exchange regime, does not tax capital flight, does not set a price for a /24, and does not decide the monetary policy of any country in its service region. It is the regional internet registry for Latin America and the Caribbean. Established in Uruguay in 2002, it administers IPv4, IPv6, autonomous system numbers and reverse resolution for a region whose public material describes more than 13,000 network operators across 33 territories. Its formal business is not macroeconomic direction. It is the accurate, secure and coherent administration of internet number resources.
Scarcity gives that administrative role an economic charge. A record keeper for a resource in abundance is a service utility. A record keeper for a scarce and tradeable input becomes part of the capital system around that input. The registry need not seize money to shape economic movement. It need only decide when address value will be recognised, under what proofs, after which payments, through which accounts, with what cross-registry coordination, and with what operational continuity. The control is not exercised at the bank account. It is exercised at the record.
The point is not that LACNIC should stop verifying transfers. A registry that cannot verify source authority, recipient identity, dispute status, documents, policy eligibility and operational continuity would be a danger to every legitimate holder. Fraudulent transfers, stale contacts, hijacked accounts, double claims, confused corporate succession, incorrect RPKI states and broken reverse DNS would erode trust and depress value. The question is where the line sits between settlement and economic permission. A settlement utility asks whether the record can safely and truthfully move. A capital-control checkpoint asks, sometimes without saying so, whether the movement is institutionally comfortable, regionally desirable or commercially deserving.
The risk is subtle because every lever has a proper administrative name. Account standing protects the service relationship. Documentation prevents theft. Recipient review preserves policy discipline. Transfer logs create transparency. Inter-regional coordination avoids conflicting records. Fees fund the institution. RPKI and reverse DNS preserve operational trust. But those same levers determine whether scarce IPv4 value can cross an organisational, regional or financial boundary. In a region marked by small island dependency, large-country gravity, volatile currencies, correspondent-banking friction, multilingual participation and uneven state capacity, that discretion is not an abstraction. It is part of the price.
Scarcity changed the registry's economic role
IPv4 addresses are awkward assets. They are not land, shares, spectrum licences or ordinary software. They exist inside a global registry system whose first purpose is uniqueness and operational coordination. The language around them remains deliberately cautious: allocation, assignment, stewardship, need, registration and service relationship appear more often than ownership. Lawyers may debate the nature of the right. Operators are more practical. They ask whether the block can be routed, secured, transferred, leased, financed, integrated after a takeover, used for customers, protected in reputation systems and recognised by the authoritative registry.
Markets usually settle vocabulary arguments by behaviour. If a resource is scarce, productive, transferable under rules, necessary for revenue and recognised by a trusted ledger, it behaves like capital even if its legal clothing is unusual. A lender considering a network expansion will ask whether the borrower has address capacity to support customers. A buyer will ask whether a target's address holdings are clean enough to integrate. A cloud provider will ask whether it can obtain enough IPv4 reachability for clients that still depend on it. A small network will ask whether unused space can fund equipment, resilience, debt reduction or a strategic retreat. An acquirer will discount space that is operationally messy, tied to old records or uncertain under registry review.
LACNIC's own exhaustion position explains why mobility now matters so much. Its IPv4 waiting list was created on August 19th 2020, when the last available IPv4 address block was assigned. LACNIC's public waiting-list material estimates, from historical recovery patterns, that the last request in the queue faces at least eighteen years of waiting and can receive at most 1,024 IPv4 addresses. Recovered blocks are unpredictable. Waiting-list positions are not transferable. Organisations must already have IPv6 resources to join. Blocks issued at that stage will have spent at least six months in quarantine, and the recipient remains responsible for any later rehabilitation if reputation problems appear.
That queue may be a fair administrative device, but it is not a source of timely working capital. It cannot meet a data-centre launch, a public-sector continuity requirement, a mobile translation platform, a merger integration, an enterprise contract, an email-reputation problem, or a customer migration scheduled for this quarter. Once the official queue is measured in decades, marginal capacity must come from another holder, from a corporate transaction, from a lease, from a transfer, from old inventory, from upstream arrangements or from engineering around shortage. The market is no longer mainly about distribution from a free pool. It is about the convertibility of recognised control.
Convertibility has several dimensions. Can a seller turn recognised control into money? Can a buyer turn money into recognised control? Can an operator in one country buy from a holder in another? Can a Caribbean network monetise unused space without the transaction costs swallowing the value of a small block? Can a Latin American buyer close before exchange rates, bank approvals, budget windows or renewal deadlines change the economics? Can a foreign buyer trust that an inter-regional transfer will settle? Can operational services follow the registry record quickly enough for the block to be useful? These are capital questions in the practical sense. They determine whether an address block can move from balance-sheet potential to economic use.
The analogy with capital control is therefore not a flourish about governments. In a conventional capital-control story, the state controls the conversion or movement of money across borders. In registry economics, the registry controls conversion of private bargain into recognised number-resource position. The bank may move dollars. The contract may allocate risk. The escrow may set conditions. But if the registry does not recognise the movement, the buyer does not have clean capacity. If recognition is delayed, value is delayed. If recognition is uncertain, value is discounted. If recognition depends on judgement that repeat players understand better than occasional participants, value migrates toward those who can manage judgement.
This is particularly important in Latin America and the Caribbean because IPv4 value does not sit in one homogeneous economy. Brazil and Mexico contain large networks, big buyers, mature advisers and repeated registry experience. Argentina, Chile, Colombia, Peru and other substantial markets have sophisticated operators but also different banking and currency pressures. Central American markets include smaller networks, public-sector relationships and cross-border operating groups. The Caribbean includes island economies where a /24 can support hotels, business services, local hosting, payment systems, emergency communications or public customers. A resource that looks small in a global market can be material to a local operator's balance sheet.
Scarcity also changes how old policy language lands. Conservation, need and responsible use made intuitive sense when the registry allocated scarce stock from a common pool. They still matter for record integrity and fair treatment. But after exhaustion, those words can drift. A rule that once rationed new supply can become a condition on market settlement. A request that once established efficient use can become a business-plan examination. A concern about hoarding can become discomfort with liquidity. A development mission can become regional retention by delay. The economic burden of that drift is not evenly distributed. Large buyers can hire counsel, wait longer, carry inventory and manage paperwork. Small networks often cannot.
The answer is not to pretend IPv4 should be unregulated capital. It is to recognise that registry recognition has become the decisive conversion point. A sound regime should protect the record, prevent fraud and keep operational trust while avoiding hidden market direction. It should let the registry be a narrow, reliable ledger rather than an economic ministry with better terminology.
What LACNIC actually settles
The most accurate description of LACNIC's transfer function is ledger and settlement utility. It is a ledger because it records which organisation is recognised for a number resource, who can act for that organisation, which contacts are visible, where reverse resolution is delegated, what service relationship applies and what history supports the present state. It is a settlement utility because private transactions are not fully settled until that ledger accepts the change and the operational services around the record can follow.
LACNIC's public transfer rules make this clear. IPv4 block transfers are allowed between local internet registries and end users, both inside the LACNIC region and between LACNIC and other regional registries. The minimum transferable block is a /24. A recipient in the LACNIC region must justify the IPv4 resources before receiving a transfer, using the applicable rules for initial or additional allocation or assignment. LACNIC or the corresponding registry verifies the holder of the resources and checks that they are not involved in a dispute. In an intra-regional transfer the parties submit a signed legal document supporting the transaction. In an inter-regional transfer the required documentation is agreed between the two registries. Once the transfer is complete, LACNIC modifies the resource information to reflect the new holder.
Those are not merely clerical steps. They define the economic attributes of the asset. A /23 that can move today is different from a /23 under a holding restriction. A legacy block entering LACNIC is different after it loses legacy status. A seller that transfers addresses becomes ineligible to receive IPv4 allocations or assignments from LACNIC for one year from the transaction date. Addresses that have been transferred may not be transferred again, in whole or part, for one year from the date in the transfer log. LACNIC allocations or assignments may not be transferred for three years after the allocation or assignment date. A buyer inside the region must pass recipient review. A seller with a disputed record cannot close like a seller with clean authority. The market prices these differences because they change liquidity, risk and timing.
The public process pages add another layer. For intra-regional transfers, the offering organisation's administrative contact must complete the form. LACNIC may request documentation confirming that the applicant is authorised to transfer and may use outside collaborators to certify authenticity. Approved parties sign a transfer agreement and joint order. If the recipient has not previously received LACNIC resources, or if it holds legacy resources, it must sign a service agreement. Administrative fees depend on block size, with one category for blocks from /24 up to smaller than /19 and another for /19 and larger blocks. A US$200 down payment is required before justification is analysed and is not refunded if justification fails and the transfer is not approved. Both sides must be current with contractual obligations where applicable.
For inter-regional transfers, the process is plainly cross-border settlement, even though the border is institutional rather than national. A transfer from LACNIC to another registry begins with verification by LACNIC, possible documentation requests, pre-approval, notice to the destination registry, analysis by that registry, signature of a transfer order and coordinated movement. A transfer from another registry into LACNIC begins with information from the source registry, followed by LACNIC contact with the receiving organisation, documentation requests and need justification. LACNIC warns that because resources move from one registry to another, services such as reverse DNS or RPKI may be affected and not immediately available.
The transfer log matters too. LACNIC must maintain a publicly accessible record showing the transaction date, the organisation that originated the transfer, the recipient, the transferred addresses and, for inter-regional transfers, the source and destination registries. The log is not a price tape. It does not disclose the private consideration. But it is market memory. It shows movement, parties and timing. It confirms that registry recognition has occurred. It also creates the date from which later restrictions run.
LACNIC is careful to say that it does not participate in the commercial transactions between parties on its IPv4 transfer listing service. That service lists possible offerors, possible recipients and optional brokers, charges an administrative fee, keeps participation active for a year and makes the information accessible only to participating organisations. Broker participation is optional. LACNIC does not audit broker services and is not liable for them. This boundary is sensible. A regional registry should not become a broker, price setter or guarantor of private bargains.
But staying out of the bargain does not mean staying out of the economics. A clearing house may not negotiate the trade and still determine whether the trade settles. A land registry may not set the price and still determine whether title can be relied on. LACNIC's power is of that kind. It is strongest when it verifies authority, applies adopted rules, records the movement, maintains operational continuity and makes enough information available for the market to trust the result. It is weakest when the same administrative checkpoints express discomfort with price, buyer type, seller motives, leasing, foreign demand or the continued commercial need for IPv4.
The legitimacy of a settlement utility depends on nexus. Does a condition protect the truth, uniqueness, security or continuity of the record? Or does it govern the economic desirability of the transaction? The first is a registry function. The second is market direction. The distinction sounds clean in prose and difficult in real files. A forged signature is easy. A corporate succession across old names, thin public records and multilingual documents is harder. A recipient that cannot explain any use deserves scrutiny. A recipient whose explanation differs from old allocation-era expectations may simply be acting rationally in a transfer market. Hard cases are precisely why the boundary must be public, reasoned and reviewable.
Recognition is the control point
Capital control by recognition is quieter than confiscation and easier to defend than an outright ban. It does not need a slogan. The registry does not take the asset away. It determines when a new economic fact becomes visible to the authoritative record. If recognition is delayed, the capital remains trapped in escrow, discount, dispute or operational uncertainty. If recognition depends on a judgement that is not well explained, the discount rises. If recognition is predictable, the market can price it. The same mechanism that protects a ledger can become a hidden tax.
Account standing is the first stage. If a seller or buyer is not current with contractual obligations, the transaction may not proceed. That protects LACNIC from becoming an unpaid service provider and prevents parties from using transfers to escape obligations. It also means that an invoice, a renewal date, a bank fee, a short receipt or a curable payment problem can stand between a private contract and realised value. In countries where firms earn in local currency but pay registry charges in dollars, or where public purchasers need formal approval to send funds abroad, that is not trivial.
Documentation is the second stage. LACNIC may ask for proof that the administrative contact or applicant is authorised. In merger and acquisition cases, public guidance asks for a legal document confirming the transfer of assets, a detailed inventory of assets used to keep the IPv4 space in use, and a list of clients and numbering plans justifying need. These are real record-protection questions. They also impose fixed costs. Fixed costs bite hardest at small block sizes, in jurisdictions with slower corporate registries, in public-sector successions, and among operators that do not have in-house counsel or repeated transfer experience.
Recipient review is the third stage. A recipient inside the LACNIC region must justify the IPv4 space to be transferred. During the allocation era this was natural: the registry was distributing scarce stock and needed to ration it. In a transfer transaction the recipient is paying another holder rather than drawing from a free pool. Willingness to pay is not perfect evidence of network need, but it is evidence. It shows that the buyer is prepared to spend scarce capital, carry opportunity cost, support customers and bear address-continuity risk. A need test that stays narrow can prevent sham transactions and policy evasion. A need test that expands can become a private planning approval.
Timing is the fourth stage. Delay is not a neutral administrative unit. In a high-inflation or currency-stressed economy, a month may change the exchange rate, the financing cost or treasury permission. A bank compliance window may expire. A public purchaser may lose budget authority. An escrow deadline may require amendment. A seller may accept a lower price to keep a buyer. A buyer may choose a more expensive supplier in another region because the timing risk looks smaller. In scarcity markets, time is part of capital cost.
Inter-regional compatibility is the fifth stage. A buyer outside the region may be funded and eligible under its own registry. That is not enough. LACNIC must verify the source, the destination registry must accept the recipient, documents must satisfy both sides, and operational services must transition. This is not a currency border, but it can act like an asset border. A LACNIC-region seller may therefore be exposed to another region's eligibility culture even when its own authority is clean. A LACNIC-region buyer importing space may face LACNIC review after the source registry has done its part.
Operational recognition is the sixth stage. RPKI, reverse DNS, contacts and public registration data convert the recognised record into functioning network capacity. A block whose holder field has changed but whose route-origin authority, reverse resolution or abuse contacts remain unsettled is not the same economic thing as a block with clean operational settlement. LACNIC's warning that reverse DNS or RPKI may be affected in inter-regional transfers is therefore a market warning, not merely a technical footnote.
Together these stages define capital control at the registry layer. They do not say that money may not leave. They say that value in a scarce resource will not be recognised until account, document, recipient, timing, cross-registry and operational requirements have been satisfied. Some requirements are essential. Some may be excessive. The important fact is that they act on mobility.
This framing should not be confused with hostility to control. A registry without controls would be worse. Forged transfers, undisclosed disputes, false succession, stale contacts, wrong ROAs, broken reverse DNS and account hijacking would make address markets more dangerous and legitimate operators poorer. The economic question is not control versus no control. It is whether each control is tied to the registry's proper settlement function.
The proper function is narrow: uniqueness, authority, record accuracy, dispute containment, clear policy compliance, security-state continuity, contactability and legal obligation. The improper function is broader: dislike of a high price, suspicion of a seller's profit, discomfort with a foreign buyer, hostility to leasing, preference for one type of operator over another, pressure to keep resources inside a local market, or an attempt to force IPv6 adoption by making IPv4 recognition harder. The first is settlement. The second is hidden industrial policy.
Proof, language and the cost of a clean file
Documentation is often treated as a neutral burden: everyone must prove authority, therefore everyone is equal. In practice proof has a fixed cost, and fixed costs are distributional. A large carrier with counsel, registry staff and previous transfer experience pays the cost once and reuses the competence. A small Caribbean provider selling a /24, a family-owned ISP whose founder is no longer involved, a municipal network cleaning up an old record, or a university whose address history predates its current administrative structure experiences the same request as a major event.
The LACNIC region is not one paper environment. Spanish, Portuguese and English all matter. Uruguay is LACNIC's legal home, and Spanish is the language in which original legal material may carry special weight when translations differ. Brazil supplies a large Portuguese-speaking technical and commercial community. The Caribbean includes English-speaking operators whose local corporate documents may come from legal systems very different from those in South America. Public networks, universities, cooperatives, family-owned access providers, privatised utilities and cross-border carrier groups all create documentary patterns that do not fit one private-company checklist.
That texture reaches the closing table. A historical administrative contact may be a founder who has died, sold the company or moved on. A public network may have shifted from one ministry to another. A small island operator may hold records that local banks understand but foreign counsel finds thin. An Argentine buyer may face foreign-currency procedure while trying to meet a non-refundable transfer down payment. A Brazilian group may acquire a smaller provider whose address records still point to an old legal name. A Caribbean operator may have to explain to both bank and registry why a locally important block is moving through a structure designed for global uniqueness rather than local corporate convenience. None of these cases is suspicious by itself. Each can become expensive if proof categories are unclear.
LACNIC must ask for evidence. The alternative is not acceptable. Scarcity creates incentives for theft, forged authority, false succession and opportunistic claims over old resources. Evidence should, however, be categorical, proportionate and predictable. Market participants need to know the ordinary evidence for routine transfer, asset sale, share sale, merger, acquisition, public-sector succession, insolvency, name change, relocation, account recovery, legacy regularisation, disputed authority and inter-regional import or export. They need to know accepted substitutes when a jurisdiction lacks a familiar document. They need to know when translation is required, when certification matters, who may sign, what triggers outside authenticity checks and what timeline is typical after a complete file.
Such a map would not reduce LACNIC to a mechanical clerk. It would make judgement visible. Staff would still handle hard cases. Applicants would know whether the problem is missing authority, missing asset continuity, unresolved dispute, incomplete recipient justification, payment status, signature mismatch or registry-to-registry dependency. A buyer could price the risk. A seller could clean records before searching for a buyer. Counsel could draft escrow conditions around evidence categories instead of a vague condition called registry approval.
Multilingual clarity is part of the same issue. A rule that exists in translation but is practically understood through one language imposes an invisible tax. If Spanish-language text prevails in a conflict, non-Spanish-speaking participants need especially clear explanations of risk points. Portuguese-speaking Brazilian operators should not have to rely on informal Spanish interpretations. English-speaking Caribbean networks should not discover during a transaction that a translated instruction missed a nuance staff apply. Language is not public relations. In a scarce address market, language is market infrastructure.
The burden is temporal as well as financial. A request for additional documentation may sound ordinary to an analyst. To a seller with a financing deadline, it is a capital event. To a buyer awaiting bank approval, it may mean renewed compliance review. To a small operator paying counsel by the hour, it may reduce the net sale price. To a public purchaser, it may trigger a new approval cycle. Documentation therefore sets the spread between theoretical address value and realisable value.
The aim should be proof without private tolls: enough to protect the record, not so much that formal recognition feels more expensive than informal side arrangements. If clean participants find the formal path obscure, the market does not become safer. It becomes more reliant on brokers, private letters, leases, delayed updates and informal authority chains. The registry then sees less of the operating reality it is supposed to make reliable.
Need review in a transfer market
Recipient review is the most delicate form of recognition control because it can be defended in technical language while operating as economic permission. LACNIC policy requires a regional recipient to justify IPv4 resources before receiving a transfer, applying the relevant rules for initial or additional allocation or assignment. Those rules include concepts such as immediate necessity, utilisation plans, previous utilisation, IPv6 resources or progress, subnetting plans and, in some end-user cases, expectations about announcing the space from the applicant's own autonomous system to at least one other autonomous system.
The historical logic is clear. During the allocation era, a registry rationed a scarce common pool. It needed to know whether a requester had real operational need, whether previous space was efficiently used and whether a plan was credible. Without such criteria, early and large applicants would have consumed more than their share and the registry would have lost control of a finite coordination resource.
The transfer era changes the premise. In a transfer, the recipient is not asking LACNIC to hand over new free-pool supply. It is buying or otherwise receiving recognised control from another holder, subject to policy. The buyer's willingness to pay is not conclusive proof of technical need. Some buyers can be speculative. Some may seek inventory because they expect prices to rise. Some may structure demand through affiliates. But payment is not irrelevant. It means the buyer is prepared to use scarce capital, carry opportunity cost, satisfy customers, take operating risk and bear the cost of address continuity. A registry that ignores this signal applies rationing logic to market settlement.
There are legitimate reasons for review. LACNIC may want to prevent shell recipients, false transfers, immediate arbitrage of recently issued resources, evasion of holding periods, misuse of the transfer channel to bypass waiting-list restrictions or movements that directly contradict adopted policy. It may want to confirm that the receiving organisation is real, accountable and able to maintain contacts, reverse DNS and security data. It may want enough operational explanation to distinguish a serious network requirement from a paper vehicle.
The danger begins when review moves from "can this recipient responsibly receive and use the resource under policy?" to "does this recipient's commercial plan deserve recognition?" The second question is capital allocation by another name. It lets the registry judge timing, customer mix, growth assumptions, inventory preference, leasing plans, foreign relationships or business line. It also favours applicants fluent in policy grammar. A large buyer can write a polished utilisation narrative. A small provider may have equally real demand and less ability to make it sound official.
This distinction is not theoretical. A small operator may need addresses for a hotel group, a public contract, business customers, a local hosting platform, NAT pressure, legacy firewalls or upstream requirements. A group serving several countries may centralise address administration in one entity while operational use appears across several networks. A buyer in a currency-stressed country may hold inventory as a hedge against future price and exchange-rate movement. A regional cloud provider may need address continuity because customers cannot move all dependencies at once. These are ordinary responses to scarcity. A review process that cannot understand them becomes a control on capital rather than a test of record integrity.
A narrow review would ask concrete questions. Is the recipient a real organisation? Is the requested amount within policy? Is the stated use coherent enough to avoid a sham? Are previous resources, if any, used or recorded in a way that supports additional need under the applicable rule? Does the transaction evade a one-year or three-year restriction? Is there a waiting-list or recently allocated resource issue? Can the recipient sign the service agreement if required? Are contacts, RPKI and reverse-DNS responsibilities clear?
A broad review asks questions it should not. Is the buyer too large? Is the buyer too financial? Does the price look high? Would the registry prefer the seller to keep the block in the region? Should the buyer lease instead? Is the seller earning a windfall? Should IPv4-dependent services be discouraged because IPv6 is the long-term architecture? Such questions may be tempting in a scarce market. They are not settlement questions unless the community has adopted explicit rules that say so and accepted the cost.
IPv6 advocacy should sharpen this boundary, not blur it. LACNIC is right to promote IPv6 deployment, training and operational competence. IPv6 is the architecture for internet growth. But IPv6 is not a wand for today's installed base. Customers, applications, enterprise systems, public-sector procurement, security appliances, mobile translation, old firewalls, email reputation and external counterparties still create IPv4 demand. Making IPv4 transfers harder does not by itself create IPv6 readiness. It may trap working capital that could otherwise fund transition.
Payments, currencies and account standing
The most prosaic controls can be the most capital-sensitive. LACNIC's transfer pages say both offering and receiving organisations, when applicable, must be current with contractual obligations. Its payment material says payments should be made in US dollars, that payers are responsible for ensuring the full amount reaches LACNIC, that wire-transfer fees must be considered, and that bank processing time should be taken into account. For wire transfers, the banking path runs through Uruguay and a correspondent bank in the United States. Online payment options exist, but the official advice still reflects a cross-border environment where timing, fees and receipt amounts matter.
For a large multinational this is treasury administration. For a small or mid-sized network, it can be a constraint. A company may earn in local currency and pay in dollars. A public-sector buyer may require budget approval. A Caribbean operator may face correspondent-banking de-risking or extra compliance questions. A firm in an inflationary economy may have a narrow window to convert local revenue into dollars. A bank may ask why money is being paid to a foreign counterparty for addresses, why a registry down payment is non-refundable, why a broker is involved, or why escrow release depends on a record held by a non-state utility in another jurisdiction.
None of this is LACNIC's fault. The registry does not create currency volatility, exchange restrictions, correspondent-banking caution or local procurement rules. But it can amplify or reduce their effect. If account standing is treated as a blunt gate, a curable payment issue can freeze capital movement. If renewal timing is unclear, a seller may discover too late that a transfer or return needed to be requested before a renewal invoice date. If the received amount is short because a bank fee was deducted, an applicant may be current in intention but not in accounting. If a category change after receiving resources creates a complementary invoice for the months remaining until renewal, the buyer's cost structure may change close to closing.
The economic issue is not whether LACNIC should collect fees. It should. A registry that cannot fund staff, security, member support and operational services cannot be reliable. The issue is whether fee collection is separated from record integrity. A transaction-fee defect is different from a dispute over resource authority. A membership renewal issue is different from a false signatory. A bank delay is different from non-cooperation. A category adjustment is different from a contested holder. If all are experienced as one undifferentiated not-current state, account administration becomes an asset gate.
The market would benefit from finer states. LACNIC could distinguish paid, pending bank receipt, underpaid because of charges, renewal at risk, complementary invoice pending, contractual defect unrelated to the transfer, contractual defect blocking service, legal hold and disputed authority. It could release aggregate information about payment-related delays without exposing private accounts. It could warn applicants clearly when renewal clocks intersect with transfer timing. It could tell parties when a payment defect can be cured without losing place and when it prevents recognition.
That would not be leniency. It would be settlement hygiene. A bank does not become more prudent by calling every issue compliance. A registry does not become more authoritative by calling every account defect a transfer block. Precision improves collection because members know what must be cured. It improves market confidence because buyers and sellers can tell whether a delayed closing is an accounting problem, a legal problem, a recipient-review problem or a record-integrity problem.
Currency reality also affects foreign-buyer confidence. A buyer outside the LACNIC region considering LACNIC-region supply will price bank, fee and documentation risk alongside registry risk. A seller in the region will price the risk that a foreign buyer's bank slows payment while registry review continues. A domestic buyer may compete against a foreign buyer that can absorb these frictions more easily. In a scarce market, the party with cheaper dollars and better compliance staff has an advantage. Registry process should avoid adding unnecessary premium to that advantage.
Small sellers feel the other side of the same problem. A /24 may be modest in the global address market and material on a small operator's balance sheet. If payment friction delays closing, the seller may lose the equipment purchase, debt payment or resilience investment that motivated the sale. If the buyer senses distress, the buyer may renegotiate. Capital control by recognition therefore affects not only buyers who want addresses but sellers who need liquidity.
Borders inside a borderless asset
Inter-regional transfers reveal the capital-control analogy most plainly. A block in the LACNIC region may have its highest-value buyer outside the region. A block in another region may be needed by a LACNIC-region operator. Either movement requires more than private agreement. The source registry must verify the holder and eligibility. The destination registry must accept the recipient under its rules. Documentation must satisfy both sides. Operational services may not move immediately. The transfer becomes a cross-border settlement event, although the border is institutional rather than national.
Regional internet registries are service territories, not economic states. Latin America and the Caribbean are not one treasury, one banking system or one exchange-control area. Yet LACNIC's service region creates a recognisable boundary for address mobility. A resource crossing into or out of that boundary must pass through compatibility between registries. Inter-regional movement can widen the buyer pool for sellers and help regional operators obtain capacity when local supply is thin. It also places institutional consent directly inside the asset path.
There are legitimate reasons for this. The same globally unique block cannot sit in two authoritative records. The source registry must be satisfied that the holder is real and not disputed. The destination registry must know the recipient and apply its own rules. RPKI, reverse DNS and contact data must transition without creating a period of ambiguity. If legacy status changes on entry into LACNIC, the buyer needs to understand the new service relationship. If a transfer order and fee payment occur after pre-approval, escrow must reflect that sequence.
The design question is whether compatibility is based on record integrity or on deeper economic ideology. Record compatibility asks whether two registries can coordinate a truthful, unique and secure transfer. Ideological compatibility asks whether the other region shares a view on need, conservation, transfer morality, leasing or out-of-region use. The first is necessary. The second can become protectionism disguised as stewardship.
LACNIC's architecture retains recipient justification for LACNIC-region recipients. Applied narrowly, that can confirm that the recipient is real and the use credible. Applied broadly, it can stop capital at the registry border because the buyer's plan does not resemble allocation-era demand. Likewise, an outbound transfer may depend on the destination registry's analysis of the recipient. A LACNIC-region seller may therefore be exposed to another region's eligibility culture even when the seller's own authority is clean.
The practical problem is timing. Inter-regional transactions combine two queues, two document cultures, two service dependencies and sometimes two banking environments. If LACNIC pre-approves but destination review drags, the seller's capital remains trapped. If the destination approves but LACNIC payment or documentation remains unresolved, the buyer's plan stalls. If RPKI or reverse DNS is not immediately available, network migration may wait even after the holder record changes. Public timing and failure data would reduce this risk premium without revealing private prices.
The regional development argument cuts both ways. Some may fear that easier inter-regional export lets addresses leave Latin America and the Caribbean for richer buyers. That concern is understandable. IPv4 scarcity can make old allocations look like regional capital. But using opaque process to keep resources near home is a dangerous remedy. It traps sellers, reduces price discovery and favours insiders who know how to move through the system. If the region wants explicit retention rules, they should be debated openly. Retention by delay, recipient-review drift or discomfort with foreign buyers is still retention. It is merely less accountable.
Small island economies make the trade-off sharper. An island provider may hold space that is locally important but globally small. It may need to sell a block to finance resilience, or buy one to support public services, tourism systems, emergency communications or local hosting. A large buyer in a continental market or outside the region may be able to pay more and close faster. That may look like extraction. It may also be the best way for a local operator to convert dormant capacity into useful investment. The registry should not decide the answer by delay. It should decide whether the record can safely move.
Leasing, delegated use and responsibility
Leasing is what markets do when purchase is expensive, transfer is slow or demand is temporary. A permanent purchase turns IPv4 into a capital outlay. A lease turns it into an operating cost. For a small provider, a regional hosting company, an enterprise migration, a seasonal project or a network with uncertain future demand, that can be the difference between serving a customer and losing the contract. Leasing also allows a holder to earn from underused space without surrendering long-term optionality. Scarcity makes this behaviour ordinary, not deviant.
In the LACNIC region, leasing is shaped by the same frictions as transfer: cross-border payments, foreign-currency exposure, small-island dependency, limited access to counsel, reputation risk, broker knowledge, uneven IPv6 deployment and different levels of registry experience. If buying a block requires large upfront dollars, a down payment, recipient justification, document review, possible service agreement, inter-regional coordination and operational uncertainty, a lease may look rational even for needs that are more than momentary.
But leasing separates the registered holder from the operational user. The holder remains recognised in the registry. The lessee may originate routes, serve customers, handle traffic, manage firewalls, need reverse DNS, answer abuse complaints and depend on RPKI authorisation. A broker may arrange the contract but not control the registry account. A lessor may have clean records, or may be one link in a chain. A sublease may place another operator behind the visible user. The public record can be accurate in showing the holder and still incomplete for the practical question: who can fix the problem now?
That is the responsibility-chain problem. LACNIC should not respond by trying to regulate rent. It is not a price commission. It does not know the fair monthly value of a /24 used by a Caribbean ISP, a Brazilian hosting cluster, a Mexican enterprise platform or a temporary migration project. It should not decide whether a lessor's yield is too high, whether a lessee should buy instead, or whether IPv4 commerce is unattractive. Those are market and contract questions unless an adopted rule directly applies.
Nor should LACNIC ignore leasing as merely private. If the public record points to a holder that cannot answer operational questions, third parties suffer. Abuse reports go nowhere. Upstreams rely on letters of authority that may be stale. ROAs may authorise the wrong origin or remain after a lease ends. Reverse DNS may point to a prior user. Geolocation and reputation problems may follow the next lessee. A serious registry cannot pretend that delegated use has no public surface.
The right line is visibility without rent control. LACNIC's concern should be who is recognised, who is authorised to originate, who can administer reverse DNS, who answers abuse, how delegated use ends cleanly and whether the holder remains accountable. It should not collect lease prices, customer lists or every private term. It should make enough responsibility visible that formal registration does not drift away from operating reality.
There are already hints of this logic in the policy environment. LACNIC's IPv4 manual requires ISP assignments of /29 or larger blocks to customers connected to their network to be registered in the public database within seven days, with organisation and contact information, though residential customer rules may differ. It also says that as long as prefixes are registered, the recipient has the right to create and administer RPKI Route Origin Authorizations for those resources. That is a powerful idea: responsibility and security authority should track meaningful delegated use. Leasing raises the same idea at a more commercial and sometimes more independent scale.
A sensible approach would distinguish ordinary downstream assignment, temporary migration, first-party lease, brokered lease, long-term delegated operation and disguised transfer. The categories would not exist to moralise. They would decide what responsibility signals are needed. If formal transfer is made too burdensome, leasing will absorb demand and the ledger will become less informative. If leasing is treated as suspicious, serious participants will hide it under other words. If leasing is made visible where it affects third parties, the market can use it as a partial workaround without turning it into a shadow registry.
The economic lesson is uncomfortable but simple. A registry that makes recognised transfer difficult does not abolish address mobility. It shifts mobility into arrangements with less public clarity. A registry that tries to punish leasing may not reduce demand. It may reduce the quality of the responsibility chain. The more useful course is to preserve the integrity of the record while acknowledging the contractual forms scarcity creates.
RPKI, reverse DNS and the last mile of value
An IPv4 transaction is not fully settled when the contract is signed. It is not even fully settled when the holder field changes if the operational services that make the block usable do not follow. RPKI, reverse DNS, public registration data, abuse contacts and technical contacts are the interfaces through which registry recognition becomes network confidence.
LACNIC's RPKI service shows how deeply the registry sits in routing trust. Its hosted RPKI service has operated since January 1st 2011, and its delegated RPKI service since December 18th 2019. Hosted service lets members perform RPKI tasks through MiLACNIC. Delegated service lets an organisation operate its own certificate authority and maintain its private key for signing cryptographic material. The architecture chosen by a member may differ, but the economic point is constant: route-origin authority increasingly depends on registry-linked certification. A buyer that cannot get timely RPKI continuity may face upstream refusal, customer concern or security-policy friction.
Reverse DNS is older but still economically relevant. LACNIC's DNS servers are responsible for reverse resolution of IP addresses assigned to ISPs and other organisations in the region. Reverse resolution delegation is registered through MiLACNIC. LACNIC material explains that reverse DNS maps IP addresses into names and that IPv4 reverse delegations must respect byte boundaries, with /24 or /16 delegations registered in LACNIC's DNS servers. For hosting, mail, diagnostics, logging, reputation and customer platforms, this is not decorative. A block whose reverse DNS cannot be delegated or corrected on time may be less useful.
Inter-regional transfers make the issue explicit. LACNIC warns that when resources move from one registry to another, reverse DNS or RPKI may be affected and not immediately available. That sentence carries financial content. If a buyer is moving customer mail systems, reverse DNS delay can create deliverability problems. If an upstream requires valid ROAs, RPKI delay can affect routing acceptance. If abuse contacts remain wrong, complaints may hit the seller or go unanswered. If a lender or buyer's diligence team checks public records before releasing funds, service lag can delay closing.
Operational settlement should therefore be treated as part of transfer settlement. Parties need to know the sequence: holder verification, recipient review, legal document acceptance, fee payment, transfer agreement or order, registry record update, transfer-log entry, RPKI availability, reverse-DNS delegation, contact update and any service-agreement activation. Some events may occur close together. Some may lag. The difference matters for escrow. A buyer may want funds released only after ROAs can be created. A seller may argue that payment should be released once the holder field changes because technical-service delay is outside its control. A bank may not understand the distinction unless the registry explains it clearly.
This is another place where capital control hides inside operational language. If RPKI or reverse DNS can be interrupted because of an unrelated account issue, a private contract dispute or a vague compliance concern, operational trust becomes leverage. If the last verified operational state is maintained while a curable defect is resolved, downstream customers are protected. A registry needs a service-continuity map that distinguishes fraud, court order, compromised account, late payment, incomplete documentation, disputed authority, sanctions concern, routine transfer and lease-related delegation. Each state should have a proportionate effect on record changes, certification, reverse DNS and contacts.
The point is not that service should never pause. If an account is hijacked, locks may be urgent. If a court order binds a resource, the record may need restraint. If authority is genuinely disputed, new ROAs may be dangerous. If a member refuses to cure serious defects, service consequences may follow. The blast radius should be explicit. Customers and counterparties should not discover that a non-routing issue has suddenly become a routing-security problem because institutional categories were not separated.
For leased space, operational settlement is even more important. A lessee may not have direct registry standing but may need the lessor to create or update ROAs, delegate reverse DNS, maintain abuse contacts and clean up after termination. If the lessor's registry account standing affects these functions, the lessee's customers bear risk they did not cause. That risk can be priced if the responsibility chain is visible. It becomes a hidden tax if the public record hides it.
LACNIC can improve market confidence by treating RPKI and reverse DNS as settlement functions rather than back-office services. Public transfer guidance should state expected availability, common causes of delay, pre-closing preparation steps and the difference between record recognition and operational-service readiness. This would not guarantee perfection. It would turn unknown operational risk into known settlement risk.
The mandate boundary
The strongest case for LACNIC is also the strongest case for restraint. Because the registry record is trusted, its mandate should be narrow. LACNIC is at its most legitimate when it verifies authority, preserves uniqueness, records transfers, maintains contacts, supports reverse DNS and RPKI, contains disputes, keeps public logs and applies clear policy. It is at its weakest when the same authority is used to shape industry structure under soft language.
The soft language is familiar: development, conservation, security, community, regional interest, IPv6 transition and responsible use. These words have legitimate content. LACNIC does support regional internet development. Conservation was central in the allocation era. Security matters. Community participation is part of policy development. IPv6 deployment is essential. But after IPv4 exhaustion, the same vocabulary can hide industrial policy. It can be used to slow sales, discourage leasing, favour certain buyers, retain resources regionally, moralise seller profit or treat market liquidity as a threat.
If LACNIC or its community wants explicit market-shaping rules, those rules should be debated as market-shaping rules. The cost should be stated. Who benefits? Who pays? Will small sellers lose liquidity? Will large incumbents benefit from slower transfers? Will foreign buyers discount LACNIC-region supply? Will leasing move into less visible channels? Will IPv6 deployment actually accelerate, or will operators spend more capital managing scarcity? Will public-sector and small-island networks face higher compliance cost? Will brokers gain from opacity?
Hidden industrial policy is worse than explicit policy because it is hard to challenge. A direct rule can be debated, amended, measured and repealed. A vague discomfort embedded in recipient review or documentation cannot. It appears only as delay, extra proof, unexplained caution or inconsistent outcomes. That kind of control rewards repeat players and insiders. It also shifts political choices onto staff, who may not want to be market regulators but are pushed into that role by broad language.
The mandate boundary should be written as a discipline of nexus. LACNIC should intervene when the concern affects record truth, authority, uniqueness, security-state continuity, reverse-DNS responsibility, contactability, clear policy compliance, account obligation directly relevant to service or applicable law. It should not intervene because it dislikes the price, seller profit, buyer scale, foreign capital, leasing revenue, broker presence or the continued commercial need for IPv4. If those concerns are to matter, they require explicit adopted rules and economic evidence.
Compliance needs the same discipline. LACNIC must obey applicable law, respect court orders, avoid facilitating prohibited transactions, protect member accounts and respond to genuine disputes. Banks, counsel and foreign counterparties will screen parties too. The danger is that compliance becomes a mood rather than a rule. A legal prohibition is one thing; discomfort with a jurisdiction, buyer type, broker, payment path or business line is another. If both bank and registry operate through vague caution, the transaction becomes hostage to institutional comfort.
A narrow compliance posture should be direct and named. Is there a court order affecting the resource? Is the requester authorised? Is the account compromised? Is a party legally prohibited? Is there a sanctions rule that applies? Is there a documented dispute over holder status? Is required payment missing? Each category has a different remedy. Treating all of them as generic concern turns a precise registry into an opaque checkpoint.
Abuse and routing incidents require the same clarity. A registry can require reachable abuse contacts, accurate assignment data and correction of false records. It can act under specific policy or law. If a ROA is wrong, it should be corrected; if an account is compromised, it should be locked and recovered; if two parties claim authority, the dispute should be marked and contained. But an abuse allegation, route leak or commercial fight should not become a capital freeze unless the record itself is at risk.
AFRINIC offers a warning, though not an analogy to be stretched beyond use. Latin America and the Caribbean should not be analysed through Africa's institutional crisis. The useful lesson is narrower: a regional registry can stop being background infrastructure and become an economic event when scarce IPv4 value, litigation, contested governance and continuity risk become entangled. The preventive lesson for LACNIC is to insulate the ledger function before any crisis. Keep record authority professional. Release evidence categories. Separate fraud from policy disagreement. Make transfer timing visible. Keep RPKI and reverse-DNS continuity rules explicit. Do not let community language conceal who bears the cost of a rule.
A narrower checkpoint
The most useful reforms are not ideological. They are mundane, measurable and market-supporting. LACNIC should release median and long-tail processing times for intra-regional transfers, outbound and inbound inter-regional transfers, merger and acquisition transfers, name changes, legacy regularisation, account recovery and dispute-affected cases. It should separate applicant delay from registry review, payment delay, documentation supplement, inter-registry coordination, legal hold, recipient-review failure and operational-service lag. Average time is not enough; the long tail is where capital freezes.
It should release a documentation map. Routine transfers, corporate succession, asset sales, public-sector reorganisations, insolvencies, account compromise, suspected fraud, court disputes and inter-regional cases should each have ordinary evidence categories, accepted substitutes, translation expectations, signature rules and cure paths. The purpose is not to make hard cases disappear. It is to stop hard cases from becoming one undifferentiated demand for more comfort.
Recipient review should be scoped in public. It can test real organisation status, coherent use, amount, policy compliance, sham risk, holding-period evasion, waiting-list evasion, prior-resource use where applicable, IPv6-related requirements where policy requires them and service obligations. It should not test price fairness, buyer virtue, seller profit, preferred industry, foreignness or general comfort with IPv4 commerce.
Operational states should be just as clear. Members and counterparties should know what happens to RPKI, reverse DNS, contacts, public registration data, transfer processing and account functions during late payment, incomplete documentation, compromised account, disputed authority, court order, sanctions issue, suspected fraud, routine transfer and lease-related delegated use. Payment states should be separated because bank processing, short receipt because of fees, unpaid invoice, renewal deadline, disputed invoice and contractual defect are not the same risk.
The transfer log should be usable enough to serve as market memory without disclosing private prices. LACNIC should also release guidance for material leased or delegated use: holder accountability, operational contacts, abuse handling, route-origin authority, reverse-DNS delegation and end-of-term cleanup. Adverse actions should be reasoned. A rejected transfer, failed recipient review, documentation hold, dispute status, service limitation or account barrier should state the reason category, the rule or legal basis, the evidence needed to cure it and the available review path.
None of this requires LACNIC to become a market exchange. None requires it to set prices, endorse brokers or promise that every transaction will close. It requires a registry that knows which parts of the market it should not control and can therefore make the parts it must control clearer. Good settlement infrastructure is boring by design. Its success is measured by the disappearance of avoidable risk premiums.
Return to the closing table. The seller, buyer, broker, bank, counsel and engineers are not asking LACNIC to decide whether the price is elegant, whether the buyer is a preferred kind of operator, whether the seller deserves a windfall, whether leasing is morally attractive or whether IPv4 dependence is a virtue. They need a narrower decision: can the record safely recognise this movement, and can the operational services that depend on recognition follow?
That decision is powerful enough. If the answer is yes, funds, usable capacity, escrow release, route-origin data, reverse DNS and responsible contacts can align. If the answer is no, the reason matters. A forged signatory is one thing; a court dispute, failed recipient review, missing bank fee, renewal deadline or inter-regional service delay is another. A suspicion that the buyer is too commercial or the seller too profitable should not be smuggled into any of them. The market can accept a narrow no. It cannot price an institutional mood.
LACNIC's regional setting makes this discipline more important, not less. Latin America and the Caribbean contain sophisticated large economies, smaller economies with thin legal and banking capacity, island networks, cross-border groups, public-sector records, multilingual participation and uneven macroeconomic conditions. A neutral rule can have unequal effects. The registry cannot equalise every balance sheet or fix every bank. It can avoid adding unnecessary uncertainty at the recognition point where those frictions already meet.
Capital control by recognition is not an insult. It is a diagnosis of function. A non-state registry becomes a capital checkpoint when scarce capacity can move only after recognition. The policy task is clear: keep the checkpoint because the record needs protection; narrow it because the registry is not an economic ministry; make it visible because markets can price clear friction; make it reviewable because unexplained discretion becomes a hidden tax.
The future of internet growth is IPv6. The present of many networks still includes IPv4 working capital. A serious registry must hold both thoughts at once. It should promote IPv6 without using IPv4 recognition as punishment, protect scarcity from fraud without treating every transaction as suspect, record transfers without blessing prices, support leasing visibility without becoming a rent regulator, and serve the region without pretending the region is one economic will.