Thread by @mraltantutar

Ethereum suffers from state and liquidity fragmentation, and extended finality times (12 minutes).

The Nuffle Fast Finality Layer (NFFL) @eigenlayer AVS, previously known as the NEAR Fast Finality Layer, is a solution to this.

Let's deep dive into how this works 🧵

NFFL is a universal, secure, and fast finality layer, enhancing interoperability between all L2s using EigenLayer security.

Applications can utilize the NFFL to build cross-chain applications that finalize in 3-4 seconds, improving cross-chain UX.

Well, how does this work?

How can one "pre-confirm" L2 state before it finalizes on Ethereum?

NFFL is a generalized solution.

When the transaction sequence is available on a decentralized data availability (DA) layer, EigenLayer operators could "pre-confirm" the state.

NFFL is not a shared/decentralized sequencer.

NFFL is a side-car product to any sequencer, regardless of the type of stack, and eventually the type of DA.

This makes NFFL highly-flexible, compatible to the changes that L2 stacks face every single day.

Rollups using NEAR DA, such as @rss3_ and many more to come, already post their sequence data to NEAR. They are automatically part of the NFFL network.

Those that don't post their DA to NEAR, @nufflelabs or the teams themselves could run relayers to post their data to NEAR.

Our team is working towards integrating other DA solutions to NFFL to make things easier in the long term.

We are planning to support @eigen_da, @AvailProject, and other DA solutions as the project matures!

Once the data is available on NEAR, the NFFL operators would read the posted block and run a full node to check and attest the current network state.

They will then send these attestations to the NFFL Aggregator.

These aggregated attestation are later served as an API, where applications could utilize this to build cross-chain applications.

Eventually, @nufflelabs team will be pushing the state roots to every different L2s, so applications looking to build cross-chain, they have everything they need by default.

This will be centralized at first, but relayers will get decentralized when the protocol matures.

What can I build with this though?

Pretty much everything:

1️⃣ I have several instances of the same applications on Optimism, Arbitrum, and I'd love to connect these two without impacting the user experience.

2️⃣ I have a social profile on @LensProtocol, and I'd like to use that to build an application on @blast.
3️⃣ I need to move fast across L2s to take advantage of the opportunities.
4️⃣ Anything that requires cross-chain logic and requires fast finality.

Bonus: The NFFL would be one of the users of the Unified Security Layer

https://x.com/mraltantutar/status/1814628953883037988

All of this is interesting to you?

Follow and turn notifications on for @nufflelabs for updates going to the NFFL mainnet.

Check our website and docs here: nuff.tech