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
In order to simplify the on boarding of new users to the taproot assets protocol, we should automatically FinalizeBatch when running MintAsset by default (and have the option when running MintAsset to not automatically FinalizeBatch if we want to do it in two separate steps). New users likely just want to test minting an asset and will be confused of the purpose of the FinalizeBatch step. The FinalizeBatch step seems to be separate so that we can run MintAsset many times and then record all minted assets with a single on chain transaction. This is a very powerful function of the protocol, but it likely won't be used by new users, especially when they may only run MintAsset one or two times and on chain fees on main net may be low at the time, or they are running on testnet or regtest where there is no concern for fees.
The text was updated successfully, but these errors were encountered:
In order to simplify the on boarding of new users to the taproot assets protocol, we should automatically FinalizeBatch when running MintAsset by default (and have the option when running MintAsset to not automatically FinalizeBatch if we want to do it in two separate steps). New users likely just want to test minting an asset and will be confused of the purpose of the FinalizeBatch step. The FinalizeBatch step seems to be separate so that we can run MintAsset many times and then record all minted assets with a single on chain transaction. This is a very powerful function of the protocol, but it likely won't be used by new users, especially when they may only run MintAsset one or two times and on chain fees on main net may be low at the time, or they are running on testnet or regtest where there is no concern for fees.
The text was updated successfully, but these errors were encountered: