Orchard Poseidon collision frontier proposal
A proposal to build a public collision-search scoreboard for the Poseidon instance used in Orchard. It states that a collision would not immediately break Orchard.
HashSmash publicly runs a collision frontier for hash functions. It tracks how far the search has progressed for two different inputs that produce the same output, against fully specified fixed instances. The proposal has two targets: one is aligned with the Ethereum Foundation's 2026 Poseidon Initiative bounty, and the other, Target B, is the P128Pow5T3 Poseidon instance deployed in Orchard.
Target B's parameters are the Pallas base field, width 3, an x^5 S-box, R_F = 8 and R_P = 56. It is pinned to halo2_poseidon 0.2.0, which the orchard crate depends on, and verified against the official Zcash test vectors. Section 4.1.2 of the Zcash protocol specification requires PRF^nfOrchard, that is, PoseidonHash(nk, rho) in section 5.4.2, to be collision-resistant for all keys. The public frontier does not take this requirement as an assumption but provides a continuously verifiable measurement.
The author makes the scope clear. A collision on this track would not by itself break Orchard. Section 8.4 of the specification states that Orchard's Faerie Gold resistance depends only on discrete-log hardness, and section 5.4.1.10 argues that the nullifier construction is secure under DDH even if the Poseidon PRF is weaker than expected. Section 5.4.1.10 also notes that existing Poseidon cryptanalysis has focused on the x^3 S-box and that the deployed round counts have a considerable security margin.
This proposal does not claim a break but measures the security margin. The author says they independently regenerated the halo2_poseidon constants and reviewed the subspace-trail results, and especially asks the protocol team for corrections and opinions on parameters, citations and wording. The full technical details are in Discussion #380 of Layr-Labs/hash-smash.
This summary is based on the original; check the original for exact details.