A Web3 platform with a token site, an NFT-linked merch store, staking, raffles and a Telegram bot — run from one admin.
Meana Raptor is a full Web3 ecosystem built to integrate blockchain with lifestyle experiences. It consists of multiple interconnected modules: an MRT token promotional site, NFT-powered golf merchandise store, staking and raffle platforms, and an automated Telegram bot for community updates. Each part of the system is managed via a robust Node.js-based admin dashboard that synchronizes product listings, raffle data, and announcements across the ecosystem.
- Role
- Full-stack developer
- Type
- Client · Core Devs
- Year
- 2025
- Stack
- Next.js · Node.js · MongoDB · Web3.js
- Result
- 5 connected products · one admin backend · Telegram bot
(By the numbers)
- connected products, one admin backend
- 5
- Google Lighthouse speed score on desktop
- 92
Lighthouse measured on meanaraptor.vercel.app, Sep 2026.
(How it works)
Order placed · holder price
Animated illustration of the real flow, with sample data — not a live system.
(What I built)
- 01Animated token site with voiced, comic-style story sections
- 02Tokenomics, staking, NFT store and raffle sections
- 03Merch store with discounts based on the MRT tokens in a wallet
- 04Telegram bot for raffle results, new products and AMAs
- 05One admin for products, raffles and bot messages
Process
(Problem → what I did)- 01
Problem
The admin dashboard, the store and the Telegram bot had to stay in sync.
What I did
- Built one Node.js and Express API that the store, raffles and bot all go through.
- Automated the Telegram bot's raffle results, new-product alerts and AMA posts.
- 02
Problem
Discounts depend on how many MRT tokens a visitor's wallet holds.
What I did
- Used Web3.js to detect the wallet, read the token balance and work out the discount live.
- 03
Problem
Animated, voiced storytelling sections still had to load fast.
What I did
- Ran voiceover and hover animations through React hooks and controlled media elements.
- Optimised images and assets with the Next.js Image component and caching.
Show all 4 stepsShow less
- 04
Problem
Several sub-sites — token site, NFT store, admin — had to look and perform the same.
What I did
- Used Next.js dynamic routing and shared components for every multi-section layout.
How it's built
The moving parts, from the people using it down to the data.
Front-ends
Token site
Next.js · lore & vision
NFT merch store
token-linked purchases
Staking & raffle
MRT holders
Telegram bot
AMAs, drops, raffle winners
Backend
Node.js + Express admin API
products · raffles · bot messages
Data & chain
MongoDB
products, raffles, users
Web3.js
wallet + MRT balance → tier discounts
Telegram API
automated posts
The product
7 screens from the real product. Click any screen to see it full size.
(On mobile)
Works just as well on the phone.
Every screen was built and checked on small screens too — the same product adapts cleanly from phone to desktop.
(Shipped)
Five connected products run from one admin backend: holders get discounts based on the tokens in their wallet, and the community hears about raffle results, new products and AMAs through the Telegram bot automatically.
