Summary

  • LACNIC cross-border-compliance analysis asks how corporate authority, notarisation, translation, banking proof, tax questions and legal opinions shape IPv4 transfer liquidity.
  • The cost is not peripheral paperwork once scarce addresses carry balance-sheet value; it changes settlement timing, escrow risk, buyer confidence and customer continuity.
  • A credible registry keeps compliance narrow and portable so evidence protects the ledger rather than becoming a capital-control machine.

An IPv4 transfer between two companies in different jurisdictions does not begin with routing. It begins with a file. Before any prefix moves, before an escrow release is authorised, before a customer can be told that capacity has been secured, the buyer and seller assemble papers that look more like a cross-border acquisition than a technical registry request. There are corporate extracts, board approvals, powers of attorney, signatory certificates, notarised documents, sworn translations, bank confirmations, payment instructions, tax memoranda, declarations on beneficial ownership, historical allocation records and assurances that the block is not trapped in a dispute left behind by a merger that closed years earlier. For a buyer in one Latin American country acquiring address space from a holder incorporated in another, this file is not clerical staging. It is where price, authority, risk and operational continuity first become inseparable.

That is the proper starting point for any serious analysis of LACNIC and cross-border compliance costs. The question is not whether compliance matters. It does. A registry cannot knowingly record a forged transfer, ignore a live corporate dispute, accept a request from an unauthorised person or update a scarce resource after receiving credible evidence that the seller has no power to dispose of it. Fraud control is part of registry accuracy. The harder question is where fraud control ends and economic control begins. Under IPv4 scarcity, that boundary has become one of the most important lines in Internet governance.

The distinction matters because this is not the same problem as sanctions screening, even if sanctions questions may occasionally touch the same file. Nor is it the same problem as national Internet registry relationships, even if local registries and domestic coordination bodies shape the operating background. The specific problem is narrower, more commercial and more measurable. A company that owns or controls a usable IPv4 block in one legal system sells or transfers it to a company in another. The two parties must satisfy their own lawyers, banks, auditors, tax advisers, customers and boards. LACNIC must maintain a correct registry record. If the registry keeps its role narrow, it reduces fraud and preserves liquidity. If it expands the role, it can turn a registry update into an unofficial license for capital movement.

That is the central institutional point. Cross-border compliance is not bureaucracy around the edge of the registry. In a scarce IPv4 market it becomes part of the price of liquidity. Every extra certificate, every translation delay, every ambiguous request for proof, every tax question pushed into the registry file and every open-ended review of corporate structure raises the cost of moving an address block to its highest-value user. Some costs are justified because they protect accuracy. Others are institutional rent, created when a recordkeeper mistakes its administrative leverage for a mandate to supervise commerce. Narrow evidence preserves ledger legitimacy. Broad discretion becomes capital control.

The document bundle is the market surface

The easiest mistake is to imagine an IPv4 transfer as a simple change in a registry record. Technically, the final act may look like that. Economically, the final act is the last step in a much larger exchange. The value is created when seller, buyer, financiers, transit providers, customers and auditors can rely on the changed record. The transfer record is therefore not merely evidence of a transaction already completed. It is one of the conditions that lets the transaction settle.

That is why the pre-transfer bundle becomes so large. Corporate authority has to be proved because the seller may be a subsidiary, a dissolved entity, a successor after a merger, a reorganised telecom group or a legacy holder whose current directors are far removed from the original allocation. Signatory authority has to be proved because the person submitting a request may be a technical contact, an outside consultant or a finance manager rather than a board-authorised officer. Notarisation has to be obtained because the parties need a reliable method of proving identity and signature across legal systems. Translation has to be arranged because a Spanish-language certificate from one jurisdiction, a Portuguese-language corporate extract from another and an English-language purchase agreement may all meet in the same file. Banking evidence has to be aligned because settlement may not occur until the buyer knows that the registry will record the transfer, while the seller may not release control until funds are secured. What looks like documentation is therefore also market plumbing.

These are real costs. They are also unevenly distributed. A large telecom group can assign lawyers, accountants and treasury staff to the file. A regional data-centre operator may have one finance lead and an outside lawyer. A small ISP may need to explain the entire market to its bank before it can even open the correct payment channel. The larger party experiences compliance as process. The smaller party experiences it as friction against growth.

This is where institutional economics clarifies what procedural language hides. Transaction costs are not incidental. They decide whether a scarce asset can move. If the cost of moving a block is high enough, a seller may keep idle resources rather than sell them. A buyer may lease short-term capacity instead of investing in longer-term control. A cloud entrant may postpone a regional build. A rural network may remain dependent on a supplier whose addresses it cannot replace. The registry may not intend any of those outcomes. But once its process determines whether the transaction clears, it is part of the market’s pricing mechanism.

The proper design question for LACNIC is therefore not how much documentation can be justified in the abstract. Almost any document can be made to sound reasonable if described in isolation. The question is which documents are necessary to maintain uniqueness, accuracy, lawful authority and dispute awareness, and which documents merely allow the registry to pull broader commercial anxieties into a technical record. A narrow file protects the market. An expanding file taxes it.

Latin America’s legal map multiplies the cost

LACNIC’s region is not one legal economy. It is a group of countries and territories with different corporate laws, notarial traditions, banking rules, tax systems, currency controls, languages, insolvency regimes and attitudes toward foreign exchange. That diversity is not a defect. It is the ordinary legal geography of the region. It does, however, make cross-border IPv4 transactions structurally more expensive than domestic transfers inside a single legal order.

In many Latin American jurisdictions, notarisation and apostille-like validation are not ceremonial. They are the method by which a document produced in one country can be trusted in another. A power of attorney may need local formalities. A board resolution may require certification by a company secretary, a public notary or a registry authority. A corporate extract may need to be current within a narrow time window. A translation may need to be sworn, not merely accurate. A bank may refuse to process a payment until it understands why an Internet number resource is being bought by an entity whose ordinary invoices concern hosting, telecom services or cloud infrastructure.

The friction is higher when the buyer and seller sit in different legal families or administrative cultures. A document that is obvious to counsel in Brazil may not be obvious to counsel in Uruguay, Chile, Mexico, Colombia or the Caribbean. A civil-law notarial certificate may carry weight that an Anglo-style director certificate does not. A corporate seal may matter in one place and appear archaic in another. Some banks may ask whether the payment is for a service, an intangible asset, a license, an assignment of rights or a membership-related transfer. Each classification can affect tax reporting, withholding, exchange-control treatment and internal approval.

These costs exist before LACNIC asks a single question. The registry’s task is to avoid turning regional legal diversity into an additional institutional toll. It should not pretend the world is frictionless. It should also not make itself the clearing house for every possible cross-border legal concern. The narrower its demands, the more predictable the transaction becomes. The broader its demands, the more it compounds the costs already imposed by local legal systems, and the more the registry’s review begins to resemble a second legal system layered on top of the first.

The registry’s legitimacy depends on understanding the difference between complexity that threatens record accuracy and complexity that merely reflects corporate life. If a person lacks authority to sign, LACNIC must stop the transaction. If two companies claim the same block, it must isolate the dispute. If a court order freezes the asset, it must respect the conflict state. But if the only issue is that the parties use different legal forms, languages and banking channels, the registry should not inflate that inconvenience into a veto over the movement of IPv4 capital.

Latin America and the Caribbean need liquidity precisely because the region is uneven. Address demand does not appear in perfect proportion to historical allocations. Some holders have unused or underused space. Others face urgent expansion needs. Scarcity can be managed through price, transfer and lease. It cannot be managed efficiently through an administrative process that imposes the same legal burden on a regional ISP as on a multinational acquirer. If LACNIC wants to preserve regional legitimacy, it must keep the common layer thin enough for legal diversity to remain manageable and thick enough only to protect the ledger from fraud, duplicate claims and live disputes.

Corporate authority is not a moral inquiry

The first real compliance question in a cross-border transfer is corporate authority. Does the seller have power to dispose of the resource? Has the buyer authorised the acquisition? Are the signatories binding the correct entities? Is the person communicating with the registry a valid representative or merely a technical contact who has accumulated operational access over time? These questions are unavoidable. They protect the registry from recording a lie.

But authority review has a precise purpose. It is not a referendum on whether the registry approves of the buyer’s business model, ownership structure, customer base or capital source. A board resolution can show that the seller approved the transaction. A corporate extract can show that the company exists and who its directors are. A power of attorney can show that a lawyer or consultant may submit the transfer request. A notarised signature can reduce impersonation risk. A legal opinion can bridge unfamiliar local law. Once those points are satisfied, authority review should end.

The danger is category drift. A registry begins by asking whether a director may sign. Then it asks why the company is selling. Then it asks whether the buyer really needs the block. Then it asks about the buyer’s future customers, the geography of use, the source of funds, the accounting treatment, the tax position and the group’s commercial rationale. At some point the question has changed. The registry is no longer verifying authority over a transfer file. It is supervising allocation of capital.

That drift is especially harmful in IPv4 because the resource is both scarce and operational. If a buyer has committed capital, negotiated a contract, arranged escrow and prepared routing plans, its need has already been revealed by economic conduct. The buyer is not asking a registry for a free allocation from an abundant pool. It is paying another holder for an asset that scarcity has priced. A residual needs test, if applied after money is on the table, functions like a rationing device. It says that market demand is not enough; administrative approval must validate demand before liquidity can be recognised.

The institutional problem is not only delay. It is uncertainty over who bears the loss. If the registry refuses or pauses the transfer after the parties have incurred legal, translation, notarial and banking costs, those costs do not disappear. The buyer may lose a business opportunity. The seller may lose a sale window. An escrow arrangement may need extension. A bank may require renewed documents. Customers waiting for capacity may go elsewhere. The registry, by contrast, usually bears little of the economic downside. That asymmetry encourages overreview because the cost of caution is paid by others and is rarely visible in the registry’s own accounts.

A narrow authority standard would reduce this asymmetry. LACNIC should require enough evidence to know that the legal entities exist, that the relevant decision-makers approved the transaction, that the signatories are empowered, that the resource is not subject to a known unresolved dispute and that the transfer will not produce duplicate registration. It should avoid turning corporate authority into a general inquiry into whether the transaction is socially, politically or commercially desirable.

