Summary

  • Cogent's public filings show that IPv4-related assets can support substantial secured financing: a bankruptcy-remote issuer placed $206.0 million of notes in 2024 and another $174.4 million in 2025, backed by addresses, customer leases, receivables and related assets.
  • That transaction does not prove that any lender can take a simple lien over any address block. Its special-purpose structure, segregated collections, trustee, liquidity reserve, utilisation tests, cash sweeps, sale directions and remedies for defective collateral transfers are evidence of the work required to manufacture control.
  • Under a common US secured-transactions analysis, a security interest may attach to a debtor's general intangible and be perfected by filing. Yet UCC section 9-408 expressly warns that overcoming an anti-assignment term for attachment or perfection does not force the obligated party to recognise the lender, render performance to it or permit enforcement of the right.
  • RIR procedures make the control gap operational. They recognise current holders or legal successors, require evidence and policy compliance, update registration to complete transfers, and may treat insolvency as a service or revocation event. A financing statement is not itself a registry transfer instruction.
  • NRS can improve collateral value through an optional portable control framework: exact prefix schedules, time-stamped security notices, agreed enforcement roles, cure and challenge procedures, one authoritative transfer state, continuity safeguards and the ability to move the registration service if an incumbent fails. It should verify facts, not adjudicate default, priority or property law.

Collateral is a promise about the day after default

Every secured loan contains an optimistic story and a pessimistic one. The optimistic story describes how the borrower will use the money and repay it from ordinary cash flow. The pessimistic story describes the collateral.

For a building, the lender knows where the asset is, which public office records the mortgage and which legal process governs sale. For listed securities, control and account rules can make priority and disposition legible. For receivables, notices can redirect payment. The legal detail is never trivial, but the lender can identify the institution that turns a security interest into practical control.

IPv4 rights do not arrive with one comparable institution. The borrower may be listed by an RIR, hold resources under a registration-services agreement, announce routes through network operators, create route-origin authorisations, lease addresses to customers and expect to transfer blocks through a regional process. Those functions can be held by different entities and governed by different instruments.

Before default, the fragmentation can be managed by cooperation. The borrower keeps the registry account current, supplies reports, maintains credentials, collects lease payments and requests transfers when needed. The lender monitors covenants and sees a portfolio whose scarcity and cash flows appear to support value.

After default, cooperation is the fact that can no longer be assumed. The borrower may dispute the default, withhold credentials, change contacts, transfer a block, allow fees to lapse, enter insolvency or continue routing while the lender seeks a sale. The registry may regard the borrower as the only recognised holder. A customer may keep paying the borrower. A buyer may refuse to fund until the RIR confirms eligibility. A court may stay enforcement.

The collateral question is therefore not whether addresses command prices. It is whether the lender can move from a private security agreement to an authoritative, lawful and operational state without destroying the cash flows that made the collateral valuable.

The Cogent transaction proves finance, not simplicity

Cogent Communications offers the strongest public demonstration that IPv4-related assets can support institutional debt.

In May 2024, Cogent IPv4 LLC, described as a special-purpose, bankruptcy-remote indirect subsidiary, issued $206.0 million of secured IPv4 address revenue notes at 7.924%. In April 2025 it issued another $174.4 million at 6.646%. Cogent's 2025 annual report refers to the combined $380.4 million as its IPv4 Notes.

The collateral package was broader than a list of prefixes. Public disclosures say certain IPv4 addresses, customer IPv4 address leases, customer receivables and other address assets were contributed or sold to the issuer. Collections were channelled through a structure involving a manager and trustee. Funds received before monthly reconciliation were held in a segregated account as collateral. Interest and specified costs were paid before residual cash returned to the parent group.

The notes also carried structural protections. The issuer maintained a liquidity reserve. Debt-service-coverage failure could trigger rapid amortisation. If utilisation - the proportion of leased addresses to total addresses owned by the issuer - fell below thresholds, collections could be applied to note repayment. In some circumstances noteholders could direct a sale of the IP address assets. Events of default included non-payment, covenant failures, bankruptcy events, specified representation breaches, ineffective security interests and judgments.

The disclosures also refer to indemnification if transfers of collateral assets were defective or ineffective.

These details matter more than the headline principal amount. They show that lenders did not rely on a sentence saying "IPv4 addresses are collateral." They relied on entity separation, ownership arrangements, leases, receivables, controlled cash, reporting, reserves, triggers, sale mechanics and legal remedies.

The public filings do not disclose every term of the private offering, every prefix, every registry arrangement or every enforcement scenario. No default performance is available from the cited record. The transaction therefore proves that sophisticated parties financed a defined package. It does not establish a loss rate, recovery rate, universal advance rate or a plug-and-play lien for the wider market.

Three assets are hiding inside one collateral label

"IPv4 collateral" can describe at least three economically distinct things.

The first is the registration and use interest in the addresses. This is the scarce resource position: the borrower or special-purpose entity is recognised for specified prefixes and can obtain benefits from using, leasing or transferring them subject to applicable rules.

The second is the contract portfolio. Customer leases or service agreements generate payment obligations. Those receivables may be easier to describe, notify and collect than the underlying registration right. Their value depends on customer credit, contract term, termination rights, utilisation and continued service.

The third is the enterprise machinery that makes the first two useful. Registry credentials, RPKI administration, reverse DNS, abuse handling, sales relationships, reputation remediation, billing, technical support and staff knowledge preserve the portfolio and its cash flows.

A lender can have strong control over one layer and weak control over another. It may perfect a security interest in receivables and obtain a segregated account, yet be unable to make the registry recognise a buyer after default. It may have a lien over a described general intangible but no access to credentials or customer information. It may acquire equity in a special-purpose company while a service provider retains practical administration.

This explains why address-backed finance is often stronger when built around revenue and entity control rather than a naked foreclosure right. Cash can be swept before a default becomes terminal. Equity can place governance around the asset-owning entity. Customer contracts can define payment redirection. Sale covenants can preserve marketability. None entirely removes registry dependence, but together they reduce the distance between legal security and practical recovery.

Valuation should follow the layers. A portfolio of unleased but clean, transferable blocks has option value and sale risk. A heavily leased portfolio has current revenue but may be harder to deliver free of customer claims. A block used in the borrower's essential network may be valuable yet costly to remove. One per-address price cannot capture these differences.

The lender should ask which layer repays the loan in the base case and which layer remains after default. If the answer changes silently from lease cash flow to forced address sale, the collateral model is weaker than its headline.

Attachment is not control

US Article 9 provides a useful legal lens because it separates several steps that commercial discussion often compresses.

Section 9-203 says a security interest becomes enforceable against the debtor and third parties when value has been given, the debtor has rights in the collateral or power to transfer rights, and the relevant authentication or control condition is satisfied. For a non-possessory intangible, the usual instrument is an authenticated security agreement describing the collateral.

That test immediately raises the first IPv4 question: what rights does the debtor have? A security agreement cannot create more than the debtor can convey. The answer may include contractual registration rights, use rights, transfer-request rights, lease contracts, receivables and proceeds. It may exclude powers reserved to a registry, rights held by an affiliate or customer, and outcomes dependent on policy compliance.

Classification matters. An IPv4-related right may be analysed as a general intangible, while receivables may fall into account or payment categories depending on the transaction. The exact answer is jurisdiction- and contract-specific. This article does not assert one legal classification for every portfolio.

Perfection is a separate step. Section 9-310 states the general rule that a financing statement must be filed to perfect security interests unless an exception applies. Filing can establish priority against competing claimants under the governing secured-transactions law. It does not update an RIR database, transfer credentials, create RPKI authority or make a network accept routes.

That gap is often obscured by the word "lien." A lender can have an enforceable and perfected security interest against the borrower while still lacking the institutional means to realise the collateral. The legal interest may rank ahead of another creditor and yet remain operationally blocked at the moment of sale.

Good underwriting must therefore trace two chains. The priority chain asks whether the lender's security interest attaches and is perfected against competing claims. The control chain asks whether the lender can preserve and dispose of the underlying rights through the institutions that make them valuable. IPv4 finance fails when the first chain is treated as proof of the second.

UCC section 9-408 names the control problem directly

The most instructive Article 9 provision is not a remedy but a limitation.

Section 9-408 addresses contractual or legal restrictions on assigning certain general intangibles, including contracts, permits, licences and franchises. In specified circumstances, a restriction is ineffective to the extent it would impair the creation, attachment or perfection of a security interest. That can stop an anti-assignment clause from making the lender's lien disappear at inception.

The section then draws a hard boundary. Where the underlying restriction would otherwise be effective, overcoming it for attachment or perfection does not make the security interest enforceable against the account debtor. It does not impose a duty on that party. It does not require recognition of the lender, performance to the lender or acceptance of performance from it. It does not entitle the lender to use or assign the debtor's rights. It does not itself permit enforcement of the security interest in the general intangible.

That structure closely resembles the lender's IPv4 dilemma, though its application to any particular registry agreement requires legal analysis. The borrower may grant a lien over all of its rights. The lender may file. Yet the registration service may not have agreed to recognise the lender, accept its instructions or process its buyer. A rule that saves the security interest between borrower and lender does not necessarily compel the service relationship to move.

This is why a portable registration right would affect credit value. It would not have to abolish registry eligibility, fraud checks or lawful restraints. It would need to define in advance how an authorised secured party can step into a limited enforcement role, what evidence triggers that role and which service must act.

Without such a mechanism, the lender prices an uncertain conversion. It may receive proceeds if the borrower cooperates, an officeholder completes a sale, a court orders relief and the registry accepts the result. But none is the same as a pre-agreed control path.

The uncertainty transfers bargaining power to the incumbent registration service. The registry may have legitimate integrity duties, but if no qualified alternative can complete a verified change, administrative discretion becomes part of collateral volatility.

Default remedies stop at the edge of another institution

Article 9 gives secured parties meaningful post-default powers. Section 9-607 can permit collection and enforcement against persons obligated on collateral. Section 9-610 permits disposition of collateral after default and requires every aspect of the disposition to be commercially reasonable. These rules organise creditor action against the debtor, cash flows and buyers.

They do not answer every third-party dependency. Section 9-607 itself says it does not determine whether an account debtor, bank or other obligated person owes a duty to the secured party. Section 9-408 supplies an even clearer warning for restricted general intangibles.

An IPv4 sale needs more than a commercially reasonable auction. A qualified buyer must be identified. The prefixes must be exact. The recognised holder or lawful successor must provide authority evidence. The receiving entity may need a registry relationship. Transfer restrictions and disputes must be cleared. The registration must change. RPKI, reverse DNS and contacts must transition. Existing lessees may need continuity.

If a lender conducts an impeccable sale but cannot secure the authoritative registration update, the buyer has not received the full economic package. If it updates registration but abruptly breaks lease service or routing-security administration, it may destroy the revenue and reputation that supported value. If it seizes credentials without authority, it may create security and fraud risk.

The remedy must therefore be designed before default. A security agreement between lender and borrower is necessary but not sufficient. The relevant registration service must acknowledge a defined role or a portable framework must allow another qualified service to do so. Customer contracts should address redirection and continuity. Corporate governance should permit a collateral manager to act if control springs.

The absence of advance design does not make recovery impossible. Courts, insolvency officeholders and registries process complex transfers. It makes recovery slower, more contested and less predictable. That uncertainty is a haircut on collateral value even when the ultimate sale succeeds.

RIR rules recognise holders and successors, not financing statements

ARIN's current policy says the source entity in a transfer must be the current rights holder recognised by the responsible RIR and must not be involved in a dispute over the resource's status. Its transfer guidance says commercial terms belong to the parties but every transfer must comply with ARIN policy. ARIN also verifies the source or legal successor using corporate, court, bankruptcy and transaction documents.

Those controls protect registry accuracy. They also show why a UCC filing is not a transfer instruction. The financing statement establishes notice and priority under secured-transactions law. It does not by itself make the lender the current recognised rights holder or legal successor. A receiver, bankruptcy trustee, secured party or purchaser must still connect its authority to the entity and transaction the registry recognises.

RIPE policy makes the registration event equally explicit. Transfers must be reflected in the RIPE Database, and the original holder remains responsible until completion. The current transfer procedure requests legal names, registration papers, authority evidence, reasons and the exact resources. In business-structure, bankruptcy and liquidation cases, official documentation matters. A voluntary transfer lock can also prevent movement during its term.

APNIC's membership agreement presents another risk. It describes delegated resources as rights provided under APNIC documents and allows termination and revocation upon an insolvency event. Its late-payment procedure also links account closure to revocation and recovery, subject to a limited reactivation period. A lender that models addresses as detached property can therefore miss the service and membership conditions supporting use.

These regions do not use one legal vocabulary or one insolvency procedure. The selected sources do not establish how often lenders are recognised, how long enforcement transfers take, or how many fail. They do establish a common institutional fact: the registry maintains an authoritative administrative state and applies its own evidence and policy process to changes.

That state can support secured lending if integrated into the transaction. It becomes a source of discretion if the lender appears only after default with a private agreement the registry never acknowledged.

Insolvency changes who can speak before it changes the prefix

A payment default under a loan and a formal insolvency are different events.

In an ordinary default, the borrower remains the legal entity controlling its business. The lender's rights come from the security documents and applicable law. A cure period may run. The borrower may contest acceleration. Registry contacts remain employees or agents of the borrower unless a pre-agreed authority becomes effective.

In insolvency, corporate authority may shift to a trustee, administrator, liquidator, debtor-in-possession or court-supervised manager. The automatic stay in a US bankruptcy can restrict acts to obtain possession of or enforce liens against estate property. Other jurisdictions have different moratoria and officeholder powers. A private "automatic transfer on default" clause cannot safely be assumed to override the applicable insolvency regime.

The registry must identify who can instruct it. That is a legitimate task. It should not decide creditor priority from first principles. If a court or authorised officeholder directs a sale, the registry verifies the instrument, resource scope, recipient and policy conditions. If creditors dispute entitlement, the registry can preserve the current state and record the restraint while the competent forum decides.

Timing still matters. Immediate service termination can destroy value before the forum acts. APNIC's agreement permits revocation on insolvency. RIPE closure materials distinguish insolvency from continued operations authorised by a national authority. A lender financing a functioning network must understand whether the relevant service can remain active during administration.

The best collateral regime therefore includes a continuity state. Registration, contacts, reverse DNS, RPKI and existing lease administration remain stable for a defined period under the recognised officeholder or collateral manager. Extraordinary transfers require authority; ordinary preservation does not stop merely because the borrower's capital structure failed.

This protects more than the lender. Customers and networks may depend on the prefixes. A rushed foreclosure that disconnects them reduces sale value and imposes costs on parties that never signed the loan.

Control is not the same as possession of credentials

An insecure lender may ask the borrower to hand over registry passwords, signing keys or route-origin controls. That is not a mature control framework.

Credentials prove access, not legal authority. A lender employee using the borrower's account could appear indistinguishable from an intruder. Shared passwords defeat attribution. Control of an RPKI key can affect routing authorisation but does not transfer registration rights. Reverse-DNS access serves another function. None by itself establishes priority or permits a sale.

Credential custody can also damage the borrower's network before default. A lender should not have routine power to change route-origin authorisations, contacts or nameservers merely because it financed the asset. Operational interference can breach customer obligations and create outages. The collateral package should preserve business use while preventing unauthorised disposition.

Proper control is institutional. The registration service knows that a security arrangement exists, knows the exact prefixes and knows the limited events on which the secured party can submit an instruction. The borrower retains ordinary administration. High-risk changes may require dual approval. The lender receives notices of proposed transfers, agreement termination, unpaid fees, credential recovery and material disputes. After a valid enforcement trigger, authority shifts through an attributable state change rather than secret credential use.

The service should support multiple roles: operating administrator, legal holder, secured-party contact, collateral manager and receiving buyer. These roles must not be collapsed into one login. Permissions should be least-privilege and time-limited.

This resembles control arrangements used elsewhere in secured finance, but the analogy should not be overstated. An IPv4 registration is not a deposit account or certificated security. The useful principle is that the third-party institution maintaining the decisive state acknowledges the secured party's conditional role before default. The implementation must be native to number-resource operations.

Without that acknowledgement, "control" is often only a covenant that the borrower will cooperate later. Default is precisely when that promise is least reliable.

A collateral schedule must describe prefixes, rights and revenue separately

The first document in a credible IPv4 financing should be a collateral schedule that can survive legal, registry and technical scrutiny.

The schedule identifies every prefix without double-counting more-specifics. It states the current registration entity, service region, registration service, agreement type and account. It records legacy status where relevant, recent transfers, voluntary locks, disputes and the legal entity chain.

It then separates rights. The borrower may have a right to use, maintain registration, request transfer, create customer assignments, administer reverse DNS, maintain RPKI and receive proceeds. Each right may have a different holder or condition. The schedule should not use "all IPv4 addresses" as a substitute for analysis.

Revenue receives its own schedule. Which customer leases relate to which prefixes? What are their terms, renewal, termination and assignment provisions? Who bills? Where do collections arrive? Are receivables pledged? Can customers set off claims? Is continued registry service a condition of payment?

Operational dependencies also belong in the record. Which route-origin authorisations exist? Who controls signing systems? Which prefixes are in active use by the borrower? Which are announced by customers? What abuse or reputation issues could reduce marketability? Which data is confidential but available to the collateral agent under controlled access?

Finally, the schedule must reconcile to accounting and borrowing-base reports. Addresses sold, transferred, returned, subdivided or newly leased should not remain eligible by mistake. If utilisation drives covenant tests, the numerator and denominator require stable definitions. Cogent's disclosed utilisation triggers show why this precision matters.

A signed registry attestation can corroborate the administrative layer. It cannot corroborate lease revenue, customer credit or every legal claim. The lender must combine independent evidence rather than ask one record to perform every function.

This discipline reduces both overvaluation and accidental exclusion. A vague all-assets lien may cover rights in principle, but a precise schedule is what enables monitoring, sale and buyer diligence.

Borrowing-base design should assume the difficult sale

A prudent lender values the collateral under stress, not at the cleanest broker quote.

Eligibility should exclude or haircut prefixes with disputed authority, incomplete registration, active transfer locks, sanctions constraints, non-transferable assignments, overlapping customer claims or unresolved reputation problems. Large blocks may deserve liquidity adjustments. Small fragments may incur higher cost. Cross-region transfers may require more time and dual-institution coordination.

The advance rate should distinguish current lease cash flow from residual sale value. Contracted revenue may support debt service, but customer concentration, churn and termination rights matter. Residual address value should be net of brokerage, legal, registry, remediation, tax and transition costs. A forced sale horizon can differ from an orderly sale.

Concentration limits can apply by registry, agreement type, customer, prefix size and legal entity. If the entire portfolio depends on one service provider or one corporate account, operational failure can affect all collateral at once. Portability can reduce this concentration only if it is real and tested.

Monitoring should include registration status, fee payment, proposed transfers, new locks, disputes, route-origin changes, lease utilisation, collection performance and material policy changes. Triggers should produce proportionate responses: reserve top-up, cash sweep, amortisation, cure, additional collateral or controlled sale.

The Cogent disclosures show several of these techniques at institutional scale: segregated collections, reserve, debt-service coverage, utilisation thresholds, rapid amortisation and directed sale rights. They do not reveal the appropriate thresholds for another borrower. A smaller portfolio, different customer base or different registry agreement may justify a different structure.

No public data set establishes a global loan-to-value ratio, default rate or recovery distribution for IPv4 collateral. The 2025 launch of a lending programme by IPv4.Global shows market interest but provides no independent evidence of underwriting outcomes. Responsible credit analysis must preserve that missing denominator rather than convert one programme and one securitisation into an industry average.

The incumbent registry receives an unpriced option

When enforcement requires an incumbent registry's discretionary cooperation, the lender has effectively granted that institution an option over timing and outcome.

The registry may exercise the option for good reasons. It may detect forged authority, overlapping prefixes, an invalid successor, a court restraint or a policy violation. Integrity review protects the lender as well as the public record.

But discretion can extend beyond integrity. A service may demand serial documents without a completion deadline, interpret a commercial objection as a transfer defect, suspend an insolvent account before a continuity arrangement is ready, or simply fail to act. If no alternative service can complete a verified transfer, delay becomes veto.

The lender bears the cost. Interest accrues. Customers leave. Market prices move. A buyer's financing expires. The block's reputation may deteriorate. Legal fees rise. The registry does not necessarily compensate the secured party for any of these losses.

This asymmetry depresses collateral value even if registries usually behave well. Credit pricing reflects tail risk and enforceability, not only average courtesy. The absence of published enforcement times and outcomes makes the tail harder to estimate.

A registry may argue that it never agreed to the security interest. That is precisely the point. The current model offers no standard way to obtain such acknowledgement and no portable alternative if the service declines. Borrower and lender can document their relationship perfectly while leaving the decisive recordkeeper outside it.

NRS should not solve this by forcing blind recognition of every private lien. It should create an opt-in standard under which the holder, secured party and qualified registration service define roles in advance. Once accepted, the service is bound to an evidence-based process, and the registration can move to another qualified service if the incumbent cannot perform.

The right being financed becomes more valuable because the means of enforcement is no longer an unpriced favour.

An NRS collateral-control framework should be optional and exact

The framework should begin with consent. A holder chooses to place specified registration rights into a collateral-control arrangement. The registration service verifies the holder, secured party or collateral agent, exact prefixes, agreement authority and signatures. It does not infer a lien from a public filing or broker email.

The accepted arrangement creates a time-stamped security notice. The notice states that a conditional secured-party role exists; it does not declare priority against the world. Sensitive loan terms remain private. A public verifier can confirm that a notice exists, its scope, status and effective time without seeing principal, pricing or confidential covenants.

The notice creates negative-control protections. A transfer, return, new transfer lock, agreement termination or material change to the listed prefixes requires notice to the secured party and satisfaction of the agreed approval rule. Ordinary routing and customer administration remain with the borrower.

The service provides status notices for unpaid fees, proposed deregistration, credential recovery, legal restraint and material dispute. Silence cannot allow collateral to disappear between reporting dates.

The agreement defines enforcement evidence. A payment-default certificate from the lender alone may be limited public evidence where default is disputed. The trigger might require borrower acknowledgement, expiry of a cure period, an independent agent's certificate, an arbitral or judicial order, or an insolvency officeholder's instruction, depending on the transaction. The registry verifies the specified form and identity; it does not decide the underlying loan case.

Upon a valid trigger, the lender receives a limited disposition role. It can maintain the registration, obtain buyer diligence and instruct a transfer to an eligible recipient. It does not automatically receive the right to route, mine customer data or operate the borrower's network.

The framework ends with authoritative completion. One transfer identifier, one current registration, signed supersession and preserved history prevent double sale or replay. Surviving disputes remain attached as notations or legally effective restraints.

This is control through procedure, not possession through force.

Portability is the missing backstop

An acknowledgement by the incumbent improves enforcement only while the incumbent remains capable and willing to perform. Portability supplies the backstop.

If the service becomes unavailable, enters a governance crisis, refuses to follow the accepted collateral-control agreement or delays beyond a defined period, a qualified receiving registration service should be able to verify the evidence and continue the case. The incumbent supplies records and objections within a short window. It cannot turn silence into permanent custody.

Portability does not erase valid law. A court order, insolvency stay, sanctions prohibition, proven authority defect or credential-compromise emergency can restrain the relevant action. The condition must be attributable, scoped and reviewable. A general statement that "policy review continues" should not freeze collateral indefinitely.

The receiving service also preserves uniqueness. The old record is marked superseded when the new state becomes authoritative. A transfer instruction is consumed once. Conflicting instructions are visible. Corrections create new events instead of rewriting history.

For lenders, this changes the risk model. Registry-service failure becomes a continuity event rather than the end of enforcement. For borrowers, it prevents an incumbent from using the lien process to demand unrelated concessions. For buyers, it provides a final registration event against which funds can be released. For customers, it supports staged operational transition.

