Summary

  • LACNIC documentation burden is proof-cost economics: who must prove authority, how fast, in which language, before which deadline, and at what price.
  • Equal document rules can impose unequal costs on small operators, family businesses, universities, public bodies, legacy holders and cross-border buyers.
  • The positive alternative is a portable proof bundle and auditable custody model that verifies facts without turning paperwork into gatekeeping.

The transfer desk is usually quiet. It is a registry ticket, a shared folder, a bank compliance query, a lawyer's list of missing exhibits and an engineer's calendar with a customer migration date circled in red. A small internet provider in Latin America or the Caribbean may have held and used an address allocation for years. The network is real. Customers are billed. Routes have been stable. Taxes have been paid. Yet the name in the registry may belong to an older company, a founder who is no longer active, a predecessor entity or a structure that made sense before IPv4 scarcity turned old paperwork into a balance-sheet item.

The buyer may be ready. The seller may have legitimate control. The engineers may know exactly which blocks are being used and why they matter. The problem begins when recognition has to move. A bank wants to know why money is crossing borders for an intangible network resource. Counsel wants current corporate authority, translated registers, a board resolution, evidence that the relevant addresses were included in an old asset transfer and proof that the person signing today can bind the holder named years ago. A notary can certify one document but not another. A public register can issue an extract, but only in the local language and not before the payment window closes. The registry has not rejected the file. It has asked for more proof.

That is the point at which documentation stops being paperwork and becomes economics. The cost is not the PDF. The cost is producing evidence that the registry, the bank, the buyer, the seller, counsel and the operating network can all treat as sufficient. In a scarce IPv4 market, that cost changes price, timing, bargaining power and who can participate at all. A large carrier can buy legal time. A family-owned access provider cannot. A university may have institutional continuity but not corporate minutes. A small island operator may possess a valuable block but lack the archive needed to make it liquid. A merger may have transferred a network in every commercial sense while failing to name the number resources in the form now expected by a reviewer.

LACNIC is the right place to examine this problem because its service region is legally and economically varied. It includes large national carriers, small access networks, state bodies, universities, cooperatives, family firms, public research networks, cross-border groups, hosting companies, cloud buyers and local networks whose records were built for operation rather than resale. It also includes several languages, different company-register systems, different notarial practices, uneven banking access and countries where even a modest transaction can carry foreign-exchange, tax and compliance complications. A requirement that looks neutral from the review desk may become unequal at the closing table.

The argument is not that LACNIC should stop demanding proof. It must demand proof. Scarce number resources attract forged authorities, captured contacts, revived shell companies, false succession claims and transactions that launder uncertainty into apparent title. The issue is whether proof requirements remain tied to the narrow facts a registry must verify: existence, authority, succession, resource inclusion, absence of a live dispute, relevant account standing and continuity of the recognised holder. When proof expands beyond those facts into general comfort, commercial judgement or institutional preference, it becomes something else. It becomes a private capital-control mechanism wearing administrative clothing.

The proof cost is the price

Documentation burden is best understood as proof-cost economics. It is the fixed and variable cost of making a legal and operational history acceptable to the institution whose recognition gives the resource its external effect. That cost includes finding old documents, translating them, certifying copies, notarising signatures, aligning company names, proving current signing authority, explaining local law, reconstructing mergers, preserving confidential terms, responding to follow-up requests and waiting while reviewers decide whether the bundle proves enough.

The decisive word is acceptable. Evidence may exist and still fail the institutional test. A purchase agreement may show that a network business was sold, but not list each address block. An invoice may show continuous operation, but not authority to transfer. A board resolution may authorise a transaction, but use a company name that differs from the registry entry. A local corporate extract may prove existence, but require translation before a foreign buyer's bank will rely on it. A founder's letter may explain history, but not bind the present company. Every gap becomes a cost because every gap must be cured, explained, insured against or priced into the deal.

Scarcity gives that cost financial weight. When IPv4 space was abundant, proof defects were often operational irritants. A network could request more space, postpone cleanup or work around a stale account. After exhaustion, a recognised block can support customer revenue, leasing income, acquisition value, financing confidence and settlement of a sale. The same block can be perfectly useful in routing and still difficult to move in law. Packets follow working configurations. Money follows recognised control. The spread between those two states is proof cost.

The spread is highest where the transaction is modest. A /24 or /23 may be important to a local operator, yet too small to justify months of counsel, certified translations and repeated documentary cycles. A large buyer can spread proof work across many transactions. A small seller encounters the system once and absorbs the learning curve alone. A rule may treat both parties equally on paper; the cost per address does not.

This is why documentation review is market design even when no one calls it that. The registry does not need to quote a price to affect price. By deciding what proof is required, how substitutions are evaluated, when review pauses, how reasons are given and how long a file remains uncertain, the registry changes the liquidity of the resource. A clean proof path lowers the cost of trust. An open-ended path raises it and transfers value from the party with weak archives to the party with better lawyers, more time or a cleaner alternative.

