Skip to content

Unify asset_vault add and remove asset APIs #3078

Description

@PhilippGackstatter

Following the introduction of AssetComposition, we can unify APIs in $kernel::asset_vault:

  • add_fungible_asset and add_non_fungible_asset -> add_asset
  • remove_fungible_asset and remove_non_fungible_asset -> remove_asset

The advantage of this is:

  • It should reduce code as we can use mostly the same logic for both asset types and dispatch when necessary.
  • It prepares for custom assets.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kernelsRelated to transaction, batch, or block kernels
    No fields configured for Refactoring.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions