In practiceServe networks today
LARUS LIMITED
LARUS keeps today’s networks running with IPv4 address services. Follow the practical problem back to Lu Heng’s larger question: who should control the records that networks depend on?
From the Notes
“LARUS exists as the continuity layer. … It is the bridge for operators who cannot wait for the final architecture before they need addresses, routing, customers, renewability, and stability.”
The problem starts in the daily life of a network
When a network grows, its operators need addresses that customers, equipment, and services can use. Getting and managing those addresses is not an abstract policy question. It is part of keeping a real network reachable and its existing work intact.
The immediate answer: make the address usable
Lu Heng founded LARUS in 2016. The company connects address holders with telecoms companies and Internet service providers, offering flexible, on-demand IPv4 address services. This is the practical answer for an operator that needs usable addresses now.
Moving an address does not change who keeps the record
A transaction can keep a service running. It does not, by itself, change who maintains the underlying number record, what authority that institution claims, or whether an operator can leave without losing continuity. That gap is where the experience of running a business meets the argument in the Notes.
The larger proposal: records should serve the network
Lu Heng’s position is that the people who build networks, invest in them, and bear their losses need reliable records and a real choice among registration services. A record keeper should coordinate uniqueness; it should not become the authority that governs everyone who depends on the record. LARUS works inside today’s system while the Notes argue for a system that can be exited, carried, and replaced.
Why the question cannot wait
Networks cannot pause while the deeper system catches up. Operators need continuity now, and they need meaningful alternatives before one registration path becomes impossible to leave. The practical service and the structural question therefore belong in the same story: solve today’s operating problem while making tomorrow’s dependence easier to change.
Read the argument, then see the practice
Note 45 examines how the story of IPv4 scarcity is built and what the address market reveals about the role of registries. Note 66 explains why brokerage cannot, on its own, remove registry risk. Read them to follow the reasoning behind this work; if you need current IPv4 address services, continue to LARUS.