The Verdigris Bureau: Office of Centennial Deposits

"High-Performance Creative Web Exploration"

A civic bureau seals your letter to 2126 under molten wax, witnessed. A civic bureau that seals letters for exactly one hundred years. Write a message to 2126, watch it set in wax, and receive your engraved certificate of deposit.

I built this project to test A civic bureau seals your letter to 2126 under molten wax, witnessed. A civic bureau that seals letters for exactly one hundred years. Write a message to 2126, watch it set in wax, and receive your engraved certificate of deposit. The core engineering challenge was sustaining uncompromised 60 FPS rendering using Canvas2D while handling continuous user interaction without framework overhead.

WHAT I WAS TESTING: I focused on two core engineering benchmarks:

Precision implementation of wax-seal SVG under continuous interactive user input

Sustained 60 FPS render performance and zero-dependency browser execution

THE TECHNICAL SIDE: Engineered directly in the browser with Canvas2D, Wax-seal SVG. The application runs without third-party frameworks or build-step dependencies, using hardware-accelerated rendering and custom event loops to achieve zero-latency response. Everything executes in the browser using Canvas2D, Wax-seal SVG. No third-party frameworks, no heavy runtime bundles, and zero external tracking.

WHAT I LEARNED: Balancing the mathematical rigors of wax-seal SVG with tactile browser interaction required tuning event throttling and memory allocation to eliminate all garbage collection stutters. Finding the sweet spot between mathematical precision and frame budget took careful profiling, but the result runs at a steady 60 FPS even on modest hardware.

TRY IT YOURSELF: The live build is deployed on Netlify. Open it in your browser, test the controls, and observe the render response times.

If you are building high-performance 3D, physics, or creative web systems and want to collaborate, reach out here on Contra.

Dynamic or static?

“Can you build this?” is usually the first question.

I like to follow it with: “What should it make easier?”

Booking a service. Buying a product. Managing an order. Finding an answer without opening five tabs.

That’s where the interesting work starts. Not with choosing a framework, but with understanding what’s getting in the way.

The goal isn’t just a finished website. It’s a useful one.

"Spot on, James! A website should solve a real business problem first—whether it's simplifying checkout or streamlining bookings. Tech stack comes second, UX and efficiency come first."