Notes & experiments
The garden.
Things learned, ideas explored, and useful details kept along the way.
All notes
157–168 of 170
- Testing ERC-4337 in a local environment
A small account-abstraction experiment: a local chain, a bundler, a mock paymaster, and a Safe smart account.
Blockchain / Tools & experiments - Time-boxed habit stacks as an interaction pattern
A historical product note about grouping routine steps and giving each step a visible timer.
Tools & experiments - Tracing duplicate Android dependencies
Use the Gradle dependency graph to locate duplicate classes before applying a narrow exclusion.
Mobile & interfaces / Tools & experiments - Tracking route visibility in a Flutter application
A RouteObserver-based mixin that separates screen activation from application lifecycle events.
Mobile & interfaces - Understanding contract addresses: CREATE and CREATE2
Creation bytecode, constructor arguments, and the difference between a sender nonce and a deterministic deployment salt.
Blockchain - Uplifting: an earlier timed-routine app note
A historical product interaction centered on task lists, reminders, and per-step timers.
Tools & experiments - What an ERC165 interface ID actually identifies
Function selectors, interface discovery, and why a support response is a capability claim rather than proof.
Blockchain - What an HTTP proxy changes on macOS
An earlier proxy-settings experiment and the limits of checking only the visible public IP.
Cloud & systems / Tools & experiments - What Bitcoin WIF encodes
An older private-key encoding example, with network and compressed-public-key context.
Blockchain - When a dependency's syntax outruns the Webpack parser
An older WalletConnect build failure around optional chaining and a narrowly scoped esbuild-loader rule.
Tools & experiments - When an invisible Flutter container misses taps
A small historical hit-testing fix, with the widget-tree assumptions kept visible.
Mobile & interfaces - When Jenkins cannot find a command on an agent
Inspect the execution environment rather than assuming the interactive shell and build share a PATH.
Cloud & systems