BUILDDays 1–21 · UTC+2 · Submissions open
H4CK&STACK — 001 / community

A Discord server for developers and security researchers who would rather ship something than talk about shipping something. One brief a month. Public work. Peer review that bites.

UTC+2 phase: BUILDDeveloper · Hacker tracksAnonymous voting days 22–27XP syncs to Discord rolesAll ages · all skill levels
02The ecosystem

Pick a lane, share the clock

The Developer and Hacker tracks run the same calendar, the same peer vote and the same XP ledger. Only the work differs.

Track 01Developer
0 shipped

Ship something that runs. Web apps, CLIs, automations, libraries — in whatever language you are trying to get good at.

monthly-build.tsx
export function Submission({ entry }: Props) {
const { votes, track } = entry;
 
return (
<article data-track={track}>
<h3>{entry.title}</h3>
<VoteRail count={votes} />
</article>
);
}
WebCLIAutomationOpen Source
Track 02Hacker
CTF · research

Break it, then write it up. Vulnerability research, CTF chains, tooling, and blue-team detections that hold under pressure.

root@h4s7 — session
recon --scope ctf.h4cknstack.com
resolving 4 hosts … 3 live
[+] 8080/tcp open http werkzeug/2.3.7
[+] 5432/tcp open postgres
fuzz --wordlist raft-medium --threads 24
[200] /internal/debug 1.4kb
[!] template injection reachable via ?q=
writeup submit --track HACKER
queued for peer review · day 22 opens voting
Vuln ResearchRed / Blue TeamSecurity Tools
The clockOne cycle, every month
UTC+2

Fixed civil days, no timezone argument. The window opens on the 1st and the results are public by the 29th.

01212531
  • Build / HackDays 1–21
  • Anonymous voteDays 22–27
  • ResultsDays 28–31

Syncing cycle clock…

GamificationXP, ranks, roles
Synced to Discord

XP comes from submissions, votes received, published writeups and your GitHub activity. Cross a threshold and the bot moves your role in the server — the badge is not decorative.

  • Newcomer0–99 XP
  • Builder100–499 XP
  • Veteran500–1,499 XP
  • Elite1,500+ XP
See where members stand
03How it works

Four steps, one loop

The same rhythm every month. Nothing to apply for, nothing to schedule around — the calendar does it for you.

Any day

One invite, no application. Pick up your role, read the current brief, and say hello in the track channel that matches how you build.

  • Two tracks: Developer and Hacker
  • Every skill level, every age — beginners included
  • Channels for review, pairing, and rabbit-hole research
Slash commandsThe bot does the paperwork
#h4s7-commands

Simulated output. Run the real thing in the server — the bot replies privately, so your rank-up is yours to share.

04Community showcaseFull leaderboard

Receipts, not promises

Every rank on this board was earned by shipping in public and getting voted on by people who read the code.

05Why join

Where the work gets read

Most servers are a feed. This one is a workshop with a deadline — and people who will tell you what is wrong with your auth flow.

  • 01

    Reviews from people who read the diff

    Post a repo and get line-level feedback in hours, not a thumbs-up emoji. Security folks read the auth flow; frontend folks read the render path.

  • 02

    A brief every single month

    No blank page. A fresh challenge lands on day one with tiers for wherever you are — first project or tenth CVE.

  • 03

    Sub-channels for the deep end

    Vuln research, red and blue team, CLI tooling, design systems. Small rooms where the conversation actually goes somewhere.

  • 04

    XP that means something

    Ranks sync to Discord roles and the public leaderboard. Ship consistently and the whole server can see it.

Days 1–21 · UTC+2 · Submissions openJoin the serverRead how it all works
Build realHack deepOwn the stackFree · alwaysh4cknstack.com