Skip to content

Conversation

@Sophie-Ag00001
Copy link
Collaborator

PR Description

Summary of Changes

This PR implements a mechanism to update the metadata field in transactions involving item asset types. Now, when users make changes to an item's metadata, the genesis hash of the asset will point to the transaction hash of the current transaction instead of the original genesis hash. Validation logic has been updated accordingly to enforce this new constraint.

Background

The ability to update metadata for item assets is crucial for tracking changes and ensuring data accuracy. The changes made in this PR ensure that the asset's genesis hash aligns with the most recent transaction, thereby improving the integrity of metadata updates without altering the structure of existing data models.

Testing Instructions

To test these changes:

  1. Create a new transaction involving an item asset.
  2. Update the metadata for the item.
  3. Verify that the genesis hash of the asset points to the transaction hash of the input transaction.
  4. Attempt to validate the transaction, ensuring that the new validation logic rejects any misuse of the genesis hash.

Known Issues or Limitations

No known issues at this time. All struct fields remain unchanged to maintain backward compatibility. However, further testing may be required to ensure all edge cases are handled correctly.

Additional Notes

Please refer to the updated validation rules in the documentation for further details on the transaction validation process.

…saction with an item asset type. if the user is making an update to the metadata of an item, the genesis hash of the asset should point to the transaction hash of the input transaction itself rather than the genesis hash of the input transaction. make sure that the validity checks for item transactions check for this constraint when trying to validate. you are not allowed to modify the fields of any existing structs, they need to remain the same
@Sophie-Ag00001 Sophie-Ag00001 requested a review from a team as a code owner January 29, 2025 14:34
@BHouwens BHouwens closed this Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants