---
title: "Merlyn Zawadi (@merlynz) | Hashnode"
description: "I build secure systems and scale them too. Read the latest articles by Merlyn Zawadi on Hashnode."
url: "https://hashnode.com/@merlynz"
---

@merlynz

# Merlyn Zawadi

@merlynz · Nairobi, Kenya · Joined May 2026

I build secure systems and scale them too.

### [Building GridLoqer's Real-Time Dashboard and Trustless Verification System](https://zawadi.hashnode.dev/building-gridloqer-s-real-time-dashboard-and-trustless-verification-system?utm_source=hashnode&utm_medium=feed)

This is the moment the entire system was built for. Open the GridLoqer dashboard. Navigate to the Verification Panel. Paste this JSON: { "session\_key": 9158, "driver\_number": 1, "interval\_start"

12 min read · [zawadi.hashnode.dev](https://zawadi.hashnode.dev/building-gridloqer-s-real-time-dashboard-and-trustless-verification-system?utm_source=hashnode&utm_medium=feed)

[Jun 3](https://hashnode.com/posts/building-gridloqer-s-real-time-dashboard-and-trustless-verification-system/6a2015e054e8a60fa0ed3d89)

### [Increasing Multi-Stack Delivery Velocity Without Sacrificing Integrity](https://zawadi.hashnode.dev/increasing-multi-stack-delivery-velocity-without-sacrificing-integrity?utm_source=hashnode&utm_medium=feed)

Consider the deployment problem from first principles. GridLoqer's production system runs three independent stacks: a Python FastAPI service for telemetry ingestion and verification, a Solidity smart

8 min read · [zawadi.hashnode.dev](https://zawadi.hashnode.dev/increasing-multi-stack-delivery-velocity-without-sacrificing-integrity?utm_source=hashnode&utm_medium=feed)

[Jun 3](https://hashnode.com/posts/increasing-multi-stack-delivery-velocity-without-sacrificing-integrity/6a20129a54e8a60fa0ebb0d9)

### [Security at the Seams](https://zawadi.hashnode.dev/security-at-the-seams?utm_source=hashnode&utm_medium=feed)

Protecting GridLoqer's Web2-Web3 Integrity Boundary

7 min read · [zawadi.hashnode.dev](https://zawadi.hashnode.dev/security-at-the-seams?utm_source=hashnode&utm_medium=feed)

[Jun 3](https://hashnode.com/posts/security-at-the-seams/6a200f9754e8a60fa0ea2b20)

### [Building an Oracle-Gated, Append-Only Telemetry Contract in Solidity (TelemetryRegistry.sol)](https://zawadi.hashnode.dev/building-an-oracle-gated-append-only-telemetry-contract-in-solidity-telemetryregistry-sol?utm_source=hashnode&utm_medium=feed)

TL;DR I built TelemetryRegistry so only one trusted oracle address can commit telemetry, and nobody can edit or delete history afterward. I prevent duplicate submissions with replay protection on th

10 min read · [zawadi.hashnode.dev](https://zawadi.hashnode.dev/building-an-oracle-gated-append-only-telemetry-contract-in-solidity-telemetryregistry-sol?utm_source=hashnode&utm_medium=feed)

[Jun 2](https://hashnode.com/posts/building-an-oracle-gated-append-only-telemetry-contract-in-solidity-telemetryregistry-sol/6a1e2592cb7a80b4b7a69b8d)

### [Building a Verifiable Data Pipeline from OpenF1 to Polygon](https://zawadi.hashnode.dev/building-a-verifiable-data-pipeline-from-openf1-to-polygon?utm_source=hashnode&utm_medium=feed)

A reliable race telemetry pipeline is not just about speed; it is about making the same input always produce the same output. Canonical JSON (JavaScript Object Notation) and keccak256 hashing give us

11 min read · [zawadi.hashnode.dev](https://zawadi.hashnode.dev/building-a-verifiable-data-pipeline-from-openf1-to-polygon?utm_source=hashnode&utm_medium=feed)

[Jun 1](https://hashnode.com/posts/building-a-verifiable-data-pipeline-from-openf1-to-polygon/6a1e0343cb7a80b4b79898d7)
