Please help!
I successfully sent my BTC from Armory 0.96.3-beta.
Before I did that I created a signed tx to transfer my BCH. I signed with the bitcoin cash signer and disabled RBL as described in this thread here.
I saved both the unsigned TXSIGCOLLECT data and the signed TXSIGCOLLECT data. I also saved the raw tx.
Passing the raw tx to http://blockdozer.com/insight/tx/send however does not work!
Also it seems like the raw tx is not even a hex. It contains a "+" character for example.
I also tried to convert this string to hex (both from ASCII and BASE64) and submit the result which also did not work.
Any help is much appreciated!
In particular I'm looking for a way to get a valid transaction from the data I have.
Topic: Using Armory on the BCH chain - page 16. (Read 45958 times)
You can do it with a cold wallet, but you need to update Armory on the cold wallet. I moved it to my offline wallet on a USB stick, and used it to sign my BCH so I could transfer them to my Ledger (Keeping two chains up to date is too much, and BCH is low priority for me. Just keeping them until I see what happens with the 2x fork).
Now with BTC on the Hot Wallet its working fine with the BCH signer on BCH chain.
My question now is about the Cold Wallet, is there any possibility to do the same?
I dont want to get my cold wallet change in a hot wallet.....
My question now is about the Cold Wallet, is there any possibility to do the same?
I dont want to get my cold wallet change in a hot wallet.....
Yes, same question here. Would this work with a cold wallet. Did you try it?
Thanks!
Thanks a lot!
Quick Q: Is the BCH signer supported for multi-sig transactions (lockboxes)? Is there a way to select BCH Signer for when creating a multi sig transaction? If not, is this a particularly easy thing to add - ability to select BCH Signer in Lockbox mode - or there are no plans to include this?
Background:
I finally got the Bitcoin ABC & Bch Signer working in a VMWare Ubuntu instance.
I'm able to see my BCH balances correctly both on regular wallets and my multi-signature (lockbox) wallets.
But, I can only select the BCH Signer for when doing transactions using regular wallets. I can't get it working with the multi-signature/lockbox wallets.
Is there any way I can at least just get the BCH out of there by somehow manually crafting the BCH signer multi-sig-transaction? (I don't mind even just sweeping private keys, but these funds are sitting in a multi-signature wallet, so I don't believe key swiping/export would work there, I don't know).
EDIT: I'm in the process of going through Bitcoin ABC node and seeing if I can manually do a multi sig transaction that way by importing private keys.
Image of when doing a Multi-sig/Lockbox transaction, error returned:
non-mandatory-script-verify-flag (Signature must use SIGHASH_FORKID)
Background:
I finally got the Bitcoin ABC & Bch Signer working in a VMWare Ubuntu instance.
I'm able to see my BCH balances correctly both on regular wallets and my multi-signature (lockbox) wallets.
But, I can only select the BCH Signer for when doing transactions using regular wallets. I can't get it working with the multi-signature/lockbox wallets.
Is there any way I can at least just get the BCH out of there by somehow manually crafting the BCH signer multi-sig-transaction? (I don't mind even just sweeping private keys, but these funds are sitting in a multi-signature wallet, so I don't believe key swiping/export would work there, I don't know).
EDIT: I'm in the process of going through Bitcoin ABC node and seeing if I can manually do a multi sig transaction that way by importing private keys.
Image of when doing a Multi-sig/Lockbox transaction, error returned:
non-mandatory-script-verify-flag (Signature must use SIGHASH_FORKID)
I'm in a similar situation. I understand that currently Armory does not allow to sign such transactions using the BCH code. Do you know of some other way I can access the BCH stored in lockboxes? Some crude export/raw hex/import/CLI magic would be a great workaround.
BCH for lock boxes: https://bitcointalksearch.org/topic/0964-rc1-2227856
Quick Q: Is the BCH signer supported for multi-sig transactions (lockboxes)? Is there a way to select BCH Signer for when creating a multi sig transaction? If not, is this a particularly easy thing to add - ability to select BCH Signer in Lockbox mode - or there are no plans to include this?
Background:
I finally got the Bitcoin ABC & Bch Signer working in a VMWare Ubuntu instance.
I'm able to see my BCH balances correctly both on regular wallets and my multi-signature (lockbox) wallets.
But, I can only select the BCH Signer for when doing transactions using regular wallets. I can't get it working with the multi-signature/lockbox wallets.
Is there any way I can at least just get the BCH out of there by somehow manually crafting the BCH signer multi-sig-transaction? (I don't mind even just sweeping private keys, but these funds are sitting in a multi-signature wallet, so I don't believe key swiping/export would work there, I don't know).
EDIT: I'm in the process of going through Bitcoin ABC node and seeing if I can manually do a multi sig transaction that way by importing private keys.
Image of when doing a Multi-sig/Lockbox transaction, error returned:
non-mandatory-script-verify-flag (Signature must use SIGHASH_FORKID)
http://i.imgur.com/MMO305O.png
Background:
I finally got the Bitcoin ABC & Bch Signer working in a VMWare Ubuntu instance.
I'm able to see my BCH balances correctly both on regular wallets and my multi-signature (lockbox) wallets.
But, I can only select the BCH Signer for when doing transactions using regular wallets. I can't get it working with the multi-signature/lockbox wallets.
Is there any way I can at least just get the BCH out of there by somehow manually crafting the BCH signer multi-sig-transaction? (I don't mind even just sweeping private keys, but these funds are sitting in a multi-signature wallet, so I don't believe key swiping/export would work there, I don't know).
EDIT: I'm in the process of going through Bitcoin ABC node and seeing if I can manually do a multi sig transaction that way by importing private keys.
Image of when doing a Multi-sig/Lockbox transaction, error returned:
non-mandatory-script-verify-flag (Signature must use SIGHASH_FORKID)
http://i.imgur.com/MMO305O.png
I'm in a similar situation. I understand that currently Armory does not allow to sign such transactions using the BCH code. Do you know of some other way I can access the BCH stored in lockboxes? Some crude export/raw hex/import/CLI magic would be a great workaround.
Now with BTC on the Hot Wallet its working fine with the BCH signer on BCH chain.
My question now is about the Cold Wallet, is there any possibility to do the same?
I dont want to get my cold wallet change in a hot wallet.....
My question now is about the Cold Wallet, is there any possibility to do the same?
I dont want to get my cold wallet change in a hot wallet.....
ok, got it to work with latest release. nice tool.
mentioned some issues in RC1 thread.
mentioned some issues in RC1 thread.
There is now a 0.96.3, you probably want that one, at least if you ever plan on creating a fragmented backup.
why don't i see any specific "offline bundles" on it's Release page? https://btcarmory.com/0.96.3-release/
There is now a 0.96.3, you probably want that one, at least if you ever plan on creating a fragmented backup.
it's been years since i've updated the offline signer. can you link me to the download version for BCH signing?
edit: nvm, i got it: 0.96.2, i think.
edit: nvm, i got it: 0.96.2, i think.
how do you deal with miner fees and change when claiming BCH?
let's say your wallet pre fork has ten UTXO's with 1BTC/BCH each. post fork, you perform a 1BTC tx to buy something and your wallet automatically pulls the miner fee from one of the other nine UTXO's and dumps the change into a new address. weeks later, you go to claim the BCH via Coin Control. how do you set this tx up using the blockchain truncating Trick?
let's say your wallet pre fork has ten UTXO's with 1BTC/BCH each. post fork, you perform a 1BTC tx to buy something and your wallet automatically pulls the miner fee from one of the other nine UTXO's and dumps the change into a new address. weeks later, you go to claim the BCH via Coin Control. how do you set this tx up using the blockchain truncating Trick?
You don't, that UTXO does not exist on the backtracked copy of the chain you have.
Quote
will Armory actually dump it into the same change address created from the original BTC tx?
No there's no guarantee of that. If you use the same wallet file, you will get a fresh address every time, otherwise, who knows.
You're doing it wrong with the fees. Go into coin control, pick the outputs you want to spend, then in the recipient frame, click "MAX". This will guarantee it will move all the coins it can to the target address without leaving anything for change. That's how you want to go about moving that stuff.
how do you deal with miner fees and change when claiming BCH?
let's say your wallet pre fork has ten UTXO's with 1BTC/BCH each. post fork, you perform a 1BTC tx to buy something and your wallet automatically pulls the miner fee from one of the other nine UTXO's and dumps the change into a new address. weeks later, you go to claim the BCH via Coin Control. how do you set this tx up using the blockchain truncating Trick?
i assume you select both UTXO's that were in the original BTC tx pre fork. i would assume you could also set a much lower miner fee than what was necessary in the original BTC tx since BCH miner fees are cheaper. do you have to worry where the BCH change goes, or doesn't it matter? will Armory actually dump it into the same change address created from the original BTC tx?
edit: now that i think about it, i'm getting more confused. i'm actually trying to claim 2BCH, right, since two BCH containing UTXO's were consumed? so do i try to send 2BCH as an amount to the receiving BCH address, minus a BCH miner fee, despite the original BTC tx sending 1BTC as the amount? if so, where does Armory pull the BCH miner fee from?
let's say your wallet pre fork has ten UTXO's with 1BTC/BCH each. post fork, you perform a 1BTC tx to buy something and your wallet automatically pulls the miner fee from one of the other nine UTXO's and dumps the change into a new address. weeks later, you go to claim the BCH via Coin Control. how do you set this tx up using the blockchain truncating Trick?
i assume you select both UTXO's that were in the original BTC tx pre fork. i would assume you could also set a much lower miner fee than what was necessary in the original BTC tx since BCH miner fees are cheaper. do you have to worry where the BCH change goes, or doesn't it matter? will Armory actually dump it into the same change address created from the original BTC tx?
edit: now that i think about it, i'm getting more confused. i'm actually trying to claim 2BCH, right, since two BCH containing UTXO's were consumed? so do i try to send 2BCH as an amount to the receiving BCH address, minus a BCH miner fee, despite the original BTC tx sending 1BTC as the amount? if so, where does Armory pull the BCH miner fee from?
There is no sorting feature atm.
since i'm in the cycle of asking stupid questions, is there a way to order the UTXO's by address in Coin Control?
Uncheck the parent section.
as a suggested UX improvement, please give us the option to Uncheck All selected UTXO's in Coin Control. currently, by default, all UTXO's are checked; this can be a major pain if we want to use only a couple of UTXO's specifically for a tx while holding thousands of UTXO's in a particular wallet. this forces us to manually uncheck those thousands of boxes down to the couple we want to specifically use.
how does one correlate block height with blockfile.dat?
Since headers first (Core 0.10), crap shoot.
how does one correlate block height with blockfile.dat?
Jump to: