The Tezos Foundation launched the Tezos betanet on June 30, 2018, proposing a genesis block and beginning validation on the first non-test instance of the protocol. Transactions could be processed immediately, turning a project defined by its 2017 fundraiser, governance dispute and repeated delays into an operating blockchain.
The milestone was consequential because Tezos had raised cryptocurrency worth approximately $232 million during its July 2017 fundraiser, according to contemporaneous reporting cited in the days before launch. That placed unusual institutional and market attention on whether the developers could deliver a functioning network. The June 30 activation established that the software could begin maintaining a live ledger; it did not resolve every legal, governance or operational question surrounding the project.
A live network with beta limits
The Foundation explicitly called the network a betanet, not a completed mainnet. Its June 30 announcement said validation—known in Tezos terminology as “baking”—had commenced and that transactions could be processed. It also warned participants to protect their private keys because the Foundation could not recover lost or stolen tokens.
Community members could connect immediately, but they were not scheduled to begin baking until the first seven cycles had elapsed. The Foundation defined that interval as 28,672 blocks, or approximately three weeks depending on actual block times. Baking rights were initially unassigned, so the announcement said no block rewards would be issued during that opening period.
Those restrictions qualify the word “live.” The ledger was operational, but its initial validation phase did not yet demonstrate broad community participation. The surviving announcement also supplied the proposed genesis-block hash, allowing operators to compare the network they joined with the Foundation’s reference. It did not provide independent measurements of node count, geographic distribution, transaction throughput or value transferred on June 30.
Why Tezos was different
Tezos was designed as a proof-of-stake smart-contract network whose protocol could amend itself through stakeholder-approved changes. Its white paper described a system in which the ledger could adopt changes to its own code, including changes to the amendment procedure, instead of treating every contested upgrade as an invitation to create a separate chain.
That design addressed a prominent problem in the cryptocurrency industry of 2018. Bitcoin’s scaling conflict had produced Bitcoin Cash in August 2017, while other networks were also debating how technical authority should be exercised. Tezos proposed placing more of that decision-making inside the protocol.
The June 30 launch did not prove that this governance system would work under contentious conditions. It merely created the network on which proposals, voting and protocol amendments could eventually be tested. Likewise, the white paper’s discussion of functional programming and formal verification described design goals and technical tools; it was not evidence that every contract or implementation error had been eliminated.
Fundraising and governance shadowed the launch
The betanet arrived nearly a year after the fundraiser and after a public dispute involving the project’s founders and the former president of the Swiss foundation responsible for the contributed assets. Contributors had also brought lawsuits alleging, among other claims, that the fundraiser involved an unregistered securities offering. Those allegations remained unresolved on June 30, 2018.
Launching the network therefore narrowed one important uncertainty—whether a usable ledger would appear—but did not settle the legal characterization of the contributions, the merits of the lawsuits or the Foundation’s stewardship. Nor did activation guarantee exchange liquidity or a stable market price for the native units.
Later context
A later Tezos Foundation report recorded that the betanet became the mainnet on September 17, 2018, with the earlier transactions preserved. That subsequent designation confirms continuity of the June 30 ledger, but it should not be projected backward: on June 30, participants were interacting with an explicitly experimental beta network whose community-validation phase had not yet begun.
The complete source packet and revision history are retained with the newsroom record.
Automated systems may have assisted with source organization and drafting. Coinburn is accountable for the published text and maintains a revision record.
This article provides news and analysis, not investment, legal or tax advice. Digital assets are volatile and may result in total loss.