NRS's role is especially constructive here. Its stated emphasis on operator control and reduced concentration can be translated into a financeable institutional right: the holder can select a qualified recorder, and an accepted security arrangement can survive that selection. NRS should define evidence portability and service obligations, not become the sole global collateral registry.

A monopoly notice system would reproduce the same control risk at another layer. The standard should allow multiple qualified services to verify one authoritative state under common rules.

Enforcement must preserve the network that supports value

The fastest legal sale can be the worst economic recovery if it breaks operations.

Leased addresses may be announced by customers around the world. Reverse DNS can support mail delivery and services. Route-origin authorisations affect acceptance. Abuse contacts and reputation remediation protect usability. Sudden changes can cause outages or filtering.

A collateral-control plan should distinguish disposition from cutover. The lender can select a buyer and complete registration while existing service continues for a defined transition. Customer contracts determine whether leases transfer, terminate or require consent. Collections can be redirected without changing routes on the same day. RPKI changes can be staged to avoid an invalid-origin interval. Reverse-DNS authority can move after data is replicated and tested.

Borrower essential-use blocks require special care. A foreclosure that removes addresses from a live access network can harm end users and reduce enterprise value. The security documents may permit a going-concern sale, substitute collateral, temporary lease-back or phased renumbering. These outcomes can produce better recovery than immediate prefix extraction.

Continuity does not give the borrower an indefinite veto. It imposes an execution standard on the secured party and registration service. Milestones, responsibilities, maximum periods and emergency contacts should be agreed. Customers should not be promised permanent use if their contracts do not provide it, but they should receive truthful notice and technically realistic transition.

The lender also needs assurance that preservation spending is permitted and recoverable. Registry fees, security operations, abuse handling and critical staff can be collateral-protection costs. A reserve or priority expense arrangement may keep the portfolio intact while sale proceeds are pending.

This is where registry expertise is useful. The service can attest operational state and coordinate safe administrative transitions. It should not decide which creditor pays or whether a customer contract was breached.

Disputes need notation, restraint and a clock

Collateral disputes vary in legal force. Treating every objection as a stop gives borrowers and junior claimants an inexpensive delay tactic. Treating no objection as a stop invites wrongful transfer.

An NRS-compatible framework should separate notation from restraint.

A notation records a claim: a borrower disputes default, another lender asserts priority, a former officer challenges authority, a customer claims contractual rights, or a registry identifies an evidence inconsistency. The notation names the claimant class, prefixes, date, asserted basis, forum and status. It travels with the registration but does not by itself prevent every action.

A restraint pauses a defined action. It requires stronger evidence: an applicable automatic stay, court order, authorised insolvency instruction, contractual standstill recognised in the control agreement, proven credential compromise or another narrowly specified condition. It states scope and expiry or review date.

Priority disputes usually belong to a court or agreed forum. The registry should preserve evidence and avoid choosing the winner. It can complete uncontested administrative acts if they do not prejudice the dispute, maintain services and require the parties to obtain a binding direction for disposition.

Every hold needs a clock. A temporary emergency hold can prevent an immediate fraudulent transfer, but it should expire unless supported by formal evidence. A lender's enforcement request should receive acknowledgement, a list of missing minimum elements and a decision deadline. Serial document requests should not restart time without cause.

These controls protect both sides. Borrowers can challenge wrongful acceleration. Lenders can prevent unsupported allegations from consuming collateral value. Registries can perform a bounded integrity role. Buyers can see whether a claim survives the sale.

The framework does not promise that difficult litigation will end quickly. It promises that institutional silence and undefined concern will not masquerade as law.

Cross-border portfolios expose the weakness of a single filing

A global address portfolio can involve a Delaware borrower, customers in many countries, a Dutch registration service, resources moving between RIR regions, contracts governed by several laws and an insolvency opened elsewhere. One financing statement cannot settle every question.

Choice-of-law rules determine where and how a security interest is perfected. Corporate changes can alter relevant jurisdiction. Local insolvency law can recognise stays, avoidance powers and officeholders differently. Customer receivables may have their own assignment rules. Data and sanctions duties can affect administration. RIR policies govern transfer eligibility and process within each service region.

The lender therefore needs a jurisdiction map, not a generic "global lien." It should identify the debtor for each right, perfection step, registration service, governing agreement, recognised enforcement agent and expected sale region. Legal opinions should address the rights actually granted rather than assume the address count is a universal asset class.

Portability can reduce institutional fragmentation but cannot abolish law. A receiving service should know which restraint applies, preserve conflicting orders and refuse to invent a global priority rule. Common evidence formats can make the legal questions visible: who granted the interest, when, over which prefixes, under which agreement, and what later event changed authority.

Inter-RIR transfers add coordination risk. A source region and recipient region may both have requirements. A lender's buyer may be acceptable in one and unready in another. Pre-enforcement planning should test destination eligibility and not wait until an auction winner asks whether delivery is possible.

