Puffer primary-source snapshot

Last reviewed: 2026-04-27 UTC

Project status snapshot

URL: https://www.puffer.fi/
Key takeaways:
- The homepage no longer presents Puffer as just a liquid restaking token or staking app; it foregrounds four major surfaces: Liquid Restaking, UniFi Based Rollup, UniFi Preconf AVS, and Puffer Institutional.
- This is the clearest high-level sign that Puffer should be categorized as broader Ethereum infrastructure rather than only a restaking protocol.
- The current public surface explicitly spans consumer/staker flows, L2 infrastructure, preconfirmation middleware, and institutional Ethereum operations.

URL: https://docs.puffer.fi/
Key takeaways:
- The docs homepage mirrors the multi-product structure and gives four main buckets: yield / liquid restaking, UniFi based rollup, Puffer Preconf, and institutional solutions.
- This confirms that the project’s own documentation treats these as live first-class surfaces, not just roadmap experiments or marketing sub-brands.
- The docs site is therefore a better source of truth for current categorization than older market memory of Puffer as only an EigenLayer-era restaking project.

URL: https://docs.puffer.fi/yield/intro
Key takeaways:
- Puffer describes itself as a decentralized native liquid restaking protocol built on EigenLayer.
- The docs emphasize permissionless validator participation, native restaking, capital efficiency, validator tickets, and the pufETH liquid restaking token.
- A notable claim is that NoOps can operate with 2 ETH of collateral while stakers fund the remaining validator capital, which is central to the protocol’s differentiation.

URL: https://docs.puffer.fi/puffer-preconf/puffer-preconf-intro
Key takeaways:
- Puffer Preconf is described as an EigenLayer-based preconfirmation service offering ~100ms execution preconfirmations for Layer 2 rollups, backed by 3M ETH of restaked security.
- The docs frame this as a gateway-based architecture where validators delegate to gateways, preconf rights are scheduled through a lookahead mechanism, and slashing / refunds are part of the safety model.
- The most important categorization signal is that Puffer is not only earning/restaking infrastructure; it is also building transaction-execution middleware for rollups.

Sources:
- https://www.puffer.fi/
- https://docs-unifi.puffer.fi/
Key takeaways:
- The homepage calls UniFi a based rollup offering instant L1 withdrawals and sub-second transactions.
- Even without diving deeply into the separate UniFi docs in this pass, the current first-party framing makes it clear Puffer operates an L2 product, not merely an auxiliary staking layer around Ethereum.
- This matters for the library because it makes Puffer a multi-layer infrastructure project spanning staking, rollup, and preconfirmation surfaces.

Sources:
Key takeaways:
- Puffer markets an institutional Ethereum infrastructure surface in addition to its user-facing protocol surfaces.
- This suggests the company is also trying to capture validator-operations and enterprise infrastructure demand, not only protocol-native token flows.
- Even if the technical detail is lighter in this pass than for yield/preconf docs, it reinforces the “multi-surface Ethereum infrastructure” categorization.

URL: https://github.com/PufferFinance
Key takeaways:
- The official GitHub organization is public and linked directly from the site and docs.
- This is useful as a first-party engineering surface for future follow-up on contracts, audits, and implementation repos.
- For this pass, the main value is confirming that the product suite is backed by an active public development identity rather than by marketing-only surfaces.

No single canonical “Puffer” whitepaper was found in this pass that cleanly covers the entire current product stack.
The strongest current primary-source corpus is the website plus the docs portal, especially the yield and preconf sections.
In practice, the docs are a better source of truth than any single paper because the project has expanded into multiple product layers.

Best current category for the library: Ethereum staking / liquid restaking / based-rollup / preconfirmation infrastructure.
Key categorization insight: Puffer should be understood as a multi-product Ethereum infrastructure platform, not just a liquid restaking protocol.
Another useful note for future scouting: Puffer’s current architecture story likely needs to be reconstructed across multiple docs surfaces (yield, UniFi, preconf, institutional) instead of from one protocol paper, which makes it a good example of a product suite whose identity has broadened over time.