Blockchain Engineering • Technical Insight
Bagaimana Saya Membangun KVP Protocol: Perjalanan Arsitektur Layer-1 (2015-2026)
Oleh Hendri Rahmat Hendrianto • Diperbarui 25 Apr 2026
KVP Protocol (Krakenum Chain) adalah inisiatif Layer-1 yang saya bangun dengan fokus utama pada deterministic monetary rules, predictable execution, dan arsitektur yang siap untuk production-grade fintech workflows. Artikel ini menjelaskan bagaimana arsitektur berkembang dari versi awal hingga pendekatan terbaru.
Phase 1: Fondasi di Go (2015-2020)
Fase awal dibangun di Go untuk mempercepat eksperimen node runtime, ledger behavior, dan model distribusi ekonomi. Tujuan utamanya: validasi core principle bahwa aturan ekonomi harus ditegakkan di level protokol, bukan hanya di aplikasi.
- Genesis and bucket-based distribution model
- Append-only transaction logging approach
- Node runtime and basic network synchronization model
Phase 2: Pematangan Protokol di Rust (2020-Sekarang)
Saat kebutuhan reliability dan determinism naik, saya migrasi core architecture ke Rust. Fokusnya adalah meminimalkan unpredictable behavior dan memperkuat state transition guarantees di environment multi-node.
- Deterministic state machine and canonical state commitment
- Leader/follower topology with snapshot by height
- P2P sync validation on devnet between Node A and Node B
Mengapa Ini Penting untuk Produk Nyata
Layer-1 architecture bukan sekadar eksperimen teknis. Protokol harus bisa terhubung dengan use case nyata: payment infrastructure, settlement flow, dan interoperable service layer untuk Web2+Web3 products.
Project Impact Snapshot
- Membangun dan mengembangkan arsitektur protokol dari 2015 hingga 2026
- Berkontribusi pada ekosistem payment yang memproses 50.000+ transaksi
- Selaras dengan sistem API produksi dengan 133 endpoint terdokumentasi
Repositori Publik vs Arsitektur Saat Ini
Repositori publik yang tersedia merepresentasikan arsitektur terdahulu (deprecated path). Untuk arsitektur terbaru sejak 2024, akses source disimpan private untuk perlindungan IP dan keamanan sistem.
Tanya langsung via email • ← Kembali ke portfolio
Blockchain Engineering • Technical Insight
How I Built KVP Protocol: Layer-1 Architecture Journey (2015-2026)
By Hendri Rahmat Hendrianto • Updated Apr 25, 2026
KVP Protocol (Krakenum Chain) is a Layer-1 initiative I built with a primary focus on deterministic monetary rules, predictable execution, and an architecture ready for production-grade fintech workflows. This article explains how the architecture evolved from its early form to the current approach.
Phase 1: Foundation in Go (2015-2020)
The early phase was built in Go to accelerate experimentation with node runtime, ledger behavior, and economic distribution models. The primary goal was to validate a core principle: economic rules must be enforced at the protocol level, not just the application layer.
- Genesis and bucket-based distribution model
- Append-only transaction logging approach
- Node runtime and basic network synchronization model
Phase 2: Protocol Maturation in Rust (2020-Present)
As the need for reliability and determinism grew, I migrated the core architecture to Rust. The focus was on minimizing unpredictable behavior and strengthening state transition guarantees in a multi-node environment.
- Deterministic state machine and canonical state commitment
- Leader/follower topology with snapshot by height
- P2P sync validation on devnet between Node A and Node B
Why This Matters for Real Products
Layer-1 architecture is more than a technical experiment. The protocol must connect to real use cases: payment infrastructure, settlement flows, and an interoperable service layer for Web2+Web3 products.
Project Impact Snapshot
- Built and evolved protocol architecture from 2015 to 2026
- Contributed to payment ecosystem handling 50,000+ transactions
- Aligned with production API systems across 133 documented endpoints
Public Repository vs Current Architecture
The available public repository represents deprecated architecture (2015-2024). The latest architecture from 2024 onward is kept private for IP protection and system security.
Ask personally via email • ← Back to portfolio