Ankit BoghraMonyo Club

Building Monyo Club

Ankit Boghra

Co-founder & CTO, Monyo Club

Building the money layer for creators — the card, the payouts and the rails underneath. Before this I spent five years as founding frontend engineer at Polygon Labs, building the wallet, bridge, staking and developer tooling the ecosystem runs on.

Full-time on Monyo Club since May 2026.

Ink portrait of Ankit Boghra
142M+users on the Polygon dApps I architected and built
$4.4B+in DeFi assets secured by those products
3Mdaily transactions, at 99%+ network uptime
5+ yearsas founding frontend engineer at Polygon Labs

Creators run real businesses on payment infrastructure designed for salaried employees. Money arrives thirty to sixty days after the work, in the currency a platform chose, through rails that charge the most to the people earning the least. A creator in Lagos or Jakarta waits on banking hours in New York to get paid by an audience that never sleeps.

I do not think another dashboard on top of the same rails fixes that. The settlement layer itself has to change — brand budgets locked before the work starts and released when the campaign is verified, payouts that clear outside banking hours, and reward amounts small enough that fixed card fees make them impossible today.

And creators should never have to know any of that is happening. They should get a card that works at the grocery store, and money that shows up when they earned it.

That is Monyo Club: fiat-first on the surface, programmable underneath. I spent five years building products people trust with billions in assets they cannot get back if the interface is wrong. This is the same class of problem with a much better reason to solve it.

Fraud versus friction is the trade every payments product lives or dies on. I have already run it once, at scale.

Founding frontend engineer at Polygon Labs, September 2020 to January 2026.

I built Polygon’s core user-facing dApps from inception and set the frontend architecture and standards the team still works to — with a global, ambitious group shipping infrastructure people trust with billions. Three of those products, and what each one taught me.

Polygon Portal

Polygon Labs · Wallet & bridge

Led frontend development of Polygon Portal — the wallet and bridge — owning cross-chain transaction UX and reliability, and resolving critical asset-transfer failures affecting more than 100,000 monthly active users.

When your interface is the last thing between someone and money they cannot get back, correctness stops being an engineering value and becomes a product one.

  • 100K+ monthly actives
  • Cross-chain UX
  • Owned reliability

AggLayer SDK

Polygon Labs · SDK & bridge UI

Architected and owned the AggLayer SDK and its UI — a production-grade TypeScript SDK powering Polygon’s primary AggLayer bridge interface and letting ecosystem partners integrate and test native cross-chain bridging with zero-config defaults and strict type safety.

Infrastructure other teams build on is a different discipline from shipping screens. The interface is the contract, and you only get to design it once.

  • Production TypeScript SDK
  • Zero-config defaults
  • Partner integrations

Polygon Faucet

Polygon Labs · Frontend and backend

Designed and built a fully dynamic faucet dApp — frontend and backend — supporting any EVM chain, letting thousands of developers get testnet tokens through GitHub and X authentication with abuse prevention behind it. The naive fix for abuse is more verification and more waiting, which solves it by punishing everyone honest.

Fraud versus friction is the same trade every payments product lives or dies on. I have already run it once, at scale.

  • Any EVM chain
  • GitHub / X auth
  • Abuse prevention

The full engineering history — services, infrastructure and the rest of the shipped surface — lives on the work page.

What I believe about building, stated plainly enough to disagree with.

If you are considering joining the first five, this is the part that matters more than the logos above.

I ship the whole thing

Interface down to infrastructure — React and the product decisions on top; Node services, auth, SDKs, deployments, secrets, monitoring and on-call underneath. I built the faucet’s backend as well as its frontend, and stood up the observability the team ran incidents on. I do not hand a problem off at the API boundary and call it done.

Correctness before cleverness

Money products are judged on the transactions that fail, not the ones that succeed. I would rather ship a smaller surface that is right every time than a larger one that is right most of the time.

Speed comes from scope, not shortcuts

The fastest teams I have worked on were not the ones cutting corners. They were the ones ruthless about what did not get built this quarter. I ship weekly and I kill features out loud.

Say what is actually live

Every claim we make carries its real status — shipped, in beta, or on the roadmap. It costs a little conversion and it buys the only thing that compounds in a money product, which is being believed.

Small team, high trust

I have hired frontend engineers from intern through Staff and mentored most of them myself. I would rather have four who own outcomes than twelve who own tickets. If you need a process to know what to work on next, we hired wrong or I explained the mission badly.

Build with the users in the room

Creators are not a persona in a deck. They tell you exactly where the money hurts if you ask them, and they will tell you within a week whether what you shipped changed anything.

Notes on creator money, and building it.

First pieces are in progress — payment rails for creators, why attribution is broken, and what building Monyo Club is teaching me about both.

Follow along on X →

Investors, engineers, and creators who are tired of waiting to get paid.

Based in Dubai, UAE, building for creators everywhere. I read everything — fastest way in is email, and say what you want in the first two lines.