Edo (PtEdoTezd)

Adds two major features: Sapling and BLS12-381 to enable privacy-preserving smart contracts and tickets for native permissions. Updates amendment process by lowering period length to 5 cycles and adding a 5th Adoption Period. Also includes minor Michelson improvements. Full changelog here.


Features

The Edo proposal, a joint effort from Nomadic Labs, Marigold, and Metastate is a protocol upgrade proposal focused on implementing new features such as Sapling and Tickets, and adding core functionality improvements to the Tezos protocol.

Sapling, originally developed by the Electric Coin Company, will be integrated to enable privacy-preserving transactions on Tezos. With recent improvements, the time needed for crafting and verifying transactions using Sapling have reached practical levels suitable for any end-user. Coupled with this is the addition of Michelson opcodes for the pairing-friendly elliptic curve BLS12-381.

Tickets provide a mechanism for smart-contract to grant portable permissions to other smart-contracts, or to issue tokens. This enables new kinds of composable contract architectures and aims to guard against common smart contract vulnerabilities.

Edo also adds several new instructions to Michelson, including LEVEL, which has been widely requested by developers exploring Layer-2 scaling solutions.

New instructions

  • New hash functions: instructions KECCAK and SHA3
  • Instruction LEVEL to query the level of the current block
  • Instructions VOTING_POWER (and resp. TOTAL_VOTING_POWER) to query the voting power of a particular delegate (resp. of all delegates)
  • Instruction SELF_ADDRESS equivalent to SELF; ADDRESS but allowed in lambdas

Amendment Process Updates

A new fifth period called “Adoption” is a means to improve governance on Tezos by providing an additional window for bakers, indexers, and end-users to upgrade their nodes once a protocol upgrade goes live. At the moment, protocol upgrades that pass go live one block after the completion of voting has been perceived to provide an insufficient update window. This Adoption period aims to provide a more suitable time window for these updates.

Additionally, amendment period lengths will be reduced from 8 cycles to 5 cycles, making the total duration of the voting procedure 25 cycles (~2 months and 10 days).

Explanation Posts

Source Code

Invoice

This proposal doesn’t contain an invoice.

Proposal archive

View this proposal on Agora

4 Likes

This is an action call to all Tezos Bakers and tez holders! Make sure your baker has voted and if not, encourage them strongly to do so. A list can be found here: https://www.tezos.help/bakers-list/

We have only 11 days and we need a lot of votes to move this very important proposal forward. We do not want to lose 3 months of time by having this fail. It’s up to us to get involved and push forward.

3 Likes

Does Ticketing allow for something similar to ERC-998? https://eips.ethereum.org/EIPS/eip-998 Composable Non-Fungible Token Standard

Is this possible using the FA2 standard?