So as I understand it, there is 0.0085 BTC sitting in 3FEmdbfBQUhxppU4yPNFM9phx295SSskib that you are trying to get.

You will need to create the transaction, sign it and then get the "mediator" to sign it as well...

Use the "New transaction" page at Coinb.in (https://coinb.in/#newTransaction)... Paste in the reedemscript... It will find the inputs, set up the outputs (leaving enough for a decent fee)... And create the unsigned transaction...

Then use the verify page to verify the transaction has been created ok... Then use the sign page to sign the transaction.

After that, you'll need to send the "partially" signed transaction to the mediator and get them to sign it and either send it back so you can broadcast, or they can broadcast it on your behalf

If you are getting 0 balance and history... then you have simply created a different valid seed by using your 24 words in a different order. Not all combinations of your words will generate a valid seed, but it is indeed possible that different combinations will generate a valid wallet.

As an example, both of these seeds use the exact same 12 words... but in a different order and are valid BIP39 seeds:

auction squirrel behind veteran series pass major donor melody orient speak animal
speak pass auction behind series major squirrel donor veteran animal melody orient

If it has been sent back to a "1" address... which you have the keys for... you could either import the private key into a wallet like Electrum which would allow you to create a transaction and send all the coins to wherever you want... Or you could do it all manually using: https://coinb.in/#newTransaction (download the offline copy as per the links at the bottom of that page)

Just put in the public address at the top, click "Load"... it'll load all the unspent inputs. Adjust the options as required (I'd recommend enabling RBF in case you miscalculate the fee). You can then input the output address and amount you want to send... (NOTE that you need to calculate the fee manually. Current recommended fees are totally retarded at 450 sats/byte!!?! )

Click submit, get the unsigned Transaction Hex...

