Commit 4c728960 authored by Julien Hamilton's avatar Julien Hamilton

A and assets under proper TZIP folders

parent 8f81fddf
---
tzip: 4
tzip: 8
title: Payment Request Format
status: Draft
type: TRC
......
---
tzip: 5
tzip: 9
title: Info Field for Payment Requests
status: Draft
type: TRC
......@@ -13,7 +13,7 @@ Miscellaneous information extension for payment requests.
## Abstract
This document describes an extension to TZIP-0004 that adds an extra field to Tezos payment requests. The field can contain simple description of payment or their purpose. Wallets can dispay this in transaction history or when approving the payment.
This document describes an extension to TZIP-0008 that adds an extra field to Tezos payment requests. The field can contain simple description of payment or their purpose. Wallets can dispay this in transaction history or when approving the payment.
## Motivation
......@@ -44,7 +44,7 @@ Information about the purpose of the payment will use a field called `info` with
## Appendix
### TZIP-0004 Implementations Supporting the Standard
### TZIP-0008 Implementations Supporting the Standard
* TBA
### Wallets Implementing the Standard
......
# Tezos Improvement Proposals
# Tezos Improvement Proposals (TZIPs)
TZIP (pronounce "tee-zip") stands for Tezos Improvement Proposal, which are documents that explain how the Tezos blockchain works or how it ought to work.
## What is a TZIP?
A TZIP is a design document providing information to the Tezos community, describing a feature for Tezos or its processes or environment, and supporting the formal protocol governance process. A TZIP should contain a concise technical specification and rationale which unambiguously articulates what the proposal is, how it may be implemented, and why the proposal is an improvement. A TZIP should additionally contain an FAQ, which which documents, compares and answers alternative options, opinions and objections.
## Current TZIPs
| TZIP | Title | Creation Date |
| :--- | :--- | :--- |
| [TZIP-0001] | TZIP Purpose and Guidelines | 04/10/2019 |
| [TZIP-0002] | TZIP Index | 04/10/2019 |
| [TZIP-0003] | TZIP Code of Conduct | 04/10/2019 |
| [TZIP-0004] | A1 - Michelson Contract Interfaces and Conventions | 04/11/2019 |
| [TZIP-0005] | FA1 - Abstract Ledger | 04/12/2019 |
| [TZIP-0006] | A1.1 - Balanced Trees for nested or and pair types | 05/04/2019 |
| [TZIP-0007] | FA1.2 - Approvable Ledger | 06/20/2019 |
| [TZIP-0008] | Payment Request Format | 06/25/2019 |
| [TZIP-0009] | Info Field for Payment Requests | 06/25/2019 |
## TZIP Formats and Templates
TZIPs should be written in [Markdown] format. You can find a template in the [Templates] folder.
[TZIP-0001]: Proposals/TZIP-0001
[TZIP-0002]: Proposals/TZIP-0002
[TZIP-0003]: Proposals/TZIP-0003
[TZIP-0004]: Proposals/TZIP-0004
[TZIP-0005]: Proposals/TZIP-0005
[TZIP-0006]: Proposals/TZIP-0006
[TZIP-0007]: Proposals/TZIP-0007
[TZIP-0008]: Proposals/TZIP-0008
[TZIP-0009]: Proposals/TZIP-0009
[Markdown]: https://docs.gitlab.com/ee/user/markdown.html
[Templates]: Templates
See [TZIP-0001](Proposals/TZIP-0001/TZIP-0001.md)
---
Headers marked with "*" are optional. All other headers are required.
tzip: <TZIP index code> (this is determined by the editor)
title: <TZIP title>
author: <a list of the author's or authors' name(s) and/or username(s), or
name(s) and email(s). [More Details](/TZIP-1.md#author-header)>
advocate *: <a list of the author's or authors' name(s) and/or username(s), or
name(s) and email(s). [More Details](/TZIP-1.md#author-header)>
gratuity *: <a Tezos address controlled by an author capable of receiving
gratuities from grateful Tezoi>
discussions-to *: <a url pointing to the official discussion thread>
status: <WIP | Draft | Last Call | Final | Active | Pending | Protocol | Rejected | Superseded>
review-period-end *: <date review period ends>
type: <Defined in [TZIP-2](/TZIP-2.md#tzip-index-types)>
created: <date created on>
updated *: <comma separated list of dates>
requires *: <TZIP indices>
replaces *: <TZIP indices>
superseded-by *: <TZIP indices>
---
## Simple Summary
“If you can’t explain it simply, you don’t understand it well enough.” Provide a simplified and layman-accessible explanation of the TZIP
## Abstract
A short (200-500 word) description of the technical issue being addressed.
## Motivation
The motivation is critical for TZIPs that want to change the Tezos protocol. It should clearly explain why the existing protocol specification is inadequate to address the problem that the TZIP solves.
## Specification
The technical specification should describe the syntax and semantics of any new feature. The specification should be detailed enough to allow competing interoperable implementations.
## Rationale
The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other languages. The rationale may also provide evidence of consensus within the community, and should discuss important objections or concerns raised during discussion.
## Backwards Compatibility
All TZIPs that introduce backwards incompatibilities or supersede other TZIPs must include a section describing these incompatibilities, their severity, and solutions.
## Test Cases
Test cases for an implementation are strongly recommended as are any proofs of correctness via formal methods.
## Implementations
Any implementation must be completed before any TZIP is given status “Last Call”, but it need not be completed before the TZIP is merged as draft.
## Apendix
A list of references relevant to the proposal.
## Copyright
All TZIPs must be in the public domain, or a under a permissive license substantially identical to placement in the public domain. Example of a copyright waiver.
Copyright and related rights waived via
[CC0](https://creativecommons.org/publicdomain/zero/1.0/).
---
Header has to be copied from the created TZIP.
tzip: <TZIP index code> (this is determined by the editor)
title: <TZIP title>
author: <a list of the author's or authors' name(s) and/or username(s), or
name(s) and email(s). [More Details](/TZIP-1.md#author-header)>
advocate *: <a list of the author's or authors' name(s) and/or username(s), or
name(s) and email(s). [More Details](/TZIP-1.md#author-header)>
gratuity *: <a Tezos address controlled by an author capable of receiving
gratuities from grateful Tezoi>
discussions-to *: <a url pointing to the official discussion thread>
status: <WIP | Draft | Last Call | Final | Active | Pending | Protocol | Rejected | Superseded>
review-period-end *: <date review period ends>
type: <Defined in [TZIP-2](/TZIP-2.md#tzip-index-types)>
created: <date created on>
updated *: <comma separated list of dates>
requires *: <TZIP indices>
replaces *: <TZIP indices>
superseded-by *: <TZIP indices>
---
## Question
Answer to the question as descriptive as possible to paint a clear picture for the reader.
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