Spire explores a fair pricing model for Ethereum’s blob transactions using Shapley Values. By aggregating transactions and distributing fees based on marginal contribution, the model ensures participants pay less than they would alone while still supporting fast inclusion. This approach reduces costs, improves fairness, and aligns with Ethereum’s modular, scalable future.

We’re sharing a live public demo of the first based L3 appchain — now running on testnet. You can try it here: https://frontend.l3testnet.spire.dev/ This post breaks down what it is, why it matters, and where we’re headed next.Synchronously composability is unlockedA “based L3” is an appchain that is sequenced by underlying L2 — no centralized sequencer, no additional trust assumptions. This enables something powerful: synchronous composability with L2, just like a smart contract on L2. In th...

One of the core promises of rollups is scalability without compromising Ethereum's neutrality and decentralisation. But many rollups today still rely on centralised sequencers—entities with privileged access to ordering transactions. While efficient, this undermines the trust-minimised ethos that makes rollups attractive in the first place. At Spire Labs, we've been exploring a new approach to this problem with Based Rollups. As part of this journey, we're releasing our Based Stack. It's a fo...

At Spire, we're building the Based Stack — letting apps spin up their own based rollup L2s / appchains. As rollup ecosystems evolve, a new frontier is emerging — L3s built on top of existing L2s. This post explores how Spire’s approach, which combines shared settlement and coordinated sequencing, can extend beyond L2s, enabling rollups to function as synchronous execution environments. This architecture extends beyond traditional rollup sequencing models, offering faster, customizable intra-b...

IntroductionAs appchain adoption grows, there will be an increasing need for chains to opt-into having their blobs aggregated and compressed with blobs from other appchains. Aggregation carries the following benefits:appchains can submit transactions to their chosen DA layer more frequently. They no longer need to wait to have enough transaction data to fill a blob before submitting, or pay the cost of submitting partially filled blobs.appchains can use blobspace more efficiently, particularl...