Use the "Verify" page (https://coinb.in/#verify) to double check everything is how you want it...

If it's all ok, then goto the "Sign" page (https://coinb.in/#sign) paste in the hex, put in the private key... and get the signed Transaction Hex...

Then use the "Broadcast" page (https://coinb.in/#broadcast) to actually send your transaction

Not necessarily... because the rest of the network would have rejected the transaction as "dust"... most of the nodes would have refused to propagate the transaction... and you transaction would have effectively "disappeared"... which it appears to have done.

At this point in time, your only hope is that CoinJar refund you your 989 sats and your CoinJar points.

In the future, I'd recommend you don't try and send anything less than 0.001 BTC from CoinJar at the very minimum. Given that CoinJar are using a default of "0.0005 bitcoin transaction fee"

I'm going to go ahead and guess that the entire transaction was rejected by the network due to the ridiculously small amount that you attempted to send. You attempted to send only 989 satoshis!!?!

Pretty sure that your 0.00000989 BTC would have been classified as "dust". Coinjar probably deducted their fees and you ended up with 0 left... or it got rejected by the network and their system failed to recognise this and hasn't put the coins back into your account.

Even if they had attached a fee of only 5 sats/byte, the transaction fee would have been like 1000 sats... which would have been more than you were attempting to send!!

If the addresses do not match, then the "Derivation Path" you are using is most likely incorrect. Double check that you have used:

m/0'/0

and

m/0'/1

The ' (apostrophe) characters are important!

Ok, so it seems that you may be getting a little confused with how the BTC and BCH fork actually works... and where your coins should be.

You stated that you moved BTC AFTER the fork, and then checked the addresses that currently have BTC and you see BTC, but no BCH... that is EXPECTED behaviour. You moved BTC to a new address AFTER the fork, that leaves the BCH on the OLD address.

That is why you see BCH on the "OLD" addresses ("last seen date states before the fork")... ONLY addresses that contained BTC at the moment the chains forked, will contain any BCH now. What you've done with BTC AFTER the fork occurred won't impact on any BCH.

So typing your addresses that currently hold BTC into blockchair, won't show BCH if those addresses received BTC AFTER the fork... you need to type in the addresses that had BTC BEFORE the fork.

Is your wallet 2FA or MultiSig?  If it is 2FA, then because it works in a slightly different way to a normal MultiSig (ie. you have TWO master private keys in the wallet) what you want to do is this:

NOTE: this exposes the xprvs for your 2FA wallet, be VERY careful and mindful of the security implications of doing this. An offline computer/VM/Live distro with no networking is recommended.

NOTE: Electrum v2.9+ required (Tested on v2.9.3)

1. Restore you 2FA wallet and DISABLE 2FA when prompted. ("File -> New\Restore -> 2FA wallet -> I already have a seed -> DISABLE")

2. DO NOT use a password

3. On the addresses tab (Wallet -> Show Addresses), right click the address you need to sign with and select details, this will give you your redeem script.

4. Goto https://coinb.in/#verify and paste your redeem script (Note down the 3 public addresses it gives you)

5. Find your "restored2FA" wallet file (%appdata%\Electrum\wallets) and open it in the Text editor of your choice. You should find sections labelled "x1/" and "x2/" that contain your two xprv "rootKeys":


6. Create a new wallet using the "x1" xprv ("File -> New\Restore -> Standard wallet -> Use public or private keys -> Paste in the xprv")

7. Look in the addresses tab for a matching address from step 4, right click and "sign/verify message"

8. Sign the message required

9. Repeat Steps 6 thru 8 with the "x2" xprv.

10. Make sure you have deleted the unencrypted "restored2FA" wallet. or alternatively, move all your coins out of your 2FA wallet as you should probably consider it compromised.

So the block count in Armory is increasing as new blocks are mined?

It's just the scanning thing at the top?

bitcoinarmory.com is the OLD bitcoin armory website... btcarmory.com is the new "official" Armory website.

Additionally, I'm not sure if that 0x98832223 cert belongs to goatpig or the old Armory company... I suspect it is the OLD cert as according to: https://btcarmory.com/docs/verify the sig listed there is "Armory signing key (4922589A)"

As above, you will need to post the armorylog.txt and dblog.txt, found in your Armory datadir.

Please use pastebin.com and then post the pastebin.com links here

Before you start, you should probably make a backup of the current wallet files

Then, in Armory... click the "Import or Restore Wallet" button in the top right corner...




Select "Single Sheet Backup"... (you may also want to check the "test" box at the bottom before you do it for real)




select "Version 1.35c (2 Lines unencrypted)"... and enter your two lines of the root key...




Armory should then recreate the wallet. If you still have that wallet loaded in your Armory, it'll probably warn you and you can either Merge or Overwrite it...



Your best option is probably to click "Merge" and reset your passphrase Then kick back and relax while it regenerates your wallet and then rescans the DB for your transactions etc.


side note: for what it's worth, a screen shot of your wallet root key is a REALLY bad way to store your root key... it's like the 12 word seed for other HD wallets... it should NEVER be stored digitally.

What wallet are did you use to send the MultiSig transaction from initially? and what type of address did the BTC get returned to? Does it start with a "1" or a "3"?

How did you cancel the transaction? Generally, once a transaction is broadcast to the network it can't be cancelled.

The BTC will not have been refunded to a wallet, it will have been refunded to an address. If the receiving party refunded to an address OTHER than the sending address, then they are at fault. You should never refund to anywhere other than the address that sent the funds or you run the risk of sending BTC to the wrong person.

In any case, if you know the address the funds were returned to, and you have the private key(s) for it... you should be able to create a transaction that sends the coins to wherever you like.

Those THREE transactions that you listed in the OP (#2 and #3 have the same TXID ) send:

0.04062145 BTC to 1H4jo73dLztygoYYfQFtSpak4oKzq6phUQ
0.04048235 BTC to 1ASS4GteXyc24qcoymN8pkbs3wXQKJmnoh
0.02218805 BTC to 1Q6JqYMixd93444AExcghDixzc4SAJ9nCj

for a total of 0.10329185 BTC sent... so I'm assuming you missed a transaction somewhere...



Where exactly is this showing? In bitpanda or in your marketplace account? If the amounts you've sent are not showing in your marketplace account, then either you sent to the wrong addresses or the marketplace is broken or a scam. You should contact their support.

Now it's using "C:\Users\*****\AppData\Roaming\Bitcoin\blocks" as your satoshi-datadir... it would appear that your "Bitcoin Home Dir" is not set correctly in Armory...

What's interesting is that it found blocks on C: Is that where the BitcoinUnlimitedCash blocks were stored?

By default, blockchair.com shows BTC... So, did you flick the switch on blockchair.com to change this:


into this:



So that you can see BCH addresses/transactions?

What wallet did you use? because all four of those transactions are indeed confirmed... and the outputs of all those transactions have already been "spent"??!?

Were you sending the coins to your own wallet or someone else?

You can't recover BCH from Electrum... You need to use a BCH compatible wallet like ElectronCash. www.electroncash.org

If you had BTC on addresses at the time of the fork on Aug 1, then those addresses will contain BCH now, regardless of what you did with your BTC after August 1st.

Ok... in that case, set the Bitcoin install directory to "D:\Program Files\Bitcoin" (without the quotes).... and the datadir as "D:\Program Files\Bitcoin\Bitcoin" (again, with the quotes)... and tick the box that says "let Armory start Bitcoind in the background"...

Then make sure that Bitcoin Core is shutdown... and restart Armory.