This is not a plea for loose process. It is the opposite. Narrow process is more disciplined than broad process because it must state what problem each document solves. A notarised power of attorney solves representation risk. A board resolution solves authorisation risk. A corporate extract solves existence and capacity risk. A dispute declaration solves conflict risk. A registry that can name the risk can ask for the document. A registry that cannot name the risk is often asking for comfort, and comfort is not a legitimate price to impose on liquidity.

Notarisation and translation turn time into a spread

Notarisation and translation are often treated as minor administrative details. In cross-border IPv4 transfers they become a measurable spread between theoretical price and executable price. A seller may quote a block at a price per address. The buyer may accept. Yet the real price is higher once the parties add lawyer time, notarisation fees, document legalisation, sworn translation, courier delays, bank review, escrow extension and staff hours spent answering follow-up questions.

Time matters because IPv4 is not a static collectible. Buyers need addresses for projects with deadlines. A hosting expansion may depend on customer onboarding. A cloud region may need enough routable IPv4 to support launch commitments. A broadband operator may need capacity to avoid delaying installations. A security provider may need clean space for network segmentation. If the transfer is delayed, the buyer may have to rent interim capacity, reassign existing blocks, postpone revenue or accept operational compromise. Those costs change the economics of the purchase.

In a cross-border file, translation can be particularly treacherous. A phrase with a stable meaning in one corporate law may not map perfectly into another language. A registry may request a translation of a document whose legal significance depends on its domestic form. A translator can translate words, but not necessarily the evidentiary role the document plays. The registry must therefore be careful not to demand linguistic precision as a substitute for legal understanding. A sworn translation can prove what the document says. It cannot prove what the document does under local law, and it should not be made to carry that burden.

Notarisation has the same limit. It can verify a signature or certify a copy. It cannot always prove that a company had substantive authority to sell an IPv4 block, especially when the resource sits in an old allocation chain or after several mergers. A notary is not a registry historian. A corporate registry is not a routing authority. Each institution answers a different question. The LACNIC process should respect those boundaries rather than stacking certifications until the file looks safe by weight.

The economic effect of overdocumentation is most visible in small and mid-sized transfers. A very large block can absorb legal costs because the transaction value is high. A smaller block may not. If the fixed cost of compliance is too high, only large transfers remain rational. That pushes the market toward larger incumbents and away from the smaller networks that often need liquidity most. A process that claims to protect regional fairness can therefore produce the opposite result, making cross-border IPv4 transfers practical mainly for the parties with the deepest administrative capacity.

The narrow solution is not to abolish notarisation or translation. It is to standardise when they are needed and what they are meant to prove. If a document proves signatory authority, say so. If a translation is needed only for registry staff to read a certificate, say so. If an apostille-style validation is necessary because the document comes from a foreign public authority, say so. If a legal opinion is needed because translation cannot explain the legal effect, say that too. Ambiguity is expensive. Predictability is liquidity.

Banking proof can protect settlement or distort it

Money is where a registry file meets the outside financial system. IPv4 transfer payments can involve large sums, foreign exchange conversion, correspondent banking, beneficial-owner questions, source-of-funds review and internal classification problems. A bank asked to process payment for an address block may not understand the asset. It may ask whether the transaction is a sale of intangible property, a service fee, a license payment, a membership transfer or something else. Each answer can produce different treatment, and each classification can slow the moment when registry approval and payment release can be matched.

There is a legitimate reason for registry attention to payment evidence. If a transfer is presented as completed but the underlying transaction is fraudulent, coerced or disputed, the registry may become part of a harmful chain. If the seller claims it has not been paid and the buyer claims settlement has occurred, the registry needs to know whether it is looking at a commercial dispute or a defect in the transfer request. Escrow arrangements can reduce this problem by separating registry approval from final release of funds.

But banking proof can also become a tool of institutional overreach. A registry does not need to become the buyer’s bank, the seller’s tax authority or the investigator of every treasury pathway. The relevant question is not whether LACNIC likes the payment structure. It is whether the registry can safely record the transfer once the parties present a valid agreement, valid authority, a settlement mechanism and no evidence of a live legal block. The registry can require confirmation that settlement conditions exist. It should not require parties to reorganise commercial payment arrangements to satisfy administrative preferences unrelated to registry accuracy.

The risk is acute in a region where currency controls, banking delays and capital restrictions can already shape cross-border transactions. Some countries have strict foreign-exchange procedures. Others experience bank-risk aversion. In some cases the buyer may pay from a parent company, an affiliate or a treasury centre because that is how the group manages international payments. In other cases the seller may require payment into an account outside its home country to satisfy lenders or foreign suppliers. These structures may be ordinary and lawful. Treating them as inherently suspicious raises costs without improving the registry record.

A well-designed process should distinguish settlement assurance from payment policing. Settlement assurance asks whether the parties have an enforceable mechanism that prevents one side from losing both money and resource control. Payment policing asks whether the registry is comfortable with the parties’ banking choices. The first is connected to registry accuracy because a failed settlement can become a transfer dispute. The second belongs to banks, tax authorities, courts and the parties’ counsel.

Escrow is useful because it narrows the problem. The buyer can place funds with a trusted provider. The seller can sign transfer documents. The registry can review authority and recordability. Funds can be released when the transfer is recorded or when defined conditions are met. Yet escrow does not eliminate registry responsibility for timing. If LACNIC review is unpredictable, escrow fees rise, funds remain locked longer and parties face extension risk. The registry’s delay becomes a financing cost.

Tax questions belong at the edge of the registry

Tax is unavoidable in cross-border IPv4 transfers, but it is not a registry function. The parties may need to decide whether the transaction is treated as a sale of an intangible asset, an assignment of contractual rights, a service-related payment, a capital gain, ordinary income or a transfer within a corporate group. They may need to consider value-added tax, withholding tax, stamp duties, foreign-exchange reporting, permanent-establishment concerns and the accounting treatment of acquired addresses. These questions can be serious. They can also differ sharply by jurisdiction, even when the technical transfer is exactly the same.

The existence of tax complexity does not mean LACNIC should become a tax gatekeeper. The registry lacks the mandate, local legal authority and institutional capacity to adjudicate tax positions across the region. If it tries, it will either create false comfort or impose arbitrary burdens. A registry officer in Montevideo cannot reliably determine the withholding obligation of a buyer in one country paying a seller in another under a contract governed by a third legal system. Nor should the registry hold up record accuracy until every possible tax question is resolved.

The proper approach is separation. The parties should be responsible for their tax compliance. Their lawyers and advisers should document the position. Banks should apply their own rules. Tax authorities should enforce public law. LACNIC should ask only whether tax issues have produced a legal restriction that affects recordability, such as a court order, a regulatory freeze or a documented dispute over the transfer. Absent that, tax belongs at the edge of the registry process.

This boundary matters because tax language can easily disguise capital control. If a registry asks for evidence that VAT has been paid, withholding has been handled or capital-gains treatment has been accepted, it may be conditioning transfer recognition on fiscal compliance in legal systems where it has no public mandate. That can trap resources when tax treatment is uncertain, when authorities are slow or when parties have lawful but contested interpretations. The registry record then becomes a lever for enforcing positions outside the registry’s competence.

There is also a fairness problem. Large buyers can obtain tax memoranda in several jurisdictions. Smaller operators may not. If LACNIC makes tax comfort part of the core transfer file, the cost of entry rises. Parties with sophisticated advisers can navigate the process. Others may abandon cross-border acquisition and continue operating with insufficient address space. That outcome does not protect the Internet. It protects incumbents from competition.

The same point applies to accounting treatment. Whether a buyer capitalises the cost, amortises it, treats it as a right of use or accounts for it under another category is a matter for auditors and applicable standards. The registry’s record may affect the auditor’s comfort, but the auditor’s conclusion should not determine whether the registry records a valid transfer. The chain of reliance must not be inverted. The registry records operational and legal control; auditors then evaluate the economic treatment. If the registry waits for perfect accounting certainty, it again converts itself into a capital allocator.

A narrow tax boundary would make the system more honest. LACNIC can require a party declaration that each side remains responsible for applicable taxes and that no known legal restriction prevents the transfer. It can accept legal opinions where there is a specific concern. It can record dispute status if a tax authority has imposed a relevant freeze. But it should not use tax uncertainty as a general reason to delay recordkeeping. In cross-border commerce, tax uncertainty is normal. Registry uncertainty should not be added on top.

Beneficial ownership must not become a veto

Beneficial ownership is one of the most delicate parts of cross-border compliance. There are good reasons to ask who ultimately controls a company. Shell structures can conceal fraud. Disqualified or criminal actors can hide behind nominees. A seller may claim authority while the real controlling shareholder disputes the sale. A buyer may be a newly formed company created only to acquire a block for a group that wants to separate operational use from asset holding. The registry cannot ignore all of this.

Yet beneficial-ownership review has to remain tied to registry risk. The relevant question is whether the disclosed ownership structure creates a reason to doubt authority, legality or record accuracy. It is not whether the registry likes the nationality, politics, financing model or corporate planning of the ultimate owner. Once a registry begins to decide which ownership structures are acceptable as a matter of policy taste, it moves from fraud prevention into economic permission, and from recordkeeping into selection of who may hold scarce capital.

IPv4 scarcity makes that shift more dangerous. A scarce asset attracts holding companies, financing vehicles, leasing structures, joint ventures and group reorganisations. That is normal capital behaviour. A company may separate address holding from network operations to isolate liability. A group may acquire addresses through a regional entity because that entity contracts with customers. A lessor may hold blocks centrally and make them available under managed arrangements. These structures can be legitimate even when they complicate the registry file.

A registry that equates complexity with evasion will penalise the very risk-management structures sophisticated operators use in other infrastructure sectors. The result is not cleaner ownership. It is less transparent ownership, because parties will design around unpredictable review. Clear standards produce disclosure. Vague suspicion produces avoidance.

