Files

2.0 KiB

Solution: LP-XXXX —

Submitted by:

Summary

Brief description of the solution and how it addresses the prize's success criteria.

Repository

Link to the repository containing the implementation.

Approach

Describe the technical approach, architecture, and key design decisions. For each significant decision, explain what alternatives were considered and why they were rejected. Note anything that was tried and did not work, as this demonstrates genuine familiarity with the problem space.

Explain why the Logos stack (LEZ, Logos Delivery, Logos Chat) is a good fit for this use case. Specifically, what properties of the stack (e.g. censorship resistance, trustless execution, decentralised messaging) matter here, and what would be lost by building on a centralised alternative.

Success Criteria Checklist

Mirror the success criteria from the prize and explain how each is met.

  • Criterion 1: explanation
  • Criterion 2: explanation
  • Criterion 3: explanation

FURPS Self-Assessment

Evaluate your delivery against each of the following dimensions.

Functionality

What the program does, which operations are supported, and any limitations.

Usability

How users interact with the system, what the onboarding experience looks like.

Reliability

How the system handles failures, consistency guarantees, and graceful degradation behavior.

Performance

Execution times, resource usage, compute unit costs, and any bottlenecks.

Supportability

Test coverage, CI status, deployment instructions, logging/debugging support, and how the codebase is structured for future maintenance.

Supporting Materials

Links to demos, benchmarks, documentation, or any other artefacts that support the submission.

Terms & Conditions

By submitting this solution, I confirm that I have read and agree to the Terms & Conditions.