Nomadic Labs
Nomadic Labs
Announcing Octez

A veteran implementation of Tezos gets a name: Octez

Rome the city, Rome the ideal

There’s a powerful scene in the film the Gladiator where the Emperor Marcus Aurelius explains that Rome is both a physical installation of bricks and mortar, and also it is the idea of Rome — an ecosystem of standards and laws by which the people lived and a city was built.

In other words: Rome is a city, and an ideal.

When you download Tezos, you are actually downloading code that runs on a machine and in so doing embodies the idea of Tezos.

In other words: Tezos is an implementation, and an ideal.

We at Nomadic Labs are proud to have played a role in the coalition of programmers that wrote a Tezos implementation which is now widely used in the community. Historically, this was the first complete implementation of Tezos, which was used to activate Tezos Mainnet (the live blockchain) back in 2018. You can download this implementation from the open source repository https://gitlab.com/tezos/tezos/, where it is actively maintained today.

However, we were so excited by this at the time that — much like the Romans — we neglected to distinguish linguistically between the ideal, and the implementation of that ideal. This may be forgivable for world-spanning preindustrial empires, but we modern software developers should be more precise. So …

The implementation is Octez; the standard is Tezos

We are happy to announce that the bundle of concrete code files maintained at https://gitlab.com/tezos/tezos/ now has a name: Octez.

Octez’ is a portmanteau of octopus and Tezos, a pun which draws inspiration from this big picture of Tezos.

The big picture

Octez’ is also a portmanteau of OCaml and Tezos (OCaml being the main programming language used in Octez), and a pun on ‘octet’.

Octez, in more detail

Octez is an implementation of a suite of Tezos-related software. It lives in this GitLab repo: https://gitlab.com/tezos/tezos/.

Octez includes:

  1. a Tezos node (which you may know as tezos-node);
  2. a Tezos client for this node (tezos-client);
  3. an implementation of the environment for the economic protocol;
  4. daemons (baker, accuser and endorser) for protocols which are active on Mainnet;
  5. a remote signer (tezos-signer);
  6. and further tools, such as an encoder-decoder for Tezos data types (tezos-codec); tezos-protocol-compiler; and tezos-validator.

Everything in the big picture above is Octez, except for

  • the Network (underneath the legs),
  • the Explorer (bottom right), and
  • the economic protocol (the green bit with PROTOCOL written in it) — though Octez is distributed with the economic protocols of Mainnet for convenience.2

Origin of the implementation

Octez was created by a coalition of teams including Nomadic Labs, Tarides, Tocqueville Group, Obsidian Systems, Tweag, and Metastate (non-exclusive list).

The work is coordinated by the merge team (list of members here), and the name Octez was proposed to and approved by them. This reflects the decentralized nature of Tezos: Octez is a decentralized implementation, and the name itself was chosen in collaboration.

Why Choose a Name Now?

When we release a new version of https://gitlab.com/tezos/tezos/ we may say something like

version 9.2 has just been released

This invites the question: Version 9.2 of what? The answer is

Version 9.2 of the Tezos implementation that lives at https://gitlab.com/tezos/tezos/,

which is a bit of a mouthful. So henceforth we can write

Version 9.2 of Octez,

with a clear conscience, complete precision — and our SEO officer would feel better about it too, if we had one.

Thanks for reading … and keep an eye out for a future post titled “Releasing version 10.0 of Octez”!


  1. See for example the files for the Florence economic protocol, which is what Mainnet is running at time of writing. 


Announcing Granada

This is a joint post from Nomadic Labs, Marigold, TQ, Tarides, and DaiLambda. We were proud to see Florence go live on the chain on 11th May 2021. In keeping with our policy of proposing upgrades on a regularly scheduled basis, we’re happy to announce our latest Tezos protocol proposal, Granada. (As is usual, Granada’s “true name” is its hash, which is PtGRANADsDU8R9daYKAgWnQYAJ64omN1o3KMGVCykShA97vQbvV). Granada contains several major improvements to the protocol, as well as...

