Improved GUID definition in PIP-0033 and in PIP-0016 added link to PIP-033.

PIP/PIP-0016.md

@@ -55,4 +55,7 @@ As mentioned in Motivation section, enveloping layer-2 protocols inside layer-1
 
 ## Backwards Compatibility
 
-This change is not backwards compatible and requires a hard-fork activation.
+This change is not backwards compatible and requires a hard-fork activation.
+
+## Related links
+- PIP-0033 DATA operation RPC implementation https://www.pascalcoin.org/development/pips/pip-0033

PIP/PIP-0033.md

@@ -103,7 +103,8 @@ Array<Operation> senddata({
 - `data_sequence [UINT16]`    
   The data sequence of the operation. If the data sequence cannot be determined (null or not given), it is 0 by default.
 - `guid [GUID]`    
-  A 16 Bytes GUID in `8-4-4-4-12` format. If null or not given, the node will generate a UUID V4 (random).    
+  A 16 Bytes GUID in `{8-4-4-4-12}` format. If null or not given, the node will generate a UUID V4 (random).    
+  Note that in Pascal programming language, GUID is wrapped in {} brackets. Example: {E7213C38-1A97-4CCA-A200-1FF094639BF5}. Brackets {} do not affect the blockchain, but {} should be part of GUID passed to JSON RPC API calls.
 - `amount [PASCCURRENCY] (defult = 0)` 
   The amount to transfer to `target`, if not given or null the default value is 0.       
 
@@ -158,7 +159,8 @@ Array<Operation> signdata({
  - `data_sequence [UINT16]`    
     The data sequence of the operation. If the data sequence cannot be determined (null or not given), it is 0 by default.    
  - `guid [GUID]`    
-    A 16 Bytes GUID in `8-4-4-4-12` format. If null or not given, the node will generate a UUID V4 (random).    
+    A 16 Bytes GUID in `{8-4-4-4-12}` format. If null or not given, the node will generate a UUID V4 (random).    
+	Note that in Pascal programming language GUID is wrapped in {} brackets. Example: {E7213C38-1A97-4CCA-A200-1FF094639BF5}. Brackets {} do not affect the blockchain, but {} should be part of GUID passed to JSON RPC API calls.
  - `last_n_operation UINT32`
     Last value of `n_operation` of the signer (or sender or target)     
  - `amount [PASCCURRENCY] (defult = 0)` 
@@ -198,7 +200,8 @@ Array<Operation> finddataoperations({
 - `target [UINT32] (default = null)`    
   The account that received the DATA operation. Optional.
 - `guid [GUID] (default = null)`    
-  A 16 Bytes GUID in `8-4-4-4-12` format. Optional.
+  A 16 Bytes GUID in `{8-4-4-4-12}` format. Optional.
+  Note that in Pascal programming language GUID is wrapped in {} brackets. Example: {E7213C38-1A97-4CCA-A200-1FF094639BF5}. Brackets {} do not affect the blockchain, but {} should be part of GUID passed to JSON RPC API calls.
 - `data_sequence [UINT16]`    
   The data sequence of the operation to search for. Optional.
 - `data_type [UINT16]`    
@@ -229,3 +232,5 @@ None.
 - UUID V4: https://en.wikipedia.org/wiki/Universally_unique_identifier#Version_4_(random)
 
 - PascalCoin JSON RPC documentation: https://github.com/PascalCoin/PascalCoin/wiki/JSON-RPC-API
+
+- DATA-OP: In-Protocol Data Exchange (Layer-2 support) https://www.pascalcoin.org/development/pips/pip-0016