Cryptographic Evidence · Solidity · Foundry · Research

Building cryptographic
evidence layers
for regulated procedures.

An open source laboratory documenting the journey of building provable off-chain and on-chain systems.

§ 01 · bunje.io

Open Source
Engineering Lab.

bunje.io is a personal lab for blockchain software engineering. Everything is built openly, documented publicly, and published on GitHub.

// What is built here

Smart Contracts — Solidity contracts for regulated workflows, public goods, and cryptographic evidence
Foundry — Testing, deployment, and debugging on EVM from day one
Open Source — Every repository is public. Every decision is documented.
Public Research — Architecture decisions, security considerations, and design tradeoffs published openly

// Approach

GitHub-first — Code, issues, and documentation live on GitHub from the start
Learning in public — Progress is visible. Mistakes are documented. No pretending.
No hype — Focused on cryptographic tools for real problems, deliberately staying away from DeFi, token speculation, and Web3 hype.
Infrastructure background — 20 years in regulated infrastructure informs every design decision

// Personal research. Does not reflect the position of my employer. No finished product. Learning by building. The GitHub repositories document the current state: early, honest, open.

§ 02 · Research

ETR · May 2026

Published in Eisenbahntechnische Rundschau (ETR), an established technical journal for infrastructure and transport.

ETR · Issue 5 / 2026

Blockchain in der Planfeststellung: Möglichkeiten für Effizienz und Nachvollziehbarkeit

Examination of cryptographic evidence mechanisms for regulated approval and infrastructure procedures.

  • A smart contract enforces formal procedural logic. The administrative decision itself stays with the authority.
  • Cryptographic integrity is not a feature — it is the prerequisite
  • The different phases of an approval procedure — modelled as a state machine on the blockchain
Journal Eisenbahntechnische Rundschau (ETR) Issue 5 / 2026 Author Klaus Walter · bunje Topic Infrastructure Governance · Blockchain

Klaus Walter: Blockchain in der Planfeststellung: Möglichkeiten für Effizienz und Nachvollziehbarkeit. In: Eisenbahntechnische Rundschau (ETR) 5/2026, DVV Media Group.

Journal at publisher →

More research in progress.

Architecture decisions, security considerations, and design tradeoffs will be published here as the projects evolve. Articles on state machine design, cryptographic evidence patterns, and lessons from applying blockchain to regulated workflows.

§ 03 · Current Focus

What I am building right now.

The stack is deliberately narrow: Solidity and Foundry until the fundamentals are solid, then Python for the verification layer.

03.1

Smart Contracts

active

Secure Solidity contracts, starting with access control, state machines, and workflow logic for regulated processes.

03.2

Foundry

active

Testing, deployment, and debugging with Foundry. Every contract has tests before it is deployed.

03.3

Python

planned 2027

web3.py for the off-chain verification layer: reading and checking hashes against the on-chain anchor, not just writing them.

Everything above is developed in public on GitHub. Code, decisions, and progress are visible from the first commit; there is no proprietary lock-in.

§ 04 · Projects

What is being
built and explored.

All projects are open source. Status reflects where each project currently stands — not where it is marketed to be.

04.1

Forsblock

research · prototype

Forsblock is the research protocol: cryptographic evidence for regulated approval and infrastructure workflows, modelled as state machines on-chain. ClaimWorkflow is the first application built on it, a workflow for claim and approval processes with a smart contract backbone, deployed on Sepolia testnet.

04.2

bunje-rwa-research

research · in progress

Two side tracks. One explores Real World Asset tokenisation and the cryptographic representation of regulated assets on-chain, where RWA meets infrastructure practice. The other is a smart contract protocol for claim and site workflow management, a state machine for structured, verifiable approval sequences.

04.3

protocol-engineering-lab

research · active

Protocol design experiments and architectural explorations. Where ideas are tested before they become contracts. Public from the first commit.

04.4

Python Toolkit

planned 2027

Planned web3.py tooling for the off-chain verification layer. Hashing documents, checking them against on-chain anchors. No code yet. The problem is clear, the timing is not.

All repositories on GitHub
Everything is open source
All work is experimental
§ 05 · Learning Journey

The timeline.
Honest.

This is where the learning actually stands. No retrospective polish — just the sequence as it happened.

§ 06 · GitHub

Every repository
documents the evolution.

The repositories are the product. Not polished demos — real code, real tests, real decisions. Including the dead ends.

github.com/bunje/buenje

Public repositories for every project stage.

Code is the documentation. Each repository includes Foundry tests, deployment scripts, and notes on design decisions. The commit history is honest — including the refactors and the mistakes.

  • Smart contract source code with full Foundry test suites
  • Deployment scripts for Sepolia testnet and local Anvil
  • Architecture notes and design decisions documented in the repository