The registry entry is only the starting point

This is not mainly an article about the visibility of registry data. Visibility matters, but it does not answer the hard transactional questions. A visible entry can show the name of a holder and still fail to show whether today's signer may authorise a transfer. It can identify an organisation and still leave uncertainty about corporate succession. It can identify a contact and still say little about whether a board, university rector, ministerial officer, liquidator or estate representative has authority to move scarce resources. The entry tells the market where to start. Documentation burden determines whether the market can finish.

Nor is the problem simply database cleanliness. An inaccurate record is harmful because it misleads counterparties. A stale record is harmful because responsibility becomes harder to locate. But proof cost often appears even when the broad picture is not obviously false. The resource may have been used continuously. The operating business may be real. Customers may have depended on the same network for years. The difficulty is that a new action, such as a transfer, merger update, regularisation, financing confirmation or account recovery, requires a higher proof standard than ordinary operation ever needed.

Confusing these two issues leads to the wrong remedies. If the issue is data quality, the answer is correction and maintenance. If the issue is proof cost, the answer is fact mapping, accepted substitutes, risk tiers, confidentiality rules, reviewable reasons and predictable timing. More visible data does not automatically reduce the cost of proving that an old asset sale included number resources. A cleaner entry does not automatically prove that a successor entity can bind the former holder.

The market sees the difference clearly. A buyer may know exactly which block it wants and which organisation appears in the registry. It may still discount the deal because the seller cannot prove succession cheaply. A bank may see the same entry and still ask for beneficial ownership, corporate authority and board approval. A registry reviewer may accept that the current operator is plausible and still require evidence that a legal chain exists. The record is the map; proof is the bridge.

That distinction is important for LACNIC because a tempting answer to messy history is to ask for more and more information until everyone feels comfortable. Comfort is not the same as proof. Each demanded document should be tied to a decision-relevant fact. If the document proves existence, authority, succession, resource inclusion, absence of dispute or another direct ledger fact, the burden may be justified. If it does not, the burden is not accuracy work. It is discretion with paper attached.

A region with different proof grammars

LACNIC's region does not have one corporate grammar. Brazil, Mexico, Argentina, Chile, Colombia, Peru, Central America and the Caribbean do not produce identical corporate files. Some jurisdictions offer digital extracts quickly. Others rely on paper, apostille, notarial certification or local filings that are slow to retrieve. Some companies operate through holding structures. Some networks belong to universities, municipalities, cooperatives or state agencies. Some small providers keep business records in a practical rather than company-secretarial form because their priority was keeping customers connected, not preparing for an address-market closing.

Language alone creates cost. Spanish and Portuguese dominate much of the region, but English, French and Dutch legal materials appear in parts of the Caribbean and in cross-border structures. A document that satisfies a local company registry may need certified translation for a buyer, bank or foreign counsel. Translation itself can create uncertainty: names, accents, abbreviations, officer titles and corporate forms may not map neatly into English. LACNIC staff may understand the local context; the buyer's bank may not. Counsel may insist on a translation that proves more than the registry needs.

Notarial culture also varies. In some jurisdictions, a notarised instrument carries strong evidentiary weight. In others, a notary certifies identity or signature, not the truth of the underlying corporate fact. An apostille may prove that a public official signed a document, not that the document proves succession. A board resolution may be ordinary for a private company and inappropriate for a university, ministry or municipal network. A one-form requirement across the region risks rewarding paper familiarity rather than truth.

The economic effect is uneven. A large group can hire local counsel in each jurisdiction and package evidence to a common standard. A small operator may ask a general commercial lawyer who has never seen a number-resource transfer. A university may need approvals from institutional bodies that meet infrequently. A municipal network may need a council minute. A family operator may need succession papers after a founder's death. These are not excuses for weak proof. They are reasons to define proof by function rather than document culture.

The right question is always: what fact must be proved? If the fact is legal existence, different jurisdictions can prove it differently. If the fact is authority, a board resolution, officer certificate, ministerial approval, court appointment, power of attorney or institutional delegation may each work depending on the holder. If the fact is succession, a merger deed, asset-sale agreement, law, insolvency order, inheritance document or continuity bundle may be relevant. Strictness is compatible with variety when the standard is truth rather than a preferred format.

Translation and notarisation turn time into money

Translation and notarisation often look like minor administrative steps. In a scarce-resource transaction they are economic instruments. They decide whether evidence can travel from local law into registry review, bank compliance and buyer diligence. They also decide how much time and money must be spent before the file becomes legible to every institution that must rely on it.

A corporate extract in Spanish may be obvious to a local lawyer and opaque to an English-speaking bank officer. A Portuguese resolution may authorise administration of network assets without naming number resources. A Caribbean certificate may use a corporate form unfamiliar to a continental buyer. A university decree may prove continuity but not resemble a commercial transfer document. Translation is not only language conversion. It is institutional conversion: the document must be made understandable to people who do not share the legal environment that produced it.

Certification adds another layer. A translator may certify accuracy. A notary may certify a signature. A public office may certify that a copy is true. An apostille may authenticate the capacity of a public official. None of those steps necessarily proves that a resource transferred, that a signer has authority or that a successor entity exists. Yet each step can be required before a counterparty feels safe. The cost multiplies when the registry asks for one proof, the bank asks for another and the buyer's counsel asks for a third.

There is also a timing cost. A document may need to be recent. A notary may be available only locally. A public office may take weeks. A translation may have to be redone if the company name is rendered differently from an earlier file. A bank's approval may expire while the registry waits for supplementary evidence. The transaction then pays twice: once for the document and once for the calendar time consumed by obtaining it.

The answer is not to abolish certification. Fraud prevention requires reliable evidence. The answer is to define when certification is needed and what it proves. If the registry needs only to know that a signer is an officer, a recent official extract may be enough. If a document is central to succession, stronger authentication may be justified. If a document is supporting context, an uncertified translation may be acceptable initially, with certified translation requested only if the file advances and the fact becomes material. Tiering reduces unnecessary upfront cost without weakening review.

Published expectations would help. LACNIC should make clear which categories usually require certified translation, which may be submitted in an original language, which require notarised signatures, which require apostille or equivalent authentication and which may be supported by a local counsel explanation. The purpose is not leniency. It is to stop parties from overbuilding proof packages because they fear an undefined comfort threshold.

Banks and escrow turn gaps into deadlines

The registry is not the only reviewer in the room. Banks and escrow providers translate proof gaps into deadlines. They may not understand number resources in technical detail, but they understand cross-border payment risk, beneficial ownership, sanctions exposure, source of funds, tax treatment and authority to sell. A bank officer may ask a simple question that becomes expensive to answer: why is money moving across borders for an intangible network resource, and what proves that the seller is entitled to receive it?

This second proof layer matters because it runs on a different clock from registry review. Bank due-diligence approvals can expire. Foreign-exchange permissions may be tied to a payment window. A corporate extract may be considered current for only a short period. A buyer's internal capital approval may lapse if settlement does not occur by quarter end. A cloud onboarding project may depend on address availability before customer migration begins. A registry request for supplementary proof can therefore reopen bank review even if the registry's own timetable remains reasonable.

The documents also do not serve identical purposes. LACNIC may need to know whether the current holder authorised a transfer. The bank may need to know beneficial ownership, payment purpose and whether the transaction price matches the contract. The buyer's counsel may need warranties and board approvals. The seller may need tax evidence. The operator may need customer migration authority. If these proof needs are not coordinated, parties produce overlapping packages, each with slightly different names, dates and translations. Small inconsistencies then create more questions.

Large firms manage this with closing checklists. They align the registry file, bank file, counsel file and engineering plan before the first submission. Small operators often discover the layers sequentially. First the registry asks for authority. Then the bank asks for translated corporate papers. Then escrow asks for proof of registry approval. Then the buyer asks for a board authorisation that names the resource more specifically. Each step may be rational. Together they turn a modest transfer into an endurance test.

LACNIC cannot control bank compliance, and it should not try. It can reduce avoidable collision by making registry milestones more legible. Parties should know which event counts as initial acceptance, which event means approval subject to signatures or payment, which event changes recognition and which deficiencies are curable. Clear milestones help banks structure conditions and help small operators avoid producing every possible document at the most expensive moment.

The bank layer shows why proof cost is not administrative trivia. It determines whether capital can move on schedule. A delayed translation can mean a missed financing window, a repriced sale or a failed customer launch. In a scarce-address market, time is part of the asset.

Authority is broader than a signature

Many documentation disputes begin with a signature and end with authority. A person signs a transfer request, a resolution, a service agreement or a letter explaining history. The signature may be genuine. The harder question is whether the person can bind the holder for the action requested.

In ordinary network operations, authority is often practical. Engineers manage routes. Finance pays invoices. A founder answers registry email. A consultant handles portal work. A local manager signs customer contracts. Scarce-resource transactions require more. They may move value, alter the recognised holder, affect lenders, change customer continuity or expose the company to indemnities. LACNIC cannot assume that the person with technical access can approve economic disposition.

Corporate authority has layers. The entity must exist. The person must hold a role. The role must include authority for the action. The company may need board approval. A shareholder agreement may restrict asset sales. A public body may need ministerial consent. A university may need approval from a council or rector. An insolvency administrator may need court authority. A subsidiary may operate the network but not own the resource relationship. Each distinction can matter when scarcity turns recognition into value.

