Browse Source

PIP-0041: formatting fixes

Herman Schoenfeld 4 years ago
parent
commit
3f4cad127e
1 changed files with 20 additions and 5 deletions
  1. 20 5
      PIP/PIP-0041.md

+ 20 - 5
PIP/PIP-0041.md

@@ -32,23 +32,38 @@ With the implementation of E-PASA, when sending transactions users can enter an
 #### 1.1 BuyAccount Operation Changes
 
 A. New transaction sub-type called "buy floating account".
-B. Same logic as "buy account" except for the following changes
-   B.1. The "account to buy" is 0 and ignored 
+
+B. Same logic as "buy account" except for the following changes:
+
+   B.1. The "account to buy" is 0 and ignored
+   
    B.2. The "account to pay" is 0 and ignored (i.e. sellers account)
-C. On execution 
-   C.1 The **first** PASA in the SafeBox with type "Floating" is selected as "account to buy" 
+   
+C. On execution
+
+   C.1 The **first** PASA in the SafeBox with type "Floating" is selected as "account to buy"
+   
    C.2 The "Sale Price" for C.1 is taken from the Block Policy variable "New PASA Fee"
+   
    C.3 The account is purchased exactly the same except "account to pay" is credited 0 PASC (i.e. the New PASA Fee is **burned**).
 
 #### 1.2 JSON API
 
 A. New method called “Pay to Key” that works as follows:
+
    A.1 Arguments are Account, Public Key, Quantity
+   
    A.2 Builds a "Buy Floating Account" as per (1) using arguments in (A.1)
+   
 
 B. Update "SendTransaction" method such that
+
    B.1 If target E-PASA is of the form *"@[Base58Key]"* then B.2 else B.3
-   B.2 Route to "Pay To Key" method using Base58Key as buyers key, and same Account, Quantity arguments 
+   
+   B.2 Route to "Pay To Key" method using Base58Key as buyers key, and same Account, 
+   
+Quantity arguments 
+
    B.3 Continue as a normal SendTransaction
 
 ### GUI Changes