Skip to the work
CyonEghosa Imasuen

WEB3 BUILDER + ECOSYSTEM OPERATOR

FRONTEND · PRODUCT · GROWTH · COMMUNITY · CONTENT · IRL

Build theproduct.
grow theecosystem.
Ship both.

I build Web3 products, grow communities and help ecosystems turn ideas into things people actually use.

4+ years across DeFi, infrastructure, privacy, gaming and payments — usually in ecosystems where the documentation is still being written. I work between the technical side and the human side, which mostly means being close to the actual work.

SEE THE BUILDS@CYON0X
Portrait of Cyon, Web3 builder and growth operator.
CYON — OPEN TO BUILDSTATUS: BUILDINGFOCUS: PRODUCT / GROWTH / ECOSYSTEMSBASE: GMT+1 · LAGOSMODE: SHIP
02IDENTITY

What I actually do

I am a Web3 builder and ecosystem operator. Four years around DeFi, infrastructure, privacy, gaming, payments and ecosystems that were still figuring out what they wanted to be. I have worked as builder, contributor, ambassador, community and growth — usually more than one of those at the same time.

I build the frontend myself: React, Next.js, TypeScript and Tailwind, wired to EVM chains, wallet connection flows and real transaction states. I am not trying to pass for a protocol engineer. What I am is someone who can take a product from an idea to a deployed interface, then explain it, grow a community around it, and put it in front of the people who will use it.

SOMETIMES THAT MEANS

  • 01Building a product.
  • 02Testing one until it breaks.
  • 03Helping a community understand what they are actually holding.
  • 04Writing the thread that makes it click.
  • 05Getting the right people into the same room.
The point is that I like being close to the actual work. Close enough that when something is broken, I am the one who notices.
NAME
Eghosa Imasuen
ALIAS
Cyon0x
BASE
Lagos, GMT+1
ACTIVE
4+ YEARS
STATUS
OPEN TO BUILD

Redbelly, Arc, Circle, Plume, Union, Monad, Swisstronik, Hyperbolic, XORA, ByRep, Aurory, MMT Finance and others. Different relationships, different jobs, one throughline: I get into the work.

ALSO DESCRIBED AS
  • Web3 BuilderProducts, prototypes and interfaces that ship
  • Frontend DeveloperReact, Next.js, TypeScript, Tailwind
  • Web2 + Web3 Product BuilderProduct thinking with wallet-native execution
  • Ecosystem / AmbassadorProgramme work across 25+ ecosystems
  • Community Growth OperatorOnboarding, activation, retention
  • Developer Relations / Ecosystem GrowthDocs, dev feedback, onboarding paths
  • Content & Community CreatorThreads, explainers, campaign assets
  • IRL Community / Event OperatorRooms hosted, planned and organised
  • Product + Growth OperatorClose enough to the work to fix it
03ECOSYSTEM GRAPH

The map, not the logo wall

Thirteen ecosystems, and a different job in most of them. Pick a node for the role, the work and the proof — or filter by what the work actually was.
FILTER
GRAPH / V113 NODES
INNER RING / PRIMARY WORK
SELECTED NODE01/13

REDBELLY

CONTRIBUTOR · BUILDER

The ecosystem I have shipped the most inside. A compliant L1 built for real world assets, and a community that needed tooling.

ROLE → WORK → PROOF

  • CONTRIBUTOR · DAO ECOSYSTEM

    Designed and built the DAO interface, redesigned the community showcase, wrote the KYC and wallet activation guide, shipped TrustPass and VAULT 01.

    PROOF · Redbelly DAO and the community showcase redesign both won Redbelly bounties; the DAO build was posted by @RedbellyNetwork.

  • CONTENT · COMMUNITY

    Educational content, memes, campaign assets, community showcases and task board campaigns.

    PROOF · The 10-week contribution broken down in Proof of Work.

BUILDPRODUCTCONTENTCOMMUNITY

INDEX

04PROOF OF WORK

Numbers I can actually point at

Anyone can say they grow ecosystems. Here is what moved, and roughly how much.

4+

YEARS IN WEB3

DeFi, infrastructure, privacy, gaming, payments, emerging L1s.

7,600+

X FOLLOWERS

Grown by explaining ecosystems in public, not by farming engagement.

25+

ECOSYSTEM PROGRAMMES

Ambassador, contributor, growth and community roles across ecosystems.

1,000+

MEMBERS ONBOARDED

Community members brought through XORA onboarding.

