[danisharora099]

Drafts LP-0027, an operator kit for the RFP-003 BTC↔LEZ atomic-swap Maker, judged by three independent operators running it on the official LEZ testnet for 30 days.

Tracks logos-co/ecosystem#176.

Number choice

LP-0027. Master has 0000–0005, 0008–0018, 0021–0023; 0019, 0020 and 0024–0026 are held by open PRs and branches (#75, #135, #138, #141). Note that #90 (June) also uses LP-0018/0019, which now clash with master's LP-0018; that PR needs renumbering regardless of this one.

Shape

• Wraps an unmodified RFP-003 Maker release (pinned tag, commit, digest). Forking or patching the Node, CLIs, SDKs or desks makes a submission ineligible, so the prize does not pay twice for what RFP-003 M3/M5 fund.
• Funds only the layer that does not exist: one-command bring-up on an operator-owned host, a pricing and exposure policy over the owner API, health and alerts, backup and restore with a drill, an operator runbook.
• Adoption is measured from outside: an offer probe run by Logos, both-chain swap records, an independence test per operator, non-author issues fixed. Follows the criteria catalogue in Define Adoption criteria #137.
• Multiple winners stated explicitly per Terms 8.1: one kit award plus up to three operator awards. Operators claim with their own short solution PR, so they are Participants bound by the Terms (CC exclusion, sanctions, licensing). Logos takes no swaps and operates nothing (Terms 13).
• Opens only once Logos has pinned an M3-accepted release and the run guide is current. Draft until then, per Franck's steer to have prizes legal-ready and published before feasible, with the gate stated.

Status: first draft, known gaps (25 Sep)

Parked for an internal pass before review. A self-review found these, to be fixed before this leaves draft:

• Award mechanism. Four claimants via separate solution PRs do not fit the one-file solutions/ workflow or the payment flow. Likely change: single winner (the kit); operator windows are its adoption evidence; any operator pay moves to LP-0028 with a stated per-award amount.
• Logos-supplied services. The draft has Logos running an offer probe, keeping an operator register with host and billing details, brokering introductions and inspecting hosts. To be replaced with evaluation from public chain data, offers on Logos Delivery, and the operator's own exports.
• Taker counts are unrealistic on a faucet testnet; will be halved and other registered operators allowed as counterparties.
• "Unmodified release" needs defining as the Node, actor, CLI and SDK binaries only; the kit must be allowed to replace Compose, units, proxies and docs. Several items should read "integrate existing X" (release pinning, evidence export, repin upgrade, health calls) rather than "build".
• Form: follow LP-0022's draft form, add the "Additional Design Choices Left to the Submitter" section, move owner-facing text to this PR, cut length and density, restore the legal Note block byte-for-byte from LP-0023.
• Gate: the earlier plan opened this only after the RFP-003 M7 security review; this draft opens after the BTC milestone. That is an open decision, not settled.

Open questions for review

1. Amount and effort. Left blank; this is Large work (software plus recruiting three operators). The budget planner currently carries it as Small.
2. Who at Logos owns the offer probe and operator register. Written as Ecosystem Development.
3. Whether legal is comfortable with operator awards claimed by solution PR under Terms 8.1, and with Logos publishing probe reports.

🤖 Generated with Claude Code

[github-actions]

✅ Validation passed

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

---

Automated check. See solution template and TERMS.

[fryorcraken]

I am not sure we are going in the right direction ehre.

What I would expect from this prize is a logos module + CLI (and optional UI) to enable added features to your maker node.

The LP node module would communicate with the RFP-003 maker module to:

• feed dynamic prizes
• manage funds, and move to cold storage, or from other wallet
• display alerts
• stop swaps under specific conditions
  etc

The Exact features can be left to the challenger. they need to build something useful for other makers.

[fryorcraken]

Suggested change

	# LP-0027: Atomic-Swap Maker Operator Kit — three independent testnet makers [DRAFT]
	# LP-0027: Atomic-Swap Advanced Maker Setup

criteria can remain in the criteria section

[fryorcraken]

The RFP-003 output should already enable anyone node operator to run a maker without writing software.

This is about enabling more advacned features such as dynamic pricing, inventory and liquidity management, cold storage move, alerts, etc.

[fryorcraken]

its owner JSON-RPC API,

What json rpc api?

What does not exist is everything an operator needs around that: a pinned, reproducible bring-up of the whole stack on a host they control;

and a runbook written for an operator rather than a developer.

a backup and restore path for the keys and state that cannot be lost;

All the above is expected to be delivered by RFP-003.

---

a policy layer that keeps an offer live and sensibly priced without a human watching; probes and alerts that say whether the maker is actually serving;

Yes

[fryorcraken]

developer who can read the Compose files.

This is expected to be removed.