Irfan Maulana Akbar.

web3 + ai engineer

Building systems that replace trust with math, and routine with intelligence.

0+
years building
0+
contracts deployed
0
dex integrations
0+
projects shipped

Mine was simple: how do you build systems that no single person can control?

At Brawijaya University, I didn't just study computer science. I obsessed over consensus mechanisms, cryptographic proofs, and the idea that code could be law. While others built CRUD apps, I was reading Bitcoin whitepapers at 2 AM.

That obsession paid off early. In 2019, I won 1st place at the UNITY Software Development Competition, not because I was the best coder in the room, but because I was asking questions no one else was asking.

B.Eng Computer Science

Brawijaya University · 2017 → 2021

1st Place, Software Development Competition

UNITY 2019 · Yogyakarta State University

But curiosity without rigor is just noise. So I channeled it into research.

My thesis on blockchain-based health records wasn't theoretical. I built a working Ethereum DApp for inter-hospital data sharing, published in ACM's SIET '21 proceedings. It was small, it was specific, and it proved I could ship, not just speculate.

An Ethereum Blockchain Based Electronic Health Record System for Inter-Hospital Secure Data Sharing

SIET '21 · ACM Digital Library · DOI 10.1145/3479645.3479699

read the SIET '21 publication on ACM →

After graduation, I had a choice: join a big tech company and write internal tools, or dive into the deep end of an industry that was still figuring itself out. I chose the chaos.

DOT Indonesia

Blockchain Developer

Jun 2021 → May 2023

I started by asking: how do you let people invest together without trusting a central authority? The DAO I built was my answer: a smart contract system that pooled crypto investments with transparent governance rules. It taught me that blockchain isn't about hype. It's about replacing trust with math.

Then came the NFT marketplace: multi-chain transactions, 0x swap protocol integration, smart contract guidelines. Each feature was a brick. Each bug was a lesson.

DAO Multi-chain 0x Protocol Solidity

YCP Solidiance

Blockchain Expert

Feb 2022 → Jan 2023

The real test: a Japanese basketball team and an idol, both needing NFT marketplaces. Not prototypes. Real platforms with real fans paying real money.

I implemented ERC721A to cut gas fees and orchestrated credit card payments alongside crypto wallets. The lesson? Blockchain has to meet people where they are, not where the ideology says they should be.

~40%gas saved · ERC721A
2marketplaces shipped
JPhigh-profile clients

NFT Sakeworld & Dragonflies

High-profile NFT marketplaces for a Japanese basketball team and idol, with secure crypto + fiat payment integration on ERC721A.

visit the Sakeworld marketplace →
ERC721A Payments NFT Marketplace

By 2022, I wasn't just writing smart contracts. I was architecting entire systems. The question evolved: how do you make blockchain invisible enough that people forget it's there?

Shinta VR

Blockchain Backend Developer

Apr 2022 → Apr 2024

The answer came in the form of a metaverse. COSMIZE wasn't just an NFT collection. It was a virtual world on the Astar blockchain where users owned land, traded assets, and built experiences.

I worked directly with the CTO on the entire backend: custom RPC deployment, Chainsafe-Gaming wallet security, and smart contracts handling land ownership, asset trading, and governance. We were building the plane while flying it.

1stmetaverse on Astar
3DVR · cross-platform
CTOdirect collaboration

COSMIZE Metaverse

First metaverse project on Astar blockchain with custom RPC, smart contracts, and cross-platform wallet integration.

visit the COSMIZE metaverse →
Metaverse Astar Smart Contracts VR

Bitzaro Pay Sdn. Bhd.

Web3 Developer

Jun 2024 → Present

Then Bitzaro asked me to solve a harder problem: how do you make crypto wallets as easy as Venmo? I built a transaction indexer for their Wallet-as-a-Service platform. It listens to chain events in real time, indexes them, and exposes clean APIs for frontends.

Smart contract deployment scripts, automated testing, security hardening. The infrastructure layer. The part users never see but everything depends on.

WaaS Indexer Security

80&Co (Freelance)

Backend Developer · JS / TS

Nov 2023 → Jan 2025

Freelancing taught me precision. A Kyoto-based client needed WebSocket integration to sync on-chain and off-chain data in real time. I built the websocket layer, CRON services for missed events, and a GraphQL indexer. Every event captured. Every state consistent. No "close enough."

TypeScript WebSocket GraphQL NFT

By 2024, I saw the pattern. I'd spent years making systems autonomous on-chain. Now the same principle was emerging off-chain, with AI.

The question became: how do you automate not just transactions, but decisions?

layer a

Blockchain

Code that enforces rules. State that no one owns. Trust replaced with math.

layer b

AI

Code that makes judgment calls. Pipelines that learn. Routine replaced with intelligence.

ACRES

Web3 Fullstack · AI Infrastructure Engineer

Jun 2024 → Present

At ACRES I operate at two altitudes simultaneously. Down in infrastructure: perpetual trading bots executing across six DEX platforms (Lighter, Apex, Extended, Nado, Variational), each with their own quirks, rate limits, and failure modes. The bots don't just trade. They manage risk, handle outages, and adapt to market conditions.

Up in the intelligence layer: I fine-tuned Qwen 3.6 and Gemma 4 with Unsloth + LoRA on our internal codebases and trading logs, then ran inference locally across llama.cpp (with llama-server), Ollama, LM Studio, and MLX on Apple Silicon, depending on the deployment target. Everything performance-critical or sensitive runs on weights we own, bypassing API rate limits and keeping proprietary signals out of third-party providers.

On top of that sits the agent layer: Hermes agents handle orchestration, function calling, and structured outputs that drive code review and trade execution. I built the eval harness too: curated datasets, agent benchmarks, DPO loops to keep the models honest. Without evals, "AI infrastructure" is just vibes; with them, you actually know what your stack is doing.

This is the convergence. Blockchain proved code can enforce rules. AI proves code can make judgment calls, when you train and serve the models yourself instead of renting them. I'm building where those two forces meet.

6dex integrations
24/7autonomous bots
2models fine-tuned · Qwen / Gemma
llama.cppself-hosted inference

Chronologic AI Pipeline

Internal AI infrastructure pairing self-hosted Qwen + Gemma with Hermes-orchestrated agents, automating code reviews, documentation, and deployment workflows across the engineering team.

visit the Chronologic pipeline site →

Internal LLM & Agent Stack

Fine-tuned Qwen 3.6 + Gemma 4 with Unsloth/LoRA on internal data; served locally via llama.cpp, Ollama, LM Studio, and MLX on Apple Silicon. Hermes agents wired into engineering and trading workflows. Custom eval harness with DPO loops for continuous improvement.

Automated Perpetual Trading System

Cross-DEX trading bots with execution strategies, risk management, and automated airdrop farming.

Perp Trading Qwen 3.6 · Gemma 4 Unsloth · LoRA llama.cpp · llama-server Ollama · LM Studio · MLX Hermes Agents DPO · Evals

06 · handshake

The system is ready.

I've spent five years proving I can build systems at the intersection of risk and reliability: DAOs, metaverses, AI infrastructure. The pattern is consistent: take something complex, make it autonomous, make it trustworthy.

I'm currently seeking a role where that pattern can scale. Whether you're building the next layer of DeFi, automating engineering with AI, or bridging on-chain and off-chain systems, I want to talk.

initiate contact