The distinction between ownership disclosure and commercial judgement is therefore crucial. LACNIC may ask for beneficial-owner information to confirm that a transfer request is not fraudulent, that the parties are not concealing a direct legal conflict and that the registry is not ignoring a binding restriction. It should not use that information to decide whether a buyer’s investors are sufficiently local, whether the acquired block will serve customers in a preferred geography or whether the group’s business model aligns with a regional narrative. Geography can organise service. It should not become a theory of ownership.

This point is particularly important for LACNIC because its region includes economies with different levels of capital access. If local operators cannot attract external capital without triggering registry suspicion, the compliance process becomes anti-developmental. The region needs investment in networks, hosting, security, cloud services and connectivity. External capital is not automatically a threat. It can be the mechanism by which regional operators obtain capacity and scale. A registry that treats every cross-border ownership layer as a reason for hesitation will reduce the capital available to precisely the networks that need it.

There is a better model. Beneficial-ownership review should be event-based and risk-specific. If a disclosed owner creates a concrete legal problem, the registry can pause and request clarification. If a company cannot identify any controlling party, the registry can ask for a lawful explanation. If a dispute exists among shareholders, the registry can isolate the conflict. But if ownership is disclosed, authority is valid, the transaction is lawful and no technical uniqueness problem arises, beneficial ownership should not become a veto over liquidity.

The market will price ownership risk if it is visible. Buyers can demand warranties. Sellers can provide indemnities. Escrow providers can require declarations. Lawyers can opine on authority. Insurers can cover defined risks. What the market cannot price efficiently is a registry’s unbounded curiosity. Curiosity without a limiting principle is discretion, and discretion is expensive.

Legacy blocks carry corporate memory

Many IPv4 blocks were allocated in a different institutional era. Some were issued to universities, early network operators, state-related entities, research bodies, telecom incumbents or companies that have since changed names, merged, spun off divisions, entered insolvency or sold network assets. The current holder may be the legal successor to an entity whose original documentation was sparse by today’s standards. The registry record may contain contacts who retired years ago. The block may have supported customers continuously while the corporate paper trail evolved around it.

Cross-border transfers expose this history. A buyer wants confidence that the seller can transfer the block. The seller wants to avoid reopening decades of corporate archaeology. The registry wants to avoid recording a transfer that later becomes contested. Each concern is rational. The problem is that perfect historical proof may be impossible, or possible only at a cost that exceeds the value of smaller transfers.

Merger residue is especially common. A telecom group acquires a hosting business and absorbs its customers but leaves the address registration in an old subsidiary. A data-centre company sells its facilities but keeps some network assets. A broadband operator reorganises after a debt restructuring. A parent company changes jurisdiction. A public entity corporatises. Years later, when an IPv4 transfer is proposed, the file must explain why the current seller is the proper party. The explanation may involve sale agreements, merger certificates, court orders, asset schedules, board minutes and old registry correspondence.

LACNIC has a legitimate role in testing the chain. A registry record should reflect reality, not nostalgia. If the company on the record no longer exists, the registry should require evidence of succession before permitting a transfer. If two successors claim the same block, the registry should not choose casually between them. If a legacy block was never clearly brought under the current contractual relationship, the record may need careful regularisation.

But the registry should also recognise the economic danger of excessive historical perfectionism. If every legacy transfer requires a museum-quality archive, many blocks will remain trapped. The cost of clearing title will exceed the expected sale value. Scarce resources will sit with entities that do not need them, while growing networks cannot acquire them. The registry will not have protected history. It will have frozen it.

The better approach is curative. Where historical documents are incomplete but practical control is clear, the registry should accept a combination of corporate declarations, legal opinions, indemnities, public corporate records, operational history and notice procedures. If no credible competing claim appears after proper notice, the record can be regularised. If a competing claim appears, the dispute can be marked and isolated. This is how mature record systems handle imperfect history: not by pretending gaps do not matter, and not by allowing gaps to immobilise every asset forever. The test is not whether the past is tidy. It is whether the present claim can be made reliable enough for the ledger.

Legacy status also raises a deeper philosophical point. The older the block, the more obvious it becomes that the registry did not create the value. The value accumulated through use, routing, customer reliance and market scarcity. The registry record matters because it describes that reality to the world. It should not be treated as if the registry is granting the economic substance anew each time a transfer occurs. That distinction is essential in the LACNIC region, where historical allocations may sit inside corporate stories that do not fit modern administrative templates.

Customer continuity is the constraint that matters

An IPv4 block is not merely inventory. It can be the public identity of customers, services, applications, mail systems, security policies, access lists, payment systems, VPN endpoints, monitoring infrastructure and supplier integrations. When a transfer involves live addresses, the transaction must preserve continuity. If it does not, the buyer and seller have not moved an asset. They have created an outage risk.

Customer continuity changes the compliance analysis. A registry may see a transfer request as a file to be reviewed. Operators see a maintenance window, a routing plan, a customer communication problem and a reputational exposure. Reverse DNS may need coordination. RPKI and route authorisations may need timing. Abuse contacts must remain reachable. Geolocation signals may need adjustment. Upstream providers may need updated letters of authorisation. Firewalls and partner systems may depend on addresses that should not suddenly lose legitimacy.

