The problem I wanted to solve I ran into a weird provenance bug while building a “digital provenance” pipeline for release artifacts. We had cryptog...
I got curious about one annoying reality in software supply chains: even when you have a hash of a build artifact, that hash alone doesn’t prove what ...
I got tired of the same old provenance story: “we stored a hash on a ledger, so trust is solved.” In practice, that’s often incomplete—especially when...
The problem I wanted to solve: “Who touched the box, and when?” I got curious about a very specific failure mode in digital provenance: cold-storage ...
The problem I tripped over I was building a small DeFi workflow where an on-chain position (think: a vault deposit) had to be tagged with a provenan...
I got obsessed with one very specific problem after watching an on-chain approval flow go sideways: how can a DeFi app prove, cryptographically and wi...
The problem I ran into I got tired of “trust me” reconciliation when integrating a small DeFi setup across two chains. The rough situation was: - C...
The problem I wanted to solve I got tired of the same pattern repeating in smart-contract prototypes: off-chain code computes something, then on-cha...
The problem I kept running into I wanted a provenance trail that could answer two very different questions about a physical artifact: 1. “What is t...
The problem I ran into I was building a provenance pipeline where files (PDFs, videos, build artifacts) were stored off-chain (S3-like storage), but...
The problem I wanted to solve I kept running into a subtle DeFi reliability issue: many “time-weighted average price” (TWAP) oracles assume they can ...
The problem I ran into (and why it’s weirdly hard) On a weekend of tinkering with DeFi flashloan arbitrage (a flash loan is a loan that must be borro...
I got annoyed the first time I tried to build a “blockchain exporter” that writes ledger data into a database: the exporter would sometimes ingest the...
Why I got obsessed with “receipt memos” I stumbled into a weird bug class while building a decentralized provenance system: the smart contract would ...
I ran into a weird but real problem while tinkering with blockchain infrastructure: node operators (including me) often have “clean” logs—until you tr...
The itch that started this I kept seeing “audit trails” in DeFi described as events in logs—and every time I dug deeper, I found the same mismatch: ...
The provenance problem that kept bothering me I kept running into the same failure mode when building “digital provenance” systems: I could store ev...
The weird problem I ran into: “same event” across chains I was building a small “digital provenance” system where an event—like “sensor reading X is ...
I got curious about something that’s annoyingly under-explained in DeFi: how to build a time-weighted average price (TWAP) oracle without trusting a c...
The problem I stumbled into I spent a weekend trying to wire an ERC4626 vault into a DeFi portfolio and then feed its “share price” into an Aave v3 ...
The problem I wanted to solve I once had to prove that a printed, scanned receipt image hadn’t been altered between a vendor’s laptop and an offline ...