This is not bureaucracy for its own sake. It prevents theft and internal abuse. A former director should not be able to monetise a block. A consultant should not be able to sign away a holder's position. A technical contact should not become a power of attorney by habit. A buyer should not acquire a claim only to learn that the seller's internal authority was defective.

The danger is overreach. LACNIC must verify authority for the requested action. It should not use authority review as a channel to examine every commercial motive. If the board, officer, public authority or court-appointed representative can lawfully authorise the action under the applicable rules, the registry's task is to test authority, eligibility, resource linkage and record safety. It is not to decide whether the seller should have leased instead of sold, whether the price is attractive or whether a particular buyer is fashionable.

Good authority review is fact-specific. It asks who can sign, under what document, for what action, in what capacity and with what limits. It should separate technical account access from legal authority, and legal authority from commercial judgement. That separation protects both sides: holders are protected from unauthorised transfers, and legitimate transactions are protected from being delayed by questions that do not prove a registry-relevant fact.

Legacy allocations carry hidden debt

Legacy history is where proof cost becomes most visible. Many allocations were made when the internet was smaller, personal relationships mattered more and few expected a mature market for address transfers. The records may contain older corporate names, outdated contacts, informal correspondence, handwritten approvals, early email addresses, predecessor networks or references to entities that later merged, dissolved or changed form. The resource may have stayed in use throughout. The documentary trail may not have stayed clean.

That creates hidden debt. The holder appears to own an operational advantage until it tries to regularise, finance, merge or sell. Then old gaps become payable. Who was the original holder? Did the business that received the allocation become the current operator? Was there a name change, a merger, an asset sale or a long informal migration? Were the number resources included expressly or only implicitly as part of the network? Were fees paid by the same legal person or by a successor? Did the registry ever recognise a change in practice without recording the full evidence?

Legacy proof is difficult because the evidence may be distributed across people, systems and institutions that no longer exist. A founder may remember the history but no longer have authority. A former lawyer may have closed the file. A company register may hold only part of the story. A tax record may prove operation but not title. A routing history may prove use but not legal succession. An invoice may prove relationship but not transfer. No single document is decisive, yet the collection may tell a coherent truth.

The registry's task should be to identify the missing fact, not to demand a perfect archive. If the issue is whether the current company is the same legal person under a changed name, official name-change evidence may solve it. If the issue is whether an asset sale included the network and number resources, the proof may require an agreement, schedules, invoices, customer migration records and a statement from a responsible officer. If the issue is whether a dormant predecessor has a competing claim, notices, dissolution records or legal opinions may be relevant.

Legacy review also needs proportionality. A stale contact update should not be treated like a value-moving sale. A transfer to an unrelated buyer deserves stronger proof than an internal correction. A plausible continuous operator should not be pushed into operational uncertainty merely because a thirty-year-old file is incomplete. Conversely, a dormant company suddenly represented by a new actor should trigger serious scrutiny. Risk tiering allows both positions to be true.

Without that discipline, old networks pay a poverty penalty for having been early. Their historical contribution becomes a liability because the evidentiary standards changed after the facts occurred. LACNIC can avoid that unfairness by accepting cumulative proof, explaining gaps and distinguishing missing formalism from suspicious contradiction.

Mergers and reorganisations create proof traps

Mergers create evidence factories. They produce purchase agreements, schedules, board approvals, tax filings, regulatory notices, employee transfers, customer assignments, debt consents and closing certificates. Yet even a large merger can fail the number-resource test if the relevant documents were drafted without address resources in mind. The deal may transfer "all network assets" or "telecommunications operations" without listing prefixes. It may move customers, routers, contracts and licences while leaving the registry entry under a predecessor name. Years later, a transfer reviewer asks for a link that the closing lawyers never wrote in the language now expected.

This is common because business lawyers historically treated number resources as operational inputs rather than standalone scarce assets. They focused on shares, licences, customer contracts, equipment, spectrum, real estate, employees and debt. Address resources sat in a technical appendix, a network operations file or no schedule at all. After scarcity, that omission becomes expensive. The current operator may have the substance of succession but not the exhibit that makes the claim easy to approve.

Reorganisations produce similar traps. A group creates a new operating company, merges subsidiaries, changes names, spins out a hosting business or centralises network assets. In commercial life, the move is clear. In registry proof, every step may need to be mapped: predecessor, successor, authority, effective date, resource inclusion and absence of competing claims. If several reorganisations occurred over years, the chain can become long enough that one missing link discounts the whole asset.

Public and regulated transactions add complexity. A privatisation, concession transfer, insolvency sale or government restructuring may move network operations by statute, court order or administrative resolution rather than private contract. A private-company template will not fit. The registry still must verify authority and succession, but it should not insist that every institutional change resemble an acquisition closing.

