WIP: RFC 1 : Abstract Syntax Tree-based output script locks

Update 2 : Rewriting with way better format to fix flaws of the first draft.

In the current Duniter protocol input and output conditions are stored in machine-readable BNF text format. This is good for human readability, but it requires parsing and takes place due to its textual format.

To lower blocksize and transactions weights; or to allow more complex conditions, it could be preferable to use a more simple binary format which need little or no parsing, close to memory and that can be converted back to text format. It can also allow to add new features without hard-forking the protocol.

0000-duip-format.md

+```
+DUIP: 0  
+Title: DUIP format  
+Author: nanocryk <nanocryk@gmail.com>  
+Status: Proposition  
+Type: Process  
+Created: 2017-11-22  
+License: GPL-3  
+```
+
+A **DU**niter **I**mprovement **P**roposal (**DIP**) is a design document describing new feature for Duniter or its processes or environment. The DUIP should provide a concise technical specification of the feature and a ratonale for the feature.
+
+We intend DUIPs to be the primary mechanics for proposing new features, for collecing community input on an issue, and for documenting the design decisions the have gone into Duniter. The DUIP author is responsible for building consensus within the community and documenting dissenting opinions.
+
+Because the DUIPs are maintained as text files in a versioned repository, their revision history is the historical record of the feature proposal.
\ No newline at end of file