FAQ

A contest platform with clear phases: submissions open, admin review, community voting, then completion. Rankings and prizes are tracked in one place so participants always know where things stand.

Yes. Sign in with your Nepher account — the same identity you use across Nepher products. The hackathon site uses that sign-in to load your profile, submissions, and votes securely.

Browse public hackathons from the header, open an event for rules and timelines, and use the dashboard after sign-in to submit, vote (when open), and manage payouts if you win.

Your Bittensor cold-wallet address (SS58). Registering it through Nepher lets the platform apply fair, stake-informed weights to community ballots without asking for seed phrases in the browser.

Follow the step-by-step coldkey guide using nepher-cli. Browser-only registration isn't offered for security and audit reasons.

No. Admins skip community coldkey gates; expert panel ballots don’t require a coldkey. Community voters typically do.

Both. Use the dashboard upload form during the submission phase, or submit the same two ZIP files with Nepher CLI — your choice. You’ll need a Nepher API key for CLI use (see the coldkey guide for keys).

Two archives: a submission ZIP with your project/source and an assets ZIP with gallery media (images, short videos, PDFs) within the limits shown on the hackathon page and on the submit screen.

One submission per person per hackathon. After a successful submit, another upload isn’t allowed for that event.

When media and archives are hosted for the event, the public submission page can offer short-lived download links. If something isn’t available, you’ll still see titles, descriptions, and discussion where enabled.

Community ballots are combined with normalized stake-derived weights so influence reflects sustained participation rather than one-off noise, as described in each event’s rules.

No — self-votes are rejected.

Rankings and winners come from the platform’s aggregated scores. During voting, standings may be provisional; finished events show the winner and gallery on the public hackathon page.

Typical flow: submissions → admin review of entries → voting → completion. Exact dates appear on each hackathon’s page and in your dashboard.

Winners open the dashboard payout flow, complete Stripe Connect Express onboarding (identity and tax handled by Stripe), and claim the prize when the platform sends the transfer.

Sometimes payouts aren’t enabled for this site yet, or the page can’t load settings. Refresh and try again; if it persists, contact the organizers — they can confirm status on their side.

Then there is no winner row and no prize transfer for that event.

Use the coldkey guide for CLI steps, and check each hackathon’s rules and deadlines on its public page.