The best fix is prospective clarity. If future deals should name number resources explicitly, LACNIC should say so plainly. If resolutions should identify the relevant ranges or authorise a category of number-resource actions, examples should be available. If a transferred business must provide customer or numbering continuity evidence, the purpose and confidentiality treatment should be defined. The cheapest documentation burden is the one prevented before the transaction is signed.

Review practice should also allow retrospective repair. Where an old merger did not list addresses, a bundle may still establish the chain: the main agreement, network schedules, customer transfers, invoices, tax records, officer certificates, prior registry communications and operational evidence. The reviewer should state which fact remains unproven rather than treating the absence of a perfect schedule as automatic failure. That approach protects against fraud while recognising how deals were actually documented.

Family operators and the cardboard-box file

Many smaller networks are not miniature versions of multinational carriers. They are family businesses, engineer-founded ISPs, regional wireless providers, local hosting firms or community-rooted operators whose files reflect survival rather than corporate polish. Their archive may be a cardboard box, a folder of invoices, regulator letters, tax records, old allocation messages, signed customer lists, founder emails and bank receipts. The file may prove a real business. It may not look like a formal data room.

This creates predictable asymmetry. Large firms keep company-secretarial records, board minutes, authorised-signatory matrices and transaction schedules. Small operators keep what was necessary to operate, satisfy a bank, pay taxes and serve customers. When scarce-resource transactions require formal proof, the small operator must convert a practical history into a legal package. That conversion can consume management time, legal fees and calendar time out of proportion to the transaction.

Family succession can be particularly hard. A founder dies, retires or transfers the business to children. The network continues. Customers are billed. Equipment is maintained. The address resources remain in use. But the registry entry may still contain the founder's email, an old company name or a predecessor entity. To regularise or sell, the new operators must prove inheritance, corporate continuity, current authority and resource linkage. A document missing from the founder's archive can become a market discount.

It is tempting for institutions to treat weak archives as suspicious. Sometimes they are. Fraudsters exploit dormant companies, old contacts and informal records. But weak archives can also be evidence of local business reality. The review problem is to distinguish missing formalism from false claims. That requires alternative evidence, phased review and reasoned categories, not blind trust and not automatic suspicion.

A small-operator-safe proof standard would ask for the strongest available evidence while explaining what fact remains missing. It would allow a bundle where no single document is decisive. It would separate low-risk contact correction from high-risk transfer. It would offer pre-clearance guidance before the operator spends heavily. It would avoid threatening operational continuity merely because a historical file is incomplete, unless fraud, competing claims, court orders or security compromise require stronger action.

The economic test is simple: can a competent small operator comply without surrendering a disproportionate share of the resource's value to proof production? If the answer is no, the rule may be formally equal but economically regressive. In a region where local providers often serve places that large networks do not prioritise, that matters. Documentation cost can decide whether a working local resource becomes safely transferable, remains trapped or moves through informal arrangements that give everyone less protection.

Universities and public bodies need their own evidence paths

Early internet development often ran through universities, research networks, state agencies and public bodies. These institutions leave different evidence trails from private companies. A university may change its legal style, centralise departments, create a network office, merge campuses or transfer operations to a national education network. A ministry may reorganise. A municipal network may become a public corporation. A state carrier may be privatised and later restructured. Authority may sit in statutes, governing-council minutes, ministerial delegations, budget approvals or administrative orders.

If the documentation standard assumes a private company with directors, shareholders and ordinary board resolutions, public and academic holders face unnecessary cost. They may not have directors in the relevant sense. They may not issue a standard good-standing certificate. They may not have a purchase agreement. Their authority may be perfectly valid but expressed through a different institutional form.

The registry still needs proof. Public status does not make a claim true. A current university officer should not be able to monetise resources allocated to a different institution without showing continuity. A ministry should not transfer a network resource if another public entity is the actual successor. A public body can be dissolved, merged or split in ways that require careful analysis. The proof target, however, should be the underlying fact, not a private-law template.

Universities and public bodies also face public accountability. A resource transfer may require procurement review, budget approval, public notice, internal audit or approval by a governing body that meets on a fixed schedule. A delay in registry proof can collide with budget windows. A translated opinion may be needed for a foreign buyer. A public institution may avoid regularisation if it fears that contacting the registry will open a complex and costly review. That avoidance leaves records stale and increases fraud risk.

Good practice would create specific paths for academic and public-sector succession. Common evidence types include statutes, ministerial orders, governing-body minutes, public-register entries, auditor confirmations, institutional letters, budget records and historical technical correspondence. LACNIC should state how confidentiality and public-law obligations are handled, which actions preserve continuity and which actions move value. A public body should not have to impersonate a private company in order to prove a public-law fact.

Academic and public-sector history should be treated as part of the region's infrastructure memory. The goal is not to exempt it from proof. The goal is to make proof compatible with the institutions that actually built and maintained parts of the network.

Fraud prevention must stay narrow

The strongest defence of documentation burden is fraud prevention. It is also the easiest defence to overextend. Fraud prevention is necessary when scarce resources can be sold, leased, financed or used to support customer revenue. A forged board resolution, captured account, false successor claim or revived shell company can move value away from the rightful holder and damage trust in recognised control. LACNIC must protect against that.

The narrow fraud mandate asks specific questions. Does the entity exist? Is the requester authorised? Does the claimant connect to the recognised holder or lawful successor? Were the resources included in the transaction being presented? Is there a live dispute? Are documents authentic? Has an account been compromised? Is a court order or lawful restriction relevant? Are account obligations directly tied to the requested registry action unresolved? These questions protect the ledger.

A broader mandate asks different questions. Is the buyer the preferred kind of operator? Is the seller making too much money? Should the resource have been used differently? Is leasing unattractive as a business model? Is the commercial structure too financial? Does the transaction feel inconsistent with institutional taste? Those questions may be debated if explicit rules are proposed. They should not be smuggled into document review.

This boundary is central. A registry may record, coordinate and protect uniqueness. It may verify proof of control. It may maintain continuity. It may not convert scarcity into a general power to approve or disapprove capital movement. Fraud control is legitimate because it protects the truth of the record. Business-model control is different because it allocates economic freedom without bearing the holder's loss.

The distinction also protects LACNIC. Overbroad demands invite disputes and suspicion. A member is more likely to accept a request for a missing authority document than a vague demand for comfort about the whole commercial plan. Courts, banks and counterparties can understand a narrow proof request. They are less likely to defer to a registry that cannot show how its demand maps to a specific risk.

Fraud prevention should therefore be written as fact mapping. Every document request should answer four questions: what risk does this address, what fact would cure it, what substitutes are acceptable and what happens if the fact remains unproven? That discipline makes strong proof compatible with market access.

Delay creates private rents

Delay is not neutral in a scarce-resource market. It reallocates value. A buyer waiting for recognition may miss a customer deadline, extend a cloud onboarding, lease temporary space or pay a premium for a cleaner alternative. A seller waiting for approval may face financing pressure, renewal costs, currency movement, bank-review expiry or renegotiation. A lender may hold funds. A broker may gain leverage because it understands the review process better than either party.

The rent created by delay often appears as expertise. Lawyers, consultants, brokers, translators and notaries can add real value by producing reliable proof. They also profit from uncertainty. If ordinary members cannot tell what evidence will be accepted, specialists become interpreters of institutional mood. That may be useful in hard cases. It is harmful when expertise is needed only because standards are unclear.

Repeat players benefit most. A frequent buyer learns which documents tend to satisfy review, which translations are accepted, which wording belongs in resolutions and which timelines are realistic. A one-time seller learns by paying. The buyer can use that knowledge to demand a discount, require pre-clearance or shift proof risk onto the seller. The seller may accept because it cannot estimate the alternative.

Delay also encourages informal arrangements. If formal transfer is slow, parties may lease, sublease, route under private letters, rely on side undertakings or postpone registry updates. Some of these arrangements may be lawful and practical. But excessive proof cost can push activity into less visible forms. The registry then loses the clarity it wanted to protect. A process designed to prevent opacity can create opacity if it is too slow or uncertain.

Time discipline is therefore part of documentation reform. LACNIC should publish target periods by risk tier, distinguish applicant delay from registry review, identify when a file is paused for external evidence, state what facts remain missing and report aggregate long-tail timing. Median timing matters, but the long tail matters more. Markets price the worst plausible delay, not average service.

Cure periods are equally important. A missing document should trigger a precise cure request. A severe consequence should require a severe ground: fraud, competing claim, court restriction, serious contractual default or security compromise. Delay should not become punishment by another name. If a file is incomplete but plausible, the registry can protect against value-moving changes while preserving ordinary continuity. That reduces bargaining harm without weakening proof.

Equal rules can impose unequal costs

A rule can be identical and still unequal. If every applicant must produce a recent corporate extract, the cost may be trivial for one company and significant for another. If every cross-border transaction requires certified translation, the cost may be absorbed by a multinational and distort the economics of a small island transfer. If every merger file expects a detailed resource schedule, recent deals will comply more easily than older deals whose documents were drafted before address scarcity created the demand.

This is a transaction-cost problem. The rule is not evaluated only by its text. It is evaluated by who must spend what to comply, who can predict the cost, who can wait, who can finance uncertainty and who captures value from others' inability to prove cheaply. Documentation burden is regressive when it contains large fixed costs and when archives are uneven.

Small-operator inequality is not solved by lowering standards for small operators. That would weaken the market and harm the same parties by making their resources less trusted. The better answer is to lower avoidable cost for everyone: clear categories, examples, substitute evidence, early triage, safe pre-clearance, confidentiality protections, timelines and reviewable reasons. Reliability can be high while the path to reliability is less wasteful.

