The noise wasn’t random. It was feedback. During testnet, we saw a flood of packages, pull requests, accounts and transactions. Some of it was genuine participation. Some of it was spam. But the more important lesson was that people were responding to the system we had put in front of them. If volume looked like contribution, volume became the strategy. That same problem is now playing out across open source at a much larger scale. Automated pull requests, spam packages and machine-generated activity are growing faster than maintainers can meaningfully evaluate them. So we went back to the application layer. Not to change the mission, but to build a better way of distinguishing activity from contribution, and noise from signal. Identity. Provenance. Repository context. Contribution evidence. Maintainer authority. That is what the last few months have been about. We’re getting close to showing you what we’ve been building.

We said: judge us by what we build. Here is one of the things Tim discussed during the AMA. This is an early testnet build of the tea Dev Wallet, running as a browser sidecar alongside https://t.co/4n46XTUCVU. Open a repository and the idea starts to become tangible. Repository evidence. Identity. Provenance. Vulnerability context. The information around the software, brought closer to the place where developers are already looking at it. And that is only one surface. https://t.co/4n46XTUCVU in the browser. Dev Wallet beside the repo. Tea CLI in the terminal. Different entry points into the same product layer. The direction is to make tea less of a destination developers have to visit, and more of an intelligence and coordination layer around the open-source work they are already doing. This is still testnet. It is still being built. But it is becoming something you can see.

tea is not building five separate products. We’re building one system, layer by layer, from the network that is live today to the repository economies we believe open source will need next. LIVE NOW Tea Network + TEA are the foundation. Tea is already a live OP Stack L2 with native verification for GPG/PGP signatures, SSHSIG and X.509 leaf certificates. That matters because developer identity, signatures and software provenance should not sit outside the economic layer. They should be usable as part of it. OCTOBER 2026 The next major step is the integrated tea Product Layer. https://t.co/4n46XTUCVU, Dev Wallet, TeaRank, PR-backed workflows and OSS Intelligence are not separate launches. They are parts of the same system. At the intelligence layer, tea is building pipelines that ingest and connect repository, package, vulnerability, maintenance, signature and provenance data into a structured OSS data lakehouse. That data can then power TeaRank, developer workflows, product surfaces and, over time, enterprise APIs. We are also building the architecture toward the controls, traceability and operational discipline expected of a future SOC 2-aligned data environment. LATE 2026 The evidence layer becomes actionable. tea-signer, CLI tooling and WebMCP extend tea into developer and agent-assisted workflows, while keeping identity, keys and authorization under developer control. EARLY 2027 The focus expands from individual actions to coordination. Repository governance. Contribution funding. Bounty and work flows. Deeper on-chain economic coordination. Aerodrome / AERO integration. 2027 HORIZON The longer-term direction is repository economies. Infrastructure that allows projects, contributors and communities to coordinate funding, incentives and economic activity around the software itself. That is the logic behind the roadmap: Network → Evidence → Action → Coordination → Economy Some dates are target windows and will move with testing, integrations and release readiness. But the direction is clear. tea is building from a live blockchain into the economic and intelligence infrastructure for open source.

The launch of TEA did not go the way we planned. We know that, and we are not going to rewrite what happened. We addressed it at the time: https://t.co/OUwPPhG4l8 Since then, we have been quieter publicly. But the work did not stop. The mission has not changed. Open source still runs modern software, and the infrastructure around how that work is understood, verified, governed and supported still has a long way to go. What has changed is the world around it. AI is accelerating how software is written, tested and changed. As producing software becomes easier, provenance, accountability, human judgment and maintainer attention become more important. Our thinking, and the product, have evolved with that reality. On September 17, we will publish our updated roadmap. On September 22, we will host an AMA on Discord. Bring the difficult questions. We do not expect one post to change anyone's mind. Judge us by what we build. Over the next two weeks, we will start showing you.

“A verdict isn't auditable if someone can quietly change it later.” @OpensourceWtf is combining source analysis, sandbox execution, and public onchain verdicts to make package risk easier to inspect while releases are still moving through the software supply chain. A strong community-built use of tea. Read the full article ↓

OpenSource WTF is live. Built by the community, @OpensourceWtf turns open-source package activity into something people can explore, compare, and discuss. This is the kind of builder energy tea was made to support. Not every useful surface around tea has to come from the core team. Community apps matter. Builder experiments matter. Making the software graph more visible matters. Explore OpenSource WTF. And to the builders behind it: thank you for building.

Rewards Update We know people are waiting for the airdrop, and we want to give a clear update on where things stand. The rewards process has taken longer than planned for two main reasons. The first is fairness. We have received over 3,000 appeals, and the team is reviewing them carefully. That process takes time, but it matters. We would rather do the work properly than rush through appeals and risk getting the distribution wrong for genuine participants. The second is utility. tea is a utility-first network, so we do not want the airdrop to happen in isolation. We want it to land alongside the new website experience, so people have somewhere useful to go and something real to do with their tokens. The site is currently in bugfixing mode. Until that is finished and the appeals review is further along, we cannot give a specific date with confidence. We know waiting is frustrating. But the work is active. Appeals are being reviewed. The site is being finalized. The distribution is being handled carefully. The goal is a fair drop for real participants, not a rushed drop that creates more problems later. Thank you for sticking with us while we get this right.

Only 8 hours left. The rewards eligibility period is closing. If you participated in ITN, Assam, or Sepolia, check your eligibility now: https://t.co/8uBhoPh2lw Use only the official link. Do not trust links in replies, DMs, or unofficial posts. https://t.co/ZgzPxU1VxE

An L2 is not just an execution environment. It needs settlement underneath it. Tea L2 is configured to settle to Ethereum mainnet. The portal, bridge, and fault-proof system contracts are deployed on Ethereum. That matters because the network is not floating in isolation. It has a foundation beneath it. That is what turns a chain from a surface into infrastructure.

A bridge is only useful if the path back exists. Tea L2 withdrawals back to Ethereum are live. A full round-trip has already been completed and finalized onchain. Like other Optimism-style networks, withdrawals include a finalization window before funds settle back on Ethereum. That wait is part of the security model. Not a defect. Tea L2 has a working path in, and a working path back.