chore: add reference to related espalier paper

CHANGELOG.md

@@ -4,6 +4,8 @@ All notable changes to the EthSystems Map are documented here.
 
 ## [Unreleased]
 
+- docs: add Espalier preprint reference to [ZK Proof Systems](patterns/pattern-zk-proof-systems.md), [Post-Quantum Threats](domains/post-quantum.md), and [Safe Proof Delegation](patterns/pattern-safe-proof-delegation.md) `## See also` sections
+
 ## [0.4.0] - 2026-07-02
 
 23 commits, 166 files changed since [v0.3.0](https://github.com/ethsystems/map/releases/tag/v0.3.0) (Apr 2026). Major additions: resilience use cases (civic participation, disbursement rails, identity continuity), I2U protection patterns, pattern/approach schema v2 (strict flip) with CROPS and post-quantum analysis, domain reframing beyond FIs, and a Q2 2026 content QA audit.

domains/post-quantum.md

@@ -127,3 +127,4 @@ Ethereum inherits PQ transport encryption for some surfaces (Go 1.24 ships hybri
 - [NIST PQC standards](https://csrc.nist.gov/projects/post-quantum-cryptography)
 - [Ethereum PQ tasklist (ethresear.ch)](https://ethresear.ch/t/tasklist-for-post-quantum-eth/21296)
 - [How to hard-fork to save most users' funds in a quantum emergency](https://ethresear.ch/t/how-to-hard-fork-to-save-most-users-funds-in-a-quantum-emergency/18901)
+- [Espalier: succinct lattice arguments for client-side proving (Palmette, 2026)](https://palmette.xyz/espalier.pdf): lattice-based transparent proof system, preprint stage

patterns/pattern-safe-proof-delegation.md

@@ -101,3 +101,4 @@ A user holds shielded balances in a mobile wallet that cannot generate zero-know
 
 - [EIP-8182: Private ETH and ERC-20 Transfers](https://eips.ethereum.org/EIPS/eip-8182)
 - [Railgun](../vendors/railgun.md)
+- [Espalier: succinct lattice arguments for client-side proving (Palmette, 2026)](https://palmette.xyz/espalier.pdf): targets on-device proving that would reduce the need for delegation, but is a preprint with no public implementation

patterns/pattern-zk-proof-systems.md

@@ -84,7 +84,7 @@ Give designers a decision framework for choosing a zero-knowledge proof system o
 | PLONK over IPA    | Transparent           | No (EC)          | ~1 KB      | Medium      | Medium        | ZCash                                                                                                  |
 | STARK over FRI    | Transparent           | Yes (hash-based) | ~50-200 KB | High        | Medium        | [Miden](../vendors/miden.md)                                                                           |
 | Hash-based SNARKs | Transparent           | Yes (hash-based) | ~70-250 KB | High        | Medium        | Plonky3, Binius                                                                                        |
-| Lattice-based     | Transparent           | Yes (lattices)   | TBD        | TBD         | TBD           | Research stage (Latticefold)                                                                           |
+| Lattice-based     | Transparent           | Yes (lattices)   | TBD        | TBD         | TBD           | Research stage (Latticefold, Espalier)                                                                 |
 
 Benchmarks for Ethereum block-proving workloads are available at [ethproofs.org CSP benchmarks](https://ethproofs.org/csp-benchmarks). The table above reflects typical privacy-application proof characteristics; block-proving benchmarks differ in scale.
 
@@ -128,3 +128,4 @@ A privacy L2 uses pairing-based PLONK for transaction proofs today. To prepare f
 - [Post-Quantum Threats](../domains/post-quantum.md)
 - [Collaborative zk-SNARKs (Ozdemir & Boneh, 2021)](https://eprint.iacr.org/2021/1530.pdf)
 - [EthProofs CSP benchmarks](https://ethproofs.org/csp-benchmarks)
+- [Espalier: succinct lattice arguments for client-side proving (Palmette, 2026)](https://palmette.xyz/espalier.pdf): v0.9 preprint, no public implementation, prover figures self-reported