REDBELLY CONTRIBUTIONA 10 WEEK PUSH
  • IMPRESSIONS
    100K
  • LIKES
    10K+
  • REPOSTS
    5K+
  • VIDEO VIEWS
    10K+
  • REPLIES
    100+
  • ARTICLES AT 15K+ IMPRESSIONS
    3+
  • NET NEW FOLLOWERS
    3K+

Roughly ten weeks of content, community and shipping inside one ecosystem. Not a campaign I ran for someone else — work I did because I was already in there.

WHERE

Redbelly, Arc, Plume, Union, Monad, XORA and others

HOW

Content, community, product, IRL, documentation

STILL

Doing all of it, mostly in public

05PROOF, NOT PROMISES

See what I have built

Seven things that are live right now. Every preview below is a real screenshot of the deployed product, and every link opens it.
  • LIVE PRODUCTS · 07
  • CHAINS · ARC / REDBELLY / RBNT
SCENE 01
01/ 07

FinFlow

Founder / Builder · ARC · CIRCLE USDC

LIVE2025

Stablecoin payments for the way money actually moves in Africa.

FinFlow takes USDC on Arc and builds the unglamorous, useful parts of payments around it: links you can send, invoices that generate themselves, batch payouts, payroll runs, escrow with real release conditions, live NGN / KES / GHS rates and a history that adds up. The line I wrote for it was “Stripe for crypto payments in Africa”. The point being that a freelancer in Benin City should not need to understand gas to get paid by a client in Berlin.

PROBLEM
Getting paid across borders is slow, and most payment tools assume you understand gas fees.
MY ROLE
Founder / Builder
RESULT
Live on Arc with Circle USDC — links, invoices, batch payouts, payroll and escrow in one product.

Payment links, invoices, payouts and escrow all run against Arc, with live NGN, KES and GHS rates on the dashboard.

  • USDC payment links
  • Invoices + PDF export
  • Batch payouts
  • Payroll runs
  • Escrow contracts
  • Recurring payments
  • Time-locked payments
  • Team wallets
  • Off-ramp path
  • Wallet connection
  • Payment history
  • Circle USDC on Arc
SCENE 02
02/ 07

VAULT 01

Design + Build · REDBELLY MAINNET · 151

A mint page for 500 Genesis tokens, 50 of them backed by physical watches.

VAULT 01 explores the seam between physical collectibles and onchain ownership. I built the mint interface around Redbelly Mainnet: chain validation, wallet connection, quantity control, a live total, real gas estimation and the transaction states people actually see when something stalls. It is EVM-compatible architecture doing a very simple job — letting someone own something without having to trust a spreadsheet.

PROBLEM
Physical collectibles still live on spreadsheets and trust, with no onchain record of what backs them.
MY ROLE
Design + Build
RESULT
Live Genesis mint on Redbelly Mainnet — 500 tokens, 50 of them watch-backed, chain ID 151.

Genesis drop: 500 tokens, 50 connected to limited-edition mechanical watches. Priced in RBNT with gas paid on top.

LIVE2025
  • EVM-compatible mint flow
  • Wallet connection
  • Chain validation · chain ID 151
  • Quantity + live total
  • Gas estimation
  • Transaction states
  • Collection metadata
  • Responsive Web3 frontend
SCENE 03
03/ 07

InfluenceFi

Founder / Builder · ARC · CIRCLE USDC

Brands hire creators. Creators get paid the moment the work is approved.

InfluenceFi holds USDC in escrow on Arc the second a brand hires a creator. Funds release when the work is approved, or automatically after 48 hours so nobody is stuck waiting on a slow approver in another time zone. Creator discovery, campaign collaboration, reputation and an onchain agreement underneath. The fee is 1% and that is the whole fee.

LIVE2025
PROBLEM
Creators wait on slow approvals and time zones for money that was already owed.
MY ROLE
Founder / Builder
RESULT
Live on Arc with USDC escrow and a 48 hour auto-release fallback, at a 1% platform fee.

Escrow releases on approval, with a 48 hour automatic fallback so creators are never held hostage by an inactive approver.

  • Creator discovery
  • Brand + creator profiles
  • Campaign collaboration
  • Onchain agreements
  • USDC escrow
  • 48h auto-release
  • Reputation
  • 1% platform fee
SCENE 04
04/ 07

Redbelly DAO

Design + Build · REDBELLY · RBNT

LIVE2025

A governance interface for a compliant L1 — and the build that won a bounty.

Redbelly is a compliant Layer 1 built for real world assets, and its community needed a place to actually govern it. I designed and built a DAO interface where the state of the network is visible before you are asked to vote: treasury, active proposals, open tasks, contributors. Three doors in — developers, DAO, institutional — and no dead ends. It won a Redbelly bounty, and the official Redbelly Network account posted it.

