Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
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
1 change: 1 addition & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,7 @@ Prizes are typically defined through an analysis of gaps in the Logos technology
| [LP-0015](prizes/LP-0015.md) | General cross-program calls via tail calls | Large | Closed |
| [LP-0016](prizes/LP-0016.md) | Anonymous Forum with Threshold Moderation | Large | Closed ([Solution](solutions/LP-0016.md)) |
| [LP-0017](prizes/LP-0017.md) | Whistleblower: document upload and indexing Basecamp app | Medium | Closed ([Solution](solutions/LP-0017.md)) |
| [LP-0026](prizes/LP-0026.md) | Simple Forum App | Medium | Draft |

> [!IMPORTANT]
> **Legacy scheme wind-down.** To make room for adoption-first prizes, **LP-0002**, **LP-0003**, and **LP-0008** close on **11 September 2026 at 23:59 CEST**. No new submissions will be accepted after that time. If you have already submitted a solution, yours will be reviewed first. In-flight submissions received before the deadline will still be evaluated. Prizes already marked *Closed* are unaffected.
Expand Down
124 changes: 124 additions & 0 deletions prizes/LP-0026.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,124 @@
<!-- Don't forget to add/update this prize in the table in README.md -->
---
dependencies: []
---

# LP-0026: Simple Forum App - [DRAFT]

**`Status`**:
- Draft: Not yet ready
- Open: Ready for application
- Completed: Submission accepted, prize completed

**`Logos Circle: N/A`**

## Overview

Public forum to allow open and educational discussion of, perhaps controversial, ideas whilst retaining fundamental rights to privacy.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Public forum to allow open and educational discussion of, perhaps controversial, ideas whilst retaining fundamental rights to privacy.
Public forum to allow open and educational discussion of ideas whilst retaining fundamental rights to privacy.

With increasing surveillance, personal identification, and targeted retaliation on social media, the internet is losing its ability for people to freely speak their mind and learn rapidly from each other. A forum with privacy at its core provides a safe space for people to exchange ideas without preempting censorship/oppression, eg politics. An important muscle to work to retain free-thinking and not accept capture by authoritarian regimes that seek to isolate individuals and limit free speech.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
With increasing surveillance, personal identification, and targeted retaliation on social media, the internet is losing its ability for people to freely speak their mind and learn rapidly from each other. A forum with privacy at its core provides a safe space for people to exchange ideas without preempting censorship/oppression, eg politics. An important muscle to work to retain free-thinking and not accept capture by authoritarian regimes that seek to isolate individuals and limit free speech.
With increasing surveillance, personal identification, and targeted retaliation on social media, the internet is losing its ability for people to freely speak their mind and learn rapidly from each other. A forum with privacy at its core provides a safe space for people to exchange ideas without preempting censorship/oppression, eg politics. An important muscle to work to retain free-thinking and not accept capture by corporations that seek to isolate individuals and limit free speech.


## Motivation

Enable people to freely discuss ideas on any topic. Filling the gap of tools that allow free and open communication without surveillance and censorship.
This prize mechanism works well to encourage developers to build for interesting domains, and possibly make unique tech choices. For example this [example forum](https://github.com/jzaki/forum-sample-app).

## Success Criteria

- A number of realistic topics and organic conversations taking place (Checks will be made to assess authenticity)

**Functionality** — what the system must do. Note: applications must not depend on any centralised server or service. Use the Logos stack for communication: **Logos Storage** (storage/data availability), **Logos Delivery** (messaging) for publishing data, **Logos Chat** (messaging) for peer-to-peer coordination.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
**Functionality** — what the system must do. Note: applications must not depend on any centralised server or service. Use the Logos stack for communication: **Logos Storage** (storage/data availability), **Logos Delivery** (messaging) for publishing data, **Logos Chat** (messaging) for peer-to-peer coordination.
**Functionality** — what the system must do. Note: applications must not depend on any centralised server or service. Use the Logos stack for communication: **Logos Storage** (storage/data availability), **Logos Delivery** (messaging) for publishing data, **Logos Chat** (messaging) for end-to-end encrypted peer-to-peer coordination.

- In summary: expected base functionality of a forum application...
- Ability to have one or more accounts to post from

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider privacy implication of keeping the same identity across the whole platform, or having manual or automated identity rotation.

- Ability to create new topics and reply to existing ones (text only). Optional extra: emoji reacts

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Ability to create new topics and reply to existing ones (text only). Optional extra: emoji reacts
- Ability to create new topics and reply to existing ones

- Option to reply anonymously, or via unique id, or alias (alongside optional uid)
- if unique id is chosen to be visible, indicate if it corresponds with msg signature

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- if unique id is chosen to be visible, indicate if it corresponds with msg signature

sounds like an unnecessary implementation detail? or do you have a specific functionality in mind?

- Single forum app, all topics at same single level. Optional extra: ability to create groups of topics

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Single forum app, all topics at same single level. Optional extra: ability to create groups of topics

I would leave teh product choice to the challenger, as long as they make something used by people.

- Optional extra: your own niche-specific flair/feature(s) if any

**Usability**
- Provide a Logos Basecamp app GUI with local build instructions and loadable in Basecamp

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and served pre-built in a catalog


**Reliability**
- If offline when would have been received, an app can obtain past msgs
- If sending a msg fails (eg offline), the text remains available locally to retry another time

**Performance**
- Does not flood the network

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the performance can be left to "adequate UX" criteria, see how I did it in wallet λ-Prize


**Supportability**
- Software design/architecture is sound for the application
- 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 Basecamp app
- A recorded video demo of the end-to-end flow is included in the submission


## Scope

### In Scope

Forum described above.

### Out of Scope

The developer can choose what to include or not, beyond basic forum functionality. This will help builders to differentiate themselves and their apps to stand out.
- Use of the blockchain module is considered out of scope for this LP so that focus may remain on core forum functionality first. This may be considered in a future LP.

## Prize Structure

- **Total Prize:** $X
- **Effort:** M
Top one (or two?) forums with meaningful activity, may be complimentary topics.

## Eligibility

Open to any individual or team. Submissions must be original work. Teams must hold the rights to all submitted code and agree to dual-license it under the MIT License and Apache License 2.0.

## Submission Requirements

> 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).
> - 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](../solutions/LP-0000.md)).

## Evaluation Process

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 application from a clean environment; the application must run 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](../README.md#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.

## Resources

- [example forum](https://github.com/jzaki/forum-sample-app)

## Potential for Subsequent λ Prizes

A follow-up prize may be opened to cover adaptation to future release set 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.

Logos makes no representation as to the legal or regulatory treatment of this Specification or any implementation of it in any jurisdiction.

Participants act independently, voluntarily and at their own initiative in connection with their Submissions and are solely responsible for:

1. assessing the risks and implications of their Participation in the Program and of any Artefacts that form part of their Submission;
2. determining whether to obtain independent professional advice;
3. 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](../TERMS.md).
Loading