Cross-border transfers amplify these issues because customer contracts may sit in one jurisdiction while registry recognition changes in another. A seller may continue to serve customers during a transition period. A buyer may acquire the block but lease capacity back temporarily. The parties may need a staged transfer so that routing, billing and customer notices do not all change at once. The registry should allow commercial structures that preserve continuity, provided the record remains accurate and no duplicate claim is created.

This is where a narrow registry role is again more useful than an expansive one. If LACNIC focuses on record accuracy, it can support continuity by making transfer timing predictable, recognising transitional arrangements where properly documented and ensuring that security-related records can be updated in a controlled sequence. If it tries to police customer geography or commercial use, it may force parties into artificial structures that increase operational risk.

Customer continuity also shows why delay is not harmless. A paused transfer can leave the parties in limbo. The seller may be contractually obliged to stop using the addresses after a certain date. The buyer may have promised capacity to customers. Transit providers may have scheduled routing changes. An escrow deadline may be tied to technical acceptance. If the registry review drifts, the operational plan becomes stale. The parties then either renegotiate or operate under temporary arrangements that were not designed for long periods.

The users affected by these delays rarely know the registry exists. They experience only the service consequence. A delayed address acquisition may mean a cloud account cannot be provisioned, a security service cannot onboard a customer, a hosting provider must ration capacity or a regional network must postpone expansion. The registry may describe its review as administrative caution. To the operator, it is a constraint on the ability to serve customers.

The correct institutional test is simple. Does a compliance requirement reduce the risk of duplicate use, fraud, misrecording or unresolved dispute? If yes, it may be justified. Does it merely allow the registry to express a preference about where customers are located, how the buyer monetises the block or whether the transaction fits an inherited view of regional stewardship? If so, it increases continuity risk without protecting the Internet. Continuity is an operational fact, not a slogan for refusing movement.

Scarcity makes customer continuity more valuable, not less. When addresses were abundant, a failed transfer could be replaced by another allocation. Now the buyer may have no easy substitute. A registry that keeps transfers narrow and predictable helps customers indirectly by allowing capacity to move toward demand. A registry that broadens review traps capacity away from demand and then calls the result prudence.

Escrow exposes the cost of registry discretion

Escrow is supposed to make a risky exchange safer. The buyer does not want to pay before the registry records the transfer. The seller does not want to give up control before payment is secure. The escrow provider holds funds or documents under defined conditions. Once the registry confirms the transfer, funds are released. In theory, this structure converts mutual distrust into manageable sequence.

In practice, escrow exposes how much of the transaction depends on registry discretion. If the registry process is predictable, escrow is a bridge. If the process is unpredictable, escrow becomes a warehouse for trapped capital. Funds sit idle. Fees accumulate. Long-stop dates approach. Exchange rates move. Financing commitments age. Legal opinions may need renewal. The parties begin negotiating not only with each other but with uncertainty itself. Settlement timing becomes a registry output, whether the registry names it that way or not.

Settlement timing is therefore an institutional performance measure. A registry may not control the parties’ banks, lawyers or translators. It does control the clarity of its own requirements, the speed of its own review and the specificity of its own objections. A vague request for more information is expensive because it does not tell the parties how to cure the file. A precise objection is cheaper because it identifies the defect. A written reason allows appeal or correction. Silence forces guessing.

The cost of discretion is not linear. The first week of review may be expected. The second may be acceptable. The third begins to affect financing and customer planning. Beyond that, the transaction can enter a zone where each party suspects the other may be using the registry delay strategically. The buyer may suspect the seller of withholding documents. The seller may suspect the buyer of delaying payment. Both may suspect the intermediary of poor handling. The registry’s uncertainty becomes private mistrust.

For smaller transfers, the effect can be fatal. Escrow fees and legal time can consume a material share of the deal. If a block is small enough, parties may decide the process is not worth the effort. They may lease capacity through informal channels, rely on upstream addresses or avoid expansion. A compliance system that is tolerable for large transactions can destroy the lower end of the market.

For larger transfers, discretion changes price. Buyers discount for execution risk. Sellers demand higher deposits. Intermediaries charge more for managing uncertainty. The result is less liquidity and wider spreads. Again, LACNIC need not intend to shape price. By controlling the recognition point, it shapes price anyway.

The solution is not automatic approval. It is procedural discipline. Requirements should be published in plain commercial terms. Standard forms should be limited to the risks the registry is entitled to manage. Objections should be specific. Cure periods should be reasonable. Appeals should be available for contested interpretation. Where a dispute is external, the registry should mark the dispute and await proper resolution rather than informally adjudicating issues beyond its role. The point is to make delay intelligible, not to deny that review takes time.

Escrow also reveals why portability matters. If a resource holder cannot choose another competent registry service when one becomes slow, conflicted or expansive, the current registry has little market discipline. The parties must wait because the recognition layer is locked. Without exit, delay becomes power. With portability, poor service has consequences. Even the possibility of exit can keep compliance narrow because the registry knows that recordkeeping quality, not institutional mythology, is the basis of continued legitimacy.

