v1.3.3

• Support Keystone

v1.3.2

• Support cursed inscription
• Optimized the UTXO selection strategy of runes to reduce gas fees
• Add runes logo
• Add Alichemypay
• Fix Runes details

v1.3.1

• Fixed the bug of runes constructing a burn transaction
• Fixed the bug of "can not convert 1+21 to bigint" appearing during transfer

v1.3.0

1. Runes Support

• View and send Runes assets on the testnet.

2. Unconfirmed Balance Mode

• Introduced a toggle for enabling unconfirmed balances.
• Unconfirmed balance usage is automatically disabled when holding #ARC20 or #Runes assets.
• You can re-enable it in Settings, but be cautious as these asset types are currently not recognized in the mempool, which could lead to asset burning risks.

3. About Unavailable Balances

• Added explanations for balances labeled as 'Unavailable', which include inscriptions, ARC20, and Runes balances. When Unconfirmed Balance is disabled, this will also include unconfirmed balances.
• Due to the system handling a maximum of 500 UTXOs at a time, any excess UTXOs at an address will temporarily be classified as 'Unavailable'.

4. Fee Rate Alerts

• No longer forcing pop-up warnings for transactions with high or low fee rates.
• Risk level downgraded, now indicated by a subtle tag.

5. Default OutputValue Adjustment

• Reverted the default inscribe outputValue to 546 sats for simplified operations.
• For certain addresses, manual adjustment to 330/294 is still possible if necessary.

6. Batch Signing Fixes and Optimization

• We've addressed the issues with batch signing and made some modifications.
• All pending transactions for signature are now explicitly listed and need to be reviewed individually.
• For now, we've withheld the feature of one-click batch transaction signing due to its associated risks.
• We want our users to fully comprehend these risks before performing such operations, and we plan to elaborate more on this in future versions.

v1.2.10

• Support 5-byte BRC20
• Improve the display of BRC20

v1.2.9

• Added memos parameter to unisat.sendBitcoin method, for constructing runes transactions (github #164 and #167)
• Fixed a bug in the unisat.sendInscription method (github #159)
• Fixed the problem where an order could not succeed when the wallet balance and the payment amount were exactly equal when inscribe a TRANSFER inscription
• Improved balance display, showing both available and unavailable balances
• Improved the asset display during transaction signing, added BRC20 display
• Improved risk warnings during transaction signing, and now requires the input of CONFIRM to proceed when warnings appear.

v1.2.8

• The unisat.sendBitcoin method has added a memo parameter, increasing OP_RETURN output when sending btc.
• A new unisat.getBitcoinUtxos method has been added, through which the developers can get users UTXO without inscription assets.
• A new unisat.signData method has been added, through which the developers can have users participate in multi-signature.

v1.2.7

• Allowing decimal inputs when inscribing BRC20 TRANSFER.
• Support more precise inscription outputValue, reduced to 294 for P2WPKH addresses.
• Use deterministic ECDSA signatures in unisat.signMessage.

v1.2.6

• Mixed inscriptions can now be sent without splitting
• Fixed an issue with the address amount input box restrictions:
  • Limited BTC input to a maximum of 8 decimal places.
  • Spaces are now ignored when entering an address.
  • Restricted ARC20 input amount.

v1.2.5

• Minimum output amount for inscriptions can now be set to 330.
• Added the ability to disable Atomicals (only when there are no Atomicals assets).
• Added the API isAtomicalsEnabled to determine if the user has enabled the Atomicals feature.
• Implemented version checking to prompt for upgrades when a new version is available.
• Fixed an issue where transferring inscriptions and ARC20 without available BTC would result in an error.