If you are evaluating Tezos for a product, two parts of the platform matter early: how the protocol changes over time, and how contracts behave once deployed. Both are described in the official Tezos documentation, and this guide stays within it.

Self-amendment instead of hard forks

The documentation says Tezos incorporates a built-in, on-chain mechanism for proposing, selecting, testing and activating protocol upgrades without the need to hard fork. That makes it a self-amending blockchain, and it allows any user to propose changes to the economic protocol, which defines the possible blockchain operations and how they are processed. This is separate from the off-chain and less formal Tezos Improvement Process.

The process has five periods, scheduled and run by the protocol itself:

  • Proposal: delegates propose changes and upvote proposals. If a quorum is met, the top-voted proposal moves on.
  • Exploration: users vote on whether to consider the top-voted proposal.
  • Cooldown: if a proposal is selected, the community can keep testing and preparing infrastructure before the final decision.
  • Promotion: users make a final vote on whether to apply the proposal.
  • Adoption: users adapt their code and infrastructure, and at the end of the period the proposal activates automatically.

Each period lasts 14 blockchain cycles, or about 14 days. Only delegates can vote. A delegate’s voting power is the tez it has staked plus the tez delegated to it, called its staking balance. In the proposal period a delegate submits the hash of the source code, and each delegate can submit up to 20 proposals in one period.

What this means for your product

For a team building on Tezos, the amendment calendar is part of your planning. Protocol changes arrive through a visible, staged process, and the adoption period exists so that you can adapt code and infrastructure before activation. Follow the proposals and the cooldown period as an input to your release schedule.

Smart contracts on Tezos

The documentation defines a smart contract as a piece of code stored on the blockchain, containing instructions and rules to trigger them. Once deployed it becomes immutable, but a user can trigger its execution without modifying it. It compares contracts to snack vending machines: the rules are fixed, while the quantities of items inside change.

A contract is a kind of account, so it has a balance and can receive and send tez, and it has storage for its data. The documentation also states a limit that shapes architecture: a smart contract can only run and interact with the blockchain it is stored on, and it cannot interact with the outside world. That is why decentralized applications exist, since they provide interfaces to the outside world.

Immutability has a practical consequence. Because deployed code cannot be changed, testing and review before deployment carry more weight. Plan for an independent review of any contract that holds value, and decide how you would handle a defect found afterwards, since you cannot edit the contract in place.

Questions people ask

How long does a Tezos protocol amendment take?

There are five periods, each 14 blockchain cycles, or about 14 days, according to the Tezos documentation.

Who can vote on Tezos proposals?

Only delegates can vote. A delegate’s voting power is the tez it has staked plus the tez delegated to it.

Can a Tezos smart contract be changed after deployment?

The documentation says a deployed contract becomes immutable. Users can trigger its execution without modifying the code.

Sources

← All insights