The finances of a regional internet registry look dull until scarcity makes the registry ledger part of the market's balance sheet. A fee invoice appears to be a charge for service. A reserve appears to be ordinary prudence. A legal budget appears to be the cost of having lawyers. A staff plan appears to be administrative capacity. Translation, meetings and training appear to be community work. In the LACNIC region, those lines sit beside IPv4 scarcity, transfers, leasing, multilingual service, uneven access to dollars, small Caribbean and rural networks, public-sector and university address histories, large-country gravity in Brazil and Mexico, and members whose ability to pay is shaped as much by banks and currencies as by technical demand. The accounting is therefore not just accounting. It is the fiscal constitution of a registry utility.
That constitution has two sides. LACNIC must be solvent before it can be neutral. Its registry records, account systems, reverse-DNS delegations, RPKI services, transfer review, support queues, security operations and legal continuity have to survive bad weeks as well as good ones. A region that includes large continental markets, island economies, rural providers, public research networks, public-sector bodies and cross-border carriers cannot depend on a thin institution that fails when a bank payment is delayed, a currency moves, a storm interrupts operations, a court order arrives, a transfer dispute escalates, a system is attacked or a key staff team leaves. The ledger has to remain boring through stress. Boring is expensive.
Yet the opposite mistake is just as serious. A registry that can charge mandatory or near-mandatory fees because members cannot choose a competing LACNIC for the same regional number-resource relationship has incentives that ordinary suppliers do not have. It can grow budget lines because the institution is important. It can defend reserves because continuity is essential. It can justify legal spending because threats are real. It can add staff because services have become complex. It can fund translation, events, training, policy support and regional programmes because participation is part of legitimacy. Much of that may be defensible. But a compulsory fee can quietly become a quasi-tax if members cannot tell which costs protect the ledger, which protect the users of the ledger, and which protect the institution's own size, reputation and discretion.
The fiscal-incentive problem is sharper after IPv4 exhaustion. LACNIC no longer operates mainly as a distributor of a meaningful free pool. It recognises control, maintains records, processes changes, reviews transfers, supports security services and arbitrates the operational consequences of scarcity. Scarcity raises the value of the record. It also raises the value of institutional permission, timing, account standing and continuity services. A renewal charge, a transfer administrative fee, a non-refundable down payment, a category change or a late-payment state can affect whether an address block moves, whether financing closes, whether a buyer can originate routes with confidence, or whether a small operator remains independent rather than accepting upstream-assigned space.
The point is not to turn every fee dispute into a morality play. LACNIC needs money to operate. It needs skilled staff, lawyers, auditors, systems, translation, security controls, member support and reserves. The point is to treat those costs as constitutional choices rather than as accounting inevitabilities. A registry utility should be able to show whether each major charge is recovering core cost, funding a regional public good, subsidising a weaker class of members, supporting a market settlement function, building a reserve, or financing institutional ambition.
That distinction matters because the region is not one fiscal market. A dollar invoice means different things in Sao Paulo, Mexico City, Montevideo, Kingston, Port-au-Prince, a rural Andean wireless network, a public university, a small hosting firm and a Caribbean access provider recovering from a storm. Spanish, Portuguese and English service are not decorations. They are access costs. A wire fee, a correspondent-bank deduction, an exchange-control delay, a public-procurement calendar or a document translation can be invisible to a large operator and decisive for a small one. The same registry rule can be neutral in form and unequal in effect.
LACNIC's fiscal design should therefore be judged by a simple standard: members should be able to tell when their money is buying continuity, when it is buying inclusion, when it is buying market settlement, and when it is buying institutional self-preservation. A solvent registry is necessary. A blank cheque is not.
A registry utility must be solvent before it can be neutral
The first discipline is to take cost seriously. A number-resource registry is not a static spreadsheet. It is a live utility with public data, private authentication, legal relationships, security systems, service portals, support queues, transfer files, reverse-DNS delegations, RPKI infrastructure, staff judgement and continuity obligations. If it fails, the cost is not limited to an internal outage. Operators can lose the ability to update records, certify origins, answer diligence questions, settle transfers, correct contacts, recover accounts, maintain reverse DNS or demonstrate recognised control to counterparties.
That is why fees exist. They fund staff who review requests, maintain member systems, answer support issues, operate security controls, translate material, organise policy forums, respond to incidents, renew infrastructure, retain counsel, pay auditors and keep the institutional shell alive. Some of those costs rise with the number of members. Some rise with resource volume. Some rise with transfer complexity. Some rise with security expectations. Some rise because the institution chooses to support regional capacity building. Treating them all as if they were the narrow cost of a database is analytically easy and operationally unserious.
RPKI is a clear example. A registry could once be imagined as a place where a holder name and contact information were published. RPKI adds a security layer in which registry-linked certification supports route-origin statements. Hosted and delegated models require systems, authentication, audits, incident response and member education. The service is not a luxury if networks increasingly rely on origin validation. But it is also not free. The fiscal questions are how much of the fee base funds RPKI resilience, how much funds related member support, how outages and account disputes are handled, and how the service is protected from becoming a discretionary enforcement lever.
Reverse DNS is older and less fashionable, but it is also fiscal. It requires infrastructure, delegation management, support and operational discipline. For hosting providers, mail systems, public-sector services, diagnostics and operational trust, reverse resolution can still affect customer confidence and commercial usability. If reverse DNS becomes unstable during a transfer, account recovery, inter-regional movement or legal hold, the block's economic value is impaired. Funding reverse-DNS continuity is not a decorative cost. It is part of the registry utility.
Legal continuity is real too. LACNIC needs a legal body to sign contracts, employ staff, collect fees, answer courts, defend data practices, manage bank relationships, purchase insurance and resolve authority disputes. Its region is legally diverse. A transfer file may involve a Brazilian corporate acquisition, a Mexican buyer, a Caribbean seller, a public university's successor documents, a bank in a correspondent chain and a registry incorporated in Uruguay. Counsel is not optional in that environment. The issue is how counsel is classified, governed and funded.
Security operations are equally difficult to minimise. Registry systems are attractive targets because they support routing authority and scarce-resource recognition. Account compromise, forged transfer documents, fraudulent successor claims, social engineering, credential theft and manipulation of stale records can all have consequences beyond LACNIC's own balance sheet. A registry needs authentication controls, monitoring, staff training, incident response, backups and assurance. Underfunding those systems saves money in the wrong place.
Solvency is therefore part of neutrality. A registry that cannot pay competent staff, maintain secure systems, translate enough material, process requests predictably or withstand a legal challenge will not be neutral in practice. It will become vulnerable to the best-funded claimant, the loudest national group, the most experienced transfer participant, the most patient litigant or the vendor with the greatest leverage. Underfunding can itself be a form of capture.
The danger is that solvency can become a universal defence. Once an institution says it is critical, every budget line can be described as resilience. Every meeting can be called participation. Every outreach programme can be called inclusion. Every staff increase can be called service quality. Every legal reserve can be called prudence. Every surplus can be called future-proofing. The vocabulary is not necessarily false. It is too elastic. A fiscal constitution has to distinguish the indispensable from the merely useful, and the merely useful from the self-protective.
The distinction should not be left to tone. It should be visible in accounts. Core registry continuity is one thing: maintaining records, authenticated access, data publication, RPKI, reverse DNS, transfer recording, security, legal compliance, audit and essential member support. Regional public-good activity is another: training, participation, fellowships, applied research, broader translation, events and measurement. Institutional defence is a third: legal positions, reputational programmes, representation and administrative expansion that may help the organisation but do not necessarily improve the ledger. Each category can have a case. They should not be hidden inside one institutional story.
The region makes the same invoice unequal
The phrase Latin America and the Caribbean compresses a large fiscal geography. Brazil and Mexico have large-country gravity: large operators, national technical communities, recurring policy participants, local counsel, deeper capital markets and more repeat experience with registry procedures. Other substantial markets, including Argentina, Chile, Colombia and Peru, bring their own operator ecosystems and legal capacity, though not always stable currency conditions. Central American networks may face cross-border wholesale dependencies. Caribbean operators may be small, exposed to storms, dependent on a few submarine paths and subject to correspondent-banking friction. Public-sector and university networks may have old address histories that do not resemble private-company paperwork.
The same fee rule lands differently across that map. A US-dollar invoice is a routine treasury item for a large multinational or a major national carrier. For a small operator paid mostly in local currency, it can be an exchange-rate event. In a country with inflation, capital restrictions or limited access to foreign currency, the timing of a bill can matter as much as the amount. In a public university or municipal network, payment may depend on a budget calendar, procurement approval or a public treasury that does not understand why an internet-number registry invoice must be paid within a narrow period. In a Caribbean jurisdiction, the wire itself may be slow, expensive or vulnerable to compliance questions from intermediary banks.
Payment friction is not a footnote. Existing regional research indicates that payers are told to ensure the full amount reaches LACNIC, to consider wire fees and bank processing time, and to use a cross-border payment path involving Uruguay and a United States correspondent bank for wire transfers. That is sound administration. Economically, it means bank fees and timing are part of the membership cost. If an intermediary deducts charges and the received amount is short, the payer's intention and the registry's accounting state can diverge. A large operator corrects the shortfall. A small one may face a service delay, a transfer hold or repeated administrative work.
Foreign exchange adds another layer. A member may owe in dollars while earning in pesos, reais, bolivars, gourdes, quetzales, pesos of another jurisdiction, or a Caribbean currency whose bank channels are priced through external relationships. The invoice amount can be known and the domestic cash requirement still uncertain. If a government body has to seek permission to pay abroad, or if an operator has to buy dollars at a spread, the effective registry fee includes policy and banking cost. A fee schedule that ignores these frictions may look tidy while imposing very different burdens.
Language has its own fiscal incidence. Spanish is central to LACNIC's legal and operational environment. Portuguese is indispensable because of Brazil's scale and because many regional debates have a Portuguese-speaking audience. English matters for Caribbean networks, international counterparties, brokers, lenders, global operators and technical documentation. Translation is not ornamental. It is part of due process, member support and market access. But translation costs money, staff time and timing discipline. If the cost is underfunded, non-Spanish or non-Portuguese participants pay through delay and weaker comprehension. If it is funded, all members pay, including those who never use a particular language channel.
The same applies to travel, meetings and community programmes. LACNIC's region benefits from forums where operators, staff, researchers, security specialists and policymakers meet. But travel culture creates unequal influence. Large carriers and large-country participants can attend repeatedly. Small rural and island operators often cannot. If membership fees fund meetings, the budget should show whether those meetings reduce regional asymmetry or reinforce it. Fellowships, remote participation, translated summaries and small-operator explainers can make participation support into infrastructure. Without evidence of reach, they can become a club good for the already present.
Member classes and fee categories make the fiscal geography more complicated. LACNIC's resource and membership structure sorts organisations by holdings or status, and invoices can change when a receiving organisation's category changes after a transfer. That is economically sensible if larger holdings impose more support, risk or common-cost claims. It is also a distributional rule. A category change is not just an accounting result; it can alter the cost of receiving scarce capacity. A receiving organisation that is not already a member can face a category invoice plus administrative fees. A receiving member whose category changes can face a complementary invoice for the remaining months until renewal. Those mechanics can matter near a closing.
The region's unevenness does not mean LACNIC should subsidise every weaker member or excuse chronic non-payment. A registry that cannot collect fees cannot provide continuity. It means the registry should treat incidence as a measurement problem rather than as a public-relations problem. How often are invoices late because of bank fees, public procurement, foreign-exchange approval, disaster hardship, mistaken references or deliberate refusal? How often do small members fall into account risk? How often do payment issues delay transfers? How often do language or document issues extend review? How often does a member in a high-friction jurisdiction pay more in bank and compliance costs than the nominal fee discussion implies?
Fiscal neutrality in such a region cannot mean identical treatment at the invoice line. It means a fee and reserve system whose burdens are visible enough that the community can decide which inequalities are justified by cost, which are unavoidable, and which are institutional choices that should be repaired.
The fee table is a constitution in miniature
A registry fee schedule looks like a price list. It is more than that. It defines who pays to enter, who pays to remain, who pays when resources move, who bears category changes, who must be current before a transaction can close, and how administrative friction interacts with scarcity. In an abundant era the fee table was mostly association finance. In a post-exhaustion era it becomes a constitution for participation in a recognised address economy.
Transfer fees show the point concretely. Existing regional research records that transfer requests under relevant LACNIC procedures carry 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 required when the transfer request begins and before justification is analysed. If the transfer cannot be justified and is not approved, that initial payment is not refunded. Both organisations, where applicable, must be current with contractual obligations. Transfers or returns must be requested at least 30 days before the renewal invoice due date or the full renewal invoice may have to be paid to complete the process.
None of those features is absurd. A transfer review costs money. A down payment discourages casual filings. Contractual standing prevents a party from using a transfer channel while ignoring the service relationship. Renewal deadlines help the registry run a predictable billing cycle. Category invoices align fees with the new resource position. The danger is not the existence of fees. The danger is the cost stack.
For a large buyer, US$1,000, US$1,500 or a US$200 non-refundable payment may be trivial compared with the value of the addresses, the legal work, the broker fee and the bank transfer. For a small operator seeking a /24 or /23, especially in a currency-stressed economy, the payment is more than a line item. It is a seriousness test, a cash-flow event and a signal of process risk. If the recipient fails a need review, the non-refundable payment becomes a cost of learning institutional expectations. Repeat players can absorb that. First-time small buyers learn under pressure.
Fees also shape timing. Suppose a small seller has a clean commercial offer, but its renewal date is close. If the transfer or return is not requested early enough, a full renewal invoice may be required. The seller may have to pay before it can monetise the block. A buyer may use that pressure to renegotiate. A broker may demand more compensation for shepherding the file. The registry has not set the private price, but its billing calendar has changed bargaining power.
Account standing is the sharpest example. A requirement that both parties be current is reasonable. But current can hide several states: deliberate non-payment, bank delay, intermediary-bank deduction, wrong reference, public-sector approval lag, exchange-control delay, disputed category invoice, disaster hardship or ordinary administrative error. These are not equivalent. If the service state is binary, a curable payment issue can freeze an asset movement whose private value far exceeds the invoice. Fee discipline then becomes capital friction.
Maintenance or renewal fees create another set of incentives. A resource holder pays to remain in good standing, to keep services available and to preserve the recognised relationship. That is ordinary cost recovery. But because the holder cannot substitute another regional registry for the same relationship, renewal fees also resemble a mandatory levy on recognised resource control. The legitimacy of such a levy depends on the cost base. If fees fund the narrow ledger, security and support, the case is strong. If they fund broad institutional activity without explicit consent and disaggregated reporting, the fee becomes more like a quasi-tax.
The fee table can encourage or discourage behaviour. A resource-sensitive category model may reduce regressivity by making larger holders pay more. It may also create cliff effects, incentives to split holdings, or reluctance to receive resources that push an organisation into a higher category. A flat or weakly differentiated fee can be simple but regressive, making small direct membership relatively more expensive than large-resource recognition. Transfer fees scaled by block size can approximate processing risk, but they can also become a toll on liquidity. Non-refundable payments can discourage frivolous filings, but also deter legitimate small recipients facing uncertain review.
These are reasons to publish a fee-incidence statement. Members should be able to see, for each material fee element, what cost it is recovering, which class of members bears it, how it affects small transfers, how it interacts with renewal timing, how often it delays transactions, and whether it contributes to reserves or only to operating cost. A fee schedule without incidence analysis is a constitution written in prices but read as administration.
The strongest LACNIC fee model would not be the lowest-fee model. It would be a model in which the member can say: this part pays for core registry records; this part pays for RPKI and reverse DNS; this part pays for support and multilingual service; this part contributes to continuity reserves; this part covers transfer review; this part supports participation or development as a deliberate cross-subsidy. That map would not end disagreement. It would make disagreement honest.
Reserves are insurance, not institutional capital
A registry without reserves is a danger to its region. It may be forced into hurried fee increases after a revenue shock, lose staff during stress, delay infrastructure replacement, compromise on security, settle weak claims because litigation is unaffordable, or fail to preserve core services during legal or banking disruption. A continuity reserve is therefore part of the product members buy. It is the silent promise that the ledger will remain available when ordinary income is interrupted.
For LACNIC, reserve logic should begin with the specific risks of the region and the function. There is revenue risk from delayed member payments, currency controls, bank fees and public-sector calendars. There is security risk from account compromise, forged transfer attempts, abuse of stale records and attacks on registry systems. There is legal risk from transfer disputes, authority disputes, successor claims, court orders, insolvency and regulatory demands. There is operational risk from critical staff dependency, vendor failure, data-centre interruption, system modernisation and disaster recovery. There is participation risk if multilingual service or policy support cannot be maintained. There is reputation risk if the institution cannot explain what happened during a shock.
Those risks justify a reserve. They do not justify an unbounded reserve. In a member-funded monopoly-like utility, accumulated money belongs morally to a purpose, not to institutional comfort. The purpose should be stated in a target band: so many months of core registry operations, so many months of total operations, a defined contingency for legal stress, a defined security recovery fund, a defined capital-replacement plan, and rules for when excess reserves reduce future fees or fund a member-approved project.
The denominator matters. A reserve measured against total institutional spending can grow as the institution grows. More programmes justify a larger reserve; a larger reserve then makes more programmes easier to defend. That circularity is the classic reserve problem. A better system would report two ratios: reserves against core registry-continuity costs, and reserves against total organisational commitments. Members could then see whether they are insuring the ledger or insuring the full institutional footprint.
Liquidity matters too. Cash, deposits, investment assets, restricted funds, prepaid expenses and property-like assets are not the same. A cyber incident, emergency rebuild or court order needs spendable money. A long-term investment reserve may not be instantly usable without loss. A legal contingency reserve may need a different liquidity profile from a system-replacement reserve. A public reserve report should classify not only the amount but the availability and intended use.
Drawdown rules are even more important. When may reserves be used for litigation? When may they be used for emergency systems work? When may they be used to subsidise member hardship during a regional disaster? When may they be used to cover a deficit caused by fee resistance? When must the board seek member approval? When must reserves be rebuilt, and by whom? Without answers, the reserve becomes discretionary capital in the hands of the institution.
This distinction is not academic. Legal stress can turn reserves into bargaining power. If LACNIC has a large legal buffer, it can defend its decisions more confidently. That may protect the ledger against bad claims. It may also make the institution less sensitive to the cost of overbroad discretion. If it has too little, a wealthy claimant or large member can pressure the registry into compromise that harms others. The optimum is a legal reserve tied to core defence of the registry record, not a war chest for every institutional preference.
Reserves can also dull member discipline. An institution with a thick cushion can survive member dissatisfaction, defer cost reform and maintain programmes after their usefulness weakens. Staff and programme inertia are normal in any organisation. Reserves reduce the urgency of choosing. That is why a reserve policy must include release valves. If reserves exceed the target band for core continuity and disclosed risks, members should know whether future fees will be reduced, whether the excess will be returned in fee credits, or whether a specific investment is being proposed for approval.
The central test is whether reserves protect the ledger or protect the institution from accountability. Protecting the ledger means continuity of records, reverse DNS, RPKI, support, security, transfer recognition, data preservation, staff continuity and emergency response. Protecting the institution from accountability means using accumulated member money to keep programmes, legal positions or public narratives alive after members have lost confidence or after the function no longer requires them. The difference must be visible in the accounts.
Reserves are therefore a form of institutional insurance. Insurance has a premium, a covered risk, an exclusion, a limit and a claim process. LACNIC's reserve policy should be readable in those terms. Members should not have to infer whether they are buying continuity insurance or contributing to an untitled endowment.
Legal budgets and the moral hazard of defence
Legal spending is where registry finance becomes most politically sensitive. A registry needs counsel. It must verify authority, draft agreements, interpret bylaws, protect data, respond to courts, manage employment and vendor contracts, review policy implementation, and defend the institution when a claimant threatens the record. In a region of many legal systems, old public-sector records, cross-border transfers and scarce resources, legal work is not a luxury.
The moral hazard appears because legal spending can defend the ledger or defend discretion. If LACNIC spends money to prevent a forged transfer, preserve the last verified record during a dispute, respond to a lawful court order, protect member data, or ensure RPKI continuity during an authority conflict, the expenditure protects the common utility. If it spends money to sustain a broad interpretation of institutional power, resist useful disclosure, delay review, or defend a policy preference whose economic cost falls on members, the same legal line has a different character.
Members cannot judge that distinction from a single professional-services number. They need categories. Routine corporate counsel is not the same as transfer dispute counsel. Employment advice is not the same as litigation over resource control. Privacy and data protection are not the same as board governance disputes. Contract review is not the same as external interventions. Election or member-meeting advice is not the same as a court fight over a disputed block. Confidentiality can protect active matters without hiding category, trend and authority.
Legal-budget moral hazard has two sides. If the registry can litigate with member money while the downside of a contested decision falls on a specific holder, it may underprice its own aggression. If a wealthy member or counterparty can force the registry into expensive defence, the claimant may underprice its own aggression. Both are real. The answer is not to weaken the registry or to deny members access to courts. It is to build intermediate mechanisms that make legal escalation less attractive: written reasons, independent review for high-impact decisions, preservation of last verified operational state, narrow dispute notation, clear appeal routes and proportional service effects.
In the fee context, legal spend should be linked to risk reduction. If legal work is rising because transfer files are complex, publish aggregate categories of complexity. If court-order handling is expensive, publish a policy for how orders are classified and implemented. If successor claims involving public-sector or university networks are frequent, publish evidence guidance that lowers future legal review cost. If disputes over account standing create legal work, publish clearer cure paths. Legal spending should teach the institution where process is failing; it should not merely consume more member money next year.
Legal reserves require still more care. A registry may need a dedicated legal contingency because one serious case can exceed annual legal budgets. But the contingency should have a purpose boundary. Defence of core registry services and protection against fraudulent claims belong in the strongest category. Defence of broad market-shaping discretion deserves stronger member oversight. Extraordinary legal drawdowns should be reported in categories after the fact, and where possible before the fact if they commit member money to a strategic posture rather than routine defence.
The region's small operators have a particular stake in this. A large carrier can read the legal environment, hire counsel and challenge a decision if necessary. A small rural ISP, Caribbean provider, university network or local hoster may simply accept a registry position because challenge is too costly. If legal budget and review mechanisms are opaque, the registry's legal confidence becomes one more scale advantage. Small members help fund the legal machinery but may not be able to use legal remedies themselves.
That asymmetry should shape the design of review. A material denial, transfer hold, service limitation, account lock or regularisation failure should have a clear, written, proportionate route of challenge. The route should not require a small operator to turn every dispute into litigation in Uruguay or another national court. Written reasons are cheaper than lawsuits. Independent review is cheaper than prolonged distrust. Interim continuity rules are cheaper than emergency injunctions.
Legal firewalls are part of the same logic. The institution needs authority to protect staff, data and records. It also needs internal guardrails so that member-funded legal capacity does not become a budgetary shield around every administrative preference. A legal matter involving fraud, account compromise or external compulsion belongs in one risk class. A legal matter involving institutional discretion over fees, disclosure, election rules or service limitations belongs in another. The first may justify rapid defence. The second should trigger stronger board visibility and, after confidentiality needs expire, member-readable explanation.
Legal budgets are therefore not only a cost item. They are a measure of whether ordinary accountability channels are sufficient. Rising legal spending may mean the environment is more hostile. It may also mean members cannot get decision-useful answers earlier. A mature fiscal report should help distinguish those cases.
Cross-subsidy can be legitimate only when it is named
Every registry budget contains cross-subsidy. The exact user of a public good rarely pays its exact cost. A small operator benefits from security architecture funded partly by large holders. A large holder benefits from a better regional routing environment supported partly by fees from small members. English-speaking Caribbean networks may benefit from translated or English materials funded by Spanish- and Portuguese-speaking members. Public universities may need unusual support that private carriers also fund. Training in one country may improve routing hygiene for others. A strict user-pays model would be too narrow for a regional utility.
The question is whether the subsidy is visible and justified. Hidden cross-subsidy corrodes legitimacy because members begin to suspect that every attractive public purpose is being funded through unavoidable resource recognition. Named cross-subsidy can be debated. Members can decide whether they want to fund multilingual services, policy forums, fellowships, applied research, RPKI training, small-operator outreach, university guidance, Caribbean resilience material, public-sector evidence templates or regional measurement projects. The same dollar feels different when the payer understands the purpose.
LACNIC's broader regional role creates this issue continuously. A registry serving Latin America and the Caribbean cannot sensibly say it is only a narrow database. Regional capacity, routing security, IPv6 deployment, applied research, technical education and participation support all relate to the health of the network. Yet those functions are not identical to the core ledger. A member should be able to see where the core ends and the public-good layer begins.
Consider translation again. Translation of transfer requirements, fee rules, account-standing consequences, hardship procedures, RPKI instructions and reverse-DNS steps is a direct registry cost because it reduces settlement errors. Translation of meeting material and community reports may be a participation cost. Translation of broader research and development material may be a public-good cost. All may be valuable. Grouping them together makes it harder to know whether fees are improving the ledger or financing regional presence.
Meetings and events have the same structure. A policy forum where transfer rules, sub-assignment, waiting-list priority or RPKI service effects are debated is part of governance. A training event that reduces route leaks may support operational security. A high-visibility institutional event may also support prestige. Prestige is not inherently bad; institutions need reputation to cooperate across borders. But reputation funded by mandatory fees should be described as such, not hidden inside the language of service continuity.
Staff time also cross-subsidises. Analysts who help small members with messy documents, payment issues or language questions are paid from general fees. That is appropriate if the aim is a better ledger. But if support burdens are systematically heavier for certain categories, members should know. Perhaps small-operator support reduces long-term record risk and deserves collective funding. Perhaps a particular service is underpriced. Perhaps a procedure is too complicated and creates avoidable staff work. Without measurement, cross-subsidy cannot be separated from inefficiency.
The most sensitive cross-subsidy concerns transfer and leasing. If transfer administrative fees recover only part of transfer review cost, annual members subsidise the transaction market. That may be acceptable because accurate transfers improve the ledger for everyone. If transfer fees exceed review cost and help fund broader budgets, transfer participants are paying a liquidity toll. If leasing-related support is heavy but formal mechanisms are underused, ordinary members may be subsidising a shadow market without visibility. The registry does not need to publish private lease prices to report support categories, failure points and cost patterns.
Cross-subsidy also interacts with large-country gravity. Large operators may pay more in absolute terms and may argue that they fund the regional commons. Small operators may pay less but may experience fees more heavily relative to revenue. Brazil and Mexico may supply expertise, funds and participation that benefit the region. Caribbean networks may require disproportionate support during payment, disaster or language problems. None of this is scandalous. It is what a region is. But a region is not a single wallet with a single interest.
A good fiscal report would therefore identify cross-subsidy deliberately. It would not pretend that every fee is exact cost recovery. It would say: this part is cost-based; this part is solidarity; this part is security insurance; this part supports participation; this part is a transfer-market charge; this part is reserve contribution. Members may still argue. At least they would argue about the real transfers.
Small operators pay most for fixed institutional cost
Fixed costs are the hidden regressivity of registry finance. A document request, a bank wire, a certified translation, a legal opinion, a transfer down payment, a renewal deadline, a support ticket, a policy consultation, a member meeting and an RPKI configuration problem do not shrink in proportion to the size of the operator. A /24 transfer may require much of the same institutional attention as a larger file. A rural provider may spend the same managerial hour that a large carrier spends, but the hour is a larger share of its capacity.
This is not simply an argument about small-operator dependency. The fiscal lens asks how the fee and budget system amplifies or reduces that dependency. A small operator may pay less in nominal annual fees than a large holder, but its all-in cost includes staff time, foreign-exchange spread, bank charges, document preparation, translation, counsel, opportunity cost, delay and the risk that a curable account issue blocks a service change. A large holder internalises those costs as administration. A small holder experiences them as strategy.
Caribbean and rural networks are the clearest stress test. In a small island market, a modest address block can support hotels, payment systems, public offices, health services, schools, local hosting or emergency communication. A fee may look small in the global address economy and large in the local operating budget. A provider may need to lease addresses rather than buy them because cash is needed for batteries, spares, radios, backhaul, disaster recovery or customer equipment. If registry fees and service states are hard to predict, the provider may accept upstream-assigned space and lose independence.
Public-sector and university networks face a different fixed cost. They may have resources assigned under old institutional names, research-network structures, ministries, public utilities or university departments. A current network may be legitimate, but its authority documents may involve decrees, procurement records, rectorate decisions, old technical contacts or reorganised public bodies. Legal proof is a fixed cost. A large public telecom group can reconstruct history. A small university may not have a dedicated team. If regularisation is costly, old records stay stale, which makes the ledger worse.
A fee model can either lower or raise these costs. Clear member categories, predictable annual charges and public transfer fees lower uncertainty. Non-refundable payments before review, renewal traps, unclear category changes and binary account-standing states raise uncertainty. A hardship path lowers the risk that banking or disaster friction becomes service failure. A vague contact-us path leaves small operators dependent on discretion.
The fiscal design should therefore include a small-operator incidence report. Not a sentimental paragraph; a measurement. How many small members fall into arrears? How many cure within a short period? How many face short payment because of bank fees? How many transfer requests involve /24 or /23 blocks, and what is their processing cost relative to value? How often does a category change create a surprise invoice? How often are hardship requests made after storms, public-sector budget delays or exchange restrictions? How often do RPKI or reverse-DNS support issues affect small members in account-risk states?
Such data would help defend fee discipline. If most arrears are chronic non-payment, members will support enforcement. If many are bank or foreign-exchange frictions, members may support clearer cure paths. If small transfers impose disproportionately high staff cost, members can decide whether to subsidise them because record accuracy is worth it. If non-refundable down payments deter weak filings, keep them. If they mainly deter legitimate small recipients uncertain about need review, revise them. Evidence is better than rhetoric.
Small-operator regressivity is also a competition issue. LACNIC should not become a telecom competition regulator. But its fee and review system can raise rivals' costs. If direct membership, clean transfer recognition, RPKI authority and reverse DNS become too expensive in attention or cash, small entrants become more dependent on incumbents for upstream space. Incumbents need not conspire. The fee structure does the work.
The solution is not blanket discounts. Discounts can create abuse and resentment. The better tools are proportional evidence, transparent timing, staged payment cure, disaster hardship, fee-incidence reporting, language access and the separation of payment defects from security or authority defects. Small operators do not need paternalism. They need the registry's fiscal machinery not to turn their smallness into a permanent surcharge.
Transfers and leasing convert fees into market microstructure
IPv4 scarcity turns transfer and leasing review into market microstructure. A private sale, merger or lease may be negotiated by parties, but the registry defines when the record is reliable enough for the market to treat the movement as settled. LACNIC can remain outside the private commercial bargain and still shape the cost, timing and risk of settlement. That boundary is important. It does not remove the fiscal effect of transfer fees, account-standing requirements and operational-service costs.
The waiting-list environment explains why. LACNIC's IPv4 waitlist was created on 19 August 2020, when the last available IPv4 block was assigned. Public material has described the late-stage queue in sobering terms: an applicant near the end may face at least eighteen years of waiting, may receive at most 1,024 IPv4 addresses, must already have IPv6 resources, and may receive recovered space that has spent at least six months in quarantine while reputation rehabilitation remains the recipient's burden. This is an orderly rationing mechanism. It is not a supply plan for present demand.
The practical burden therefore shifts to transfers, mergers, acquisitions, leases, upstream space, carrier-grade NAT, legacy regularisation and operational redesign. Each path has a fiscal interface. Transfers carry administrative fees and possible category changes. Leases may not be transfer fees, but they create support needs around RPKI, reverse DNS, abuse contacts and holder responsibility. Mergers require legal review. Upstream space reduces registry fees for the dependent operator but increases dependence on a provider. Carrier-grade NAT avoids address purchase but imposes equipment, logging and support cost. Every choice is a fiscal trade.
The registry's fee design can encourage formal movement or push activity into informal channels. If transfer fees are predictable, evidence categories are clear, payment states are granular and operational-service timing is known, parties are more willing to use the official route. If a small buyer cannot predict need review, fears a non-refundable payment, worries about renewal timing, or cannot know whether RPKI and reverse DNS will be available after record update, it may lease informally or rely on upstream space. Informal arrangements reduce the registry's direct workload in the short term and degrade the record in the long term.
Leasing is the most delicate case. It converts IPv4 from capital expenditure into operating expenditure. For a small hoster, access ISP, migration project or Caribbean service provider, that may be rational. The registry should not regulate rent or judge the commercial margin. It should care about responsibility: who is the recognised holder, who can originate routes, who can create or request RPKI authorisations, who manages reverse DNS, who answers abuse, what happens at termination, and whether the holder remains accountable.
Those responsibility functions cost money. A formal sub-assignment or delegated-use mechanism requires systems, WHOIS or RDAP presentation, public movement logs if policy requires them, staff review, support, dispute handling and perhaps additional guidance. If those costs are pushed entirely onto participants, small users may avoid the mechanism. If they are subsidised by general fees, members should know. The benefit is a cleaner ledger. The cost is staff and system work. That trade should be visible.
Transfer listing services raise the same questions. A list of possible offerors, recipients and optional intermediaries can reduce search cost. If participation lasts one year for a fee and access is limited to participating organisations, the list can protect privacy and reduce noise. It can also favour those already prepared to pay and participate. The fee should be justified by the cost of operating a useful discovery tool, not by the registry's privileged position near the market.
The fiscal goal should be formalisation without extraction. Fees should make transfers and responsible leases sustainable for the registry. They should not make formal settlement so costly or uncertain that the market moves into private opacity. If LACNIC wants an accurate ledger, it should price the path to accuracy with that public benefit in mind.
RPKI, reverse DNS and account standing are funded continuity services
RPKI and reverse DNS are often discussed as technical services. In the fee-and-reserve economy, they are continuity services funded by members and exposed to account states. They make the registry relationship operationally meaningful after a block is allocated, transferred, leased or regularised. If the services become unreliable, the value of the resource record falls.
RPKI changes the meaning of registry recognition because it connects the holder relationship to cryptographic statements about route origin. A network may have a commercial contract for addresses and still need the registry-linked path to create valid route-origin authorisations. Upstreams, peers and customers increasingly care about routing security. A delay in RPKI after a transfer, an account recovery or a delegated-use change is not merely a service inconvenience. It can affect routing acceptance, incident response and customer confidence.
Reverse DNS remains economically relevant for mail, logs, diagnostics, customer platforms, operational reputation and some diligence procedures. A buyer may not treat a block as fully usable until reverse delegation is in place. A hosting provider may face customer complaints if reverse records lag. A lessee may depend on a holder to delegate correctly. A public-sector migration may be blamed on the local provider if reverse resolution is wrong, even when the underlying problem is a registry or holder transition.
Inter-regional transfer guidance, as reflected in existing research, warns that services such as reverse DNS or RPKI may be affected and may not be immediately available when resources move between registries. That warning is technically modest and economically large. It means a transfer's settlement sequence has several stages: authority verification, need review where applicable, documentation acceptance, fee payment, agreement or order signature, registry record update, transfer log entry, RPKI availability, reverse-DNS delegation and contact transition. If members do not know which step may lag, escrow and financing must guess.
Funding these services requires stable fees and reserves. Maintaining RPKI repositories, signing infrastructure, monitoring, support and incident response has cost. Maintaining reverse-DNS infrastructure and delegation support has cost. Publishing documentation in multiple languages has cost. Training members to avoid mistakes has cost. A registry that charges too little may underinvest and create regional risk.
The account-standing interface is where the fiscal risk appears. What happens to RPKI and reverse DNS if a member is late on renewal? What if the late state is caused by bank deduction? What if a public university's payment is delayed by treasury approval? What if a holder is in a transfer dispute but the last verified ROA supports live customers? What if a lessor's account state threatens a lessee's customer network? What if an account appears compromised? These are different states, yet a blunt service limitation can produce collateral damage.
LACNIC should be able to enforce payment. The question is blast radius. Non-payment after notice may justify staged limitations. A compromised account may require immediate locks. A disputed authority claim may justify preserving the last verified state while blocking new changes. A bank shortfall should have a cure path. A disaster hardship should have continuity defaults. A court order should be implemented narrowly. Members should not have to discover these distinctions during a crisis.
That means the fee system needs a service-state map. For each account state, the map should say what happens to record publication, contact updates, RPKI changes, existing ROAs, reverse-DNS delegation, transfer requests, support, billing cure and appeal. It should distinguish late payment, payment mismatch, public-sector delay, disaster hardship, suspected fraud, account compromise, legal hold, disputed authority, ordinary transfer, inter-regional transfer and lease-related delegated use. Each state should have a reason, expected duration, cure path and continuity default.
Such a map is not leniency. It is risk control. It tells the market whether a billing issue can become routing risk. It tells a small operator whether to seek help before a deadline. It tells a lessee what assurance to demand from a lessor. It tells a buyer when to release funds. It lets the registry defend fee enforcement without appearing to use security services as leverage.
If member fees fund RPKI and reverse DNS, members are entitled to know how those funded services remain available during ordinary fiscal stress. The registry utility is not merely the ability to invoice. It is the ability to keep the operational record coherent when the invoice becomes difficult.
Staff scale and budget inertia after IPv4 exhaustion
IPv4 exhaustion did not make regional registries irrelevant. It changed their workload. The free-pool allocation function declined, but transfer review, legacy regularisation, RPKI, reverse DNS, security, account recovery, dispute handling, policy support, data services and member education became more important. A registry that once rationed new addresses now manages recognition, movement and continuity around a scarce stock. That can require skilled staff.
Still, post-exhaustion institutions face a survival incentive. An organisation built to allocate and administer a growing resource system may not shrink when allocation falls. It may redefine its centrality through security services, development programmes, data platforms, policy support, measurement, training, international coordination and community engagement. Some of that is real adaptation. Some can become institutional expansion justified by the memory of an older role.
The danger is budget inertia. Last year's staff count becomes the baseline. Programmes acquire constituencies. Meetings have calendars. Translation services have expectations. Legal and security teams can always identify more risk. Data and measurement projects can always be improved. Policy support can always be deepened. Member engagement can always be broadened. The institution's importance supplies a reason to keep doing more.
This is not a claim that staff expansion is bad. LACNIC's region is too varied for a brittle staff model. Reviewers need legal and linguistic sensitivity. Security teams need competence. Transfer staff need to understand fraud and market timing. Member support must handle payment friction, public-sector documents and small-operator constraints. RPKI and reverse DNS require technical depth. A cheap registry with thin staffing may become slow, arbitrary and dependent on a few individuals.
The issue is cost causation. Which staff roles are tied to core registry continuity? Which are tied to transfer-market complexity? Which are tied to RPKI and reverse-DNS service growth? Which are tied to meetings, training, applied research, external representation or internal administration? Which have grown because members need more help, and which have grown because the institution has chosen broader ambition? The answers determine fee legitimacy.
A budget can be transparent and still not decision-useful if it does not classify functions in that way. Members need a core-continuity statement: the minimum staff, systems and support required to keep records, account access, RPKI, reverse DNS, transfer processing, security, support and legal compliance running safely. Then they need a broader services statement: what additional staff support training, participation, research, external coordination and institutional engagement. Then they need a change statement: why each major increase occurred and what metric will show whether it worked.
Staff scale also affects incentives in policy. Complex policies create staff work. Staff work justifies budget. Budget supports institutional scale. Institutional scale makes complex policy easier for the registry than for small members. This loop is subtle but powerful. A rule that seems administratively implementable because LACNIC can staff it may still be too expensive for small operators to comply with. Budget analysis should therefore include external cost, not only internal cost.
Translation and community spending belong in this classification. Spanish, Portuguese and English support is a genuine access function when it helps members understand invoices, account states, RPKI, reverse DNS, transfers and evidence requirements. It is less clearly core when it funds broad institutional messaging, travel-heavy engagement or outputs whose users are not measured. The distinction is not anti-community. It protects community spending from suspicion by making the public-good component explicit.
The right target is a lean but capable registry. Lean does not mean small at any cost. It means each staff and programme line can be traced to a function, a risk, a member benefit and a metric. Capable means the institution can handle shocks without improvisation. Budget inertia is defeated not by austerity but by classification and review.
In the post-exhaustion era, staff scale should be justified by the work of a registry utility: preserving accurate records, supporting security services, handling legitimate movement of scarce resources, reducing transaction cost, helping weaker members comply and preventing disputes from contaminating operations. It should not be justified merely by the institution's desire to remain central after the old allocation story has ended.
Hardship paths should preserve discipline and continuity
Hardship is often treated as the opposite of fee discipline. It should not be. A mature registry needs both. Fee discipline protects paying members, funds continuity and prevents chronic free-riding. Hardship paths protect the ledger from avoidable damage when a member's failure to pay or comply is caused by conditions that do not reflect bad faith and can be cured.
LACNIC's region makes hardship practical rather than sentimental. Members can face currency devaluation, exchange-control delays, public-procurement calendars, disaster damage, bank de-risking, wire-fee shortfalls, local political disruption, tax-document requests and correspondent-bank delays. Caribbean operators can face storms, power problems and undersea-cable incidents. Public universities can face budget cycles. Small rural providers can face customer-payment shocks. Treating all of these as ordinary delinquency is bad economics.
At the same time, treating hardship as a vague excuse would be unfair to members who pay on time and to the institution that must maintain services. Hardship should be rule-bound. It should require early notice where possible, evidence proportional to the claim, a defined cure period, staged consequences, and protection only for essential registry functions unless the board or staff have approved broader relief. The key is classification.
A payment taxonomy would help. Categories might include ordinary current; late but curing; bank-fee short receipt; payment sent but not received; public-sector approval pending; exchange-control delay; disaster hardship; disputed invoice; suspected avoidance; chronic non-payment; and account compromise. Each category should have a service effect. A bank-fee shortfall should not be treated like refusal. A public-sector delay should not be treated like fraud. Chronic non-payment after cure opportunities should have consequences.
Service continuity should be staged. Existing public records should remain visible except in narrow security or legal circumstances. Existing ROAs and reverse-DNS delegations that support live networks should be preserved where safe while payment is cured. New transfers or discretionary changes may be paused in some states. Support should remain available enough to cure the problem. This is not indulgence. It prevents fee enforcement from creating avoidable network harm.
Hardship also matters before transfers. A seller with a curable arrears issue may be trying to monetise unused addresses to pay debt, fund network repair or exit a business line. If the arrears block the transfer absolutely, the seller may be trapped. The registry has a legitimate claim to payment, but it should consider structured settlement: a portion of proceeds pays outstanding fees at closing, the transfer remains conditional until settlement, and the record is not moved until the obligation is satisfied. Such mechanisms protect the registry without destroying liquidity.
Public-sector and university networks may need special evidence paths, not special treatment. A university budget delay is not proof that fees are optional. It is proof that the cure timeline may differ. A ministry reorganisation may complicate signatory authority. A municipality may need a council resolution. LACNIC should publish examples so public entities can prepare before deadlines.
Disaster hardship deserves separate rules. In hurricane-exposed island markets, a provider may need RPKI changes, reverse-DNS updates or contact recovery precisely when invoices or documents are disrupted. The registry's continuity default should prioritise restoration of last verified operational service, not punishment of administrative delay. After the crisis, normal payment and documentation should resume. A disaster rule that is explicit is less vulnerable to abuse than improvised discretion.
The fiscal reason for hardship paths is simple: unpaid fees are a cost, but broken records are also a cost. If harsh enforcement pushes members into stale contacts, hidden leases, upstream dependency or avoidance of regularisation, the ledger suffers. If lenient enforcement erodes payment culture, the ledger also suffers. A classified hardship system is the middle path.
Board and member oversight must reach the budget machinery
Member oversight is often discussed through elections, policy processes and public meetings. In a fee-funded registry, fiscal oversight is just as important. The board and members do not merely approve an accounting result. They decide the economic settlement between the registry and the operators that rely on it. That settlement includes fees, reserve targets, legal spending, staff scale, programme scope, hardship rules and the degree of cross-subsidy in the region.
The difficulty is information. A budget can be published and still leave members unable to judge incentives. Legal, professional services, community, training, security, operations and member services are broad labels. They do not tell a small operator whether its fee funds RPKI continuity, transfer-market review, meeting travel, a legal fight over institutional authority, a multilingual support channel, or reserves above a target band. Oversight requires categories that match the economic risks.
Board oversight should therefore separate three questions. First, what must be funded to keep the core registry safe? Second, what should be funded because it creates regional public goods? Third, what is being funded because the institution has become accustomed to doing it? The first question deserves strong protection. The second deserves member-visible justification. The third deserves periodic challenge.
Member votes or consultations on fees should include incidence analysis. Who pays more? Who pays less? Which member categories are affected? How do changes fall on small blocks, large holders, end users, public-sector networks, new recipients, transfer participants and members in high-friction payment environments? Does a fee increase restore reserves, fund staff, fund security, cover legal risk or expand programmes? Does it preserve the existing budget path or change it? A vote without incidence information is a choice without a map.
Reserve approvals should include target bands and drawdown authority. The board should not need member approval for every ordinary operating decision. It should need a clear policy for extraordinary reserve use, especially legal drawdowns, emergency capital projects, deficits caused by deliberate fee policy, and projects outside core registry service. Members should know what counts as core, what counts as strategic, and what counts as discretionary.
Legal oversight should be strengthened before crisis. Active matters can remain confidential. Categories and authority should not. The board should receive and publish, at suitable aggregation, legal spend by purpose: routine corporate, transfer and resource disputes, data and privacy, governance, employment, contracts, litigation, regulatory response, security incident, and external institutional engagement. If a category spikes, the board should explain why in general terms. This protects the institution because it reduces suspicion before a dispute becomes public.
Conflict disclosure belongs in fiscal oversight as well as policy oversight. Board members, committee participants or advisers may have ties to large holders, brokers, buyers, vendors, training programmes, national associations, public-sector bodies or policy factions. That does not make them unfit. In a small expert community, expertise often comes with interests. The issue is disclosure and recusal when budget lines, transfer rules, fee changes or service priorities could affect those interests.
Member oversight should also reach service metrics. If fees are raised for better service, members should see processing times, support response, transfer delay categories, RPKI availability, reverse-DNS update performance, account recovery, billing disputes and hardship outcomes. If reserves are defended for continuity, members should see continuity tests and incident readiness. If translation budgets are defended for inclusion, members should see which materials and service channels are covered and whether usage justifies expansion or change.
The board's role is not to micromanage staff. It is to keep the fiscal machinery aligned with the registry's limited utility function. Staff should run systems, review files and support members. The board should ensure that the budget does not quietly transform service dependence into institutional self-protection. Members should have enough information to approve, resist or revise that direction.
In a registry, financial accountability is not a side branch of governance. It is the place where mission language becomes enforceable. A board that cannot explain the fee model cannot credibly ask members to trust discretion elsewhere.
Toward an incentive-compatible fiscal constitution
An incentive-compatible fiscal constitution for LACNIC would not require a revolution. It would require public classifications that connect fees, costs, reserves, services and accountability. The objective is not to make every line item controversial. It is to prevent the unavoidable fee base from becoming a black box.
The first element is a core-continuity budget. This would identify the cost of maintaining registry records, account authentication, member support necessary to the record, WHOIS or RDAP publication, reverse DNS, RPKI, transfer recording, security operations, backups, disaster recovery, essential legal compliance, audit and minimum governance. It should include staff and overhead genuinely necessary for those functions. It should not include every community or development activity merely because the institution is important.
The second element is a public-good and participation budget. This would cover training, meetings, fellowships, applied research, measurement, community support, broader translation, policy forums and external coordination. These activities may be valuable. Separating them protects their legitimacy. Members can then decide whether the public good is worth mandatory funding, whether sponsorship or grants should support some of it, and whether outcomes justify the expenditure.
The third element is a reserve target band. The reserve policy should state target months of core-continuity expenditure and target months of total expenditure; liquidity levels; legal, security and disaster buckets; permitted drawdowns; board authority; member-approval thresholds; and rules for excess reserves. It should say what happens if reserves fall below the band and what happens if they rise above it. A reserve without a ceiling is institutional ballast.
The fourth element is fee-incidence reporting. Every material fee change should report distribution by member category, resource size, transfer role, new recipient status, small-block effect, public-sector or university relevance where possible, payment-friction risk, and expected behavioural responses. If a fee element is intended as cost recovery, show cost. If it is intended as solidarity or public-good funding, say so. If it contributes to reserves, identify the bucket.
The fifth element is transfer-cost accounting. LACNIC should publish aggregate cost and revenue for transfer review, listing services and related support. It need not publish private prices or confidential files. It should show processing times, denial or withdrawal reasons, document supplement categories, payment-related holds, inter-regional coordination delays, RPKI or reverse-DNS service lags, and fee revenue relative to service cost. This would distinguish settlement fees from liquidity tolls.
The sixth element is account-state mapping. The registry should publish how payment, contract, security and legal states affect record publication, RPKI, reverse DNS, transfers, contact updates and support. The map should include cure paths, appeal routes and continuity defaults. It should be written for real operators, not only lawyers.
The seventh element is legal-spend classification. Annual reporting should distinguish routine counsel, governance, employment, contracts, transfer and resource disputes, data and privacy, litigation, regulatory or court response, security incident support and external institutional engagement. Active matters can remain confidential. Trends should not.
The eighth element is small-operator and public-sector support metrics. The registry should report aggregate outcomes for hardship, payment friction, document defects, language support, small-block transfers, regularisation, account recovery and disaster-related support. It should not expose private member details. It should reveal whether the fiscal system is regressive in practice.
The ninth element is board and member decision records for major fiscal choices. When the board proposes a fee change, reserve drawdown, major system investment, significant legal strategy or programme expansion, the public record should state purpose, cost, expected benefit, risk, affected groups and review date. The goal is not theatre. It is to make institutional memory usable.
The tenth element is sunset and review. Programmes funded by mandatory fees should have review dates. If a training programme improves RPKI adoption or routing security, renew it. If a meeting format does not reach small operators, change it. If a transfer fee over-recovers cost, reduce it or allocate the surplus openly. If reserves exceed the target, lower future fees or seek member approval for a named use. A fiscal constitution without review becomes ceremony.
These reforms would not remove conflict. Large holders and small operators will still disagree about burden. Transfer participants and pure service users will still disagree about fees. Security advocates and fiscal minimalists will still disagree about investment. The point is to replace suspicion with evidence. A registry that can show what each dollar does is harder to accuse unfairly and easier to correct when incentives drift.
LACNIC's strongest future is not as the cheapest possible registry or the most expansive regional institution. It is as a solvent, narrow, auditable utility whose broader public-good work is explicit rather than hidden. That is how fees become legitimate and reserves become insurance rather than power.
Watchpoints for the next phase
The first watchpoint is the reserve ratio. Members should ask not only whether reserves rise or fall, but how reserves compare with core registry-continuity expenditure and total organisational expenditure. A reserve that protects twelve months of core ledger service may be prudent even if it looks large; a reserve that grows without a target or release rule may indicate institutional ballast. The question is whether reserves protect the ledger during shocks or protect the institution from fee discipline.
The second watchpoint is legal spend. Category-level legal reporting should show whether money is going to routine counsel, resource disputes, transfer cases, governance questions, privacy and data, contracts, employment, court orders, security incidents or broader institutional defence. Rising legal spend is not automatically bad. It becomes a danger when members cannot tell whether their money defends accurate records or defends discretionary power.
The third watchpoint is fee incidence by member size. Annual, maintenance, renewal and transfer charges should be assessed by their effect on small Caribbean and rural providers, public-sector and university networks, large-country incumbents, hosting firms, data-centre operators, cloud buyers, legacy holders and first-time recipients. A fee can be equal in form and regressive in effect. A resource-sensitive fee can be fair and still create cliffs.
The fourth watchpoint is payment failure handling. Members should look for data on late payments, short receipts caused by bank fees, foreign-exchange delays, public procurement delays, disaster hardship, wrong references, disputed invoices and chronic non-payment. The registry should distinguish these states and publish the service consequences. A payment issue should not automatically become a transfer freeze, RPKI risk or reverse-DNS risk without a narrow reason.
The fifth watchpoint is hardship. The existence of a hardship path is not enough. It should have criteria, cure periods, continuity defaults, reporting and appeal. Watch whether small operators in arrears can cure without losing essential registry functions, whether public-sector networks can manage budget timing, and whether disaster-exposed operators have practical restoration support.
The sixth watchpoint is transfer and lease fee effects. Transfer administrative fees, non-refundable down payments, renewal timing, category changes, listing-service fees and delegated-use support should be judged as a combined cost stack. If small transfers decline, if responsible leasing mechanisms are underused, if informal arrangements grow, or if brokers profit mainly from hidden process knowledge, the fee and review system is shaping the market more than it admits.
The seventh watchpoint is RPKI and reverse-DNS service continuity funding. Members should ask whether the budget identifies these services as core, whether service availability and update performance are measured, whether inter-regional transfers produce lag, and whether account states can impair existing ROAs or reverse delegations. A funded security service should not become an unpriced enforcement lever.
The eighth watchpoint is conflict disclosure. Board members, committee participants, advisers and active policy figures may have ties to large resource holders, brokers, buyers, vendors, national organisations, public-sector bodies or programme beneficiaries. The issue is not exclusion but disclosure and recusal. Fiscal decisions around transfer fees, reserves, legal spend and programmes should show how conflicts are managed.
The ninth watchpoint is budget votes and member oversight. Fee changes and reserve policies should come with incidence statements, core-versus-broader cost separation, reserve targets, legal-spend categories and service metrics. A budget vote should not ask members to approve a bundle they cannot interpret. The more compulsory the fee, the more decision-useful the budget must be.
The tenth watchpoint is small-operator arrears. Rising arrears among small providers, public networks or Caribbean operators would be a warning that the fee system is colliding with currency, banking, disaster or revenue constraints. Low arrears would support the claim that the fee burden is manageable. In either case, publish the categories.
The final watchpoint is the hardest: whether reserves and fees protect the ledger or protect the institution from accountability. A registry needs money to keep the address book accurate, secure and continuous. It does not need a blank cheque to preserve every programme, every legal theory, every staff baseline or every expression of institutional ambition. The member invoice should buy continuity, not deference. The reserve should insure the utility, not enthrone the bookkeeper. In the scarcity era, that fiscal boundary is one of the main tests of LACNIC's legitimacy.