Skip to content

template: require Mac + Linux build support #67

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
fryorcraken wants to merge 4 commits into
base: master
Choose a base branch
from
+10 −0
Open

template: require Mac + Linux build support #67

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
84998ad
template: require Mac + Linux build support
fryorcraken May 26, 2026
2fd35ce
template: drop prescriptive how-to, add module-builder requirement
fryorcraken May 26, 2026
4712402
template: require module catalog publishing via logos-modules-release…
fryorcraken Aug 10, 2026
952dc77
template: align with recent LPs; platforms recommended, macOS via ado…
fryorcraken Oct 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions prizes/LP-0000.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,11 +56,17 @@ dependencies: []
>
> **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`](https://github.com/logos-co/logos-module-builder) (`mkLogosModule`).
> - Logos Basecamp modules are published to a module catalog: a fork of [`logos-modules-release-base`](https://github.com/logos-co/logos-modules-release-base), publishing releases via [`logos-modules-release-action`](https://github.com/logos-co/logos-modules-release-action). The catalog's `logos-repo.json` URL 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=0` was active.
>
> **Adoption** — traction attributable to the submission (see the Adoption section of recent adoption-first prizes, e.g. [LP-0023](LP-0023.md), 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
Expand Down Expand Up @@ -92,6 +98,10 @@ Submissions must be original work. Teams must hold the rights to all submitted c

> 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.json` URL.
> - Evidence for each adoption criterion.
>
> A narrated video walkthrough demo is always required (see [demo requirements](../README.md#evaluation-policies)). 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).
Expand Down
Loading