Commit cde85a71 authored by Julien Hamilton's avatar Julien Hamilton

Merge branch 'patch-1' into 'master'

Patch 1

See merge request !32
parents 76f72ab7 e768b83c
......@@ -48,7 +48,7 @@ them in the context of a larger standards process.
## What's to prevent TZIP from becoming a centralized authority like EIP?
EIP has power in Ethereum because it acts as [Schelling
point](https://en.wikipedia.org/wiki/Focal_point_(game_theory) in their system
point](https://en.wikipedia.org/wiki/Focal_point_(game_theory)) in their system
of hard fork governance. This is reinforced by the fact that the EIP editors
are substantially the most influential or notable members of the Ethereum core
developer community.
......
......@@ -21,8 +21,7 @@ inhibit collaboration across different projects, companies and continents.
This can lead to duplication of effort and low attention density on specific
issues. Poor information flow leads to resource misallocation and can
cause confusion in users and outside observers. At the same time, the
distributed nature of Tezos gives the project vitality and dynamism. As
they say in the game of Go: "Many eyes make life."
distributed nature of Tezos gives the project vitality and dynamism.
This document proposes a central clearinghouse for standards documents by
modifying the Ethereum Improvement Process to be a descriptive rather than a
......@@ -30,8 +29,7 @@ prescriptive social institution. Unlike Ethereum, Tezos already has a
prescriptive decentralized governance institution: The quorum of Tezos bakers
and delegates. The goal of this proposal is to support that institution by
encouraging high quality technical discussion, documentation and, where
appropriate, non-binding standardization. Or in other words, Tezos already
has its Parliament, but does not yet have its *[Hansard]*
appropriate, non-binding standardization.
## What is a TZIP?
......@@ -322,10 +320,7 @@ Each TZIP should have the following parts:
## TZIP Formats and Templates
TZIPs should be written in [markdown] format. Image files should be included in
a subdirectory of the `assets` folder for that TZIP as follow: `assets/X` (for
tzip **X**, replacing any `.` with `_`). When linking to an image in the TZIP,
use relative links such as `../assets/X/image.png`.
TZIPs should be written in [Markdown] format.
## TZIP Header Preamble
......@@ -354,7 +349,7 @@ gratuities from grateful Tezoi>
`* review-period-end:` <date review period ends>
` type:` Defined in TZIP-0002:
` type:` Defined in [TZIP-0002]
` created:` <date created on>
......@@ -462,10 +457,9 @@ Copyright and related rights waived via
[Morley]: https://gitlab.com/tezos-standards/morley
[Liquidity]: http://www.liquidity-lang.org/
[Fi]: https://learn.fi-code.com/
[last-call.xml]
[Markdown]: https://docs.gitlab.com/ee/user/markdown.html
[Hansard]: https://en.wikipedia.org/wiki/Hansard
[TZIP-0002]: /Proposals/TZIP-0002/TZIP-0002.md
[TZIP-0003]: /Proposals/TZIP-0003/TZIP-0003.md
[tip-1]: https://gitlab.com/tips2/TIPs/blob/master/TIPS/tip-1.md
......
......@@ -150,8 +150,8 @@ or serial numbers from external platforms (such as `RFC` or `EIP` numbers), the
letters `TZIP` should be prepended to the code like so:
```
TZIP-FA2
TZIP-A3.4
TZIP-0012 FA2
TZIP-0013 A3.4
```
Meta-level standards (such as this one `TZIP-0002`) should always have `TZIP`
......@@ -217,7 +217,8 @@ Additional types of TZIP may be proposed, and existing TZIP types may also be
deprecated by future Meta TZIPs. The TZIP Editors will maintain up-to-date list
of active TZIP types in [TZIP-0002: TZIP Index][TZIP-0002].
[TZIP-0001]: (/Proposals/TZIP-0001/TZIP-0001.md)
[TZIP-0001]: /Proposals/TZIP-0001/TZIP-0001.md
[TZIP-0002]: /Proposals/TZIP-0002/TZIP-0002.md
[issue-20]: https://github.com/ethereum/EIPs/issues/20
[issue-16]: https://github.com/ethereum/EIPs/issues/16
[pubprocess]: https://www.rfc-editor.org/pubprocess/
......
---
tzip: A1
tzip: 4 (A1)
title: Michelson Contract Interfaces and Conventions
status: WIP
type: Application
......@@ -73,7 +73,7 @@ with field annotations, and all top-level union type arguments are unannotated.
Nevertheless, it is advisable that specific implementations adhere to a
consistent tree-struct convention, examples of which can be seen in various
extensions of this standard (such as [`TZIP-A1.1`](/Proposals/TZIP-0006/A1.1.md)).
extensions of this standard (such as [`TZIP-0006 (A1.1)`](/Proposals/TZIP-0006/A1.1.md)).
### Example
......@@ -186,7 +186,7 @@ indentation and whitespacing rules.
This standard defines only tuples and unions of size two.
Introduced syntax sugar becomes especially useful in extensions of the
standard where this syntax is generalized
(see [`TZIP-0006/A1.1`](/Proposals/TZIP-0006/A1.1.md) for example).
(see [`TZIP-0006 (A1.1)`](/Proposals/TZIP-0006/A1.1.md) for example).
# CASE macro
......
---
tzip: FA1
tzip: 5 (FA1)
author: John Burnham, Konstantin Ivanov
created: 2019-07-17
---
......
---
tzip: FA1
tzip: 5 (FA1)
title: Abstract Ledger
status: WIP
type: Financial Application
......
---
tzip: A1.1
tzip: 6 (A1.1)
title: Balanced Trees for nested or and pair types
type: Application
author: John Burnham, Konstantin Ivanov
......@@ -9,9 +9,9 @@ created: 2019-05-04
## Summary
This standard extends `TZIP-A1` by defining a right-hand balance tree structure
This standard extends `TZIP-0004 (A1)` by defining a right-hand balance tree structure
for `or` and `pair` types. Structure of comb defined in
[TZIP-A1](/Proposals/TZIP-0004/A1.md#entrypoints) is the most obvious one, but the worst-case
[TZIP-0004 (A1)](/Proposals/TZIP-0004/A1.md#entrypoints) is the most obvious one, but the worst-case
performance of operations on it scales linearly with number of elements
in the comb which is suboptimal. Whereas tree structure allows reaching better
average performance of access and update operations.
......
---
tzip: FA1.2
tzip: 7 (FA1.2)
author: Konstantin Ivanov, Ivan Gromakovskii
created: 2019-04-12
---
......
---
tzip: FA1.2
tzip: 7 (FA1.2)
title: Approvable Ledger
status: WIP
type: Financial Application
......
......@@ -15,8 +15,8 @@ A TZIP should additionally contain an FAQ, which which documents, compares and a
## Current TZIPs
| TZIP | Title | Creation Date | Status |
| :--- | :--- | :--- | :--- |
| [TZIP-0001] | TZIP Purpose and Guidelines | 04/10/2019 | Proposal |
| :---: | :--- | :---: | :--- |
| [TZIP-0001] | TZIP Purpose and Guidelines | 04/10/2019 | Improvements in progress |
| [TZIP-0002] | TZIP Index | 04/10/2019 | Proposal |
| [TZIP-0003] | TZIP Code of Conduct | 04/10/2019 | Proposal |
| [TZIP-0004] | A1 - Michelson Contract Interfaces and Conventions | 04/11/2019 | Proposal |
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment