diff --git a/.github/ISSUE_TEMPLATE/lambda-prize-claim.yml b/.github/ISSUE_TEMPLATE/lambda-prize-claim.yml index e5ecf8e..bc05bbb 100644 --- a/.github/ISSUE_TEMPLATE/lambda-prize-claim.yml +++ b/.github/ISSUE_TEMPLATE/lambda-prize-claim.yml @@ -18,6 +18,23 @@ body: > [!IMPORTANT] > The prize amount will be paid in **USDT on Ethereum** to the **Ethereum wallet address** you enter below. + - type: dropdown + id: release + attributes: + label: Which release is this? + description: > + Prizes are split 50% delivery / 50% adoption. Most claims are the full + prize, released once adoption is verified. Choose "Delivery only" if you + were told the delivery half is being released early because the consumer was + unresponsive, and "Adoption" if you are now claiming the remaining adoption + half. + options: + - Full prize (delivery + adoption) + - Delivery only (consumer-unresponsive release) + - Adoption (remaining half after an earlier delivery-only release) + validations: + required: true + - type: input id: typeform_response_id attributes: diff --git a/prizes/LP-0000.md b/prizes/LP-0000.md index 5604c7d..8301a93 100644 --- a/prizes/LP-0000.md +++ b/prizes/LP-0000.md @@ -22,9 +22,28 @@ dependencies: [] **`Status`**: - Draft: Not yet ready - Open: Ready for application -- Completed: Submission accepted, prize completed +- Up for fork: Original builder disengaged; another builder may take the existing work forward toward adoption (set at Logos discretion) +- Completed: Submission accepted and adopted, prize completed -**`Logos Circle: `** +## Consumer + +> A prize is not published (Draft → Open) until a named consumer is identified: the +> party that will adopt the deliverable, and the accountable person who gives the +> adoption green light. Adoption by this consumer is the win condition (see Success +> Criteria → Adoption). + +- **Type:** Circle / Sample-app integration (Eco Dev Eng) / Partner +- **Consumer:** +- **Adoption green-light owner:** +- **Contact channel:** +- **Redundancy / fallback:** + +> Out of scope as a consumer: a RFP that needs this LP; a LP that depends on a PR +> being merged into Logos (a PR against `scaffold` / `spel` is fine); another LP +> consuming this one. The consumer must already exist and be independently useful, +> not be built in order to consume this prize. ## Overview @@ -58,10 +77,15 @@ dependencies: [] > - A README documents end-to-end usage: deployment steps, program addresses, and step-by-step instructions for interacting with the program via CLI and Basecamp app. > - A reproducible end-to-end demo script is provided and works against a real local sequencer with `RISC0_DEV_MODE=0`. > - A recorded video demo of the end-to-end flow is included in the submission; the recording must show terminal output (including proof generation) to confirm `RISC0_DEV_MODE=0` was active. +> +> **Adoption** — the win condition. State the concrete, verifiable adoption the named +> consumer (see Consumer section) must demonstrate. Pre-mainnet this is binary: the +> consumer has integrated the deliverable and runs it on testnet. (Quantitative +> thresholds such as users / TVL / usage apply to a later mainnet adoption stage.) -- [ ] Criterion 1 -- [ ] Criterion 2 -- [ ] Criterion 3 +- [ ] Functional criterion 1 +- [ ] Functional criterion 2 +- [ ] **Adoption:** has integrated this and runs it on testnet ## Scope @@ -77,7 +101,13 @@ dependencies: [] - **Total Prize:** $X - **Effort:** XS / S / M / L / XL / Variable +- **Split:** 50% delivery (Logos-owned acceptance: criteria met, license, security, reproducible demo) / 50% adoption (the named consumer uses it, verified by Logos) > Leave prize pool blank — this will be determined by the Logos team. Single winner by default. Detail here if otherwise. +> +> The default is a single payout released once Logos verifies adoption. The split +> becomes two separate releases only if the consumer is unresponsive for two weeks: +> the delivery half is then released so an engaged builder is not blocked by an +> absent consumer, and the adoption half stays open until adoption happens. ## Eligibility @@ -97,6 +127,12 @@ dependencies: [] > The demo must make it easy for evaluators to verify that the implementation meets the stated criteria. > > Submissions must include a FURPS self-assessment as part of the solution (see [solution template](../solutions/LP-0000.md)). +> +> **Operational security.** The named consumer will run this code, potentially with +> real keys and value. Beyond functional correctness, the submission must include +> what an adopter needs to run it safely: key handling, any required sandboxing, +> dependency/supply-chain notes, and deployment guidance. The Logos security review +> covers this as part of acceptance. ## Evaluation Process diff --git a/solutions/LP-0000.md b/solutions/LP-0000.md index c9d8411..0064990 100644 --- a/solutions/LP-0000.md +++ b/solutions/LP-0000.md @@ -26,6 +26,18 @@ - [ ] Criterion 2: _explanation_ - [ ] Criterion 3: _explanation_ +## Adoption Evidence + +> Adoption by the prize's named consumer is the win condition. State who the consumer +> is and the current status of their integration, and link the evidence. Logos +> verifies this before releasing the adoption half of the prize. + +- **Named consumer:** +- **Contact channel:** +- **Integration status:** +- **Evidence:** + ## FURPS Self-Assessment > Evaluate your delivery against each of the following dimensions.