Research through code

Experiments

Small systems built to answer a technical question. I record the method, the evidence that exists today, and the boundary between a working result and an unfinished claim.

Voting escrow over a Polkadot light client

Prototype

Question: Can a browser application interact with a Substrate-based chain without treating a hosted RPC endpoint as its source of truth?
Method: Run Smoldot through Substrate Connect, connect the application with Dedot, and carry chain specifications into the browser for local consensus and finality verification.
Evidence: The repository contains light-client configuration, Substrate Connect hooks, chain specifications, account queries, transfers, staking, and voting surfaces.
Current limit: The implementation is public, but its repository documentation and reproducible evaluation still need to be brought up to the standard of the technical notes.

Read full experiment →Technical study →Integration note →Source ↗

Polkadot · Smoldot · Substrate Connect · TypeScript

Axon Cluster

Working prototype

Question: Can low-power machines securely delegate local AI inference to a stronger machine without exposing the cluster as a public service?
Method: Use a private libp2p network with a pre-shared key, Noise-encrypted transport, mDNS discovery, and a leader/subordinate request protocol backed by Ollama.
Evidence: The Rust implementation includes leader and subordinate modes, protocol framing, Ollama integration, an HTTP bridge, a web interface, and a recorded demo.
Current limit: The current design targets trusted devices on one local network; it does not claim Byzantine fault tolerance, public discovery, or multi-leader scheduling.

Read full experiment →Source and demo ↗

Rust · libp2p · Ollama · Local AI

Kaizen

Early exploration

Question: What are the minimum architectural boundaries needed to assemble an EVM-compatible Layer 2 node in Go?
Method: Separate node lifecycle, batching, execution, proof, and bridge concerns behind a small command-line node scaffold before committing to a proving or settlement design.
Evidence: The repository contains a Go CLI and initial packages for node composition, L2 batching, EVM execution, zero-knowledge proving, and an L1 bridge.
Current limit: This is a work-in-progress architecture scaffold, not a functioning rollup. Its proving, settlement, data-availability, and security claims remain unvalidated.

Read full experiment →Source ↗

Go · Ethereum · Layer 2 · Architecture