PROBLEM
The community had no single place to see the state of the network before being asked to vote.
MY ROLE
Design + Build
RESULT
Won a Redbelly bounty, and the official Redbelly Network account posted the build.

The interface leads with treasury, active proposals, open tasks and contributor count — the numbers a voter needs before reading a proposal.

  • DAO interface
  • Proposal interaction
  • Network pulse readouts
  • Wallet integration
  • Voting flow
  • Treasury + contributor surface
  • Responsive Web3 UI
SCENE 05
05/ 07

ChessHatch

Co-builder · Product & Frontend Contributor · BUILT WITH MALEEKSKIES

LIVE2026

Chess for the people who never got past the rules — lessons, a bot ladder and a live coach.

ChessHatch is a learning-first chess platform I co-build with Maleekskies. Most chess sites assume you already know what you are doing; this one starts at the board itself: a twelve-lesson beginner course, a nine-level bot ladder that unlocks one win at a time, pass-and-play with a live coach, and a landing page that plays the first three moves of a real game before handing you into the app. I work across the frontend and the product — landing page, lesson flow, bot progression, responsive layout and the QA passes that catch the rough edges before testers do.

PROBLEM
Most chess tools assume you already know how the pieces move, so beginners bounce before the first lesson.
MY ROLE
Co-builder · Product & Frontend Contributor
RESULT
Live in closed beta — lessons, the bot ladder and live matches shipped collaboratively with Maleekskies.

Every move a learner makes is validated against the live position with chess.js — an illegal move is refused, never advanced.

  • Motion landing page
  • Beginner lesson system
  • Nine-level bot ladder
  • Live coach feedback
  • Pass-and-play + vs computer
  • Responsive layout
  • React + Vite
  • Supabase auth + data
  • QA + UX fixes
SMALLER BUILDS

Two more that exist because something annoyed me. One is a token that cannot be farmed by bots. The other is the onboarding guide I kept having to write out by hand.

LIVE2026

TrustPass

06 / 07

Build · REDBELLY TESTNET · 153

A Sybil-resistant ERC-20 that only verified humans can mint.

Most Sybil resistance is a whitelist wearing a costume. TPASS does not keep a list at all. It reads Redbelly's native onchain identity infrastructure and gates the mint on verification state, so eligibility is a chain read rather than a spreadsheet someone has to maintain. Small, deliberate, and honest about what it can prove.

  • ERC-20
  • Onchain KYC gate
  • No centralized whitelist
  • Sub-8k gas eligibility check
  • Test coverage
  • Redbelly Testnet · chain ID 153
LIVE2026

KYC & Wallet Activation

07 / 07

Research + Write · REDBELLY

The onboarding document I kept having to paste into DMs.

KYC and wallet activation is where most newcomers to Redbelly stall, and the answers were scattered across docs, community channels and screenshots. I turned it into one linear path — verify, then activate — with every claim labelled by source so a reader can tell what is official and what is community-reported. This is the guide I use when I bring people in.

  • Two-phase flow
  • Source-labelled claims
  • Newcomer-first copy
  • Five recurring questions answered
  • Plain language
BOUNTY WONBOUNTY / 01

Redbelly DAO

governance interface

  1. DESIGN
  2. BUILD
  3. SHIP
  4. WIN

I designed and built a DAO interface for the Redbelly ecosystem. It won a Redbelly bounty, and the official Redbelly Network account posted it.

No trophy graphic. Just a build that went out and came back with a receipt.

RECEIPT2025 · VERIFIED
PROJECT
Redbelly DAO
TYPE
Governance interface
NETWORK
Redbelly · RBNT · chain 151
STACK
Next.js · TypeScript · Web3 UI
OUTCOME
Bounty won
RECOGNITION
Posted by @RedbellyNetwork

Designed and built end to end: information architecture, interface, wallet connection, proposal and treasury surfaces.

07STATUS BOARD

Currently building

A live board, not a highlight reel. This is where the time is going right now.

If you want to know what changed this week, ask me directly. The board moves faster than the website does.

08CAPABILITY

Four things, done together

No percentages. Nobody has ever hired someone because a bar was 90% full. Here is the work, grouped.

Products with real wallets, real chains and real transaction states.

  • React
  • Next.js
  • TypeScript
  • JavaScript
  • Tailwind CSS
  • Web3 frontend architecture
  • Wallet connection flows
  • EVM integration
  • Smart contract interaction
  • Solidity experimentation
  • USDC / stablecoin payments
  • Vercel
  • GitHub
  • AI-assisted development
