Blurtopian's contributor rewards platform is powered by a multi-service AWS stack — purpose-built for scalability, reliability, and global reach. This page documents each layer of the architecture and the role AWS plays in running the platform end-to-end.
Each layer maps to a distinct responsibility. AWS services handle compute, storage, analytics, and content delivery. The Blurt blockchain handles reward distribution.
Submit work via blurtopian.com
Post announcements, manage projects
Review and approve contributions
Caches static assets and API responses globally across edge locations
Hosts api.blurtopian.com — handles all submission, moderation, and rewards endpoints
Event-driven functions aggregate stats, calculate moderator rewards, power /api/stats
Stores users, contributions, moderation decisions, reward records, project config
Proof-of-Brain consensus distributes BLURT tokens to approved contributors after 7 days
Verifies pull requests, forks, and open source contribution authenticity
Each AWS service was chosen to solve a specific platform requirement. Here's what each one does and why it was the right choice.
EC2 hosts the Blurtopian REST API at api.blurtopian.com. Every action on the
platform — submitting a contribution, triggering a moderation review, fetching project posts,
loading moderator profiles — is handled by this API layer. EC2 was chosen for its flexibility
to run a persistent, stateful Node.js API server with full control over networking and scaling.
RDS runs the PostgreSQL instance that stores every piece of platform data. Using a managed database service eliminates the operational overhead of patching, backups, and failover — critical for a platform where contributor reward records must never be lost. Multi-AZ deployment ensures high availability.
Lambda functions run on a scheduled basis and in response to platform events to compute aggregate statistics. Because these workloads are periodic and short-lived, Lambda is significantly more cost-efficient than running dedicated compute for analytics tasks.
total_paid_authors, total_paid_curators, total_pending_rewards, total_paid_rewards and caches the results for the /api/stats endpoint
Blurtopian serves contributors across the globe — Southeast Asia, Europe, Latin America, and beyond. CloudFront ensures that static assets (the Vue.js frontend, CSS, JavaScript, and project images) are delivered from the nearest edge location, keeping load times fast regardless of where contributors are located.
/api/stats and project listing responses to reduce EC2 load on high-traffic periods
From the moment a contributor submits their work to the moment they receive a reward, every step passes through the AWS infrastructure. Here's the full journey.
The contributor fills out a submission form on blurtopian.com. The page and its assets are served from the nearest CloudFront edge location.
The form data hits the EC2-hosted REST API at api.blurtopian.com. The API validates the payload, checks the contributor's account, and writes the submission to the database.
PostgreSQL on RDS records the contribution with status pending. The moderation queue is updated so an available moderator sees it next.
A moderator loads the queue via the API (EC2), reviews the work against category rules, and submits their decision. The result is written to the moderation records table in RDS.
An approval event triggers a Lambda function that recalculates platform-wide stats and updates the cached /api/stats response. A second function recalculates moderator reward shares.
Approved contributions are published to the Blurt blockchain. After 7 days, the community's votes determine the final payout. Lambda monitors the blockchain and records the finalized amount back to RDS.
The contributor sees their earned BLURT in their wallet. The reward is traceable back through the full audit trail stored in RDS.
| Platform Area | AWS Service | What it does | Why AWS |
|---|---|---|---|
| REST API | EC2 | Hosts api.blurtopian.com — contributions, moderation, rewards, moderator endpoints | Full control over runtime, networking, and persistent connections to RDS and the Blurt blockchain node |
| Database | RDS PostgreSQL | Stores all users, contributions, moderation decisions, and reward ledger | Managed backups, Multi-AZ failover, and automated patching — no DBA overhead for a small team |
| Analytics | Lambda | Aggregates platform stats, calculates moderator rewards, processes blockchain payout events | Pay-per-invocation pricing is ideal for scheduled, short-lived analytics jobs with irregular traffic |
| Content Delivery | CloudFront | Serves frontend, caches API responses, delivers project images globally | Blurtopian's user base spans 5+ continents — edge caching is essential for acceptable load times |
| Reward Distribution | Blurt Blockchain | Distributes BLURT tokens to approved contributors via community voting (Proof-of-Brain) | Decentralized, transparent reward mechanism — no platform funds needed to pay contributors |
| Contribution Verification | GitHub API | Verifies pull requests, forks, and contribution authenticity via git_archiver | First-party verification source for open source contribution proof |