SDF developer marketing lead Jeremy and judge Ash Francis (3x Stellar Hacks winner) host a Twitter Space walking developers through ZK hackathon submission requirements before the July 3 deadline. Key topics include ensuring code repos are public (not private—a common mistake), demo videos that are viewable (unlisted or public, not private), and creating comprehensive READMEs that accurately reflect your project scope, including any mock data or incomplete features. Speakers discuss the advantage of submitting early and iterating, proper GitHub branching strategies for ongoing development, and address frequently asked questions about technical pitfalls. The session emphasizes that judges read your README first, making clarity and accuracy essential for standing out.
In this Twitter Space, Stellar Development Foundation developer marketing lead Jeremy and judge Ash Francis, a three-time Stellar Hacks winner, guide participants through submitting to the ZK hackathon before the July 3, 16:00 UTC deadline. The session covers critical submission requirements: ensuring your code repository is set to public (not private), demo videos that are either unlisted or public (not private), and creating comprehensive READMEs that accurately reflect your actual code, with clear callouts of any mock data or incomplete features. Speakers emphasize that judges read your README before running anything, so clarity matters. They discuss the strategy of submitting early and iterating before the deadline, using GitHub branches to scope your hackathon entry separately from ongoing project development, and answer frequently asked questions on common technical mistakes that disqualify submissions. The focus is practical: no technicalities should cost you a submission.
