LP-0028: Sustained Atomic-Swap Maker Operation on the Logos testnet

[danisharora099]

Drafts LP-0028, paying an independent operator for keeping a BTC↔LEZ atomic-swap maker live on the official LEZ testnet for 90 days at a stated availability and price quality, serving at least 15 independent takers.

Tracks logos-co/ecosystem#177.

Number choice

LP-0028, next after LP-0027 (#165, opened alongside). See that PR for the numbering survey.

Why testnet, not mainnet

ecosystem#177 was written as a mainnet liquidity prize with exchange price feeds. Logos mainnet is not live, RFP-003 delivers and tests on test networks only, no exchange feed is in its scope, and the M7 security review has not run. The budget planner already retitled this item to testnet on 15 September. The mainnet version is named in "Potential for Subsequent λ Prizes" and gated on mainnet plus M7.

Shape

• Operation, not code: pinned unmodified RFP-003 release, operator-held keys, both directions, offers within a band around a fixed reference ratio written into the prize at opening (evaluation number, not a price feed).
• Adoption: 90 consecutive days from registration, 95 % probe availability, 50 settled swaps from 15 independent takers spread across the window, zero unrecovered incidents, operations log with linked issues.
• Multiple winners stated per Terms 8.1: up to three operator awards, FCFS by registration. No program-funded inventory; testnet faucets only.
• Eligibility calls out Terms 12(d): operators act as principals and carry any licensing or regulatory obligation of running such a service.
• Depends on LP-0027 having a winner; does not open while LP-0027 windows run.

Status: first draft, known gaps (25 Sep)

Parked for an internal pass before review. The main question is whether this is a λPrize at all as written: it pays for operating a service over time with no code artefact, which sits badly with Terms 5.3 (public source and deployable artefact are mandatory), Terms 3 (no contract for services) and Terms 13 (Logos does not operate or facilitate exchange). Three options, to settle with Franck before polishing:

1. Keep as a λPrize with a real artefact: the operator's published configuration, policy and runbook amendments are the deliverable; the 90 days are its adoption window.
2. Move to the RFP programme, whose contract terms allow paying for services.
3. Fold into LP-0027 as a "still running after 90 days" retention tranche.

Other known gaps: the Logos-declared reference ratio should go (replace with "offers match the operator's published pricing policy"); taker and swap counts need halving and other registered operators allowed as takers; the hard dependency on an LP-0027 winner pushes this to 2027 and should become a soft one; #177's "two pairs" is dropped without saying so; the flywheels plan still lists a mainnet liquidity prize as a launch-day dependency, which this testnet prize does not close.

Open questions for review

1. Amount. Left blank; planner carries $3,000, size Small.
2. Whether legal is comfortable paying for operation of a service over time under the current Terms, and with the Terms 12(d) wording in Eligibility.
3. Reference ratio and band: to be filled at opening. Who publishes it.

🤖 Generated with Claude Code

[github-actions]

✅ Validation passed

A reviewer will assess against the prize criteria.
ℹ️ Prize proposal for LP-0028.

---

Automated check. See solution template and TERMS.