Skip to content

Commit

Permalink
CIP-0068 | Allow [* bounded_bytes] for images (#809)
Browse files Browse the repository at this point in the history
* cip-68 image update

* bounded bytes on second uri

* Update README.md

Also modify Line # 436 to match the proposed new format for URI

* version update

* adding version commit

---------

Co-authored-by: Adam Dean <63186174+Crypto2099@users.noreply.github.com>
  • Loading branch information
nicholas-maselli and Crypto2099 authored Jun 2, 2024
1 parent c5f40f4 commit aef3538
Showing 1 changed file with 11 additions and 6 deletions.
17 changes: 11 additions & 6 deletions CIP-0068/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -191,7 +191,7 @@ metadata =
; A valid Uniform Resource Identifier (URI) as a UTF-8 encoded bytestring.
; The URI scheme must be one of `https` (HTTP), `ipfs` (IPFS), `ar` (Arweave) or `data` (on-chain).
; Data URLs (on-chain data) must comply to RFC2397.
uri = bounded_bytes ; UTF-8
uri = bounded_bytes / [ * bounded_bytes ] ; UTF-8
; Custom user defined plutus data.
; Setting data is optional, but the field is required
Expand All @@ -200,7 +200,7 @@ extra = plutus_data
datum = #6.121([metadata, version, extra])
version = 1 / 2
version = 1 / 2 / 3
```

Example datum as JSON:
Expand Down Expand Up @@ -307,7 +307,7 @@ metadata =
; A valid Uniform Resource Identifier (URI) as a UTF-8 encoded bytestring.
; The URI scheme must be one of `https` (HTTP), `ipfs` (IPFS), `ar` (Arweave) or `data` (on-chain).
; Data URLs (on-chain data) must comply to RFC2397.
uri = bounded_bytes ; UTF-8
uri = bounded_bytes / [ * bounded_bytes ] ; UTF-8
; Custom user defined plutus data.
; Setting data is optional, but the field is required
Expand All @@ -316,7 +316,7 @@ extra = plutus_data
datum = #6.121([metadata, version, extra])
version = 1 / 2
version = 1 / 2 / 3
```

Example datum as JSON:
Expand Down Expand Up @@ -442,7 +442,7 @@ extra = plutus_data
datum = #6.121([metadata, version, extra])
version = 2
version = 3
```

Example datum as JSON:
Expand Down Expand Up @@ -550,7 +550,8 @@ version of these tokens from any point in time with the following format:
1. [6d897eb](https://github.com/cardano-foundation/CIPs/tree/6d897eb60805a58a3e54821fe61284d5c5903764/CIP-XXXX)
2. [45fa23b](https://github.com/cardano-foundation/CIPs/tree/45fa23b60806367a3e52231e552c4d7654237678/CIP-XXXX)
3. **Current**
3. [bfc6fde](https://github.com/cardano-foundation/CIPs/tree/bfc6fde340280d8b51f5a7131b57f4cc6cc5f260/CIP-XXXX)
4. **Current**
```

Each time a new version is introduced the previous version's link MUST be updated to match the last commit corresponding
Expand All @@ -573,6 +574,10 @@ versions of the affected tokens. `asset_name_labels` **MUST** only be marked obs

- Added new RFT asset class (444)

#### version 3

- Added [* bounded_bytes] support to the image and src tags on the metadata

## Rationale: how does this CIP achieve its goals?

Without separation of `reference NFT` and `user token` you lose all flexibility and moving the `user token` would be
Expand Down

0 comments on commit aef3538

Please sign in to comment.