FreeWallet 2.0.4

Release Notes

• migrated get_running_info to v2 API
• migrated getrawtransaction and get_unspent_utxos to v2 API
• fixed issue with off by one satoshi problem in dispensers
• fixed issue with dispenser and destroy forms not working with quantities over 999

Important

This version of FreeWallet allows you to perform transactions on the Counterparty 2.0 platform and ledger

FreeWallet 2.0.3

Release Notes

• Revert to using nwjs.io v0.92.0 for builds (fixes right-click issues)

Important

This version of FreeWallet allows you to perform transactions on the Counterparty 2.0 platform and ledger

FreeWallet 2.0.2

Release Notes

As of counterparty-core 10.9, the core developers have determined that passing script_pubkey as has been done for the past 10+ years is now considered a bug. This resulted in signing libraries being unable to sign transactions generated with counterparty-core 10.9+ (electrum, bitcore, sparrow, bitcoinjs, etc)

In addition, in counterparty-core 10.9+ the transaction version has been forced from 1 to 2, which also caused problems for above mentioned signing libraries. Version 2 is typically only used when time locks are required, which is not the case in counterparty transactions. Since counterparty will need to use time locks in atomic swaps in the future, the cp core devs felt it was most appropriate to force ALL transactions to use version 2, instead of just those that use time locks, which in turn caused additional signing issues

This update resolves these issues by:

• Requesting tx data for every input in a tx and updating the tx with the input type
• Converting tx back to version 1 so that libraries are able to sign them again

Changelog

• Updates to allow signing of txs generated by counterparty-core 10.9+ (more info)
• Updates to prevent calls to cp 2.0 API unless have values for required fields (more info)

Important

This version of FreeWallet allows you to perform transactions on the Counterparty 2.0 platform and ledger

FreeWallet 2.0.1

Release Notes

• Fix ‘auto-convert BTC send to dispense` functionality
• Add back support for “fair mints”
• Clarify that API errors are coming from the CP API

Important

This version of FreeWallet allows you to perform transactions on the Counterparty 2.0 platform and ledger

FreeWallet v2.0.0

Release Notes

• Add tag as required field to /compose/destroy
• Updates to detect BTC payment to address with open dispenser
• Updated MPMA sends support new memo format (CounterpartyXCP/counterparty-core#2568)
• Re-enable form submit button after fee estimation failures
• Updates to support creating CP 2.0 dispense transactions
• update buy from dispenser form to use dispense instead of send
• Updated default servers for counterparty 2.0 APIs and Explorer

Important

This version of FreeWallet allows you to perform transactions on the Counterparty 2.0 platform and ledger

FreeWallet Classic v0.9.38

Release Notes

FreeWallet Classic is a release for users who wish to use the Counterparty Classic (9.62.0) version of Counterparty.

Tip

A release of FreeWallet which allows you to perform transactions on Counterparty 2.0 (10.4+) can be found here.

v0.9.37

• Updates to support counterparty-core /v2/ API

v0.9.36

• Updates to support Fair Minting

v0.9.35

Updates

• Disabled origin functionality in dispensers (counterparty-core 10.4 Required)
• Disabled P2SH encoding on MPMA Sends (counterparty-core 10.4 Required)

Developer Release Notes

Counterparty 10.4 removed dispenser origin functionality

This means no more simple opening up dispensers on an address other than source in a single transaction, thereby requiring 3 transactions and making dispensers more expensive to use and difficult to manage.

This is unfortunate as it has the following consequences :

Before counterparty-core 10.4 :

• Open dispenser was 1 transaction (fund dispenser address with asset and open dispenser)
• Close dispenser and return funds was 1 transaction (close dispenser and return funds to origin address)
• Could trigger a dispenser with a normal BTC send from any address (onboarded lots of ppl to Counterparty)

After counterparty-core 10.4 :

• Open dispenser is 3 transactions (1=send BTC to dispenser address, 2=send asset to dispenser address, 3=open dispenser)
• Close dispenser and return funds is 3 transactions (1=Close Dispenser, 2=send asset from dispenser address back to source, 3=Send BTC from dispenser address back to source)
• Must use a counterparty wallet in order to trigger a dispenser (Users must first download counterparty wallet before being able to use dispensers)

I raised this issue to the core devs and was ignored : CounterpartyXCP/counterparty-core#1764 (comment)

Counterparty 10.4 disabled P2SH encoding

As of counterparty-core 10.4, P2SH encoding is disabled and multisig is required for MPMA/Multi Sends.

This is unfortunate as it has the following consequences :

• Sends are now much more expensive due to being forced to use multisig encoding, which requires more outputs to encode the data than P2SH encoding did
• Sends using multisig result in leaving small amounts of BTC in multisig outputs, which requires the user to collect the outputs at a high cost in the future.

v0.9.34

• Fix issue with divisiblity on Reset Supply form
• Updates to support datatables 2.1.5