Repository navigation
LP-0028: Sustained Atomic-Swap Maker Operation on the Logos testnet - #166
Draft
danisharora099 wants to merge 1 commit into
Draft
danisharora099 wants to merge 1 commit into
danisharora099 wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
✅ Validation passedA reviewer will assess against the prize criteria. Automated check. See solution template and TERMS. |
fryorcraken
requested changes
Oct 16, 2026
|
|
||
| ## Overview | ||
|
|
||
| This prize pays an independent operator for **keeping a BTC↔LEZ atomic-swap maker live on the official Logos LEZ testnet for 90 consecutive days**, serving real, unaffiliated takers with executable offers priced against a published reference. Where LP-0027 proves that strangers can stand a maker up, this prize proves that one can be run as a service: continuously, at a stated quality, for people who are not the operator. |
Collaborator
There was a problem hiding this comment.
Where LP-0027 proves that strangers can stand a maker up
I don't understand this sentence.
|
|
||
| This prize pays an independent operator for **keeping a BTC↔LEZ atomic-swap maker live on the official Logos LEZ testnet for 90 consecutive days**, serving real, unaffiliated takers with executable offers priced against a published reference. Where LP-0027 proves that strangers can stand a maker up, this prize proves that one can be run as a service: continuously, at a stated quality, for people who are not the operator. | ||
|
|
||
| It is a testnet prize by design. Logos mainnet is not live, RFP-003 delivers and tests on test networks only, and the atomic-swap protocol has not had its independent review. When mainnet and the M7 review exist, a separate mainnet liquidity prize will replace this one with value-at-risk criteria. |
Collaborator
There was a problem hiding this comment.
Suggested change
| It is a testnet prize by design. Logos mainnet is not live, RFP-003 delivers and tests on test networks only, and the atomic-swap protocol has not had its independent review. When mainnet and the M7 review exist, a separate mainnet liquidity prize will replace this one with value-at-risk criteria. | |
| It is a testnet prize by design. Logos mainnet is not live, RFP-003 delivers and tests on test networks only, and the atomic-swap protocol has not had its independent review. When mainnet and the M7 review exist, a separate mainnet liquidity prize may replace this one with value-at-risk criteria. |
|
|
||
| A swap network needs makers who stay. Short observation windows show that a kit works; they do not show that anyone will keep inventory funded, offers fresh and a host healthy through three months of testnet resets, chain stalls and quiet weeks with no takers. That operational habit is what a later mainnet market needs, and it is cheaper to learn on a faucet testnet than with real funds. | ||
|
|
||
| Paying for operation rather than code is unusual for a λPrize, so the criteria below are written to be checked from outside: an external offer probe, both-chain swap records, and takers whose independence can be inspected. Nothing depends on the operator's own reporting. |
Collaborator
There was a problem hiding this comment.
Suggested change
| Paying for operation rather than code is unusual for a λPrize, so the criteria below are written to be checked from outside: an external offer probe, both-chain swap records, and takers whose independence can be inspected. Nothing depends on the operator's own reporting. |
just remove. We need to stop seeing LPs as a code only program. it was never meant to be.
|
|
||
| ## Motivation | ||
|
|
||
| A swap network needs makers who stay. Short observation windows show that a kit works; they do not show that anyone will keep inventory funded, offers fresh and a host healthy through three months of testnet resets, chain stalls and quiet weeks with no takers. That operational habit is what a later mainnet market needs, and it is cheaper to learn on a faucet testnet than with real funds. |
Collaborator
There was a problem hiding this comment.
The motivation is several folds. RFP-003 is a key component to get onboard users and liquidity in the Logos ecosystem, hence, we want to:
- properly dogfood RFP-003
- ensure that other apps that may integrate RFP-003 have the opportunity to do so with testnet data, and can dogfood themselves; whether they are covered by aLP or not.
|
|
||
| ### Functionality | ||
|
|
||
| - [ ] The maker runs a **pinned, unmodified RFP-003 release** (tag, commit, digest recorded at registration), on a host the operator controls, with keys the operator holds. Running the LP-0027 winning kit is expected but not required; an operator using their own tooling must meet the same criteria. |
Collaborator
There was a problem hiding this comment.
why unmodified?
Suggested change
| - [ ] The maker runs a **pinned, unmodified RFP-003 release** (tag, commit, digest recorded at registration), on a host the operator controls, with keys the operator holds. Running the LP-0027 winning kit is expected but not required; an operator using their own tooling must meet the same criteria. | |
| - [ ] The maker runs a RFP-003 release, on a host the operator controls, with keys the operator holds. Software with criteria similar to LP-0027 may be used. |
Collaborator
There was a problem hiding this comment.
Follow-up: no need for unmodified, but the release version and any modifications should be disclosed, the point is to dogfood RFP-003.
|
|
||
| ## Eligibility | ||
|
|
||
| Open to any individual or organisation that is not a Logos CC (including the RFP-003 contractor and its sub-contractors), not the LP-0027 winning team, and not affiliated with either. Participants operate as principals in their own name and are solely responsible for any legal, licensing or regulatory obligation that applies to them for running such a service, even on a test network (see [Terms & Conditions](../TERMS.md)). |
Collaborator
There was a problem hiding this comment.
not the LP-0027 winning team
Why?
| ## Submission Requirements | ||
|
|
||
| - Registration record (operator, Delivery identity, host, release pin, start date) filed with Logos before the window. | ||
| - The Logos probe report for availability and price quality. |
Collaborator
There was a problem hiding this comment.
How do they submit that?
|
|
||
| ## Evaluation Process | ||
|
|
||
| Registrations are accepted first-come-first-served once the prize is open. A registration cannot qualify before its 90-day window has elapsed. Logos runs the external offer probe for every registered operator; Logos does not take swaps, hold funds, or operate any maker. Evaluators will contact takers directly and will inspect taker accounts, hosts and funding flows for independence. |
Collaborator
There was a problem hiding this comment.
Logos does not take swaps, hold funds, or operate any maker.
Sounds irrelevant
|
|
||
| The following policies apply to all prizes (see [evaluation policies](../README.md#evaluation-policies)): | ||
|
|
||
| - **Submissions:** each operator is allowed one registration at a time and a maximum of **3 submissions** for this prize. |
Collaborator
There was a problem hiding this comment.
I don't think this apply; do note that they need to submit a "start" and "end" event.
Comment on lines
+120
to
+122
| ## Potential for Subsequent λ Prizes | ||
|
|
||
| A **mainnet liquidity provision** prize is planned once Logos mainnet is live and the RFP-003 M7 review and remediation are complete. It will replace testnet counts with value-at-risk criteria: inventory held continuously, real taker volume, and exchange-referenced price quality, across at least two pairs. |
Collaborator
There was a problem hiding this comment.
Suggested change
| ## Potential for Subsequent λ Prizes | |
| A **mainnet liquidity provision** prize is planned once Logos mainnet is live and the RFP-003 M7 review and remediation are complete. It will replace testnet counts with value-at-risk criteria: inventory held continuously, real taker volume, and exchange-referenced price quality, across at least two pairs. |
remove
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
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:
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
🤖 Generated with Claude Code