You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currenlty the mintin process does not allow for explicitly creating multiple assets from different asset IDs with the same script key. During MarkBatchConfirmed we use the script key as the unique identifier for the asset. We should add the actual 32-byte asset ID into that query to support asset script reuse over different Asset IDs.
Now that users can provide external script keys, many of the assumptions about per-batch script key uniqueness are now invalid. The only enforced-unique field for batches is the asset name.
We could use TapCommitmentKey() + AssetCommitmentKey() as the unique ID here.
Currenlty the mintin process does not allow for explicitly creating multiple assets from different asset IDs with the same script key. During
MarkBatchConfirmed
we use the script key as the unique identifier for the asset. We should add the actual 32-byte asset ID into that query to support asset script reuse over different Asset IDs.taproot-assets/tapdb/asset_minting.go
Line 1617 in 1083cf1
The text was updated successfully, but these errors were encountered: