n8n Automated Workflow: Built a production-ready n8n automation workflow that fetches data from a REST API, transforms and processes 100+ items, then splits into two parallel pipelines. The upper branch filters records by user, aggregates data per user, generates a CSV report, and writes it to disk. The lower branch prepares a full JSON export, saves all posts, builds a summary report, and writes it to file. Demonstrates API integration, data transformation, conditional filtering, aggregation, and automated file-based reporting, all orchestrated in n8n with zero manual intervention.
1
245
2Settle — a crypto-to-fiat payment engine I built (Node.js/TypeScript). Users pay in crypto and settle in local currency; it powers spend.2settle.io (https://spend.2settle.io) and chat.2settle, with $583K+ processed YTD. Multi-chain (BTC/ETH/Tron), HD wallets (BIP32/39/44), deposit monitoring, fraud detection, and fiat settlement. API + docs at api.2settle.io.
0
114
Architected and delivered a semi-decentralized USDT ↔ KRW trading platform, balancing centralized compliance controls with decentralized transparency to enable secure, real-world crypto–fiat exchange in a regulated market.
Co-designed a regulation-friendly transaction flow with product and compliance, enabling secure on-/off-ramp operations tailored to Korean financial regulations and reducing manual review overhead.
Led multilingual localization (Korean/English), expanding regional adoption and driving a 40% increase in active users within the first year of launch.
Optimized frontend performance and API design, cutting page load time by 35% and improving transaction completion rates through reduced latency and error handling.
Owned end-to-end development across React, Node.js, and MongoDB, ensuring production-grade scalability and reliability for high-volume financial transactions with sub-second response times.
0
55
"If money touches your system, a ledger should touch it first."
Your backend should be ledger-first by design.
If there's even a 0.00001% chance that money, balances, fees, commissions, credits, refunds, rewards, or anything involving an amount will flow through your system, every movement should be recorded in a ledger using double-entry accounting principles.
This isn't just for banks, fintechs, or payment processors.
Whether you're building:
=>A payment rail
=> An e-commerce platform
=> A marketplace
=> A grocery delivery app
=> A subscription service
You need to be able to answer:
> Where did this money come from?
> Where did it go?
> Who owns it right now?
> Why did this balance change?
> Can we prove it months or years later?
A ledger provides an immutable audit trail, complete traceability, and financial correctness. It eliminates balance drift, simplifies reconciliation, and gives your team confidence when investigating disputes or anomalies.
You don't need to hold funds to need a ledger. The moment your system represents value, tracks balances, calculates fees, records payouts, or reports financial activity, you're already dealing with accounting.
Design for auditability from day one. Retrofitting a ledger later is one of the most expensive engineering decisions you'll make.
1
222
Title:
Bella Vista Restaurant Website
Role: Project Manager
Bella Vista is a concept web project demonstrating my approach to managing website delivery. I defined project requirements, organized workflows, coordinated deliverables, and ensured the project met business and user experience goals.
Responsibilities
Project planning
Scope definition
Workflow coordination
Feature documentation
Quality assurance planning
Delivery management
1
137
