CNX Network DeFi ecosystem
As CTO, I grew a DeFi ecosystem from 10k to 40k+ users and $400k+ revenue: token contracts, a multi-chain wallet, a token swap service, a launchpad, an authenticator and a chat app, across web and mobile.
- 01Web & mobile apps
- 02Node.js backends (WalletX, swap, chat)
- 03Ethereum · BNB Chain · Bitcoin
- 04CNX token contracts
Problem
CNX had a token and a community, but needed a whole product ecosystem around it: somewhere to hold and send assets, a way to buy the token, a launchpad, account security and a place to talk. All of it had to work on web and mobile while the user base grew fourfold, with one technical owner across contracts, backends, apps and blockchain nodes.
What I built
- ERC20 / BEP20 token contracts and their deployment on Ethereum and BNB Chain.
- WalletX: the backend for a multi-chain mobile and web wallet covering Ethereum, BNB Chain and Bitcoin (legacy and SegWit).
- A token swap service that watches incoming BNB payments, verifies each transaction and sends CNX tokens automatically.
- A launchpad website for token presales and swaps with MetaMask and WalletConnect.
- An authenticator app (like Google Authenticator) for time-based one-time codes.
- Metachat: a chat app backend with phone-number OTP sign-in, chats and media uploads.
- Blockchain node management, Docker builds and CI/CD to Azure for every service.
Stack
- Solidity
- ERC20 / BEP20
- Node.js
- Express
- ethers.js
- web3.js
- bitcoinjs-lib
- MongoDB
- Docker
- Azure
- GitHub Actions
Result
- Users grew from 10,000 to 40,000+ (about 4×).
- $400k+ in revenue.
- Wallet, swap, launchpad, authenticator and chat products on web and mobile, sharing one set of contracts and backends.
Engagement
Multi-year CTO engagement
My role
I joined CNX Network in 2021 as lead blockchain developer and served as CTO until 2023. I owned the technical side end to end: smart contracts, backends, web and mobile apps, blockchain nodes and deployment. During that time the user base grew from about 10,000 to more than 40,000, and the ecosystem passed $400,000 in revenue.
WalletX: a multi-chain wallet backend
WalletX was the centre of the ecosystem, the wallet users held CNX in, available as a mobile app and a web version. I built the Node.js / Express backend behind it:
- Wallet creation and import for EVM accounts (new wallets, mnemonic phrases or private keys) and for Bitcoin, in both legacy and SegWit address formats.
- Balances across chains: native ETH, BNB and BTC plus ERC20 / BEP20 tokens, with batched balance requests so a full portfolio loads in one call.
- Sending: native coins, tokens and Bitcoin, including fee estimates before a user confirms.
- Transaction history per coin and per token, pulled from Etherscan and BscScan with a faster path for large histories.
- Live prices from Binance, refreshed every five minutes, so balances show their USD value.
- Two-factor security with time-based one-time codes, plus request validation on every endpoint.
The services were containerised with Docker and deployed to Azure through GitHub Actions.
Token swap: pay in BNB, receive CNX
To let people buy the token without a manual step, I built a swap backend. A user sends BNB to the project wallet and submits the transaction; the service checks it on-chain, makes sure the same transaction hash can never be paid out twice (stored in MongoDB), works out the CNX amount at the current rate and sends the tokens. It ran as a Node.js cluster across all CPU cores, with separate testnet and mainnet configurations.
Launchpad, authenticator and chat
- Launchpad: a presale and swap site for buying tokens, connecting through MetaMask or WalletConnect.
- Authenticator: an app in the style of Google Authenticator for time-based one-time codes, used to protect accounts.
- Metachat: the backend for a chat app, with phone-number sign-in by one-time code (Twilio / MessageBird), user profiles, chats and media uploads (Cloudinary), on MongoDB.
What I’d point to
The interesting part wasn’t any single contract. It was keeping a whole product family, three chains and two platforms consistent while the user base quadrupled: shared contracts, shared backend patterns, repeatable deploys, and security (2FA, validation, duplicate-payment protection) built in from the start rather than added after an incident.