Projects & participation
Project discovery, detail pages, sale and token information, contribution screens, claims and wallet-linked profiles.
Full Force gave Web3 projects a way to allocate investment opportunities to active community members. Participants connected a wallet, completed missions and followed their rank on a campaign leaderboard.
A participant joined with a wallet, chose a project and completed missions such as posting a COREx thread or sharing testnet results. Each campaign kept its own leaderboard.
Project discovery, detail pages, sale and token information, contribution screens, claims and wallet-linked profiles.
A connected wallet can trigger the dice contract. Its result is persisted as an event that the interface watches and turns into an animation.
The ForcePad repository contains its public site, a CMS for managing projects, and a Parse Server backend.
This portfolio serves archived campaign data. Wallet, social and transaction actions are offline.
The launchpad used a wallet for identity and transactions. Firestore connected the web app to the services that scored missions and recorded dice rolls.
user_missions and project dataupdateUserMissionCloud Function updates the leaderboard, user XP and project totals in one transactionaddContributionThe dice listener writes dicePoints. The mission function updates total_score, the field used to rank participants.
The browser submits the transaction, a NestJS listener reacts to the contract event, and Firestore carries the result back to Mission Control. The interface listens for that persisted event.
MissionControl checks for a connected wallet and the selected chain, then calls getRandomNumber().
DiceService subscribes to RandomNumberGenerated, reads the result, caller and block, then calculates roll × 100 points.
FirebaseService stores an event document with its address, result, block and server timestamp, then increments a dice-points field for the address and project.
MissionControl subscribes with onSnapshot to events for the connected address and animates a recent result. It also reads recent events to set a 24-hour countdown.
The event document ID combines address, result and block. The leaderboard writer uses an address/project document ID and increments dicePoints.
events · leaderboard · dicePoints
The rendered leaderboard query filters by projectId and orders by total_score, then joins public user records.
where(projectId) · orderBy(total_score)
The mission update function writes projectId and total_score in a Firestore transaction alongside user experience and project totals. The dice listener uses a separate dicePoints field. An event can animate in the browser without changing the score used for ranking.
The NextAuth credentials provider verifies a Sign-In with Ethereum message against the configured host and CSRF nonce. Its JWT session creates a Firebase custom token, which the client uses for Firebase Auth. This lets a wallet address bridge app sessions and Firebase reads, while making nonce, domain and token boundaries central to the security model.
Mission Control subscribes to Firestore onSnapshot
after the user starts a roll. The listener handles the chain connection for all clients. If the listener falls behind, a confirmed transaction can appear in the UI late.
The leaderboard starts with 20 rows and loads another 50 from a Firestore snapshot cursor ordered by score. Each row then fetches its public user profile. Cursor pagination avoids offset scans. The per-row profile lookups create a fan-out cost worth revisiting as the table grows.
ForcePadHub creates sale contracts from a template. Sale rounds define who can contribute, the amount each participant can contribute, and the currency accepted.
The Foundry suite exercises whitelist and public rounds, native-currency and ERC-20 contributions, allocation limits and withdrawals.
d9af2e4 and a89b7d2.All 15 directories in the Full Force archive, including the product code, prototypes, example projects and duplicate checkouts.
Next.js campaign pages, wallet sign-in, missions, claims, profiles and paginated leaderboards. The functions directory contains Firestore triggers, including mission scoring.
NestJS and Ethers service listening for dice events; writes event records and dice-point increments to Firestore.
Foundry contracts for a role-managed sale hub, deterministic sale clones, whitelist allocations, sale phases and ETH/ERC-20 contributions.
Three-part product repository: a Parse Server backend, a project-management admin CMS and the public ForcePad site.
A Next.js token and launchpad application with token creation forms, sale creation, sale discovery and MongoDB-backed APIs.
Telegram polling prototype classifying message and media types and deriving text metrics. Its current Firestore writer replaces per-user metric fields rather than accumulating them; leaderboard scripts are exploratory.
Prototype that retrieves recent posts and their likes, reposts and replies, stores per-post results in MongoDB, then exports engagement aggregates to CSV.
A Foundry experiment that derives a number from block data, emits the result and limits each address to one roll in 24 hours.
Organization profile and collaboration templates for the Full Force GitHub organization.
An earlier checkout of launchpad-frontend, with a February 2024 version of the same app.
A fork of the Unlock Protocol monorepo, containing membership contracts, apps, subgraph and supporting packages.
An earlier workspace snapshot of the Unlock Protocol codebase.
Reference implementation of session handling and sign-in with NextAuth.
Upstream Sign-In with Ethereum and NextAuth tutorial example.
A minimal Wagmi debugging project for reproducing a wallet integration issue independently of the launchpad.
The campaign index preserves the original featured card and completed-sales layout.