Status:
- Draft: Not yet ready
- Open: Ready for application
- Completed: Submission accepted, prize completed
Logos Circle: <City/Chapter or N/A>
One or two paragraphs describing what this prize is for and why it matters to the Logos ecosystem.
Why does this need to exist? What gap does it fill? Why is a competitive prize the right mechanism rather than an RFP?
Concrete, measurable outcomes that determine a winner. Be specific — TVL thresholds, performance benchmarks, adoption metrics, etc. Each item should be a testable statement.
Consider including criteria from each of the following areas (remove any that don't apply):
Functionality — what the system must do. Note: applications must not depend on any centralised server or service. Use the Logos stack for communication: Logos Delivery (storage/data availability) for publishing data, and Logos Chat (messaging) for peer-to-peer coordination.
Usability — standard requirements for Logos apps (adapt as needed):
- Provide a module/SDK that can be used to build Logos modules for interacting with the program.
- Provide a Logos Basecamp app GUI with local build instructions, downloadable assets, and loadable in Logos app (Basecamp).
- Provide an IDL for the LEZ program, using the SPEL framework.
Reliability — fault tolerance, consistency, graceful degradation, error handling.
Performance — throughput, latency, resource usage. Document compute unit usage of each operation (LEZ's per-transaction compute budget may change during testnet).
Supportability — standard requirements (adapt as needed):
- The program is deployed and tested on LEZ devnet/testnet.
- Platform support (recommended): support all platforms Logos Basecamp supports, i.e. Linux and macOS, and from testnet 0.4 also Windows and Android. This is not a separate build gate; macOS coverage is checked through the Adoption criteria below.
- Logos Basecamp modules are built with
logos-module-builder(mkLogosModule).- Logos Basecamp modules are published to a module catalog: a fork of
logos-modules-release-base, publishing releases vialogos-modules-release-action. The catalog'slogos-repo.jsonURL must be included in the submission so evaluators can install the module through the package-manager UI /lgpd.- End-to-end integration tests run against a LEZ sequencer (standalone mode) and are included in CI.
- CI must be green on the default branch.
- 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=0was active.Adoption — traction attributable to the submission (see the Adoption section of recent adoption-first prizes, e.g. LP-0023, for the standard preamble and dimensions). Adapt thresholds per prize. Standard requirement:
- Adoption evidence (third-party apps, users, testimonials) must include macOS users or installs as well as Linux, so that macOS support is demonstrated by real use rather than by a separate build requirement.
- Criterion 1
- Criterion 2
- Criterion 3
What the prize covers.
What the prize explicitly does not cover.
- Total Prize: $X
- Effort: XS / S / M / L / XL / Variable
Leave prize pool blank — this will be determined by the Logos team. Single winner by default. Detail here if otherwise.
Who can participate? Any restrictions?
Submissions must be original work. Teams must hold the rights to all submitted code and agree to license it under MIT and Apache-2.0.
What must be delivered? Repos, documentation, deployments, demos, etc.
Standard items (adapt as needed):
- Logos Basecamp modules published to a module catalog (see Supportability): include the catalog's
logos-repo.jsonURL.- Evidence for each adoption criterion.
A narrated video walkthrough demo is always required (see demo requirements). The demo should specifically showcase and discuss:
- End-to-end usage of the solution, from deployment (or setup) through interacting with the program/app/module in all major user scenarios.
- Successful execution of all core functionality, with relevant terminal and/or UI output visible (e.g., proof generation, state changes, error handling).
- Any required integration with the Logos stack (e.g., use of Logos Delivery, Logos Chat, or other modules).
- Any features addressing explicit evaluation or success criteria (e.g., handling of error cases, reliability under failure, compliance with FURPS requirements).
- Unique or innovative design choices, with a brief discussion or illustration during the demo.
- (If applicable) Performance metrics, support/deployment workflow, or anything relevant the evaluators should notice. 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).
By default, submissions are evaluated first-come-first-served against the success criteria. The first submission that meets all criteria wins. Describe any deviations from this default here.
Evaluators will independently clone the repository and run the demo script from a clean environment; the script must succeed without modification. Evaluators may also ask technical follow-up questions to verify authorship and understanding of the implementation.
The following policies apply to all prizes (see evaluation policies):
- Submissions: each builder (or team) is allowed a maximum of 3 submissions per prize, with at most one submission/review per week.
- Feedback: initial evaluation feedback is limited to a pass/fail indication against the success criteria.
Links to relevant specs, documentation, APIs, or prior work that participants should know about.
The Resources referred to are for informational purposes only and are intended solely as guidance regarding tools or other artefacts that may be relevant to preparing a Submission for a Prize. The Resources may include, or may refer to, earlier published Prizes or Specifications, some of which may have received Submissions. Logos does not endorse or approve, and makes no representation regarding any Submission or referenced material. Ultimately, it is the Participant's responsibility to determine whether, and how, if at all, to use any Resource.
If this prize targets a specific testnet, codebase version, or external dependency that is expected to change, note here whether a follow-up prize may be opened to cover adaptation to future versions.
Note: The Specification in this Prize describes an outcome that Logos intends to benefit the Logos ecosystem. It sets out criteria and certain requirements a Participant should fulfill in order to potentially be eligible to be awarded a Prize amount, and is not intended to be an instruction or to direct a Participant's initiative or approach. They are guided by existing approaches and implementations in other mature blockchain systems and their ecosystems, as well as by functional requirements particular to the Logos technology stack or perceived usefulness to such stack or the wider community building on it.
Prizes may contain adoption criteria which are intended to demonstrate real world-interest and the extent to which others are building on, testing, or experimenting with a submission. It may further indicate a submission’s potential usefulness to the Logos technology stack and the community around that.
Prizes may also refer to different Prizes or its Specifications. These are referred to solely for the purposes of identifying criteria applicable to an Artefact of a Submission that may need to also be developed and included as part of a Submission for that Prize. Such references do not require nor direct a Participant to use, extend, modify or otherwise rely on any previous code, implementation, Artefact or Submission associated with the referenced Prize or Specification. Where such references are made, it is up to the Participant to determine how best to develop or incorporate an Artefact to satisfy the relevant Specifications of the current Prize, whether to develop it themselves or otherwise.
Logos does not endorse, approve any Submission and does not guarantee that they are safe, reliable, or fit for any particular purpose. Logos further makes no representation as to the legal or regulatory treatment of this Specification or any implementation of it in any jurisdiction. Anyone interacting with Submissions should do so cautiously and at their own risk and should treat them as unverified code.
Participants act independently, voluntarily and at their own initiative in connection with their Submissions and are solely responsible for:
- determining the approach and how to develop an Artefact as part of a Submission;
- assessing the risks and implications of their Participation in the Program and of any Artefacts that form part of their Submission;
- determining whether to obtain independent professional advice; and
- complying with all applicable laws to them and in connection with the Program, including, where relevant, any licensing, registration, sanctions or anti-money laundering obligations that may arise from operating any software-as-a-service or business.
Artefacts developed by Participants in connection with the Program are published and maintained by Participants and not by Logos or its Affiliates. Logos and its Affiliates do not build, host, maintain, deploy, operate, use or control any Artefacts arising out of any Submission.
Participants or other persons who choose to build upon, host, maintain, deploy, operate, use or publicly promote any Artefacts, do so at their own risk and as a principal and in their own name. Any such persons are further solely responsible for complying with any legal or regulatory requirements that apply to them with such use. Logos does not make any representation, provide any advice or assume any responsibility regarding the use of such Artefacts, or any determination of compliance with applicable law or regulation.
For further details of the above and what terms and conditions apply to a Participant, please refer to the λPrize Program – Terms & Conditions.