Full-stack audit and takeover of a DeFi trading and hedging platform
Client: A Dubai-based DeFi platform founder who moved delivery to Robral from a previous technology vendor.
- Industry
- Blockchain · DeFi
- Chain
- Base (Ethereum L2)
- Region
- Dubai, UAE
- Scope
- Contracts, backend, frontend
The challenge
The founder inherited a complex codebase from a previous vendor and needed an independent security and quality review.
The platform handles user funds: token swaps, limit orders, BTC-backed hedging, daily rewards and a five-level affiliate programme.
Upgradeable contracts, KYC-gated access and off-chain sync left room for hidden logic and access flaws.
What Robral did
Took over the full codebase and audited every layer: Solidity contracts, the Node.js backend and the Next.js frontend.
Reviewed contract logic, upgradeability (UUPS), role-based access, pausing, reward maths and Merkle-proof whitelisting.
Checked integrations with 1inch and Uniswap, wallet-signature login, KYC flows, event listeners and job queues.
Fixed the issues found directly in the code, then became the engineering owner for ongoing changes.
- 3 layerssmart contracts, backend and frontend, audited end to end
- 5upgradeable smart contracts reviewed
- ~2,200lines of Solidity examined
Outcomes
- An independent, end-to-end picture of the platform's security and code quality for the founder.
- Issues identified and remediated across contracts, backend and frontend.
- A clean handover from the previous vendor, with Robral as the accountable engineering partner.
Technology & capabilities
Platform stack
- Solidity
- OpenZeppelin (UUPS)
- Hardhat
- Node.js
- MongoDB
- Redis / Bull
- Next.js
- wagmi
- 1inch
- Uniswap
- Docker
Audit toolkit
- Slither
- Mythril
- Solhint
- Hardhat tests
- solidity-coverage
- SonarQube
- ESLint
Relevant forWeb3 founders taking over code from another vendor, or preparing a DeFi or staking platform for launch or a formal audit.
Delivered by Robral Technologies. Client identity is withheld; details are shared at a level that protects the client's confidentiality.
Facing something similar?
Tell us about your system. The usual first step is a 14-day proof of concept on one real slice.
Start a conversation