Read More
Simulating Tenderbake

Announcing a simulator for Tenderbake

If you’re impatient, you are welcome to read the guide and jump right to the simulator now. See also the implemented algorithms below. If you find that reading about it helps you get excited before using your simulator, then read on … Background The consensus algorithm is a crucial part of any blockchain project. Because of the distributed nature of blockchains, different nodes can have different ideas of what the current state of the blockchain is supposed to be....

Read More
Faster finality with Emmy*

Announcing forthcoming upgrade of consensus protocol, giving quicker time to finality (i.e. shorter transaction settlement times)

We are happy to announce that Emmy* is set to be included in the next Tezos protocol proposal Granada,1 replacing the current consensus algorithm Emmy+. If Granada is adopted, Emmy* will generally halve the time between blocks, from 60 seconds to 30 seconds, and allow transactions to achieve significantly faster finality than under the current consensus algorithm, Emmy+. Specifically, Emmy* updates Emmy+ by: a tweak in the definition of the minimal delay function, and an increase in...

Read More
Announcing the report “Possible evolutions of the voting system in Tezos”

Announcing a report on possible evolutions of the voting system in Tezos

Nomadic labs has an ongoing research relationship with INRIA (a French national technology research agency). In the context of this relationship, Nomadic Labs commissioned a short report to explore what a privacy-preserving amendment procedure might look like on Tezos, authored by three experts in voting protocols and cryptography: Véronique Cortier, Pierrick Gaudry and Stéphane Glondu. There is no plan to implement the contents of the report for now, but we welcome and...

Read More
Tezos calling convention migrating from Breadth-First to Depth-First Order (BFS to DFS)

Summary: If the Florence proposal is adopted, we recommend you do not deploy new Michelson contracts that are dependent on the BFS calling convention. We do not expect this to be a problem in practice. However, those planning on deploying contracts in the near term should check that their contract’s correctness is unaffected by the change in calling convention. The current calling convention for intercontract calls in Tezos is that they are added to a “first-in,...

Read More
Baking Accounts proposal contains unexpected breaking changes

Summary Ongoing testing and review of baking accounts has uncovered some important and previously undocumented breaking changes (see the section on breaking changes in the TZIP for Baking Accounts) in the baking account proposal. These issues are significant, and affect the functionality of both existing and future smart contracts; they are detailed below. Bakers should please these carefully when casting their vote. We believe Baking Accounts should be postponed until a thorough audit of functionality is...

Read More
Florence: Our Next Protocol Upgrade Proposal

Announcing Florence Proposal

UPDATE: We believe that the baking accounts implementation is significantly flawed. See: Baking Accounts proposal contains unexpected breaking changes This is a joint announcement from Nomadic Labs, Marigold, DaiLambda, and Tarides. As we described in this post, several development organizations in the Tezos ecosystem are now collaborating to submit protocol upgrade proposals every few months, which is the interval permitted by the Tezos on-chain governance process. When the Edo upgrade went live on February 13,...

Read More
A technical description of the Dexter flaw

In this technical blog post, we detail the flaw found in the Dexter contract and the exploit used to “white-knight” the funds in those contracts. Background The Dexter contract contains several entrypoints allowing users to perform various operations, such as adding and removing liquidity, or converting tokens to tez back and forth. The exact interface is given by the type of the contract’s parameter: parameter (or...

Read More
Dexter Flaw Discovered; Funds are Safe

TL;DR: A flaw was found in the camlCase’s Dexter contract. The funds have been removed from the contract and returned to their original holders. A high level explanation follows; technical details of the Dexter flaw will be described in a separate post to come. As many of you know, we have been working on a new Tezos upgrade proposal. This proposal, if accepted, will change the calling convention from breadth first ordering to depth first ordering. In...

Read More
  • 1
  • 2