Crypto Gloss

Puffer UniFi Litepaper (2024): Based Rollup Design

Puffer UniFi Litepaper is a project-authored design paper, Version 1.0 dated June 20, 2024. It proposes UniFi as an Ethereum based rollup built around Ethereum-layer-1 sequencing, validator preconfirmations, cross-rollup composability, and a native-yield model. This page summarizes that 2024 document; it is not a current implementation manual. For the broader project, see Puffer Finance.

The problem the paper describes

The authors argue that a rollup-centric Ethereum can scale execution while leaving liquidity, applications, and users spread across separate layer-2 networks. Each network may have its own sequencer, bridge paths, and developer integrations. The paper frames that fragmentation as a cost to users and builders, and asks whether rollups can share more of Ethereum’s transaction ordering and economic activity. This is the paper’s thesis, not a neutral measurement of every rollup.

Based sequencing and preconfirmations

A based rollup, also called an L1-sequenced rollup, uses Ethereum block proposers to order its rollup transactions. The 2024 paper proposes combining that sequencing with preconfirmations from Puffer validators. A preconfirmation is an earlier signed commitment about a transaction; it can improve perceived speed, but it is not the same thing as a sealed Ethereum block or final settlement. The paper describes a roughly 100-millisecond target. Ethereum Research explains the general based-rollup and preconfirmation concepts separately from Puffer’s specific implementation.

The proposal aims to reduce dependence on a single rollup sequencer and to align some transaction ordering with Ethereum. Those benefits depend on the rollup’s actual contracts, data-availability and proving choices, validator commitments, and operating setup. The term “based” alone does not prove that every security property of Ethereum is inherited.

Composability between rollups

The litepaper presents synchronous composability as a way for applications on compatible based rollups to interact with less reliance on delayed bridge transfers. It imagines a connected family of app-specific rollups around UniFi. This was a design goal in Version 1.0; it should not be read as a guarantee that arbitrary networks or contracts can interact atomically, or that bridge and execution risks disappear.

pufETH and unifiETH in the proposal

The paper connects rollup activity to Puffer’s staking and restaking design. It describes pufETH as Puffer’s liquid restaking token and presents unifiETH as a universal gas token intended to bring yield into the UniFi user experience. The document’s “gasless” framing means that costs would be subsidized or paid through the proposed system; it does not mean that validators, users, or applications face no economic cost. Token mechanics, yield sources, and deployed contracts must be checked against current documentation rather than assumed from a 2024 proposal.

How the 2024 paper differs from current documentation

Puffer’s current UniFi documentation describes an evolving product with based-OP sequencing, a Signal Service for L1-to-L2 composability, and gateway-based preconfirmations. Its RPC guide says a preconfirmed receipt can appear before a block is sealed and warns that state can be volatile during that interval. The current guide also directs users toward testnet onboarding. These are Puffer’s current product descriptions as checked on October 16, 2026; they are not independent performance or security audits, and the product may change.

Limits and risks to evaluate

  • Preconfirmation is not finality: users and applications need to understand what a commitment guarantees, who signs it, what penalties apply, and what happens before the block is sealed.
  • Rollup security is multi-part: sequencing does not by itself settle proof validity, data availability, upgrade control, bridge safety, or withdrawal assumptions.
  • Restaking and hardware assumptions: validator commitments, slashing rules, EigenLayer participation, and any trusted-execution or proving components add distinct dependencies and failure modes.
  • Economic design can change: the paper’s pufETH, unifiETH, and native-yield ideas are design claims from 2024, not a promise of a fixed return or current token behavior.

Social Media Sentiment

A small July 2024 discussion in r/ethereum introduced the litepaper. The post had seven votes in the captured discussion; one reader described the idea as promising while saying they still needed to examine how it worked and asking about the eventual user experience. This is a small early reaction to the proposal, not a measure of current or representative community sentiment.

Last updated: 2026-10-16

Related Terms

See Also

Sources