Ludium Portal
Sponsor–builder contract smart contracts and the GraphQL backend API for a Web3 talent platform
- Client
- Ludium (Web3 builder community)
- My role
- Smart contract, Backend API (GraphQL)
The challenge
Sponsors fund a program, sign contracts with builders and pay out per milestone — all of it had to live on-chain, while the portal's v2 rebuild needed backend APIs for hiring, applications, dashboards and community.
Key decisions
No contract without the builder's signature
A sponsor can only create a contract by submitting terms the builder already signed; the contract verifies the signature so only the agreed amount and duration go through, and stores a snapshot hash to match the off-chain agreement.
Milestone payouts and the unhappy paths
Milestone completion pays out net of fees; pausing, resuming and cancelling contracts, program refunds and emergency stops are split by role. Deployed behind UUPS so the contract could follow changing requirements.
The v2 GraphQL API
Built program, milestone, application, portfolio, dashboard, article, thread and notification APIs with Pothos, batching relation lookups through DataLoader to cut N+1 queries, and migrated program IDs to UUIDs without losing existing data.
Results
- Contract deployed to testnet with 41 tests
- v2 GraphQL API features merged PR by PR into dev
Tech
- Solidity — Sponsor–builder contract and milestone payouts
- EIP-712 — Builder signature check before a contract is created
- Upgradeable contracts (UUPS) — UUPS
- Hardhat — Deploy/upgrade scripts and tests
- GraphQL — Mercurius + Pothos, DataLoader
- Node.js — Fastify
- Drizzle ORM — Schema and migrations
- PostgreSQL
- TypeScript
Planning & collaboration
- Architecture & user flows — Designed the sponsor–builder contract flow and the contract/API structure