Tallinn (PtTALLiNt)

This is a joint post from Nomadic Labs, Trilitech, and Functori.

We are pleased to introduce our next Tezos protocol upgrade proposal. Destination: Tallinn!

As usual, the “true” name of the proposal is its hash: PtTALLiNtPec7mE7yY4m3k26J8Qukef3E3ehzhfXgFZKGtDdAXu

The command to inject or upvote the proposal via the Octez client is:

octez-client submit proposals for <baking_key> PtTALLiNtPec7mE7yY4m3k26J8Qukef3E3ehzhfXgFZKGtDdAXu

The Tallinn proposal builds on features introduced in recent upgrades and focuses on lower latency, faster finality, leaner consensus, stronger security, and improved on-chain efficiency.

The main changes are:

  • 6-second block time: Lower latency and faster finality for a smoother overall experience.
  • All bakers attest every block (once at least 50% use tz4): Stronger security, less load on nodes, and more predictable staking rewards.
  • Address Indexing Registry: Improved efficiency and lower storage costs for Michelson apps.

Below, we expand on the proposed changes. For more technical details and additional minor changes, see the Tallinn proposal’s changelog. Note that the proposal also introduces breaking changes, listed here.

6-second block time

Continuing the trajectory of previous upgrades – and taking another step on the Tezos X roadmap – the Tallinn proposal reduces Layer 1 block time from 8 seconds to 6 seconds.

Shorter block times mean lower latency and faster finality. With Tallinn, Tezos’ two-block finality on Layer 1 would be reduced from 16 seconds to just 12 seconds.

Layer 2 solutions such as Etherlink also benefit, as data publication for Layer 2 is secured through inclusion in Layer 1 blocks. Interchain bridging benefits in a similar way.

The 6-second block time is achieved without increasing hardware requirements for bakers. Keeping validation accessible to everyone is key to maintaining a broad validator set for genuine decentralization and censorship resistance.

For more information about how the 6-second block time has been tested, see this post.

All bakers attest every block (once at least 50% use tz4)

The recent Seoul upgrade made it possible to aggregate hundreds of attestations into a single signature in each block, using the BLS signature scheme behind tz4 addresses.

Besides enabling drastic on-chain efficiency gains, aggregation also makes it possible to switch to a new approach to attestation: Having all bakers attest to every block instead of a limited subset of bakers.

With aggregation, more attestations will not consume more block space, and having all bakers attest brings several benefits:

  • Stronger security: All bakers participating in consensus for each block improves robustness and fault tolerance.
  • Predictable rewards: Attestation rewards become directly proportional to baking power, eliminating randomness from attestation committee selection.
  • Leaner consensus: Removing selection logic lightens the load on nodes, enabling even shorter block times and more streamlined validation.

The Tallinn protocol proposal implements this change, but the feature will only activate once at least 50% of bakers use tz4 addresses. This is to ensure a smooth transition with bakers setting the pace.

Once active, the feature remains enabled, even if participation dips later. Baking from tz1/tz2/tz3 addresses will still be possible.

We remind bakers that current Ledger hardware signers are unable to process tz4/BLS signatures fast enough for Tezos consensus needs. However, tz4-compatible alternatives have been introduced, including Tezos RPi BLS Signer, TezSign, and Signatory.

For more details on the switch to all bakers attesting, see this post.

Address Indexing Registry

The Tallinn proposal also introduces the Address Indexing Registry for Michelson apps.

The registry can greatly reduce contract storage footprint, especially for NFT contracts and other large ledgers, by eliminating redundant address data. Instead of each token contract storing full addresses repeatedly, each address is stored once and assigned a compact numeric ID, cutting storage needs by up to 100x for some contracts.

Existing contracts will need to be updated to make use of this feature, but doing so benefits both the contract owners and the network as a whole.

  • Cost-efficiency: Large NFT collections and token contracts become much cheaper to operate.
  • Network-wide efficiency: The network-wide storage footprint grows more slowly.
  • Higher throughput: Smaller operation size means more operations fit in each block.

While the Tallinn proposal introduces this registry on Layer 1, the mechanism will also be available on Tezlink, the upcoming Layer 2 for Michelson apps.

To learn more about the Address Indexing Registry, see this post.

Next steps

We encourage developers, bakers, and ecosystem teams to test their applications and tools on the dedicated test network, Tallinnnet, which will be live soon. We are happy to answer questions and receive feedback in the Tezos Discord.

A release candidate for Octez v24.0, which contains the Tallinn protocol, as well as general improvements, will be published shortly.

The proposal period ends on November 29. Don’t forget to vote!

If adopted, the Tallinn proposal would activate in early 2026, which is shaping up to be a pivotal year for Tezos. The changes in Tallinn streamline Layer 1 to ensure a fast, secure, and efficient consensus layer underpinning the next-level blockchain experience envisioned with Tezos X.

As always, with no compromise on decentralization.

Let’s go to Tallinn!

I’m a little stressed out regarding the BLS signer stuff :sweat_smile: What exactly will happen if I continue to bake with my current setup? I will upgrade, but would feel more comfortable if I knew that it would still keep working if we reach 50% before I have had time to switch to BLS :see_no_evil_monkey:

1 Like

I was in the same spot as well, BUT the switch was way easier than I expected.

What’s holding you back from moving to the BLS? If it’s just access to the hardware, that makes sense, I know they’re not always easy to find. I’m just trying to understand what feels like the pain point, because the upgrade really does give you something better, open source, and ready for future network improvements.

As for your question: from what I know, the Ledger setup should keep working for quite a while. It just depends on your model, eventually you might start missing more attestations as the network demands more speed for the signer.

1 Like

Honestly just the mental overhead from having to revisit my setup and figuring out how to switch to BLS :sweat_smile: I have a custom signer, which I have been working on to support BLS but it’s still not working properly :see_no_evil_monkey: So either I have to work more on that (which is what I want and should) or I need to switch signers which I don’t want to but might do if there is a rush :thinking: Would just be good to know that my baker is not thrown out if I don’t get this done in time. But hearing it was easy to switch is good :+1:

1 Like

I know exactly how you feel, been there done that, not wanting to touch anything because everything was working, and we all know the first rule of tech is: don’t poke the dragon. But honestly, the new setup turned out way better (goodbye ledger), noticeably faster, and way easier to setup as I said.

The fact that I got it done in under 30 minutes should be a confidence booster for anyone even remotely tech-inclined. You? You’ll probably smash it in under 10 minutes… unless you stop for coffee halfway through.

2 Likes

Thanks a lot @LiberteZ ! Great summary.

Just one small addition for clarity: bakers do not need to switch to tz4 consensus keys, even once all bakers attest is active.
They can continue baking and attesting with tz1 / tz2 / tz3 keys and their usual signers.

We remain available on Tezos Discord for any questions or help with tz4 / BLS installation or migration: #┃tz4-bls-consensus-signers

2 Likes