Primary language Solidity Test framework Foundry Networks Sepolia · Anvil · Local License Open Source
View repositories on GitHub →
§ 07 · Research Project

Forsblock Protocol.
Experimental.

An experimental protocol exploring cryptographic evidence mechanisms for regulated workflows. A research project built in public, without a product or a company behind it.

Layer 01

Cryptographic Foundation

hashing · signatures · timestamps · merkle trees · audit trail · off-chain storage

SHA-256 hashing, digital signatures, qualified timestamps, immutable audit trail. Everything else is built on this layer.

Layer 02

Blockchain Infrastructure

ethereum ecosystem · layer-2 · protocol-neutral · on-chain anchoring

Public blockchain anchoring. Tamper-resistant, long-term verifiable, vendor-independent. Anchors the hashes from Layer 01.

Layer 03

Forsblock Protocol

ContractAnchor · PerformanceLog · ApprovalProtocol · EvidenceExport

Construction law translated into machine-verifiable state machines. Roles, workflow gates, variation order protocols, coded rather than described. Intended as an open standard.

Layer 04

ClaimWorkflow

solidity · foundry · role management · sepolia testnet

First application built on Forsblock. Cryptographic state machine for claim and approval workflows. Deployed on testnet, experimental.

The ClaimWorkflow state machine runs through five phases:

Phase 01

Submit

Submission, hash, anchoring

Phase 02

Review

Inspection, signature, timestamp

Phase 03

Negotiate

Bilateral, deadlines, protocol

Phase 04

Approve

Decision, both signatures

Phase 05

Prove

Export, auditable

// Construction law translated into machine-verifiable process logic · Forsblock Protocol · Klaus Walter / bunje · 2025–2026 · Experimental

Forsblock isn't for sale.

It's a research project, built in public because the problem is real and worth studying openly — not a product with customers or a token behind it. Anyone can read the code, challenge the design, or build on the concept.

§ 08 · Outlook

Agents need
verifiable ground truth.

The evidence layer is not an alternative to AI. It is the precondition that makes AI usable in regulated procedures at all: the record has to be verifiable before any inference on top of it is worth anything.

08.1

Plausible answers, unsafe ground

the problem today

Point an agent at a project folder and it finds seventeen versions, three file formats, and no record of which one was approved. It will still answer. That is the danger: the output reads confidently and cannot be checked.

08.2

Provenance before inference

the precondition

Hashes, timestamps and signatures turn a document into a checkable claim: this file, this state, this approver, this moment. An agent working against anchored data can cite evidence instead of producing prose.

08.3

Checking, not deciding

what becomes possible

Deadline monitoring, version conflicts, missing approvals, a Z0 in the Bautagebuch against a Z2 on the Lieferschein. Mechanical checks against a verifiable record. The administrative decision stays with the human, and that is the legal order, not a limitation.

08.4

Nothing built yet

not started

There is no agent code in any repository. This section describes a direction, not a feature. The off-chain verification layer (Python, planned 2027) comes first. Agents come after, if at all.

No language model is part of the Forsblock protocol.

The protocol produces verifiable records; whether an agent later reads them is a separate, open question with its own problems — liability, explainability, and the boundary between preparing a decision and making one. Building the evidence layer first is the whole point. An agent on unverifiable data reproduces the problem faster, it does not solve it.

§ 09 · About

Infrastructure engineer.
Learning Solidity.

Not a startup founder. Not a crypto native. An infrastructure engineer exploring how cryptographic software can improve evidence, transparency, and workflow integrity.

// Background

Dipl.-Ing. — 20+ years in transport infrastructure
Project management — Roads, urban squares, rail planning procedures
Procurement & contract law — HOAI, VOB, VgV, VwVfG, AEG. Lived practice, not textbook.
Traffic signal engineering — Development and control of traffic signal systems. The same state machine logic that now drives smart contracts.
Variation order disputes — Document preparation and fact reconstruction under pressure.

// Currently learning

Solidity · Foundry — Smart contract development on EVM. Started 2025.
Open Source — Building publicly from day one. GitHub is the primary output.
Python — Planned for 2027. web3.py for the off-chain verification layer.
Forsblock Protocol — Research project. Construction law as state machines on blockchain.

// Personal research. Does not reflect the position of my employer. No finished product. Learning by building. The GitHub repositories show the current state: early, honest, open.

If you are working
at this intersection.

Infrastructure practice meets cryptographic software engineering. If any of this resonates — write.

"Mein Gott, Walter…" — That is what colleagues said when I named a situation everyone knew but no one had articulated precisely. That is still the starting point of everything here.