STACK
FRONTEND
ReactNext.jsTypeScriptTailwindFigma
WEB3
EVMWallet integrationsSmart contractsUSDC / payments
CHAINS
ArcRedbellyCircle USDCPlumeMonadUnion
SHIP
GitHubVercelAI-assisted development
09IN PERSON

Some of this happens offline

I have hosted, planned and organised IRL events for different Web3 projects and ecosystems. Benin City, mostly: rooms with real people, first wallets, first questions, and the kind of conversation a thread cannot have.
Group photo of Benin City builders outside after a community meetup.
THE ROOM / BENIN CITY
EVENT ARCHIVE / 04 FRAMES
A large group of attendees posing together in front of a black sponsor wall covered in Web3 partner logos at an in-person community event.
COMMUNITY DAY / GROUP SHOT
THE JOB / IN PERSON
  • HOSTED

    On the mic and on the day: the room, the run of show, the questions that come after.

  • PLANNED

    Concept, format, venue and the guest list, well before anyone walks in.

  • ORGANISED

    Partners, logistics, first wallets and the follow-up once everyone has gone home.

ECOSYSTEMS SO FAR: ARC / PLUME / UNION / JUP

A host holding a phone while addressing a packed room of seated attendees at a community meetup.
ON THE MIC / FULL HOUSE
Five organisers standing arm in arm in front of a large portrait mural painted on the venue wall.
ORGANISERS / VENUE WALL
Two hosts seated on high stools either side of a speaker, beneath an {ARCHITECTS} Meetup banner during a community panel.
PANEL / ARCHITECTS MEETUP
HOSTED
Ran the room and the run of show
PLANNED
Concept, format, venue, guest list
ORGANISED
Partners, logistics, follow-up
ACTIVATED
Onboarding and first wallets in the room

HOSTED-EVENT ARCHIVE · HOSTED / PLANNED / ORGANISED

ROUTE / 04 COMPLETED · 01 OPEN
ROUTE PROGRESS
10TESTIMONY

What people say.

Feedback from ecosystems and teams I have worked with as an ambassador, tester and community contributor.
PlumeLEAD FEEDBACK

“Cyon, I agree with your bio. Ever since I brought you on board, I do feel as though we are now a well-seasoned entrée.”

Plume — Ecosystem Team
SwisstronikFEEDBACK

“Good job Cyon, good job — and keep working, Cyon.”

Swisstronik — Ambassador Program
MonadFEEDBACK

“Cyon caught issues in our testnet flow our own QA missed. That's the kind of feedback that actually ships fixes.”

Monad — Product Team
UnionFEEDBACK

“Every campaign Cyon touches gets more organic than paid. The community trusts him because he actually uses the product.”

Union — Growth Lead
PharosFEEDBACK

“We handed Cyon a rough dApp and got back a full report — bugs, UX friction, even copy suggestions. Rare to find that level of care.”

Pharos — Product Testing
CronosFEEDBACK

“Cyon doesn't just post about ecosystems, he understands them. His content answers questions before people even ask.”

Cronos — Community Team

REPRODUCED AS PROVIDED · NO EDITS

11METHOD

How I work

Five steps, repeated until the thing is good. This is the honest version, not the agency version.
  1. 01

    Find the problem

    Not the one in the pitch deck. The one that shows up when someone tries to actually use the thing.

  2. 02

    Build the first version

    Small, ugly, working. A wallet connects, a transaction lands, a number changes.

  3. 03

    Put it in front of people

    Real users, real rooms, real Telegram groups. Watch where they hesitate.

  4. 04

    Learn what breaks

    It is almost never the part I was worried about. It is the copy, the empty state, the wait.

  5. 05

    Ship again

    Then tell people about it properly. Shipping quietly is the most common way good work dies.

12CONTACT

Got something to build?

If you have a product, an ecosystem, a community or a strange idea that needs someone willing to get into the work — pick the closest door.
AVAILABLE FOROPEN TO BUILD

BUILD

  • Frontend / Web3 frontend
  • Web3 product building

GROW

  • Ecosystem growth
  • Ambassador programmes
  • Community growth
  • Developer relations

REACH

  • Content / social campaigns
  • IRL activations
  • Product + growth roles
BUILD SOMETHING

Let's talk product.

If you have a product that needs building — frontend, wallet flows, EVM integration, payment logic — I would rather see the messy version than the pitch.

DIRECTOPEN TO BUILD

Discord has no public handle link, so the handle copies to your clipboard instead.