The trade is not closed until the record moves
An IPv4 transfer looks, from a distance, like a simple private bargain. One network has more addresses than it now needs. Another has customers, equipment, contracts or migration plans that require more IPv4 reach than its existing stock can provide. A price is agreed. Lawyers draft warranties. A broker may introduce the parties. An escrow provider waits for instructions. Money and addresses appear ready to pass in opposite directions.
That view misses the decisive actor. The deal is not economically complete when the seller signs, the buyer wires funds or the broker congratulates both sides. It is complete only when the registry recognises the new holder and the surrounding operational machinery begins to follow. The block must be clean enough to move, the seller must be authoritative enough to transfer it, the buyer must be eligible enough to receive it, the documents must satisfy the category of transaction, and the public record must settle the question of who is responsible for the resource.
That is why transfer architecture matters. In a post-exhaustion IPv4 market, registry process is not a clerical afterthought. It is part of the asset. The same /22 can be worth different amounts depending on whether its holder records are current, whether the resource has been involved in a dispute, whether reverse DNS and RPKI can be transitioned without friction, whether the buyer can pass a need review, whether a renewal invoice is about to complicate closing, and whether the transaction must be coordinated with another regional internet registry. Price is therefore not only a judgement about scarcity. It is a judgement about settlement risk.
LACNIC's setting makes that point sharper. It serves Latin America and the Caribbean, a region that contains large continental economies, small island networks, volatile currencies, public-sector networks, family-owned providers, cross-border groups, universities, data-centre operators, mobile networks and global platforms. LACNIC is an international, non-governmental organisation based in Uruguay. It manages IPv4, IPv6, autonomous system numbers and reverse resolution for the region, and its own public description places it among more than 13,000 network operators across 33 territories. Those facts explain the institutional setting. They do not answer the market-design problem.
The problem is that a registry with a technical mandate now sits at the closing table of a scarce asset market. LACNIC does not set the price of a block. It does not promise liquidity. It says it does not intervene in the commercial operations between the parties to a possible transfer. Yet its rules decide when a private bargain becomes a recognised resource movement. A minimum transferable size shapes supply. Need review shapes demand. A holding period changes inventory strategy. A dispute check protects title but can also freeze capital. Documentation categories decide who needs counsel and who can close cheaply. Transfer logs reduce information asymmetry if they are usable. Inter-regional compatibility widens or narrows the buyer pool.
That is not a complaint that LACNIC has a role. It must have one. A registry that recognised transfers without verifying authority, identity, disputes, signatures and operational responsibility would invite theft, double sale, forged documents and routing confusion. The question is whether that role is designed as an exacting settlement utility or as a hidden market regulator. The difference is measured in documentary proportionality, timing, reviewability, operational continuity and the discount a buyer demands for registry uncertainty.
The best transfer architecture is therefore neither laissez-faire theatre nor suspicion dressed as stewardship. It recognises that IPv4 addresses are not ordinary property, but also that scarcity and recognised transferability make them behave like assets. It protects the record without pretending that the registry can abolish the economics of scarcity. It lets underused resources move toward productive use without letting market pressure corrode the trust on which the registry record depends.
Finality is the product
The buyer in an IPv4 transaction is buying more than a string of numbers. It is buying the confidence that those numbers will be uniquely registered, operationally usable and accepted by counterparties as belonging under its administrative responsibility. That confidence is what turns a private claim into network capacity. Before recognition, the buyer may have a contract against the seller. After recognition, the buyer has a public point of reference that suppliers, customers, lenders, upstreams and abuse desks can use.
That distinction is why settlement finality should be the organising concept for LACNIC transfer policy. A transfer is not just a change in a database field. It is a sequence of risk reductions. The old holder is verified. The resource is checked for dispute. The receiving organisation is assessed under the applicable policy. The legal document is accepted. In inter-regional cases, the source and destination registries coordinate their recognition. The resource information is modified. Public registration data, contact data, reverse DNS and RPKI then have to become coherent with the new state of the resource.
LACNIC's transfer rules make this architecture visible. IPv4 transfers can occur within the LACNIC region and across regional registry boundaries. The minimum transferable block is a /24, a practical floor that aligns the market with the smallest generally routable IPv4 unit. A recipient inside the LACNIC region must justify the IPv4 resources before LACNIC under the applicable initial or additional allocation and assignment policies. LACNIC, or the corresponding registry in an inter-regional case, verifies the holder and checks that the resources are not involved in a dispute. For intra-regional transfers, the parties must submit a signed legal document supporting the transfer. For inter-regional transfers, supporting documentation follows what the relevant registries have agreed. When the transfer is completed, LACNIC modifies the resource information to reflect the new holder.
Each step has a record-protection logic. Minimum size prevents the market from encouraging fragments that are of little use and harmful to routing discipline. Holder verification prevents theft. Dispute checks keep a registry from laundering contested control into clean commercial title. Legal documents tie the registry record to corporate authority. Inter-regional coordination avoids inconsistent recognition of a globally unique resource. Updating the record gives the market a settled reference point.
The economic effect lies in the same steps. A seller with clean authority can demand a better price than one with stale contacts and missing corporate history. A buyer that has already passed or prepared for need review can move faster than one that treats eligibility as a post-signature nuisance. A broker with repeated LACNIC experience earns a return not merely for finding supply, but for knowing where settlement can slow down. A bank or escrow provider that understands the registry milestones can release funds with more confidence. A small operator that does not understand those milestones pays, in price or delay, for uncertainty.
Finality must therefore be visible enough to be priced. Markets can bear friction when the friction is legible. A buyer can accept a need test if it knows what the test examines. A seller can accept a dispute check if it knows what counts as a dispute and what evidence clears it. A lawyer can draft a closing condition if the registry's recognition events are defined. An escrow provider can stage release if it knows the difference between approval, record update, public log entry and operational-service availability.
Opacity works differently. If the process can stretch because an undefined comfort level has not been met, the market turns caution into a premium. Sellers accept discounts. Buyers demand broader warranties. Brokers become interpreters of institutional mood. Repeat players gain a structural advantage over one-off participants. LACNIC does not need to intend any of these outcomes. They follow from settlement design.
The strongest transfer regime is strict but bounded. It says what facts matter, what documents normally prove them, what happens when evidence is incomplete, how disputes are classified, how inter-regional handoffs proceed, and which operational services may lag after recognition. It does not promise instant transfers. It promises that delay has a reason tied to the truth of the record, the authority of the parties, a policy requirement or an operational dependency. That is the kind of finality that markets can trust.
Documentation sets the spread
Documentation is often described as administrative burden. In an IPv4 market it is better understood as spread. It creates the difference between the headline value of a block and the price a buyer is willing to pay after accounting for the cost of proving that the block can move. It determines whether a seller can close with ordinary paperwork, whether a buyer must hire specialist counsel, whether escrow instructions can be simple and whether a broker is a convenience or a necessity.
LACNIC's public material distinguishes several kinds of documentation. In a routine intra-regional transfer, the administrative contact of the offering organisation starts the request and provides information about the resource, the receiving organisation and the reason for the transfer. LACNIC may ask for documents showing that the applicant is authorised to request the transfer, and it may use external collaborators to certify the authenticity of documents. If the request is approved, the parties sign a transfer agreement and a joint order. If the receiving organisation has not previously received LACNIC resources, or if it holds legacy resources, it must sign a service agreement with LACNIC.
Corporate events require a different frame. In mergers, acquisitions, reorganisations, relocations or name changes, LACNIC processes and registers IPv4 resource transfers arising from those events, whether complete or partial and whether the resources are held by an ISP or an end user. The applicant must submit legal documentation supporting the operation, with LACNIC retaining discretion over what is sufficient. Public instructions refer to documents supporting the transfer of assets, an inventory of assets used to keep the IPv4 space in use, and customer lists or numbering plans to justify need. That is not the same transaction as a negotiated sale between unrelated parties, even if both end with a changed holder.
Inter-regional transfers add a second institutional layer. A transfer from LACNIC to another registry begins with the offering organisation's administrative contact and LACNIC's verification. If it passes, LACNIC pre-approves the request and notifies the destination registry. The destination registry then analyses the receiving organisation. When that registry approves, the operation proceeds in coordination. A transfer into LACNIC reverses the sequence: LACNIC receives the request from the origin registry, contacts the recipient in the LACNIC region, asks for documentation and additional information to justify need, and coordinates the transfer if the request is approved.
These categories matter because they carry different settlement risks. A current LACNIC member selling a cleanly held /24 to another current member is one profile. A sale involving a privatised public network, a dissolved parent company, a cross-border treasury function, a founder who remains the historical administrative contact, a Caribbean corporate registry, an asset sale rather than a share sale, or a block that must enter from another region is another. The registry may view both as ordinary enough to process. The market will not price them the same.
The fixed cost of documentation is not neutral. A multinational operator can maintain staff who know registry procedure, outside counsel who understand asset transfers, and brokers who have closed similar deals. A large Brazilian or Mexican buyer may have repeated experience with regional resource channels. A cloud or hosting company may have a standard transfer playbook. A small seller disposing of a /24 or /23 may have one engineer, one local lawyer and a bank that is already uncomfortable with a foreign payment for an intangible network resource. The phrase "additional documentation" does not fall equally on both sides.
That does not mean proof standards should be relaxed for small organisations. Lower proof would weaken the record and invite exactly the fraud that makes transfers more expensive for everyone. The better answer is categorical clarity. LACNIC can reduce transaction costs by publishing, in operational language, the ordinary evidence expected for common cases: routine holder transfer, merger, acquisition, asset sale, share sale, name change, relocation, public-sector succession, insolvency, legacy regularisation, account recovery, suspected fraud, court-disputed resource and inter-regional import or export. For each category, the market would benefit from knowing the normal document types, acceptable substitutes, translation expectations, signature authority, timing target and escalation path.
That kind of documentation map would not be bureaucratic ornament. It would be liquidity infrastructure. It would let sellers know before negotiation whether their records are marketable. It would let buyers distinguish a slow file from a hopeless file. It would let lawyers draft warranties and escrow triggers around known evidentiary milestones. It would reduce the private premium earned by those who know the process by reputation rather than by published rule. It would also protect LACNIC staff, because applicants pressing for special treatment could be pointed back to a common standard.
The point is not that every case can be reduced to a checklist. Cross-border corporate history, old allocations and contested authority will always produce hard files. But a registry that classifies difficulty helps the market carry it. A registry that treats difficulty as an undifferentiated request for more comfort turns process into price.
The need test after the pool has gone
Need review is the most delicate part of LACNIC's transfer architecture. The policy requires an organisation inside the LACNIC region to justify IPv4 resources before receiving a transfer. LACNIC also recommends that receiving organisations apply to the List of Possible IPv4 Transfers so that they can show they meet the requirements and justify the IPv4 space to be transferred. For inbound inter-regional transfers, LACNIC asks the receiving organisation for documentation and additional information showing how the addresses will be used. A down payment is due before justification is analysed, and it is not refunded if the transfer cannot be justified and is not approved.
The ancestry of need review is defensible. During the allocation era, registries rationed a scarce common pool. It was reasonable to ask whether an applicant had a real network plan, whether previous allocations were efficiently used, whether a numbering plan was credible and whether the request matched policy. A registry giving out new stock had to guard against waste and premature accumulation.
A transfer market is different. In a transfer, the recipient is not asking the registry to distribute fresh capacity from a common pool. It is buying or otherwise receiving capacity already issued to someone else. The registry is being asked to recognise movement, not to give away stock. That does not eliminate the need for eligibility review. It changes the danger. If the review behaves like old allocation rationing, it can misread market need as hoarding, strategic inventory as speculation and commercial optionality as waste.
Willingness to pay is not a complete substitute for technical review. A shell buyer can pay. A speculative intermediary can pay. A transaction designed to evade a holding period can pay. The registry should be able to test whether the recipient is real, whether the amount requested is within policy, whether the stated use is coherent, whether prior claims are materially false and whether the transfer is being used to defeat a clear rule. But a buyer's willingness to pay is also evidence that the resource has economic use. In a region where capital is costly, few operators buy IPv4 space merely for decoration.
The hard line is between settlement filter and business-plan approval. A settlement filter asks whether the recipient can be recognised consistently with policy and operational responsibility. Business-plan approval asks whether the buyer's use is sufficiently virtuous, whether the price is too high, whether leasing is morally suspect, whether a large buyer already has enough or whether one customer segment deserves capacity more than another. The first protects the record. The second turns the registry into a private capital-allocation committee.
LACNIC's own policy background contains a useful clue. The manual recognises that, although address allocation and assignment policies were originally based on need justification, the implementation of transfers eliminates the need to maintain that justification, so returning resources to LACNIC is no longer required in cases of failed transfers or mergers and acquisitions. That statement accepts that the transfer era changed the justification bargain. If ongoing use is not supervised in the old way after a transfer or corporate event, then entry review should be narrow enough to serve settlement rather than broad enough to police economic destiny.
The regional context makes this more than a theoretical concern. In a high-interest or currency-constrained economy, a buyer may have to close quickly because financing expires, a bank will not hold dollars indefinitely or equipment procurement is tied to a customer deadline. A small operator may not have a polished twelve-month forecast but may know that a hotel chain, municipality, enterprise customer or hosting contract requires IPv4 continuity. A cross-border group may purchase through one legal entity and operate through another. A public-sector network may have procurement documents that do not resemble a private company's address plan. If need review cannot recognise these realities, it favours applicants whose needs look conventional and whose staff know the language of the test.
The review should therefore be explicit about what it tests. It can test identity, authority, amount, coherent use, policy compliance, sham risk, waiting-list evasion, holding-period evasion, service obligations and, where policy requires it, IPv6-related context. It should not test price fairness, seller profit, buyer virtue, preferred business model or a general discomfort with IPv4 commerce. Those concerns may belong in community policy debates. They should not appear as discretionary friction at closing.
Narrowing the need test would not weaken LACNIC. It would make its intervention easier to defend. A buyer denied recognition would know what fact failed. A seller would know whether the risk is curable before losing time. Escrow could define consequences. Brokers would have less room to sell guesses about institutional preference. The market would still have rules, but rules would replace mood.
Two registries at the same closing table
Inter-regional transfer policy makes IPv4 settlement resemble cross-border capital movement. A block may leave the LACNIC region for another registry. A block may enter LACNIC from another registry. In either direction, the private bargain depends on two institutions whose policies, documents, clocks and operational services must align closely enough for the transaction to settle. The source registry must verify the holder and resource. The destination registry must accept the recipient. Each side must avoid recognising a state the other side cannot complete.
The anti-fraud case for coordination is obvious. Without it, a disputed holder might seek recognition abroad, or one registry might treat a block as exported while another refuses to treat it as imported. For a globally unique resource, inconsistent recognition is not merely a private inconvenience. It can undermine routing trust, registration accuracy and operational accountability. The settlement chain has to establish the block, the old holder, the new holder, the registries involved, the policy basis and the date on which responsibility changes.
The economic consequence is equally important: compatibility determines the buyer pool. A seller in the LACNIC region can command a better price if it can reach buyers outside the region under predictable rules. A buyer in the region can obtain supply from global sources if inbound transfer mechanics are clear. A region that makes inter-regional movement too difficult may imagine it is protecting local availability, but it can also depress the value of local holdings, discourage formal sales and push supply into leasing or informal arrangements. A region that allows movement too casually can invite fraud or accelerate concentration. The design problem is to allow movement without losing the record.
LACNIC's sequence of conditional approvals is therefore not a mere technicality. For outbound transfers, source-side verification and destination-side recipient analysis must both succeed. For inbound transfers, LACNIC analyses the receiving organisation and requires justification. Fees and service agreements may apply. Operational services such as reverse DNS and RPKI may be affected and may not be immediately available. A buyer and seller are thus contracting for a transaction whose performance depends on two registry processes and on services that may lag the commercial closing.
Currency and banking friction make the timing more consequential. A seller in a smaller LACNIC economy may be paid by a buyer in another region. The price may be denominated in dollars while the seller's taxes, debt, wages or shareholders sit in local currency. Banks may ask for contracts, invoices, beneficial-ownership documents, registry evidence and an explanation of why address space has a price. If registry approval takes longer than expected, exchange rates can move, escrow deadlines can expire and compliance files can have to be refreshed. LACNIC does not create those conditions. Its timing and clarity decide whether they become manageable background noise or a deal risk.
The largest participants can absorb much of this. A cloud provider, major carrier or established broker can run several files, hold counsel on retainer and wait. A small seller may be trying to convert unused or reorganised address space into equipment, debt service, resilience spending or an orderly exit. If the inter-regional path is opaque, the buyer demands a discount for registry risk. If the seller cannot demonstrate clean settlement quickly, it loses bargaining power. That is how neutral process can produce unequal market outcomes.
The answer is not to trap resources inside the region. Nor is it to treat every export as harmless. The answer is to make inter-regional settlement observable. The market needs clear eligibility rules, clear document categories, timing ranges, explanations of where the source registry's role ends and the destination registry's role begins, and practical guidance on RPKI and reverse DNS transition. If the LACNIC community wants to restrict particular forms of movement, it should do so openly through policy. It should not rely on uncertainty to perform the restriction silently.
Brokers, escrow and the price of knowing
LACNIC is right not to become a broker, price-setter or escrow house. A registry that certifies intermediaries too heavily can create a new gate and a new set of conflicts. A registry that sets price would exceed its technical role. A registry that holds commercial funds would import risks it is not designed to manage. The separation is sound: LACNIC recognises resource movements under policy; private parties negotiate price and closing arrangements.
Yet separation does not mean neutrality in the intermediary market. Brokers exist because IPv4 supply is uneven, search is costly, sellers are often unfamiliar with registry procedure, buyers need particular block sizes or reputational profiles, and closing risk must be managed. Escrow exists because neither side wants to perform first: the seller does not want to lose recognised control without payment, and the buyer does not want to release funds before recognition and operational use are secure. Counsel exists because the transaction sits awkwardly between contract, corporate authority, registry policy and network dependency.
When registry process is predictable, intermediaries compete on genuine services: finding supply, screening counterparties, negotiating warranties, arranging escrow, coordinating closing and managing reputation. When registry process is opaque, they compete on privileged process knowledge. They know how LACNIC tends to read need justifications, which documents usually satisfy a file, when renewal timing becomes dangerous, how to frame legacy continuity, and how to avoid a request for further evidence late in the transaction. That knowledge may be valuable to clients. It also makes access to the market more expensive.
The transfer fee schedule illustrates how procedural knowledge becomes economic. LACNIC's transfer categories include an administrative fee of US$1,000 for a block larger than or equal to a /24 and smaller than a /19, and US$1,500 for a /19 or larger. A US$200 down payment is made when the transfer request begins and before justification is analysed; if justification fails and the transfer is not approved, that initial payment is not refunded. If the receiving organisation is a LACNIC member and its category changes, a complementary invoice is issued for the remaining months until renewal. If it is not a member, it receives the corresponding category invoice plus the administrative fee. The parties, when applicable, must be current with contractual obligations to LACNIC.
None of those amounts is shocking in isolation. But combined with need review, renewal timing, service agreements and cross-border payment friction, they become closing mechanics that sophisticated participants plan around. A broker knows whether the buyer should seek eligibility before signing. Counsel knows to define who bears the down-payment loss if need review fails. A seller knows, or should know, that transferred addresses generally cannot be transferred again for one year and that LACNIC-issued allocations and assignments cannot be transferred for three years from their allocation or assignment date. A novice often learns these facts after price has already been set.
Escrow must translate registry events into financial triggers. Does payment release when LACNIC approves the request, when both parties sign the transfer order, when resource information changes, when the transfer appears in the public log, when WHOIS or RDAP reflects the new holder, when RPKI can be used, when reverse DNS has moved, or after a specified period without dispute? If the contract does not define these events precisely, the buyer and seller may both believe the other is holding up a settled deal. Registry finality is not a single moment in the parties' imagination. It is a chain of observable steps.
Inter-regional transfers make this harder. The origin registry may pre-approve while the destination registry is still reviewing. The destination registry may approve while operational services are not yet available. LACNIC's warning that reverse DNS and RPKI may be affected in inter-regional transfers is therefore an economic warning, not just a support note. A buyer whose customer migration depends on routing-security objects or reverse DNS needs to price that lag. A seller whose payment is conditioned on operational continuity needs to know whether the lag is within its control.
The cure is not registry regulation of brokers. It is reduction of the private return to institutional opacity. Publish better decision categories. Publish timing statistics. Publish aggregate reasons for delay or denial. Make service-continuity expectations clear. Make the transfer log easier to analyse. Brokers will still be useful because markets need search, negotiation and risk allocation. They should not be necessary because the registry process is hard to decipher.
Legacy blocks and old paper
Legacy resources are the place where the early internet meets a modern transfer market. LACNIC describes legacy resources as IP addresses and autonomous system numbers assigned by InterNIC or IANA before the current regional registry system existed, and not subsequently subject to a LACNIC membership agreement. In 2026 LACNIC called on organisations holding or using legacy IPv4 resources to contact it within six months, from June 16 to December 16, as part of a process to update information, verify rights of use and ensure registry data is accurate, current, verifiable and reliable. It also stated that if a holder does not contact LACNIC within the period, or if after analysis it cannot justify its right of use, LACNIC will cease providing registration services to those organisations.
That is a significant fact for transfer architecture. Legacy uncertainty is settlement risk. A legacy block may be valuable because it is old, large, unfragmented or historically well regarded. It may also carry diligence problems. Does the organisation in the old record still exist? Did the resource move through a merger, privatisation, public-sector reorganisation, family succession, asset sale or name change? Who can sign today? Are contacts current? Has the block been leased, routed, unused or split operationally? Is there a corporate or court dispute? If a legacy resource is transferred into LACNIC, does it cease to be legacy, and what obligations follow?
These questions affect price before anyone reaches a philosophical view about legacy rights. A buyer discounts a block when the authority chain is unclear. A seller may believe it has a valuable asset but discover that its records do not support quick recognition. A broker may locate demand but be unable to cure a documentary gap. A bank may hesitate if the historical holder, present operator and payment beneficiary do not match neatly. The registry's legacy process can therefore either unlock liquidity by cleaning records or increase risk by appearing to reopen settled history without a predictable path to finality.
LACNIC has a legitimate reason to regularise stale records. A trusted registry cannot allow old contact data, dead entities or obsolete mailboxes to become a route to address theft. Legacy regularisation protects buyers, operators and the community. It lowers diligence costs and reduces the risk that a contested or hijacked block enters the market. It can turn ambiguous space into usable, recognised capacity.
But legacy resources also test restraint. An inquiry into identity, authority, continuity and operational responsibility protects the record. A broad retrospective judgement about whether an old holder has used space according to contemporary preferences would look different. Many legacy histories are messy without being fraudulent. Public universities, government agencies, former monopolies, privatised networks, family firms and defunct affiliates can require patient reconstruction. Treating every historical complication as suspicion would make formal engagement less attractive and reduce the chance of cleaning the record.
The rule that incoming legacy resources transferred into the LACNIC region cease to be considered legacy is also a pricing term. A seller outside the region and a buyer inside it must account for the loss of legacy status. The buyer may accept that in exchange for modern recognition and services. Another buyer, in another region, may value the same block differently. The rule is not merely an administrative label. It changes bids, obligations and post-closing expectations.
Legacy policy should therefore be tied to finality. Once a holder completes regularisation, the market should know what has been settled: identity, authority, service status, transfer eligibility, contact accuracy, RPKI and reverse DNS availability, and any limits on future movement. If LACNIC asks holders to come forward but leaves the endpoint uncertain, regularisation becomes another risk factor. If it offers a bounded path to stable recognition, it improves both trust and liquidity.
Holding periods, disputes and market memory
Some of LACNIC's transfer rules are best read as market-stability devices. The organisation originating a transfer becomes ineligible to receive IPv4 allocations or assignments from LACNIC for one year from the transaction date recorded in the transfer log. Addresses that have previously been transferred cannot be transferred again, in whole or in part, for one year from that date. Addresses from LACNIC initial or additional allocations and assignments cannot be transferred for three years from their allocation or assignment date. LACNIC must verify that resources are not involved in a dispute. It must maintain a publicly accessible transfer log recording the transaction date, originating organisation, receiving organisation, transferred addresses and, for inter-regional transfers, the source and destination registries.
These rules restrain obvious abuse. The one-year ineligibility period discourages a holder from selling space and immediately returning to LACNIC for more. The one-year restriction on re-transfer discourages quick flipping. The three-year restriction on newly allocated or assigned resources protects against free-pool arbitrage. Dispute checks stop the registry from converting contested control into settled recognition. The transfer log creates a memory of resource movement.
The value of explicit rules is that they can be priced. A buyer knows acquired inventory cannot be resold immediately. A broker knows which blocks are temporarily unavailable for onward transfer. A seller knows that selling may affect future eligibility. A lender or acquirer can look for public evidence that a resource moved. A small operator can learn from the log instead of from rumours. LACNIC can point to adopted rules rather than improvised judgement.
The cost is rigidity. A one-year holding period may be sensible as an anti-speculation rule, but it can also burden a buyer that must restructure after a failed acquisition, financing change, customer loss or corporate reorganisation. A three-year rule for recent allocations is easier to defend, yet it can still collide with mergers or distress events. A seller barred from receiving more IPv4 resources may not care if the practical prospects of new stock are remote, but a new entrant or small network may still treat the restriction as meaningful.
That is why market-stability rules need carefully bounded review paths. A court-ordered restructuring, insolvency sale, merger cleanup or public-sector reorganisation is not the same as speculative resale. A distressed small operator selling address space to finance network continuity is not the same as a shell vehicle built to arbitrage policy. Exceptions must be narrow because every exception can become a loophole. But a rule set that cannot distinguish continuity from speculation will impose avoidable costs.
Dispute checks require the same discipline. A real dispute is serious. If two parties claim the same block, if a court order exists, if a corporate successor is contested or if an account appears compromised, LACNIC should not hurry the transfer. But "dispute" should not become an all-purpose label for discomfort. A competitor's objection, an abuse report unrelated to holder authority, a vague allegation or a political objection to a sale should not automatically freeze recognition. The registry should distinguish legal dispute, corporate authority dispute, account compromise, fraud suspicion, payment defect, policy ineligibility, documentation incompleteness and third-party complaint. Each category should have different consequences and a different path to cure.
The public transfer log is the low-cost antidote to much uncertainty. It does not need to publish prices or private contracts to be valuable. It can show which sizes move, which regions interact, how often inter-regional transfers occur, which types of participants appear repeatedly and whether resources are flowing out of smaller markets. Its usefulness depends on structure. A log that is formally public but hard to search, download or analyse leaves much of its market value unused. A log designed as market memory helps small participants as well as large ones.
The log also disciplines narrative. If policymakers worry that transfers are draining a subregion, concentrating resources or bypassing local need, the log should provide the starting evidence. If brokers tell sellers that no comparable transfers exist, the log can challenge or confirm the claim. If buyers exaggerate uncertainty to demand a discount, public market memory can limit the tactic. Transparency does not make scarcity fair. It makes arguments about scarcity less dependent on private anecdotes.
The renewal clock is part of the price
Payment mechanics often look too mundane to belong in a discussion of market design. In a transfer market they belong at the centre. LACNIC has to fund registry services and prevent members from using transfers to evade obligations. It is reasonable to require fees, current contractual standing and clear invoicing. But in a region with uneven dollar access, inflation, exchange controls, correspondent-banking scrutiny and public-sector procurement delays, the payment path becomes part of settlement risk.
The transfer fee itself is usually not the largest economic variable in an IPv4 transaction. The larger issue is timing and classification. A non-refundable US$200 down payment before justification is analysed is a small diligence cost for a repeat buyer and a more material signal for a small recipient uncertain about eligibility. A complementary invoice after a category change may be ordinary administration for a large member and a surprise for a smaller network budgeting in local currency. A requirement that both organisations be current with LACNIC obligations protects the institution, but if applied without proportion it can turn a curable account issue into a capital-control event.
The renewal clock is especially important. Transfers or returns must be requested at least 30 days before the renewal invoice due date, or a full renewal invoice may have to be paid to complete the process. That rule may be administratively sensible. It is also a settlement-cost rule. A seller negotiating close to renewal faces a different market from one with months of runway. A buyer can use timing risk to demand a discount. A broker who identifies the deadline early can preserve value. A seller that discovers the rule late may have to pay a full invoice, delay closing or accept worse terms.
Bank compliance adds another layer that LACNIC cannot control but should understand. Address transactions are strange to many banks. They involve intangible network resources, cross-border counterparties, escrow, corporate documents and sometimes old registry histories. A bank may ask for the purchase agreement, proof of registry approval, invoices, beneficial ownership, tax treatment and an explanation of why an address block is being monetised. If registry approval takes longer than expected, the bank's compliance window can expire. If exchange rates move, payment instructions may need amendment. If the seller is in a smaller jurisdiction, correspondent banks may impose additional scrutiny or fees.
This is why timing data would have immediate economic value. If the market knew median and long-tail processing times by transaction category, parties could set escrow deadlines rationally. If LACNIC published how often files require supplemental documents, how often need review fails, how often renewal timing affects completion, how often payment defects delay recognition and how often inter-regional transfers experience RPKI or reverse DNS lags, the risk premium would fall. The data would not make transfers instant. It would make uncertainty tradable on known terms.
Payment discipline should remain narrow. A registry cannot run a reliable service if members ignore invoices or use transfers to escape fees. But account standing, transaction fees and record integrity are different questions. A payment issue affecting a transfer fee is not the same as a dispute over holder authority. A membership standing issue is not the same as a forged document. A bank delay in a hard-currency jurisdiction is not the same as bad faith. Blurring these categories may help collection in the short run, but it makes the market treat administrative finance as a private lever over capital movement.
For small operators, this is not an abstraction. A Caribbean seller may need transfer proceeds to pay suppliers or finance resilience. An Argentine buyer may face foreign-currency procedures. A public-sector network may require budget approval. A small ISP may need to absorb the down payment before knowing whether need review will pass. Large buyers experience these as closing costs. Small actors experience them as gates. LACNIC's role is not to subsidise small transactions. It is to measure whether its mechanics unnecessarily convert scale into settlement power.
Operational settlement after the signature
An IPv4 block can be legally sold and still not be operationally settled. Registration recognition is the core event, but the buyer also needs the services and public data that make the resource usable. RPKI, reverse DNS, WHOIS or RDAP, administrative contacts and abuse contacts are not ornamental. They translate recognition into trust, routing confidence, customer support and accountability.
LACNIC's inter-regional transfer instructions warn that, because resources move from one registry to another, services such as reverse DNS or RPKI may be affected and may not be immediately available. The warning is modest in wording and large in economic meaning. A buyer may need route-origin authorisation to satisfy upstreams, customers or internal security controls. A hosting provider may need reverse DNS for mail reputation and customer migration. A network may need accurate abuse contacts so complaints do not go to the former holder. A lender or acquirer may need public records showing that a dependency has moved.
RPKI has made operational settlement more consequential. The registry does not operate the buyer's routers, but it helps define who can make trusted statements about route origin for a prefix. If RPKI continuity is delayed or ambiguous, a buyer may face routing-security friction even after the holder field has changed. As more networks rely on RPKI validation, this becomes part of asset quality rather than a specialist concern.
Reverse DNS is older, less fashionable and still economically relevant. Mail systems, diagnostics, logs, security tooling, customer platforms and operational reputation can depend on it. A transfer that moves the record but leaves reverse DNS unresolved can create avoidable customer pain. Contact data matters in the same way. If abuse reports and operational notices still point to the wrong party, responsibility is not legible even if the private contract says it has changed.
Operational settlement should therefore be described as part of transfer architecture, not left as a support afterthought. Parties need to know the normal sequence: holder verification, need review, legal document acceptance, fee payment, agreement or transfer order signature, registry record update, transfer log entry, RPKI availability, reverse DNS delegation and contact-data transition. Some events may happen together. Others may lag. The market needs to know which events are prerequisites, which are consequences and which are independent service transitions.
Leasing makes the issue sharper. LACNIC's transfer rules address transfers, not every commercial lease of address use. Leasing can be a financing tool where buying is too expensive or demand is temporary. It can also separate the registered holder from the operational user. If a lessee originates routes, receives abuse complaints, serves customers or needs reverse DNS, the public record must remain useful. A registry that ignores leasing because it is not a transfer can allow operational reality to drift away from registration responsibility. A registry that tries to regulate every lease can become a market regulator. The better approach is to focus on responsibility: who is the recognised holder, who is authorised to create routing-security objects, who manages reverse DNS and who is reachable for abuse and operational notices.
Operational settlement also belongs in escrow. A buyer may not want to release all funds until it can create RPKI objects or confirm reverse DNS delegation. A seller may not want payment held for a delay caused by inter-regional technical coordination outside its control. Staged release can make sense: part on registry approval, part on record update, part on operational-service availability. But staged release works only if the registry's events are observable and the normal timing is understood.
The registry does not need to guarantee that every operational dependency is instant. It does need to make clear what is under its control, what may lag, what the parties can prepare before closing and what evidence shows completion. In a market where an address block is valuable because it works, operational transition is part of settlement finality.
Unequal patience in a regional market
LACNIC is a regional registry, but the region is not a single market. Brazil and Mexico have large operator ecosystems and national structures that shape parts of the resource relationship. Argentina, Chile, Colombia, Peru and other larger markets contain sophisticated networks, but not always stable financing conditions. The Caribbean and smaller continental economies can face thin staffing, higher connectivity costs, banking de-risking, storm exposure, small domestic markets and limited legal specialisation. A transfer process that looks neutral from an institutional desk can produce unequal bargaining power at closing.
Small sellers are not necessarily hoarders. A small island operator may have unused space after losing a customer, consolidating a network, changing upstreams, merging operations or exiting a service line. A public institution may hold addresses that no longer match its structure. A family-owned ISP may need proceeds to fund equipment, resilience or debt. The block may be small by global standards and large on the seller's balance sheet. If records are old, contacts have changed, corporate documents are missing or payment must travel through a cautious bank, the seller absorbs a discount.
Large buyers are not automatically villains. A regional carrier, cloud provider, hosting company or content network may have legitimate need for IPv4 continuity. It may serve customers in multiple countries and need clean registration to maintain routing security, abuse accountability and contractual service. It may be willing to pay a price that moves underused resources into productive use. Liquidity is not the enemy of stewardship. A market that allows resources to move formally can be better than one that leaves them idle because transfer is too uncertain.
The issue is asymmetry. Large buyers can hire counsel, maintain registry specialists, work with experienced brokers, prepare need justifications and wait out uncertain timing. Small sellers often cannot. If a transfer slows, the buyer may renegotiate. If documentation is incomplete, the buyer may demand indemnities the seller cannot evaluate. If bank compliance drags, the seller may accept a lower price to keep the deal alive. If LACNIC process knowledge is concentrated among repeat players, small sellers pay an invisible tax for unfamiliarity.
The List of Possible IPv4 Transfers is a partial answer. It can help organisations willing to offer IPv4 blocks, organisations wishing to receive them and intermediary organisations find one another. Participation lasts one year for a fee. Limiting access to participating organisations may reduce noise and protect privacy, but it also means public price discovery remains limited. The existence of the list confirms that LACNIC understands the market needs an interface. The design question is whether that interface lowers asymmetry or mainly serves those already prepared to navigate the process.
Public logs and timing data can do more for small participants than paternalistic restriction. A small seller should be able to see whether similar blocks have moved, whether inter-regional transfers are common, whether large buyers are active, whether holding periods are relevant and what kinds of delays occur. It should not have to rely entirely on a broker's assertion about what is normal. A small buyer should know whether need review is likely to be a narrow eligibility test or a broad business-plan inquiry. A public-sector network should be able to align procurement and registry milestones without guessing.
Protecting small markets should not mean preventing them from selling. That would trap value and reduce local options. The better protection is settlement literacy: clear evidence categories, plain-language transfer guidance, predictable timing, renewal-deadline warnings, operational-service transition notes, searchable logs and a review path for disproportionate documentation burdens. The registry cannot equalise balance sheets. It can avoid making unequal patience the hidden currency of transfer settlement.
A narrow registry is a stronger registry
LACNIC's power comes from trust in its record. That power is legitimate when it protects uniqueness, authority, accuracy and operational responsibility. It becomes dangerous when recognition is used to decide which transactions should happen, which buyers deserve capacity, which sellers may monetise old holdings, which brokers are respectable, which regions should retain capital or which business models are virtuous. The line is not always obvious. That is why the line must be designed.
LACNIC's current architecture contains both market support and gatekeeping potential. It recognises intra-regional and inter-regional transfers. It publishes rules, fees and transfer-log obligations. It says it does not intervene in commercial operations between the parties. These features restrain the institution from becoming a marketplace operator.
At the same time, LACNIC retains need review, documentation discretion, external authenticity checks, service-agreement leverage, contractual-standing requirements, renewal timing effects, one-year and three-year holding restrictions, legacy regularisation power and operational-service dependencies. Each element can be justified. Together they make LACNIC a settlement bottleneck. The bottleneck is acceptable only if it is predictable, narrow and reviewable.
Hidden regulation often appears as process rather than explicit policy. A file is delayed by undefined document requests. A need narrative is judged against an unwritten expectation. A payment delay in a hard-currency jurisdiction is treated as indifference. A broker learns informal preferences that others do not know. A legacy holder is asked to prove more than continuity. A transfer is slowed because the buyer appears too financial or too large. An abuse complaint becomes an authority dispute. None of these moments has to look dramatic. In aggregate, they allocate capital.
The better standard is nexus. If the issue affects the truth of the record, the authority of the requester, the absence of duplicate claims, legal ability to transfer, application of a clear policy rule, security of RPKI or reverse DNS, accuracy of contacts or a specific legal obligation, LACNIC should act. If the issue is mainly discomfort with price, buyer type, seller profit, leasing economics, regional capital movement or the pace of IPv6 migration, LACNIC should point to an adopted rule or step back.
That standard would strengthen the registry. Staff could tell applicants what fact is missing rather than ask broadly for more comfort. Applicants could cure defects. Brokers would have less room to sell mystique. Buyers and sellers could price settlement risk more accurately. Small actors would face fewer hidden costs. The registry would be less vulnerable to the charge that it regulates by delay.
IPv6 advocacy should be governed by the same restraint. LACNIC is right to promote IPv6. IPv6 is the long-term answer to address scarcity. But many networks still need IPv4 while deploying IPv6: for customers, legacy applications, public-sector systems, security appliances, hosting, mobile translation, enterprise dependencies and global reachability. Making IPv4 transfers harder does not automatically accelerate IPv6. It can trap working capital and delay investment. A registry can promote the future without using recognition of the old resource as a disciplinary tool.
The narrow registry is not a weak registry. It is a registry that knows why it intervenes. It is strict about fraud, false authority, stale contacts, hijacked accounts, disputes and operational responsibility. It is restrained about price, commercial taste and moral judgement. Its authority is stronger because applicants can see the connection between the request and the mission.
How to make the market less brittle
The safeguards LACNIC needs are practical, not ideological. The first is a fuller documentation map. The market needs more than a general invitation to provide supporting documents. It needs categories, normal evidence, acceptable substitutes, translation expectations, signature rules, timing targets and escalation paths. Routine holder transfer, merger, acquisition, asset sale, share sale, public-sector succession, insolvency, name change, relocation, legacy regularisation, account recovery, suspected fraud, legal dispute and inter-regional movement should not look like one undifferentiated file.
The second safeguard is timing transparency. LACNIC should publish median and long-tail processing times by category, separating incomplete applicant files, registry review, inter-regional coordination, legal holds, need-review failures, payment issues and operational-service delays. Average time alone is not enough. The long tail is where failed escrows, distressed sellers and risk discounts live. Timing data can be published without revealing private prices or confidential contracts.
The third safeguard is scoped need review. The review should state what it tests and what it does not test. It can test amount, coherent use, policy compliance, sham risk, prior utilisation where applicable, waiting-list evasion, holding-period evasion and service obligations. It should not test whether the price is attractive, whether the seller profits, whether the buyer is a preferred kind of operator or whether IPv4 commerce is aesthetically pleasing to the registry. If the community wants such rules, they should be adopted as rules.
The fourth safeguard is operational-settlement guidance. Transfer pages should explain what normally happens to RPKI, reverse DNS, public registration data, abuse contacts and certification in intra-regional and inter-regional cases. They should identify what may be unavailable, what the parties can prepare before closing and what event marks service availability. This would help contracts, reduce post-closing disputes and make escrow triggers more precise.
The fifth safeguard is a more usable public log. The existing obligation is valuable, but market value increases when the log can be searched, downloaded and analysed by date, block size, transfer type, source and destination registry, and other broad categories that respect privacy and policy. The goal is not to publish prices. It is to let participants see how settlement actually works. A public log is not only transparency. It is market infrastructure.
The sixth safeguard is reasoned review. A denied transfer, failed need review, documentary rejection, dispute hold or service-agreement obstacle should come with a reason tied to policy, contract or law. The applicant should know what evidence would cure the defect and whether a separate reviewer can examine the decision. In a scarce market, unexplained delay is not merely customer-service friction. It is capital risk.
The seventh safeguard is payment-friction awareness without fee indiscipline. LACNIC should collect fees and enforce obligations. It should also distinguish bad faith from banking delay, exchange-control friction, renewal-clock confusion and curable account defects. Clear pre-transfer warnings about renewal deadlines would prevent avoidable full-invoice surprises. Payment categories would help members plan. This is not subsidy. It is settlement hygiene.
The final safeguard is institutional humility. The registry should protect the record, not allocate commercial destiny. It should be firm against fraud, false authority and contested control. It should be cautious about turning recognition into a tool for shaping buyer composition, seller motives, broker economics or regional capital flows unless the community has adopted explicit policy. The more valuable IPv4 becomes, the more tempting it is to use registry recognition to nudge behaviour. That temptation is precisely why restraint needs to be designed, not merely asserted.
The architecture beneath the policy
The visible language of LACNIC transfers is administrative: forms, documents, fees, agreements, justification, logs and service obligations. The economic language underneath is settlement: finality, liquidity, transaction cost, information asymmetry, risk allocation and market access. The administrative language is necessary. The economic language explains why the details matter.
At the closing table, the parties already know that IPv4 is scarce. They are not debating whether IPv6 is the future or whether the free pool has been exhausted. They are trying to move a scarce resource in a region where capital is uneven, legal forms vary, banks can be slow, old records can be messy and operational trust depends on registry services. The buyer wants usable capacity. The seller wants recognised delivery and payment. The broker wants the deal to close. Counsel wants authority and warranties to match registry reality. The bank wants compliance comfort. Operators want RPKI, reverse DNS and contacts to work. The registry must decide whether recognition can safely move.
The best version of LACNIC's role is neither passive nor expansive. It is an exacting settlement utility. It verifies authority without judging commercial virtue. It checks disputes without letting complaints become vetoes. It requires documents without making proof a private moat. It applies holding periods without confusing every resale with speculation. It recognises inter-regional movement without ignoring operational consequences. It regularises legacy records without retroactively moralising old holdings. It publishes logs without becoming a price regulator. It keeps operational services aligned with responsibility so that addresses are usable, not merely recorded.
That is a demanding standard, but also a modest one. It does not ask LACNIC to solve exchange controls, correspondent banking, inflation, carrier concentration, small-island fragility, IPv6 unevenness or global IPv4 scarcity. It asks LACNIC not to add avoidable uncertainty at the settlement point where those problems already meet. In a region where the cost of capital can be high and network margins can be thin, reducing registry uncertainty is itself infrastructure support.
The transfer market will not be made fair by slogans about community or by hostility to brokers. It will be made less brittle by better microstructure: visible rules, proportional evidence, scoped need review, predictable timing, usable logs, operational-service continuity and reviewable decisions. Those features do not abolish scarcity. They make scarcity less dependent on insider knowledge.
LACNIC's challenge is to keep its record strong enough for the market to trust and narrow enough that trust does not become permission. When it records a valid transfer, it is not blessing the price. When it asks for proof, it is not entitled to redesign the buyer's business. When it warns that RPKI or reverse DNS may lag, it is identifying a settlement risk that parties must allocate. When it logs a transfer, it is providing market memory. When it regularises a legacy holder, it is turning history into usable finality.
The economics of transfer market architecture are therefore not outside the registry's mission. They are what the mission becomes after exhaustion. A clean record lowers the risk premium. A predictable process improves liquidity. A narrow review preserves legitimacy. A public log distributes information. A restrained registry lets addresses move toward productive use without becoming a hidden market regulator. That is the architecture LACNIC needs if recognition is to remain a public utility rather than a private gate.