PIP-0031: rename to PIP-0031A in anticipation of alternative proposals

PIP/PIP-0031.md → PIP/PIP-0031A.md

@@ -1,5 +1,5 @@
 <pre>
-  PIP: PIP-0031
+  PIP: PIP-0031A
   Title: New Wallet: Multi-Platform & Multi-Paradigm
   Type: User Interface
   Impact: None
@@ -47,7 +47,7 @@ The wallet is comprised of the following sub-systems:
 * **Processing-Layer**: this is a well-defined set of Javascript APIs that are used by the Presentation-layer for all it's Create/Read/Update/Delete operations. Whilst the interface into this layer is constant, the implementation can vary between platforms.
 * **Node**: this is a full node that the Processing-layer depends on. It can be either in-process, out-of-process or even remote. Typically, it will be the PascalCoin daemon.
 
-![Wallet Architecture](resources/PIP-0031/Wallet-Architecture.drawio.png)
+![Wallet Architecture](resources/PIP-0031A/Wallet-Architecture.drawio.png)
 
 The above architecture is **abstracted** since it is intended to be deployed in a variety of specialized, concrete architectures. These architectures include:
 
@@ -55,7 +55,7 @@ The above architecture is **abstracted** since it is intended to be deployed in
 
 This deployment configuration is intended to be shipped with desktop installation of PascalCoin. It can compliment Classic GUI and provide macOS users with a GUI.
 
-![Wallet Architecture](resources/PIP-0031/Wallet-Delta-Configuration.drawio.png)
+![Wallet Architecture](resources/PIP-0031A/Wallet-Delta-Configuration.drawio.png)
 
 **Key Points**
 * Web-server initially delivers the Presentation-layer to the users browser, which can be cached long-term.
@@ -66,7 +66,7 @@ This deployment configuration is intended to be shipped with desktop installatio
 
 This deployment configuration will be used to deliver the wallet as a web application to the user. This is typically known as a **web wallet**.
 
-![Wallet Architecture](resources/PIP-0031/Wallet-Omega-Configuration.drawio.png)
+![Wallet Architecture](resources/PIP-0031A/Wallet-Omega-Configuration.drawio.png)
 
 * Web-server initially delivers the Presentation-layer to the users browser, which can be cached long-term.
 * Key and settings state is managed client-side using [HTML5 Web Storage][1]
@@ -78,7 +78,7 @@ This deployment configuration will be used to deliver the wallet as a web applic
 
 This deployment configuration will be used for full-node mobile apps.
 
-![Wallet Architecture](resources/PIP-0031/Wallet-Omicron-Configuration.drawio.png)
+![Wallet Architecture](resources/PIP-0031A/Wallet-Omicron-Configuration.drawio.png)
 
 * Same as Omega, except HTML is hosted inside an app with an embedded browser (the app host).
 * A platform-specific mobile component plugs into into processing layer and intercepts certain calls, for native UX.

PIP/README.md

@@ -36,6 +36,6 @@ If they wish to continue, copy [this template](PIP-template.md) and ensure your
 | [28](PIP-0028.md)     | E-OP: Layer-2 operation encoding standard for smart-contracts | Herman Schoenfeld            | Front-End       | Draft |
 | [29](PIP-0029.md)     | Account Seals: Cryptographically Secure Account Histories  | Herman Schoenfeld            | Protocol   | Draft |
 | [30](PIP-0030.md)     | SafeBoxRoot: Deletable SafeBox and Light-Nodes  | Herman Schoenfeld            | Protocol   | Proposed |
-| [31](PIP-0031.md)     | New Wallet: Multi-Platform & Multi-Paradigm   | Herman Schoenfeld            | Protocol   | Proposed |
+| [31A](PIP-0031A.md)     | New Wallet: Multi-Platform & Multi-Paradigm   | Herman Schoenfeld            | Protocol   | Proposed |