Skip to content

Commit

Permalink
Updated Release Notes
Browse files Browse the repository at this point in the history
  • Loading branch information
ACStone-MTS committed Mar 17, 2023
1 parent 9d9bf0a commit 8305968
Show file tree
Hide file tree
Showing 3 changed files with 16 additions and 7 deletions.
16 changes: 13 additions & 3 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,13 +13,23 @@ All notable changes to this project will be documented in this file. The format

### Added

* Added a new modality named `EventsMode` that dictates how the installed instance of CEP-78 will handle the recording of events. Refer to the README for further details
* Added a new modality named `EventsMode` that dictates how the installed instance of CEP-78 will handle the recording of events. Refer to the [README](./README.md#eventsmode) for further details

* Added the ability to define additional `NFTMetadataKind`s as either `additional_required_metadata` or `optional_metadata`. Refer to the `Installing the Contract` section of the README for more information on using these arguments.
* Added the ability for the contract to specify one or more metadata schemas, with the option to further specify optional metadata schemas. Additional required metadatas are specified by `additional_required_metadata`, while additional optional metadata schemas can be specified using `optional_metadata`. Refer to the [`Installing the Contract`](./README.md#installing-the-contract) section of the README for more information on using these arguments.

* When upgrading from a contract instance, you may now change the `total_token_supply` to a number higher than the current number of minted tokens, but lower than your previous total. The number cannot be zero. More information is available in the upgrade tutorials.

* Added the ability to revoke approval.
* Added a new entrypoint called `revoke` that allows token owners to revoke a single approval.

* Added a new entrypoint `is_approval_for_all` that allows a caller to check if they are considered an `operator` for a token owner.

* For js-client changes, please view the respective [change log](./client-js/CHANGELOG.md).

### Changed

* `OwnerReverseLookupMode` now contains an additional option, `TransfersOnly`, which begins tracking ownership upon transfer. More information can be found [here](./README.md#ownerreverselookupmode).

* Optimized the `set_approval_for_all` entrypoint implementation to reduce gas costs.

## Release 1.1.1

Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -260,7 +260,7 @@ This modality provides the following options:

1. `NoLookup`: The reporting and receipt functionality is not supported. In this option, the contract instance does not maintain a reverse lookup database of ownership and therefore has more predictable gas costs and greater scaling.
2. `Complete`: The reporting and receipt functionality is supported. Token ownership will be tracked by the contract instance using the system described [here](#owner-reverse-lookup-functionality).
3. `TransfersOnly`: The reporting and receipt functionality is supported alike `Complete` however it is not directly active after minting but only after a first transfer. This modality is for usecases where the majority of NFTs are owned by a private minter and only NFT's that have been transferred benefit from reverse lookup tracking. Token ownership will be as well tracked by the contract instance using the system described [here](#owner-reverse-lookup-functionality).
3. `TransfersOnly`: The reporting and receipt functionality is supported like `Complete`. However, it does not begin tracking until the first transfer. This modality is for usecases where the majority of NFTs are owned by a private minter and only NFT's that have been transferred benefit from reverse lookup tracking. Token ownership will also be tracked by the contract instance using the system described [here](#owner-reverse-lookup-functionality).

Additionally, when set to `Complete`, causes a receipt to be returned by the `mint` or `transfer` entrypoints, which the caller can store in their account or contract context for later reference.

Expand Down
5 changes: 2 additions & 3 deletions client-js/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

### Added

- Added support for CEP47Events
- Added support for CEP47 Events
- Added support for CES events basing on ces-js-parser
- Some small code cleanups (added typings etc)
- Some changes in `examples/`
Expand All @@ -30,5 +30,4 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

### Fixed

- Fixed how `migrate` deploy is constructed.

- Fixed how `migrate` deploy is constructed.

0 comments on commit 8305968

Please sign in to comment.