Exchange Protocol App Engine - SafeSlingerProject/SafeSlinger-Media GitHub Wiki

#SafeSlinger Exchange Protocol v1.8 for App Engine

This specification details the messages used in the SafeSlinger Exchange protocol, specifically to run the protocol using the demo server implementation on App Engine. We have outlined a more abstract list of messages to model protocol communication over other modes of transportation if you need. All messages are sent in a HTTPS POST request body, and received in the same HTTPS POST response body.

Terms

• data: the data we intend to verify, commonly a public key, account number, or other PII.
• -commit: 256-bit length, SHA-3 root of commitment tree.
• -id: integer (low entropy, often ranging 11-99).
• link-id: integer, common lowest -id number for grouping.
• -encdata: 1920-bit minimum length, a triplet of 3 values: 128-bit minimum AES encrypted data, 1536-bit DH 1/2 key, 256-bit SHA-3 hash of decision fork.
• -sig: 512-bit length, 2 256-bit SHA-3 or error nonce values of tree match/error decision fork.
• -node: 1536-bit length, STR public node value (for 3+ users).
• -encnonce: 256-bit length, AES encrypted 256-bit match nonce.

#Content-Type text/plain

This content type expects the request and responses to be formatted in JSON-formatted text given the following specification.

Forthcoming...

#Content-Type application/octet-stream

This content type expects the request and responses to be formatted as big-endian binary data given the following specifications.

Forthcoming...