feat: add "Exploring Hardened Shielded Pools" blog post

[Meyanis95]

Blog writeup — "Exploring Hardened Shielded Pools" — building on the shielded-pool-extension PoC. It covers epoch nullifiers (bounding on-chain nullifier state) and PIR (private commitment-path reads), and frames private selection as the harder problem that remains.

Addresses all inline + issue threads from @oskarth and @rymnc (accuracy, wording, and a voice pass), plus a follow-up annotation round.

Notes for reviewers

• Retitled from "The Next Iteration for Private Payments" during review — more neutral and technical, per @oskarth.
• Hero image is included in this PR at public/assets/images/2026-06-11-next-iteration-shielded-pools/hero.png, matching the frontmatter image: path. (Supersedes the earlier description, which pointed at a …next-generation-… path and said the asset was missing.)
• Publish gating is now enforced in code, resolving @oskarth's note that published: false was silently ignored. A shared isPublished helper (src/lib/posts.ts) filters the blog index, homepage latest-posts, and static path generation by the post's date, compared as a full timestamp (hour + timezone aware). The published flag was removed; date is the single source of truth.
• Release: the post is dated 2026-06-11T07:00:00-04:00, so it stays out of the build output until a build runs at/after 7am ET on June 11. Merge anytime — it stays hidden — then publish by triggering a build at/after the cutoff (push to main, or run the Deploy workflow via workflow_dispatch).
• PoC link points at the shielded-pool-extension path on master (iptf-pocs PR #74); confirm once it merges.

[oskarth]

Minor: the PR description looks stale. It says the hero image should be added at 2026-06-11-next-generation-shielded-pools/hero.png and that the asset is not in the PR, but the diff now includes public/assets/images/2026-06-11-next-iteration-shielded-pools/hero.png, which also matches the frontmatter. Worth updating the description before merge so reviewers do not chase the wrong path.

[oskarth]

Overall looks good, some general comments and also on language

[oskarth]

High-level style note: I think this needs one more voice/humanizer pass before publishing. The technical throughline is good, but parts of the piece still read a bit too polished/AI-shaped: broad framing phrases, abstract transitions, and explainer metaphors that sound smooth but make the argument less precise.

Examples are the lines already called out: the title/description feel a bit salesy, “the cleanest picture is a librarian,” “the catch, and it matters in a minute,” and “That is exactly the question...” Similar patterns show up later in phrases like “same problem wearing two hats,” “small toolbox,” “where this leaves us,” and “two fronts that are starting to meet in the middle.”

I’d suggest a pass that makes the piece more concrete and R&D-native:

• use more technical nouns in the title/description: PIR, epoch nullifiers, private selection
• replace generic bridge phrases with direct claims
• reduce metaphors where they obscure the mechanism
• make the final thesis sharper: the PoC solves known-index private reads and bounded active nullifier state, but exposes private selection as the harder remaining problem

[Meyanis95]

Thanks for the comments; addressed all threads. Highlights:

• Retitled to "Exploring Hardened Shielded Pools"; description rewritten around the mechanisms (epoch nullifiers, PIR, private selection) + a voice pass throughout.
• Accuracy: "billions in value" → transaction volume; light-client claim reframed as target design with a PoC caveat (RootVerifier port; e2e trusts a dev stateRoot); corrected the read-side framing (wallet knows the index, fetches the path).
• Wording: FOCIL, "remember it forever", Groth16 de-anthropomorphized, generic node provider, "per-database hint" gloss, hashUp → root_from_path, PIR acronym, Kohaku link, numbered open problems.
• Publish gating: published: false was silently ignored — replaced with real date-based gating (src/lib/posts.ts, applied to blog index, homepage, and static paths). Post is dated 2026-06-11T07:00:00-04:00 and stays out of the build until then.