Skip to content
DEVFRIDGEHACKATHON / BUILD SEASON

GUIDE 05 / PREPARATION EDITION

Participation & conduct

Build in public with care. Make the work reviewable and the experience welcoming.

Preparation rules

This is the initial preparation handbook. The gallery uses reviewed GitHub PRs. Competition dates, judges, final eligibility and any prize-specific terms will be published before competition entries open. No prize, grant, token allocation or acceptance is promised by this page.

Solo builders and teams may prepare projects now. Disclose pre-existing code, templates and earlier game versions so reviewers can understand what you added. AI assistance is encouraged; identify the tools and review the output yourself.

Project requirements

  • Provide a playable browser game with desktop and mobile support, a complete gameplay loop and a distinct community concept.
  • Demonstrate Phantom and DevFridge timelock integration. Label fixtures and incomplete mainnet work honestly.
  • Provide a repository reviewers can access, setup instructions, an immutable commit reference and a brief demo video.
  • Include the access policy, fee and expiry disclosures, test evidence, asset attribution and an AI build log.
  • Make the demo assessable without spending money. A practice mode must be clearly separated from real gated access.

Respect users and other builders

  • No harassment, discrimination, impersonation, plagiarism or malicious code.
  • No seed phrase or private-key collection, concealed transfers, deceptive approvals or undisclosed fund movement.
  • Use assets and dependencies you have rights to use; document licences. Publishing code does not waive its existing licence.
  • Do not spam communities or promise investment returns. Do not treat TVL, token price or buying volume as a judging criterion.
  • Report security issues privately through the project’s published security policy. Use the official DevFridge contact directory for organizer questions.

Ownership, privacy and affiliations

Creators retain rights to their work, subject to existing licences. Make the review permissions and third-party licences clear. Reusing the live DevFridge program is different from relicensing or redeploying its source; check repository terms.

Use test wallets and redacted logs in demos. Wallet addresses and blockchain activity may be public; never submit secrets or unnecessary personal data. This preparation site does not collect application forms.

This is a DevFridge initiative. Mentioning Solana, Pump.fun, Phantom or coding agents describes compatible tools and audiences, not an announced sponsorship or partnership.