Legal opinions should narrow uncertainty, not transfer power

Legal opinions are useful in cross-border IPv4 transfers because they translate unfamiliar local law into a form the registry and counterparty can rely on. A lawyer in the seller’s jurisdiction can opine that the company exists, that the board approval is valid, that the signatory has authority and that the transaction does not violate a known restriction. A lawyer in the buyer’s jurisdiction can opine on capacity to acquire. Counsel may address merger history, insolvency issues, beneficial-ownership conflicts or the effect of a court order.

But legal opinions can also be abused. A registry may ask for an opinion not because a specific legal issue exists, but because it wants to shift risk without defining the risk. That makes the opinion a substitute for institutional clarity. The registry avoids stating its standard, counsel is asked to provide broad comfort and the parties pay for ambiguity. The thicker the requested opinion, the less clear the registry’s own role often is.

A proper opinion should answer a defined question. Does the seller have authority? Is the approving resolution valid? Is there a known legal prohibition? Did a merger transfer the relevant business assets? Does a power of attorney permit the filing? These are legal questions with boundaries. They can be answered, qualified or refused. A request for counsel to certify that the transfer is acceptable in all respects is not a legal standard. It is an anxiety transfer.

The better model is tiered. Routine transfers with clear corporate records should not require heavy legal opinions. Transfers involving legacy history, insolvency, conflicting claims, unusual powers of attorney or cross-border restructuring may justify targeted opinions. The required question should be named. The acceptable qualifications should be understood. The registry should not demand impossible certainty. Commercial law rarely offers it, and forcing counsel to pretend otherwise only hides the true decision-maker.

Legal opinions can make the market safer when they reduce uncertainty. They harm the market when they become a way for the registry to avoid drawing its own boundaries. The institutional responsibility belongs to LACNIC: decide what risks are registry risks, state them clearly and request legal support only when local law is needed to resolve them. A registry that cannot describe the legal question should not make the parties pay to answer it.

Appeals are part of liquidity, not public relations

Every serious compliance process needs a remedy for error. In cross-border IPv4 transfers, errors are inevitable. A document may be misunderstood. A translation may obscure the legal effect of a certificate. A registry officer may apply a domestic assumption to a foreign corporate form. A request for beneficial-owner information may go beyond what the risk requires. A tax concern may be treated as a recordability issue when it belongs to the parties. If there is no effective appeal, these errors become hidden taxes.

Appeal should not be confused with lobbying. A party should not have to know the right staff member, attend the right meeting or use the right public vocabulary to correct a transfer decision. The appeal mechanism should be written, timely and focused on the disputed issue. It should state what requirement was not met, what evidence would satisfy it and what authority supports the interpretation. If the registry relies on discretion, it should say why discretion is being exercised and what limits apply.

This is not merely procedural fairness. It is economic infrastructure. A market can price a rule. It cannot price a mood. If parties know that a missing corporate extract will delay review, they can obtain it. If they know that legacy succession requires a legal opinion, they can budget for it. If they know that a live shareholder dispute will pause the file until resolved, they can plan around it. What they cannot manage efficiently is a sequence of unexplained concerns that change as the file develops.

Appeals must also be proportionate. A transfer cannot remain suspended indefinitely because an internal review has no deadline. The resource may be needed for customers. Escrow may expire. Exchange rates may shift. A seller’s board approval may have a time limit. A remedy that arrives after the transaction dies is not a remedy. It is a post-mortem.

LACNIC’s institutional legitimacy is strengthened, not weakened, by acknowledging that compliance decisions can be contested. A registry that explains itself looks more reliable than a registry that hides behind general policy language. The goal is not to win every dispute. The goal is to make disputes narrow enough that the market can continue functioning around them. Appeal is therefore not a courtesy after the real process has ended. It is one of the devices that keeps compliance from hardening into permission.

Portability is the missing external discipline

Compliance costs become dangerous when there is no exit. In an ordinary service market, a customer dissatisfied with a provider can move. In the RIR system, the ability to move number resources across institutional boundaries remains constrained. That gives each regional registry a monopoly-like position over the recordkeeping interface for resources under its region. When a cross-border transfer sits inside LACNIC’s process, the parties cannot simply choose a different registry service with lower transaction costs or clearer settlement timing.

That lock-in changes behaviour. A registry may speak as if it is offering a service, but the parties experience it as a gate. If the gate is narrow, clear and tied to uniqueness, the system remains legitimate. If the gate widens into commercial supervision, there is little immediate market correction. The cost is spread across delayed transactions, discounted prices, abandoned deals and slower network expansion.

Portability would not eliminate compliance. A receiving registry would still need accurate records, fraud control and dispute awareness. But portability would introduce comparison. If one registry consistently turns transfers into broad inquiries while another keeps review narrow and efficient, operators would notice. Institutional discipline would come from the possibility of exit rather than from public assurances. The ability to leave is what turns stewardship claims into service quality.

The importance of portability is especially clear for cross-border assets. IPv4 use is global. A block historically associated with one service region may support customers elsewhere. A company incorporated in one country may serve users across several. A regional boundary can be useful for administration, language and local support. It is not a natural property line. When scarcity turns addresses into capital, the inability to move the recordkeeping relationship becomes an economic constraint.

