745 and 765 to Accepted, 755 and 756 to Council Review (#773)

Signed-off-by: Michael Garber <michael.garber@swirldslabs.com>
hashgraph · Aug 1, 2023 · 9ff3fc5 · 9ff3fc5
1 parent 38958dc
commit 9ff3fc5
Show file tree

Hide file tree

Showing 4 changed files with 33 additions and 9 deletions.
diff --git a/HIP/hip-745.md b/HIP/hip-745.md
@@ -6,11 +6,11 @@ working-group: Simi Hunjan <@SimiHunjan>, Ognyan Chikov <@ochikov>, Peter Tonev
 type: Standards Track
 category: Application
 needs-council-approval: No
-status: Last Call
+status: Accepted
 last-call-date-time: 2023-07-28T07:00:00Z
 created: 2023-05-30
 discussions-to: https://github.com/hashgraph/hedera-improvement-proposal/discussions/746
-updated: 2023-07-14
+updated: 2023-08-01
 ---
 
 ## Abstract

diff --git a/HIP/hip-755.md b/HIP/hip-755.md
@@ -6,11 +6,11 @@ working-group: Richard Bair (@rbair23), Jasper Potts (@jasperpotts)
 type: Standards Track
 category: Service
 needs-council-approval: Yes
-status: Last Call
+status: Council Review
 last-call-date-time: 2023-07-28T07:00:00Z
 created: 2023-06-14
 discussions-to: https://github.com/hashgraph/hedera-improvement-proposal/pull/755
-updated: 2023-07-14
+updated: 2023-08-01
 ---
 
 ## Abstract

diff --git a/HIP/hip-756.md b/HIP/hip-756.md
@@ -6,11 +6,11 @@ working-group: Richard Bair (@rbair23), Jasper Potts (@jasperpotts)
 type: Standards Track
 category: Service
 needs-council-approval: Yes
-status: Last Call
+status: Council Review
 last-call-date-time: 2023-07-28T07:00:00Z
 created: 2023-06-14
 discussions-to: https://github.com/hashgraph/hedera-improvement-proposal/pull/756
-updated: 2023-07-14
+updated: 2023-08-01
 ---
 
 ## Abstract

diff --git a/HIP/hip-765.md b/HIP/hip-765.md
@@ -6,15 +6,40 @@ working-group: Ashe Oro (@Ashe-Oro), Michiel Mulders (@michielmulders)
 type: Standards Track
 category: Service
 needs-council-approval: Yes
-status: Last Call
+status: Accepted
 last-call-date-time: 2023-07-28T07:00:00Z
 created: 2023-07-11
 discussions-to: https://github.com/hashgraph/hedera-improvement-proposal/pull/765
-updated: 2023-07-20
+updated: 2023-08-01
 ---
 
 ## Abstract
 
+
+This HIP proposes the addition of the metadata field to Non-Fungible Token Class, taking after the individual Non-Fungible Token (NFT) metadata field which was added in HIP-17. While HIP-17 metadata is scoped to a single NFT, here we propose adding metadata scoped to an entire token class.
+
+## Motivation
+
+Similar to NFT's on the network, the fungible token implementation is largely functional. There is a need for a token creator to specify additional "metadata" about the token. The data and formatting is explored in HIP-YYY but there is no field suitable for storing the link to this metadata. 
+
+The most 'logical' field proposed to store this data is the existing 'memo' field, however a dedicated metadata field is more appropriate.
+
+## Rationale
+
+The success of HIP-412 in standardizing the individual NFT space on Hedera demonstrates the potential of standardized metadata functionality for NFT Collections as well. Wallets, explorers and other applications can display relevant supplementary information about tokens to users in a decentralized fashion.
+
+## User stories
+
+As a token creator, I want a platform-standardized method to host information about my NFT Collection in a decentralized fashion, allowing applications to query data such as token icon, featured image and website.
+
+As a wallet or explorer, I want to query a mirror node to obtain the metadata for any NFT Collection token, similar to current individual non-fungible tokens. Mirror nodes currently return metadata for individual NFTs; but for an NFT Collection token genrally, we want to get **Token-level** (ie Collection-level) metadata.
+
+As a developer, I want to store the metadata uri in a dedicated field, to avoid ambiguity of using an overloaded field such as 'memo'.
+
+## Specification
+
+## HAPI Changes
+=======
 This HIP proposes the addition of the metadata field to Non-Fungible Token Class, taking after the individual Non-Fungible Token (NFT) metadata field, which was added in [HIP-17](https://hips.hedera.com/hip/hip-17). While HIP-17 metadata is scoped to a single NFT, here we propose adding metadata scoped to an entire token class.
 
 ## Motivation
@@ -81,7 +106,6 @@ message TokenCreateTransactionBody {
 2. Permit updates by adding a new field to [`TokenUpdateTransactionBody`](https://github.com/hashgraph/hedera-protobufs/blob/main/services/token_update.proto),
 
 **Updating the metadata field should require a metadataKey (ie [HIP-657](https://github.com/hashgraph/hedera-improvement-proposal/blob/main/HIP/hip-657.md))**
-
 ```
 message TokenUpdateTransactionBody {
     ...