When the registrar stalls: qualifying an asset swap that must never commit twice

A permutation trade on Domain Permute is a distributed transaction with no shared clock. On one side a car title, a land deed or a property interest sits in escrow, and on the other the domain moves through a registrar. At idle the registrar answers fast and the reservation on the name never comes close to expiring. Under load the order of events changes, that reordering is where the real defect lives, and the qualification plan has to manufacture it on purpose.

The defect that only exists when things are slow

Every offer takes a reservation lease on the domain, and the reference configuration sets it at 900 seconds. A burst of offers on a hot name slows registrar acknowledgments, so a transfer can still be pending when the lease expires. The orchestrator then sees a free name, accepts a second founder's offer and opens a second escrow. Two counter-assets are now locked against one domain that can only settle once. Nothing crashes and no alert fires. The functional suite stays green because each step, taken alone, behaved correctly.

The test that forces the race

Point a load generator at a single premium name and keep concurrent offers arriving faster than the registrar sandbox is allowed to answer. Between the orchestrator and the registrar, insert a fault proxy that stretches acknowledgment latency past the lease and silently drops a share of the callbacks. Midway through the run, kill the orchestrator instance that owns the oldest open saga and let a standby resume from the persisted log. Throughput is not the pass criterion. Afterwards a reconciler compares the registry's sponsoring record, the escrow ledger and the saga log, and the test fails if any name has more than one committed swap or if any asset left escrow without a matching registry state. Run it again with the registrar slow but alive and with the registrar completely dark, because each of those triggers a different compensation path.

What holds when one part fails

Resilience here rests on one discipline: an expiring timer may cancel an intent, but only a confirmation read back from the registry may release an asset from escrow.

The rule to write into the plan

Size the lease from measurement, not from the configuration file. Take the slowest acknowledgment tail observed at qualified load and add one full retry. If that total doesn't fit inside the lease, either the lease grows or the system stops accepting offers on that name until the pending transfer resolves. Our measurements put that tail at a few minutes during registrar peak hours, an estimate that shifts with each registrar and each extension. Tie the evidence to the inter-registrar transfer rules that govern locks and authorization codes, such as ICANN's transfer policy, because those rules decide when a name can legally move and so when compensation is still possible. What remains is a commercial trade-off: a longer lease protects the invariant, but it keeps a sought-after name off the market while a slow registrar thinks, and that cost falls on the founder who made the second offer.

Why not simply make the reservation lease very long?

A lease that never expires turns an abandoned offer into a frozen domain, and on a marketplace of scarce names that is a failure of its own. The lease should expire, but its expiry may only cancel the intent. It must never settle anything.

Back to Domain Permute · Domains

← Back to Domain Permute
Engineering & Architecture Brief

When the registrar stalls: qualifying an asset swap that must never commit twice

A permutation trade on Domain Permute is a distributed transaction with no shared clock. On one side a car title, a land deed or a property interest sits in escrow, and on the other the domain moves through a registrar. At idle the registrar answers fast and the reservation on the name never comes close to expiring. Under load the order of events changes, that reordering is where the real defect lives, and the qualification plan has to manufacture it on purpose.

The defect that only exists when things are slow

Every offer takes a reservation lease on the domain, and the reference configuration sets it at 900 seconds. A burst of offers on a hot name slows registrar acknowledgments, so a transfer can still be pending when the lease expires. The orchestrator then sees a free name, accepts a second founder's offer and opens a second escrow. Two counter-assets are now locked against one domain that can only settle once. Nothing crashes and no alert fires. The functional suite stays green because each step, taken alone, behaved correctly.

The test that forces the race

Point a load generator at a single premium name and keep concurrent offers arriving faster than the registrar sandbox is allowed to answer. Between the orchestrator and the registrar, insert a fault proxy that stretches acknowledgment latency past the lease and silently drops a share of the callbacks. Midway through the run, kill the orchestrator instance that owns the oldest open saga and let a standby resume from the persisted log. Throughput is not the pass criterion. Afterwards a reconciler compares the registry's sponsoring record, the escrow ledger and the saga log, and the test fails if any name has more than one committed swap or if any asset left escrow without a matching registry state. Run it again with the registrar slow but alive and with the registrar completely dark, because each of those triggers a different compensation path.

What holds when one part fails

Resilience here rests on one discipline: an expiring timer may cancel an intent, but only a confirmation read back from the registry may release an asset from escrow.

The rule to write into the plan

Size the lease from measurement, not from the configuration file. Take the slowest acknowledgment tail observed at qualified load and add one full retry. If that total doesn't fit inside the lease, either the lease grows or the system stops accepting offers on that name until the pending transfer resolves. Our measurements put that tail at a few minutes during registrar peak hours, an estimate that shifts with each registrar and each extension. Tie the evidence to the inter-registrar transfer rules that govern locks and authorization codes, such as ICANN's transfer policy, because those rules decide when a name can legally move and so when compensation is still possible. What remains is a commercial trade-off: a longer lease protects the invariant, but it keeps a sought-after name off the market while a slow registrar thinks, and that cost falls on the founder who made the second offer.

Technical FAQ: Why not simply make the reservation lease very long?

A lease that never expires turns an abandoned offer into a frozen domain, and on a marketplace of scarce names that is a failure of its own. The lease should expire, but its expiry may only cancel the intent. It must never settle anything.