One coherent route from browse to claim
The product is intentionally narrowed around a single chain, portfolio-first claims, and a vault-like interface so the user sees fewer moving parts at once.

Fhenix-FairMarket
Auction Protocol
About
Fhenix-FairMarket is a privacy-first auction desk designed to feel calm, legible, and trustworthy even when the underlying protocol path is complex.
The product is intentionally narrowed around a single chain, portfolio-first claims, and a vault-like interface so the user sees fewer moving parts at once.
Mission
This product exists to make sealed-bid auctions feel operationally calm. The goal is not to expose every protocol concept on first contact, but to make each action legible: browse, bid, wait, settle, and claim.
That is why the interface now centers around quiet surfaces, wallet-aware routes, and portfolio-first outcomes instead of noisy dashboards or speculative price theater.
Why sealed bids
Bids stay sealed until the protocol can settle the lot, which reduces unnecessary signaling during the auction window.
Portfolio, marketplace, and settlement routes are organized around what the user can do next rather than protocol jargon.
One supported chain keeps wallet guidance, recovery language, and contract references predictable while the product hardens.
Technical view
The current release centers on a market proxy, settlement engine, slashed pot, and AVS-facing path, all kept on Sepolia so state transitions remain understandable while the platform hardens.
The live interface references the Fhenix coprocessor compatibility surface rather than forcing those details into every task screen. This keeps protocol depth available without crowding the primary user journey.
Current mode: reference
Trust links
Use the docs for architecture context, release notes, and deployment guidance.
Open referenceRepositoryBrowse the frontend, contracts, keeper flows, and the privacy milestones that shaped this release.
Open referenceExplorerThe market proxy stays visible on the block explorer so users can verify the release target directly.
Open referenceCompatibilityThe Fhenix compatibility reference explains the CoFHE context surrounding the confidential settlement path.
Open reference