FULL FORCE
Engineering case study · 2024

Inside the
Full Force launchpad.

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.

Product

Inside a campaign

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.

LAUNCHPAD

Projects & participation

Project discovery, detail pages, sale and token information, contribution screens, claims and wallet-linked profiles.

MISSION CONTROL

Missions and rewards

A connected wallet can trigger the dice contract. Its result is persisted as an event that the interface watches and turns into an animation.

FORCEPAD

Campaign administration

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.

Architecture

System design

The launchpad used a wallet for identity and transactions. Firestore connected the web app to the services that scored missions and recorded dice rolls.

How the Full Force launchpad connected wallets, Firebase and EVM contracts Wallet sign-in passes through NextAuth to Firebase Auth. Campaign missions trigger scoring in Firestore. Dice transactions emit an event that a NestJS listener writes to Firestore, which pushes the result to the browser. Contributions go directly to a project's sale contract. CLIENT IDENTITY, DATA & CONTRACTS SERVICES Sign message Token via browser Submit mission Read / subscribe Mission updated Write scores & XP Sign transaction Dice event Record roll and dice points Launchpad + wallet Next.js web app Campaigns · Mission Control NextAuth Verifies the wallet signature Issues a Firebase custom token Firebase Auth Exchanges the custom token for a Firebase session Cloud Firestore Missions · events Leaderboard · project totals Mission scoring Firestore-triggered function updateUserMission EVM contracts Dice · getRandomNumber Sale · addContribution Dice listener NestJS service on Cloud Run Subscribes to dice events
Wallet sign-in
WalletConnect and sign a SIWE message
Launchpad + NextAuthSIWE verifies the wallet signature
Firebase AuthBrowser syncs signed-in identity
Mission scoring
LaunchpadSubmit missions and read campaign data
Firestoreuser_missions and project data
updateUserMissionCloud Function updates the leaderboard, user XP and project totals in one transaction
Dice roll
Wallet + browserSubmit dice call
EVM · dice contractEmits roll result event
NestJS dice listenerStores event and increments dice points
Firestore → browserLive event animates in Mission Control
Token sales
Wallet + launchpadCall addContribution
CommunityRaiseThe project’s sale contract accepts the contribution
ForcePadHubA sale admin sets up each sale through the clone factory

The dice listener writes dicePoints. The mission function updates total_score, the field used to rank participants.

Related systems in the repository collection
  • ForcePadPublic site and admin CMSParse Server
  • Telegram engagementTelegram botFirestore engagement records
  • X engagement prototypePosts and interactionsMongoDBCSV reports
  • Bonsai3Token and sale screensNext.js API routesMongoDB
Event flow

From a dice roll to the screen

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.

Wallet · transaction

Ask the contract to roll

MissionControl checks for a connected wallet and the selected chain, then calls getRandomNumber().

Ethers · listener

Receive the emitted result

DiceService subscribes to RandomNumberGenerated, reads the result, caller and block, then calculates roll × 100 points.

Firebase · persistence

Write event and 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.

React · live feedback

Animate the new document

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.

Listener writes

The event document ID combines address, result and block. The leaderboard writer uses an address/project document ID and increments dicePoints.

events · leaderboard · dicePoints

Launchpad reads

The rendered leaderboard query filters by projectId and orders by total_score, then joins public user records.

where(projectId) · orderBy(total_score)
How mission scoring differs

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.

Engineering

Three engineering decisions

Wallet identity across services

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.

React to persisted events

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.

Page the leaderboard by cursor

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.

Sale contracts

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.

Thomas GuntenaarBuilt the dice event listener and Firestore writer. In the launchpad, the 24-hour dice countdown and cursor-based leaderboard pagination are documented in commits d9af2e4 and a89b7d2.
NorbertDesigned and implemented the original Full Force frontend, including the launchpad experience preserved here.
Codebase

The repository map

All 15 directories in the Full Force archive, including the product code, prototypes, example projects and duplicate checkouts.

launchpad-frontend

Next.js campaign pages, wallet sign-in, missions, claims, profiles and paginated leaderboards. The functions directory contains Firestore triggers, including mission scoring.

event-listener

NestJS and Ethers service listening for dice events; writes event records and dice-point increments to Firestore.

fullforce-contracts

Foundry contracts for a role-managed sale hub, deterministic sale clones, whitelist allocations, sale phases and ETH/ERC-20 contributions.

forcepad-main

Three-part product repository: a Parse Server backend, a project-management admin CMS and the public ForcePad site.

bonsai3

A Next.js token and launchpad application with token creation forms, sale creation, sale discovery and MongoDB-backed APIs.

telegram_engagement_bot

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.

x_engagement_bot

Prototype that retrieves recent posts and their likes, reposts and replies, stores per-post results in MongoDB, then exports engagement aggregates to CSV.

random-contract

A Foundry experiment that derives a number from block data, emits the result and limits each address to one roll in 24 hours.

ff-github

Organization profile and collaboration templates for the Full Force GitHub organization.

launchpad-frontend copy

An earlier checkout of launchpad-frontend, with a February 2024 version of the same app.

unlock

A fork of the Unlock Protocol monorepo, containing membership contracts, apps, subgraph and supporting packages.

unlock-old

An earlier workspace snapshot of the Unlock Protocol codebase.

next-auth-example

Reference implementation of session handling and sign-in with NextAuth.

siwe-next-auth-example

Upstream Sign-In with Ethereum and NextAuth tutorial example.

reproducable-wagmi-issue

A minimal Wagmi debugging project for reproducing a wallet integration issue independently of the launchpad.

Full Force · Launchpad

Explore the launchpad

The campaign index preserves the original featured card and completed-sales layout.

View project overview