renamed CIP-30 to CIP-31

CIP-0030/CIP-0030.md → CIP-0031/CIP-0031.md

@@ -1,5 +1,5 @@
 ---
-CIP: 30
+CIP: 31
 Title: On-Chain Token Metadata Standard
 Authors: Matt Ho <matt.ho@gmail.com>
 Comments-URI: https://github.com/cardano-foundation/CIPs/pull/137
@@ -11,7 +11,7 @@ License: CC-BY-4.0
 
 # Abstract
 
-This specification defines a new transaction metadata label (i.e. `20`) and entry for [CIP-0030] to associate token metadata 
+This specification defines a new transaction metadata label (i.e. `20`) and entry for [CIP-0031] to associate token metadata 
 during a minting transaction.  Unlike CIP-28, this proposal is intended to define a specific schema to allow basic information
 about fungible tokens to be provided On-Chain.
 
@@ -100,7 +100,7 @@ mechanism provides users a better understanding of where their tokens came from.
 The url provided in the token metadata should return content in either html or JSON format.  
 
 * In JSON format, the url should return a JSON block of the same shape as the on-chain token metadata that includes both the policy-id and asset-name to be verified.
-* In HTML format, the url should contain the a `meta` tag with `name` of `cip-30:authenticate` and a value of a comma separate list of tokens to declare as authenticate where tokens are formatted as `{policy id}{hex-encoded asset name}` with no space in between
+* In HTML format, the url should contain the a `meta` tag with `name` of `cip-31:authenticate` and a value of a comma separate list of tokens to declare as authenticate where tokens are formatted as `{policy id}{hex-encoded asset name}` with no space in between
 
 ## Example 1 - On-Chain Metadata
 
@@ -129,7 +129,7 @@ The metadata attached to this transaction is as follows:
 When I visit, the url, `https://example.com/`, I am returned HTML which includes the following tag:
 
 ```html
-<meta name="cip-30:authenticate" value="123456789012345678901234567890123456789012345678901234564558414D504C452F50"/>
+<meta name="cip-31:authenticate" value="123456789012345678901234567890123456789012345678901234564558414D504C452F50"/>
 ```
 
 ## Example 2 - On-Chain Reference
@@ -212,7 +212,7 @@ boilerplate required to satisfy this CIP.
 This CIP is intended to handle the common use faced primarily by exchanges as wallets that need to display tokens to their users.  
 Other standards, like `CIP-25`, the NFT metadata standard, will be more appropriate for handling specialized use cases.  
 
-It is not expected nor desired for all tokens to contain `CIP-30` metadata.
+It is not expected nor desired for all tokens to contain `CIP-31` metadata.