This distinction matters in a region where small networks may serve places and customers that large networks do not prioritise. A rural wireless provider, local hosting company, municipal network or island ISP may hold modest resources that support real services. If proof costs make those resources illiquid, the local economy loses options. The addresses may remain trapped, underused or leased informally because formal movement consumes too much value.

The same applies to buyers. A small buyer may need only a modest block to serve a real customer base. If recipient proof, bank compliance and translation costs are high relative to the block, the buyer may abandon the formal path. A large buyer can buy larger blocks, amortise cost and wait. Equal documentation can therefore concentrate market access.

LACNIC cannot equalise every balance sheet. It can avoid adding unnecessary inequality at the proof layer. It can design for the operator with a data room and the operator with a cardboard box, without pretending their files are identical. The standard of truth can be common. The evidence routes should be diverse enough to make truth provable.

Documentation can become hidden capital control

Capital control usually suggests a state restricting money movement. In number-resource economics the mechanism is quieter. A registry does not need to block bank transfers or set prices. It controls the recognition point at which a private bargain becomes a settled resource position. If recognition is slow, uncertain or conditional on broad comfort, capital is trapped. If recognition is narrow and predictable, capital can move.

This is hidden capital control because it operates under administrative names: documentation, account standing, authority review, recipient justification, dispute check, translation, authenticity certification, service agreement and risk review. Each category can be legitimate. Together they become a market-shaping system if they are not bounded. The registry may say it is only protecting the ledger. The holder may experience a permission regime over whether value can be realised.

The danger is greatest when proof standards drift from record truth into commercial preference. A documentation request that proves corporate succession protects the ledger. A request that effectively asks whether the transaction is socially desirable controls capital. A delay caused by a real dispute protects against false finality. A delay caused by unease over seller profit or buyer type is market direction. A requirement to prove signing authority is necessary. A requirement to justify the entire business future of an already issued resource can become rationing after the rationed pool is gone.

Hidden control is harder to challenge than explicit policy. If LACNIC adopted a rule directly restricting certain transfers, members could debate it and measure its effect. If the same effect appears as unpredictable proof demands, applicants may not know whether they face law, risk, staff preference, institutional caution or missing evidence. The cost appears privately as delay and discount. It rarely becomes visible enough for collective correction.

The remedy is not deregulation. It is nexus. LACNIC should intervene when the matter affects uniqueness, recognised authority, legal ability to act, fraud risk, dispute containment, operational continuity, clear rule compliance or directly relevant account obligation. It should step back when the matter is price, profit, buyer identity as a matter of taste, broker presence, leasing yield, capital movement or moral discomfort with IPv4 commerce, unless an explicit rule squarely governs the issue.

A registry that keeps this boundary becomes stronger. It can be strict without being suspected of discretionary control. It can reject weak files with reasons. It can protect small holders from fraud while preserving liquidity. It can avoid becoming an economic ministry in registry clothing.

Holder rights and running-code primacy

The proper starting point is the holder and the running network, not institutional self-description. Networks carry customers, uptime obligations, contracts, routers, bank debt, regulatory duties and business risk. Registry recognition matters because it supports those real operations. It is not the source of all value. Value arises from scarcity, customer demand, operational reliance and the ability of networks to use unique identifiers without collision.

Holder rights follow from that reality. A holder should have the right to accurate recognition, operational continuity, proportionate proof, reasoned adverse decisions, confidentiality, transfer without permission theatre and protection against the use of documentation as punishment. These rights do not eliminate registry authority. They discipline it. A registry may verify. It should not rule beyond the facts that make verification necessary.

Running-code primacy is the practical expression of the same principle. The internet was built by working networks that coordinated because coordination made operation possible. Registry procedure is legitimate when it helps those networks avoid conflict, preserve uniqueness and maintain trust. It loses legitimacy when procedure becomes more important than the continuity of services already running. A missing document may justify pausing a value-moving transfer. It should not casually endanger customers who depend on an established resource, unless fraud, court order or security necessity requires it.

This does not mean incumbents can hide behind operation. A running route is not proof of legal authority. A long-used resource may still be contested. A holder may need to produce evidence before transferring, leasing or changing recognised control. Running-code primacy is not a licence to ignore proof. It is a warning against using proof gaps to create disproportionate operational harm.

The liability asymmetry makes the warning sharper. Registries exercise powers whose economic effect can be large while their contractual liability is often limited. A delayed or refused update can affect transaction value, customer migration, financing and service continuity. The registry may not bear the proportional loss. That asymmetry requires stronger procedural discipline: narrow reasons, documented fact mapping, review paths and continuity preservation.

Mandate laundering occurs when a registry uses broad institutional language to expand discretion beyond the ledger function. Documentation review is one of the easiest places for that to happen because the expansion looks technical. A narrow holder-rights framework prevents the drift. It says: prove what the ledger needs, protect what runs, explain what is missing and do not convert evidence into rule.

