Alpha-3 has been drumming along for one month now! Let's take a look at what’s happened.

Stats updates

Three weeks ago, our stats were:

📤 Unique proposers → 150

✅ Unique provers → 67

🕒 Average block time → 3.5 seconds

🤝 Total transactions → 1,312,898

🧱 Total blocks → 185,351

💻 Wallet addresses → 207,063

See our tweet thread for a full recap: https://twitter.com/taikoxyz/status/1669605951576625153

And as of today, our stats are:

📤 Unique proposers → 3469

✅ Unique provers → 462

🕒 Average block time → 8.4 seconds

🤝 Total transactions → 3,424,675

🧱 Total blocks → 558,377

💻 Wallet addresses → 360,293

Many of these stats have increased significantly, especially the number of unique proposers and provers! The number of unique proposers increased by a lot because we distributed TTKO to previous testnet participants, which is needed in order to propose a block.

You can find other interesting stats on ZKDash.

Issues identified

Disable system proof overwriting

We've upgraded Taiko's alpha-3 testnet by disabling system proofs to be overwritten by regular ZKPs. This brings the block reward back to normal for all blocks. You can see more details here: https://github.com/taikoxyz/taiko-mono/pull/14113.

What's next

Staking design

We are implementing a new staking mechanism, and this has already been added to our internal devnet. We are mainly addressing the prover redundancy issue where multiple provers are racing to prove a block, and only one receives the reward. This design is still under construction, so stay tuned for updates on documentation here. You can read the preliminary docs here: https://github.com/taikoxyz/taiko-mono/blob/alpha-4/packages/protocol/docs/tokenomics_staking.md.

Inception layer (L3)

We are working towards adding an inception layer (L3) to the testnet. This could include the greater ZK circuit coverage and new staking mechanism.

Greater circuit coverage

We have made significant progress in circuit coverage and are currently integrating that into our internal devnet. Heads up—this will increase the hardware requirements for generating a proof (and that theme will continue as we integrate more circuit coverage). We will give this heads up again before we add any large amount of circuit coverage like this into the testnet.

Docs to run Taiko

We’ve received some community requests to answer “How can I deploy Taiko?” (see: https://community.taiko.xyz/t/any-docs-for-setting-up-a-l3-on-top-of-taiko-or-our-own-deployment-of-a-parallel-testnet/612/1). Thus, we are taking a look at creating some docs for the community to enable them further with this experimentation. We expect the initial docs to this to be for the more advanced user, and can improve from there. Stay tuned!

Join the fun!

Take a look at all the guides on how you can take part in the testnet: https://taiko.xyz/guides

You can also participate by helping us improve our protocol, node running, or documentation! See the full contributing guide here: https://github.com/taikoxyz/taiko-mono/blob/main/CONTRIBUTING.md.

Lastly, you can find a guide to integrate your project here: https://taiko.xyz/docs/resources/integration-guide

Thank you all so much for testing Taiko, trying to break things, hacking away at client modifications, sending tokens to each other, helping the community in the Discord, joining in on the calls, and much more! You all have been the spirit of what Taiko is aiming to achieve ❤️

Stay updated 🥁

Stay in the loop on all these upcoming changes 👇

• Website: https://taiko.xyz

• Discord: https://discord.gg/taikoxyz

• GitHub: https://github.com/taikoxyz

• Twitter: https://twitter.com/taikoxyz

• Forum: https://community.taiko.xyz