Skip to content

Commit

Permalink
[2137]: Add some changelog entries.
Browse files Browse the repository at this point in the history
  • Loading branch information
SpicyLemon committed Sep 30, 2024
1 parent 3feeca2 commit e9c0ab2
Show file tree
Hide file tree
Showing 2 changed files with 11 additions and 0 deletions.
10 changes: 10 additions & 0 deletions .changelog/unreleased/api-breaking/2137-bank-scope-value-owners.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
* The `Ownership` query in the `x/metadata` module now only returns scopes that have the provided address in the `owners` list [#2137](https://github.com/provenance-io/provenance/issues/2137).
Previously, if an address was the value owner of a scope, but not in the `owners` list, the scope would be returned
by the `Ownership` query when given that address. That is no longer the case.
The `ValueOwnership` query can be to identify scopes with a specific value owner (like before).
If a scope has a value owner that is also in its `owners` list, it will still be returned by both queries.
* The `WriteScope` endpoint now uses the `scope.value_owner_address` differently [#2137](https://github.com/provenance-io/provenance/issues/2137).
If it is empty, it indicates that there is no change to the value owner of the scope and the releated lookups and validation
are skipped. If it isn't empty, the current value owner will be looked up and the coin for the scope will be transferred to
the provided address (assuming signer validation passed).
* An authz grant on `MsgWriteScope` no longer also applies to the `UpdateValueOwners` or `MigrateValueOwner` endpoints [#2137](https://github.com/provenance-io/provenance/issues/2137).
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
* Use the bank module to keep track of the value owner of scopes. [#2137](https://github.com/provenance-io/provenance/issues/2137).

0 comments on commit e9c0ab2

Please sign in to comment.