This complexity supports conservative valuation. It does not make cross-border collateral worthless. Sophisticated finance routinely manages assets governed by multiple institutions. The distinctive weakness of IPv4 rights is the absence of a standard acknowledgement and portable control event at the registration layer.

NRS can supply that event while leaving applicable-law analysis to the parties and competent forums.

The FCC analogy shows why regulation and credit need not be enemies

Communications licences provide a useful but limited comparison. The FCC has historically resisted a private security interest that would let a lender obtain a licence automatically without prior regulatory approval. Its stated concern is that the agency must assess the qualifications of a transferee. At the same time, decisions have recognised that security interests in proceeds can be structured without bypassing the public-interest review.

IPv4 registrations are not FCC spectrum licences. RIRs are not government spectrum regulators, their legal authority differs, and no direct rule should be imported. The analogy is valuable for one reason: an institution can preserve eligibility review while allowing credit to attach to economic value and sale proceeds.

The choice is not between unrestricted foreclosure and no collateral. A lender can receive notice, cash control, conditional disposition rights and proceeds while the registration service checks identity, authority, uniqueness and recipient eligibility. The review should be bounded to those functions. It should not become a discretionary judgment about whether the lender deserves repayment.

This division also clarifies NRS's position. NRS need not declare IPv4 resources absolute property to make them financeable. It can recognise that holders possess valuable registration and use rights, that those rights can support agreed security, and that enforcement remains subject to stated legal and integrity conditions.

The comparison also warns against false automation. A smart contract, key transfer or registry API cannot lawfully decide every default and qualification. Technology should carry signed evidence and execute an authorised state transition. It should not conceal a legal judgment inside code.

A well-designed control framework therefore improves both credit and stewardship. The lender knows the path. The registry preserves its legitimate checks. The borrower knows the conditions. The public record remains unique.

The registry should attest, not adjudicate

Collateral value will not improve if registries are turned into private bankruptcy courts.

The registration service can attest that the borrower is recognised for specified prefixes, that a security notice was accepted on a stated date, that listed roles were verified, that a transfer lock or legal restraint exists, that fees are current, and that an enforcement submission matches the agreed evidence form.

It can reject a forged signature, mismatched prefix, ineligible recipient, replayed instruction or request contrary to a specific lawful restraint. It can preserve records and explain its decision.

It should not decide whether a financial covenant was calculated correctly unless the control agreement gives an independent agent that certification role. It should not rank competing liens under unfamiliar law. It should not decide whether a bankruptcy stay applies without reliable legal evidence. It should not value the portfolio or choose the sale method. It should not infer fraud from a low price.

Where the evidence conflicts, the service places a scoped hold and directs parties to the agreed forum. It maintains continuity in the meantime. Once a competent decision arrives, it implements the registration consequence and records the basis.

This boundary limits liability and bias. It also makes portability feasible. A receiving service can reproduce factual checks from exported evidence. It does not need to inherit the incumbent's private view of the loan.

Auditability matters. Every notice, objection, expiry, role change and final transfer should carry an attributable timestamp. Sensitive documents can remain confidential while their verification hashes and evidence classes are preserved. Later reviewers should be able to distinguish an action based on court order from one based on contractual certification.

NRS should publish performance measures: acknowledgement times, completed enforcement transfers, holds by reason, expired holds, reversals, continuity incidents and service-provider failures. Counts need context and should not expose private borrowers. Until such data exists, no claim about typical enforcement speed or recovery success is justified.

Lenders should price the right they can enforce, not the address count they can see

A strong underwriting memorandum ends with a recovery path that can be rehearsed.

It identifies the recognised holder and exact prefixes. It confirms the holder's agreement and transfer rights. It classifies the pledged interests under applicable law and completes perfection. It obtains registry acknowledgement or documents why none is available. It separates receivables, leases, proceeds, equity and registration rights. It tests customer-notice and cash-control mechanics.

It then walks through default. Who certifies? What cure period applies? Who preserves registry service? Does an automatic stay intervene? Can the lender prevent a transfer? Who selects a buyer? What recipient eligibility must be met? Which registry updates complete delivery? How do RPKI and reverse DNS move? How are customers protected? Where do proceeds flow? What happens if the incumbent does not act?

Every unanswered step becomes a valuation adjustment, covenant or condition precedent. The answer should not be "the borrower will cooperate." Cooperation can be a base-case assumption, not the sole recovery mechanism.

The same discipline protects borrowers from overreaching. A lender that receives only a limited disposition role cannot interfere with routing during ordinary performance. A registry notice makes secret duplicate pledges harder. Cure and challenge procedures reduce opportunistic acceleration. Commercially reasonable sale duties remain. Surplus proceeds return according to law.

The IPv4 address count remains relevant. It is not the collateral value. Value is the expected benefit after legal priority, registry recognition, customer claims, sale time, operational continuity and transaction cost.

No selected source provides the denominator needed to say what percentage of address portfolios are financeable, pledged, in default or successfully recovered. Cogent is a large public example, not an industry census. IPv4.Global's product announcement is evidence of an offering, not evidence of loan performance. RIR transfer lists record approved transfers, not secured-credit outcomes.

Precision about this absence is part of credible market development.

A portable control right would move risk to the party best able to manage it

Today, the lender often bears registry risk without being able to select or discipline the registry. The borrower selected or inherited the service. The registry controls the decisive update. The lender receives the loss if enforcement stalls.

Portability changes the allocation. A service that accepts a collateral-control arrangement becomes responsible for timely, evidence-based performance. If it fails, the case and registration can move to another qualified provider. The holder and secured party choose the service subject to common integrity standards. The institution controlling the process therefore bears reputational and contractual consequences for poor service.

This does not guarantee recovery. Market prices can fall. Customers can default. Courts can stay sale. A borrower may never have held the rights it claimed. A lender may fail to perfect. A buyer may be ineligible. Portability addresses one risk: dependence on an incumbent that is not accountable to the financing outcome.

The reform can increase collateral value without encouraging reckless leverage. Better enforceability should be paired with exact schedules, conservative advance rates, continuity protections, dispute procedures and transparent limits. Easy seizure without diligence would create fraud and network harm. Verifiable control makes diligence more important, not less.

NRS is institutionally suited to advocate this division because its model starts from the holder's registration rights rather than a registry corporation's permanent custody. Its strongest contribution would be a neutral standard for acknowledgement, role separation, evidence export and final transfer across qualified providers.

It should not promise that registration rights are identical in every jurisdiction. It should promise that the administrative facts do not disappear when the borrower, lender or service provider changes.

That promise is modest compared with declaring a new global property regime. It is also more useful to a credit committee deciding whether collateral can actually be realised.

The market needs an enforcement record before it needs a grand valuation theory

IPv4-backed credit has moved beyond speculation. Public companies have recognised large address assets. A major operator has placed hundreds of millions of dollars of secured address-revenue notes. A marketplace has advertised lending against address holdings. Transfers and leases are ordinary enough to support specialist institutions.

Yet the evidence remains concentrated. Public sources do not show a broad history of defaults, contested foreclosures, registry response times, forced-sale discounts or customer continuity outcomes. The market can describe origination more confidently than enforcement.

That imbalance should shape the next phase. NRS and participating registration services should collect anonymised performance evidence from opt-in collateral arrangements. How many notices remain current? How often do borrowers cure? Which events trigger control? How long do transfers take? Which holds arise from authority, law, dispute, service failure or recipient eligibility? Do operational incidents occur? How do sale outcomes compare with orderly expectations?

The data should preserve denominators. Ten delayed cases mean little without the number and complexity of all cases. A recovery ratio needs a consistent definition of exposure, collateral scope, costs and timing. Voluntary pilot portfolios should not be presented as representative of all holders.

Until that record develops, lenders should treat structural protections as substitutes for missing history. Special-purpose ownership, cash control, reserves, reporting, triggers, precise notices and portability can contain risk. They cannot produce certainty from absent observations.

The governance opportunity is therefore practical. Build the control path, test it under simulated borrower non-cooperation and service failure, publish bounded performance, and let credit terms respond to evidence.

The decisive question is who can cause the recognised change

IPv4 collateral debates often become arguments about whether addresses are property. That question matters in particular legal contexts, but it can obscure the financing decision.

The lender needs a narrower answer. After default and any required legal process, who can cause the authoritative registration to change? What evidence must that actor present? Which institution must recognise it? What happens if that institution refuses or fails? How are customers and routing controls preserved while the sale completes?

Cogent answered much of the question through private architecture: a bankruptcy-remote issuer, contributed assets, customer cash flows, trustee control, reserves, triggers and directed-sale provisions. That architecture demonstrates commercial possibility. Its complexity is also an indictment of the missing public right.

Article 9 sharpens the point. Attachment and perfection can protect a lender against the borrower and rival creditors without compelling a third party to recognise or perform. RIR rules sharpen it again. Transfers complete through registry updates based on recognised authority and policy compliance, not through the mere existence of a financing statement.

The lender's control problem is the gap between those systems.

NRS can close part of it without pretending to resolve all property or insolvency law. A holder can opt into a precise security notice. A registration service can acknowledge conditional roles. A valid enforcement instruction can receive bounded review, a clock and an authoritative completion event. Disputes can be noted or restrained according to evidence. Operational services can transition safely. If the incumbent cannot perform, the registration and evidence can move.

That design would not make every address portfolio good collateral. It would make bad assumptions easier to see and valid rights easier to realise.

Credit follows enforceability. Where enforceability depends on registry discretion, the registry captures power and the lender charges for uncertainty.

Where registration is portable, the recordkeeper protects integrity without owning the outcome.

The loan then rests on a right the lender can describe before default and execute after it - subject to law, visible to all relevant institutions and no longer trapped inside an incumbent's grace.

Sources