Re: [ANN] [BTCP] BitcoinPrivate: A Truly Private Bitcoin [Equihash]

This is working now for ZCL (last example below was not working before), what about BTC balances (first two examples)?

Address 1F34duy2eeMz5mSrvFepVzy7Y1rBsnAyWC converted to b1JWGK6p2PoQ6D3mRsQ5o6VwoAHZGANqsZq https://blockchain.info/address/1F34duy2eeMz5mSrvFepVzy7Y1rBsnAyWC
Address 13MAXoPLQEmrtSTASDZrGNNpmsZ1gsAUnn converted to b16pNCzEL9Poy1imjPMzprsMWQ9G5xfAwNS https://blockchain.info/address/13MAXoPLQEmrtSTASDZrGNNpmsZ1gsAUnn
ZCL Address t1JrGxVYSS2N3LuWozafz5Hpxv5YbtiFYNy converted to b15SsdLyJCrcYsYnV1JHqXyhjHh4bSfqof7 http://zclassicexplorer.com/insight/address/t1JrGxVYSS2N3LuWozafz5Hpxv5YbtiFYNy

By some miracle the BTC utxos are now visible in the explorer, example: https://explorer.btcprivate.org/address/b1JWGK6p2PoQ6D3mRsQ5o6VwoAHZGANqsZq

As we can see this was done the 3rd of March by sending "Newly Generated Coins" to the addresses

This means that the method for moving/claiming BTCP from BTC is not the same than for ZCL since previous transactions on BTC chain do not exist on BTCP one

How to do it is explained here: https://bitcointalk.org/index.php?topic=2827163.msg31911075#msg31911075

Of course, there is another funny thing to keep the mess moving on with this fork: segwit is not supported by BTCP, neither BIP143 signing, apparently there is a kind of workaround (https://github.com/BTCPrivate/BitcoinPrivate/pull/77), which is for now unclear and maybe not working (https://github.com/BTCPrivate/BitcoinPrivate/pull/140), then funds on segwit addresses cannot for now be moved