Some defenders of thick regional control argue that portability would weaken regional stewardship. The better answer is that stewardship without exit is not stewardship; it is lock-in. If a registry’s value comes from competent, neutral recordkeeping, members will remain because the service is good. If they remain only because the resource cannot leave, the institution is relying on captivity rather than legitimacy.

For LACNIC, portability should be understood as protection rather than threat. A region with diverse legal systems benefits from a registry that can demonstrate discipline. If LACNIC keeps compliance narrow, predictable and commercially literate, it has little to fear from comparison. Indeed, it could become a model of thin coordination in a difficult legal environment. If it cannot keep compliance narrow, portability becomes the safety valve operators will eventually demand.

The absence of portability also intensifies the capital-control problem. A bank or tax authority exercises power under public law and within a jurisdiction. A registry exercises recognition power across a technical system that private networks have voluntarily accepted. When that recognition power is locked to a region and used to delay or condition cross-border asset movement, it begins to resemble capital control without the accountability of public law. That is precisely the role a registry should avoid.

Exit is not an attack on coordination. It is what keeps voluntary coordination honest. The Internet’s routing layer works because networks interconnect by agreement, not because a single institution can force all economic actors to stay inside one administrative boundary. The registry layer should learn the same lesson.

LACNIC’s institutional bargain is narrowness

LACNIC’s region gives it a difficult job. It must maintain records across many legal systems, languages, currencies and corporate forms. It must reduce fraud without freezing legitimate commerce. It must support a scarce IPv4 market without pretending to be the market’s owner. It must serve operators that range from large telecom groups to small access networks and local hosting companies. Its legitimacy therefore cannot rest on grand claims. It rests on a narrower bargain: keep the ledger accurate, protect uniqueness, respect lawful authority, isolate disputes and do not turn compliance into control.

That bargain is more demanding than it sounds. A narrow registry must be precise. It cannot hide behind broad language about community, region or stewardship when a transfer file raises a concrete question. It must say whether the issue is identity, authority, dispute, fraud, record accuracy, security metadata or something outside the registry’s role. It must resist pressure to use the transfer process as a substitute for tax enforcement, industrial policy, foreign-exchange supervision or moral judgement about IPv4 markets. Precision is not minimalism for its own sake. It is how the recordkeeper shows that its questions are tied to the ledger and not to economic preference.

The temptation to thicken the role will grow as IPv4 becomes more valuable. Higher prices attract more sophisticated buyers, more complex financing, more disputes, more historic title questions and more political attention. Each development can be used to justify another layer of review. But the correct response to higher value is not broader discretion. It is stronger narrowness. The more valuable the asset, the more important it becomes that recordkeeping be predictable, reviewable and limited to the risks the recordkeeper is competent to manage.

That is the lesson institutional economics brings to the registry world. When a record system sits above scarce capital, it becomes part of the asset’s cost structure. If the record system is neutral and efficient, it supports price discovery. If it is discretionary and expansive, it imposes a discount. The discount may not appear as a line item, but it is paid in lower sale prices, slower transfers, higher financing costs, reduced collateral value and delayed network expansion. Liquidity is not created by approving every request. It is created by making the conditions for refusal narrow, knowable and reviewable.

The region cannot afford that discount. Latin America and the Caribbean need more infrastructure investment, not less. They need regional cloud capacity, stronger access networks, better security services, more hosting options and resilient connectivity. IPv4 scarcity will not disappear because a registry dislikes the market. The practical question is whether scarce addresses can move through lawful, transparent and efficient channels toward the operators that can use them. Narrow compliance helps that happen. Broad compliance prevents it.

A disciplined LACNIC process would treat each cross-border transfer as a recordkeeping problem with commercial consequences. It would ask who the parties are, whether they have authority, whether the block is the block they claim, whether any known dispute or legal order prevents transfer, whether the settlement mechanism avoids obvious fraud and whether the post-transfer record will remain accurate. It would leave tax classification to tax authorities, banking review to banks, corporate strategy to boards and customer economics to operators.

That division of labour is not anti-registry. It is the only way a registry remains trusted when the resources it records become valuable. If LACNIC narrows compliance, it strengthens its role. If it expands compliance into economic approval, it weakens the basis on which operators consent to its authority. The registry record works because networks believe it describes reality better than the alternatives. When the recordkeeper starts deciding which lawful transactions deserve to become reality, that belief erodes.

The future of cross-border IPv4 liquidity in the LACNIC region will not be decided by slogans about scarcity or stewardship. It will be decided in ordinary files: a board resolution from one country, a notarised signature from another, a translation, a bank confirmation, a tax memorandum, a beneficial-ownership declaration, a legal opinion, an escrow condition, a legacy succession memo, a customer migration plan and a registry officer’s decision about whether the next question is necessary. The economics are hidden in that decision. Keep the question narrow, and compliance is a cost of accuracy. Let it expand, and compliance becomes a price of permission.

Sources and further reading

These references provide the article's public doctrine and background context. They are used for institutional-economic framing, not for adopting any registry or official-sector narrative.