Portability would discipline proof

Documentation burden is heavier when holders cannot exit. If a registry is the only recognised path for a holder's resources, every proof demand carries monopoly weight. The member can comply, delay, litigate or accept a discount. It cannot easily move its recognition relationship to a better administrative environment. Coordination becomes lock-in.

Portability would change the incentive structure. If number resources could be transferred between compatible registry service providers without losing the resource, a registry would need to compete on clarity, fairness, timing and reliability. Overbroad documentation demands would become costly to the institution because holders could choose a better proof service. Exit would discipline discretion more effectively than service language alone.

Portability does not mean weak verification. A portable system would still need proof of control, uniqueness, dispute status, authority and continuity. In fact, portability requires better evidence because another registry or custody layer must be able to rely on the file. The difference is that proof becomes a portable asset rather than a hostage record. Once a holder has assembled a verified bundle, it should not have to rebuild the same history from zero for every institutional interaction.

The absence of portability deepens small-operator inequality. Large actors can manage registry dependency through lawyers, brokers, patience and visibility. Small operators are more exposed. They cannot credibly threaten exit. They may fear that challenging a request will worsen the relationship. Documentation then becomes discretionary leverage even when no one intends abuse.

A portability discipline would require common proof categories: holder identity, current authority, resource range, succession chain, dispute state, prior recognition events, confidential-evidence attestations and operational-continuity commitments. It would also require auditability so receiving institutions can see why a fact was accepted without necessarily seeing every confidential document. This would lower repeated proof costs while preserving fraud controls.

For LACNIC, portability thinking is useful even before formal portability exists. The registry can behave as if its proof decisions should be understandable to an independent reviewer and reusable by the holder. It can create records that survive staff turnover, cross-border transactions and future disputes. It can treat evidence as a holder asset, not merely an intake burden. That is the path from gatekeeping to custody.

NRS as auditable custody infrastructure

The positive future is not a registry that stops asking for proof. It is a system in which proof becomes portable, auditable and controlled enough that holders do not have to surrender economic freedom to administrative uncertainty. The Number Resource Society, or NRS, points toward that model. Its importance lies not in replacing one gatekeeper with another, but in changing the architecture: from isolated holders pleading through repeated document cycles to resource holders carrying verifiable proof bundles that can be checked, updated and relied upon across service contexts.

A portable proof bundle would contain the evidence needed to establish control without exposing every private document to every counterparty. It could record the resource range, recognised holder, current authority, historical succession, prior transfers, dispute status, relevant agreements, confidential-document attestations, operational-custody arrangements and review history. Sensitive contracts and personal data could remain protected, while hashes, attestations or audit statements preserve integrity. The bundle would not be a marketing brochure. It would be a custody file.

Auditable custody would separate facts from discretion. One layer would say which facts are verified. Another would say which actions are requested. A third would record restrictions, disputes or pending evidence. A reviewer could see whether a transfer is blocked because authority is missing, a document is forged, a court order applies, an account obligation is unresolved or the institution is merely uncomfortable. That distinction is the difference between ledger protection and hidden capital control.

Such a model would help LACNIC-region holders precisely because their proof environments are diverse. A family ISP could assemble a continuity bundle before seeking a sale. A university could preserve institutional authority evidence without converting itself into a private-company template. A public body could attach statutory proof. A cross-border group could maintain resource schedules through reorganisations. A small operator could reuse verified evidence for bank review, buyer diligence and registry review. Proof would become capital-preserving infrastructure.

NRS also aligns with the narrow-ledger doctrine. It does not ask a registry to become a capital controller. It does not sacrifice fraud prevention to market speed. It starts from holder rights, portability, continuity, auditability and running-code primacy. It treats registry recognition as coordination, not command. It makes the proof file legible without making every private document public. It gives the holder a durable evidence asset rather than forcing the holder to reconstruct history under deadline pressure each time a transaction, bank inquiry or institutional update arises.

The transfer desk at the opening of this article should not have to choose between fraud risk and economic paralysis. The small ISP should be able to prove who it is, how it inherited the allocation, who may sign, what documents support the chain and what remains uncertain. The buyer, bank, counsel and registry should be able to rely on an auditable custody file rather than recreate history from fragments. If the proof is weak, the market should see why. If the proof is strong, recognition should not be delayed by institutional mood.

That is the real reform. Documentation should prevent theft, not manufacture dependency. It should lower the cost of trust, not convert old archives into poverty penalties. It should make scarce resources more safely movable, not trap them behind discretionary comfort. LACNIC's legitimacy in the IPv4 scarcity era will not be measured by how much paperwork it can demand. It will be measured by whether proof is narrow, portable, reviewable and tied to the running networks that give the ledger its purpose.

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.