WIP: RFC 2 : New binary Duniter protocol
Update 2 : Improved structures and explanations
In the current Duniter protocol all documents are managed in a textual format. While being practical as readable and verifiable by humans, it's less beneficial for programs usage since it needs parsing, fields content verifications and waste space with unused codepoints of text formats.
We propose a new protocol format which reuses ideas of the current protocol while providing a more concise and less error-prone structure while staying simple enough so it can be analysed with appropriate tools or even converted to text.
Edited by nanocryk
Merge request reports
Activity
assigned to @c-geek
assigned to @librelois
assigned to @nanocryk
added 1 commit
- 40663549 - Typo; private key text format; Removed transaction comment constraints
added 1 commit
- 6fe3752a - "peer" documents have nothing to do in the blockchain protocol
added 1 commit
-
785882dc - Usage of term
blockstamp; Revocation document; Transaction comment format; Clarifications
-
785882dc - Usage of term
added 1 commit
- a910d34b - Multiple scripts acting like functions (see DIP0001)
added 1 commit
-
2cdaa137 - Removed
previous_hash, we can useblockstampinstead.
-
2cdaa137 - Removed
64 64 65 65 ## Identities 66 66 67 Each identity is identified by an *identity uid* composed of an hash of the username and the *blockstamp* of the identity creation. 67 Each identity is identified by an *identity uid* composed of an hash of the username and puybkey and the *blockstamp* of the identity creation. 68 68 69 69 ``` 70 identity_uid = SHA256(username + blockstamp) 70 identity_uid = SHA256(username + pubkey + blockstamp)
Please register or sign in to reply