The place where builders find their home — and coordinate it on-chain. Verify your on-chain identity, match with Hacker Houses you actually qualify for, and co-live with trustless escrow on Arbitrum.
Builders travel to the same events but have no structured way to find each other, and coordinating a Hacker House still depends on one organizer manuall chasing payments, holding funds on faith, with no automatic refund if things fall through.
Hacker House Protocol turns that responsibility into trustless, automatic, verifiable on-chain infrastructure — without replacing the organizer.
VERIFY → MATCH → CO-LIVE
• VERIFY — Your on-chain identity is your credential:
POAPs from events you attended, wallet history, skills. You don't declare it, you prove it. Data wallets must prove ownership (Privy signature) and can't be reused across users — credentials stay private and tamper-proof; a normal user can never bypass that.
• MATCH — Explore Hacker Houses that fit your profile AND that you qualify for. Each house sets its own on-chain access gates: minimum builder skills, number of POAPs, or specific event POAPs.
• CO-LIVE — Once accepted, you coordinate your spot on-chain on Arbitrum.
Builders pool funds, automatic release to the organizer when the house fills, automatic refund if it doesn't, and a booking NFT lands in your wallet. Trust runs both ways: community/company houses pass a manual review to earn a ✓ Verified seal.
Three real funding models, all crypto-native: co-payment between builders, sponsor-funded houses, or staking as commitment (locked funds earn yield while they wait).
Smart contracts:
Factory: 0x751ea80Fae2F714812bF0317bE4df96FD3ffcfB5
MockUSDC: 0x999579cc79400a1b59b119b6697664Dd9122Ad93 (Arbitrum Sepolia).
• Smart contracts deployed & verified on Arbitrum Sepolia: HackerHouseFactory + MockUSDC (verified on Arbiscan), auto-deploying a HackerHouseEscrow, SpotNFT (booking NFT) and a yield adapter per house. • Escrow flow: createHouse → deposit (pooled funds) → automatic release to host / automatic refund on deadline → booking NFT mint. 0.5% protocol fee on principal only. • Three modalities: co-payment, sponsor, and staking/hybrid — staking funds earn GMX yield while locked, distributed to host or split among builders on release. • App ↔ contract integration live: house creation deploys the escrow via ERC-4337 account abstraction (ZeroDev smart accounts + Privy embedded wallet signer), payment/staking UI, and an owner-only deploy-retry if the first deploy is rejected. • Identity gates: houses gate access by Builder Skills, POAP count, or specific POAPs, enforced server-side. • Secure multi-wallet: ownership proof via Privy linkWallet + global anti-reuse so credentials can't be spoofed; only verified wallets feed POAPs/gates. • Supporting platform: communities with mini-events + RSVP, event catalog with admin review, builder discovery + algorithmic matching, interactive map, notifications, and an admin panel.
Not currently raising. Open to pre-seed conversations post-buildathon. Post Buildathon nex steps: Hacker House Protocol — Roadmap ⭐PHASE 1: - Multisig / multi-host houses — multiple organizers co-manage a house treasury via ERC-4337 smart accounts, with threshold approvals for release and dispute windows. - Privacy bridging — carry credentials and funds across chains without doxxing: deposit from any chain, settle on Arbitrum, shielded/private deposits. - NFT gates — gate houses by holding a specific NFT / collection (ERC-721 & ERC-1155). - ⭐ PHASE 2: - Mainnet launch — migrate off testnet/MockUSDC to Arbitrum mainnet + real USDC. - Sponsored houses live — Base House, Arbitrum House — branded, with the ✓ Verified seal. - On-chain reputation: "shipped-with" / "co-lived-with" attestations that travel between events. - ⭐ PHASE 3: - Community governance — who earns the ✓ seal, which houses get featured. - In-app chat between matched builders and houses. - Gamified experience — streaks, badges, builder levels, skins.
