 Show Posts
|
|
Pages: [1]
|
goatpig, please explain a little more what I need to do, thanks!
It thinks your ZC output is worth 0. Did you try to empty your wallet in one go? Yes, I was trying to move my funds to Ledger before all those forks. What is ZC output? |
|
|
|
There's a fix in the testing branch, just haven't bothered putting out a build. Open source and all you know, build it yourself blah blah. If you can't build from source, you're at my mercy blah blah. Progress! I built the testing branch, now, right clicking and selecting bump fee shows a dialog that says: RBF Failure: You are trying to bump the fee of a broadcasted unconfirmed transaction. The process failed unexpectedly. To double spend your transaction, pick the relevant output from the RBF Control, found in the Send dialog in Expert User Mode. Clicking "ok" leads to the send dialog. I clicked on the RBF Control button and reviewed the outputs, went back to the send dialog and lowered the send amount. Clicking send results in an error message: Coin Selection Failure: Coin selection failed with error: Invalid spend value goatpig, please explain a little more what I need to do, thanks! |
|
|
|
|
0.96.3.99 does not work too
|
|
|
|
Will look into it. For now, you can grab the output through the RBF coin control dialog and bump yourself.
How do I do what you suggested? |
|
|
|
|
Yes, but how do I modify the fees in the raw Hex?
|
|
|
|
|
My transaction has been visible in blockchain.info for a week though. So I think our problems are different. I just need instructions on how to broadcast manually.
|
|
|
|
|
It is still not working (using armory_0.96.3.99-gcc4.7-noasm_amd64.deb). Also, what is the RBF coin control dialog? No dialog shows up when bump fee is selected.
I am considering clearing unconfirmed and making a few tx, any concerns there?
|
|
|
|
I got it working  I followed goatpig's instructions. I am augmenting them in-line here to make it easier for noobs like myself to understand. If you want to dump BCH but don't want to bother with the BCH node/don't trust their code, you can get around it with this trick:
1) You know all your prefork coins are also available on the BCH chain, therefor you only need blockchain data up to the fork point to move these coins.
2) You have all this data already in the form of the Bitcoin blockchain pre fork, so why not just use that?
3) You'll want to create a copy of your blockchain data then remove blkXXXXX.dat files up until the fork point . I don't know which file this is, something around 950~960, I'm sure someone will figure out the exact file. Note that if you did not move any coins post fork yet, you do not need to delete anything.
Important: If you did not move any coins post fork yet, you do not need to delete anything. But if you do, you need to delete enough for the newest blocks such that your transactions post fork are obscured. If you use armory on Linux, delete blocks in ~/.bitcoin/blocks 4) With this done, you want to sync a fresh DB against this blockchain folder. Do not run a node against it, just start ArmoryDB against this folder, then start ArmoryQt, it will pick up on that DB.
Basically, instead of clicking on the armory icon, go to /usr/local/bin to run ArmoryDB and armory manually. But I found it difficult, what I did instead was to, while Armory was running, go to the Help menu and choose to rescan and rebuilt data base. A pop up will show up asking to confirm that you want to rescan and rebuild the next time armory starts and that it will take a lot of time. Accept. Restart armory, and use the terminal to shut down bitcoind by running pkill bit. This way armory will remain offline 5) Once you're synced (it will show you as offline), you can create your transactions. You should pick utxos manually and keep track of them so as to not create conflicting transactions.
You need to be in expert mode. While armory is running, go to the user menu and select expert. Click on your wallet and select to send bitcoin. Enter the bitcoin cash address and the amounts and the fees (fees for the cash network are x10 lower, I used 20 satoshis per byte and it got confirmed really quickly. 6) Once your tx is ready, make sure to create it as unsigned, even if your private keys are online. You will get a blob of text that you can feed back into the offline tx GUI. There you will get to sign the tx (make sure to pick the BCH miner), and you will get another blob of text. On the right side of that dialog, you will have a button that's called "Copy Raw Tx (Hex)". This is what you are after. This hex string is your signed tx.
The glob of text is a rectangular block. Copy that, and then click on Offline Transactions on the main armory window (I spent a lot of time looking for this on the menu bar and was trying to figure out if Broadcast Raw Transaction was what I wanted, but no it isn't, the button is in the main window). Paste the block, click sign, choose the signer and in the window where you pasted the glob, there is another button like goatpig said "Copy Raw Tx (Hex)". Click that and you get a long string. 7) With the signed tx, all you need now is some online service that will broadcast it to the BCH network for you, and voila.
Paste that here: https://blockdozer.com/insight/tx/sendAnd you are done. |
|
|
|
|
I am trying to split my coins. I just sent a transaction using the legacy signer to a new btc address. But I am unable to make another transaction using the BCH signer as my balance is now 0. How can we see my balance on the cash chain? Do I need to start armory with a modified bitcoind that looks at the cash chain? Is it possible to resend the same transactions with a different signer?
|
|
|
|
Just use the noasm builds. If you're looking to update, you'll need a stronger CPU anyways (seeing you're going online with this machine), blockchain ain't getting smaller! But I digress. Generally, laptop CPUs have much less silicon to save on power, so only mid-high end laptop CPUs will have all the good stuff. Desktop CPUs are different, basically any i3 from 2010 will have all that you need.
Got it. Thanks You can 'sudo make install' after building from source.
That does not work, the installed version crashes (did that in my first post, for v0.96.3 branch and testing branch). Or maybe I did something wrong or got confused. |
|
|
|
It's more than just SSE4, there's also pclmul and AES. Also washed down iteration, such as SSE4.a won't cut it. Thanks for the explanation. Do you have a recommended list of proccessors? (so I can buy one that will work well next time) Perhaps "not installed" would be a more appropriate phrasing. Basically, running Armory by doing: Btw, noasm works great! This means you need to delete .lmdb mirror wallets in your Armory datadir.
I am not seeing this error any more. This tip will be helpful if it comes up again. Thank you so much for clearing this up. |
|
|
|
It works But I'd like to not have to run the uncompiled version all the time. Any help to resolve this will be appreciated. Thanks. |
|
|
|
After trying a few more times, Armory managed to unfreeze itself, going unresponsive for long stretches of time, but I managed to create a new wallet. Restoring the old wallet worked too, though it shows a zero balance. I then restarted armory using the compiled version, but it failed: $ armory
/home/caleb
(ERROR) ArmoryUtils.py:3716 - Unsupported language specified. Defaulting to English (en)
/usr/lib/armory/armoryengine/Transaction.py:2882: SyntaxWarning: import * only allowed at module level
def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
(WARNING) PyBtcWallet.py:2448 - ***WARNING: last file operation failed! Restoring wallet from backup
Illegal instruction (core dumped)
$ armory
/home/caleb
(ERROR) ArmoryUtils.py:3716 - Unsupported language specified. Defaulting to English (en)
/usr/lib/armory/armoryengine/Transaction.py:2882: SyntaxWarning: import * only allowed at module level
def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
-ERROR - ;�: (WalletManager.cpp:78) Failed to open wallet with error:
missing main wallet entry
Illegal instruction (core dumped)
Starting again using uncompiled version, finally scanning transactions history, with thousands of the following error: (python:6945): Gtk-CRITICAL **: IA__gtk_progress_configure: assertion 'value >= min && value <= max' failed
High hopes that it will finally work after it finishes scanning. |
|
|
|
Update: Running Armory uncompiled results in something slightly different: $ python ArmoryQt.py
/home/caleb
********************************************************************************
Loading Armory Engine:
Armory Version: 0.96.3.99
Armory Build: e47d6641aa
PyBtcWallet Version: 1.35
Detected Operating system: Linux
OS Variant : ('Ubuntu', '16.04', 'xenial')
User home-directory : /home/caleb
Satoshi BTC directory : /home/caleb/.bitcoin
Armory home dir : /home/caleb/.armory/
ArmoryDB directory : /home/caleb/.armory/databases
Armory settings file : /home/caleb/.armory/ArmorySettings.txt
Armory log file : /home/caleb/.armory/armorylog.txt
Do wallet checking : True
(ERROR) ArmoryUtils.py:3720 - Unsupported language specified. Defaulting to English (en)
/home/caleb/Documents/BitcoinArmory/armoryengine/Transaction.py:3075: SyntaxWarning: import * only allowed at module level
def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
(WARNING) SDM.py:439 - Spawning bitcoind with command: /usr/bin/bitcoind -datadir=/home/caleb/.bitcoin
(WARNING) SDM.py:396 - Spawning DB with command: /home/caleb/Documents/BitcoinArmory/ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/home/caleb/.bitcoin/blocks" --datadir="/home/caleb/.armory/" --dbdir="/home/caleb/.armory/databases"
BDM is ready!
At wallet creation, instead of crashing, it freezes. Progress. I hit CTRL-C ^C(ERROR) Traceback (most recent call last):
File "/home/caleb/Documents/BitcoinArmory/ui/Wizards.py", line 127, in initializePage
self.createNewWalletFromWizard()
File "/home/caleb/Documents/BitcoinArmory/ui/Wizards.py", line 180, in createNewWalletFromWizard
extraEntropy=entropy,
File "/home/caleb/Documents/BitcoinArmory/armoryengine/PyBtcWallet.py", line 992, in createNewWallet
Progress=Progress, doRegister=doRegisterWithBDM)
File "/home/caleb/Documents/BitcoinArmory/armoryengine/PyBtcWallet.py", line 1107, in fillAddressPool
doRegister=False)))
File "/home/caleb/Documents/BitcoinArmory/armoryengine/PyBtcWallet.py", line 1054, in computeNextAddress
[[WLT_UPDATE_ADD, WLT_DATATYPE_KEYDATA, new160, newAddr]])
File "/home/caleb/Documents/BitcoinArmory/armoryengine/Decorators.py", line 124, in inner
rt = func(self, *args, **kwargs)
File "/home/caleb/Documents/BitcoinArmory/armoryengine/PyBtcWallet.py", line 2336, in walletFileSafeUpdate
touchFile(mainUpdateFlag)
File "/home/caleb/Documents/BitcoinArmory/armoryengine/ArmoryUtils.py", line 3732, in touchFile
os.fsync(f.fileno())
KeyboardInterrupt
Traceback (most recent call last):
File "/home/caleb/Documents/BitcoinArmory/ui/Wizards.py", line 127, in initializePage
self.createNewWalletFromWizard()
File "/home/caleb/Documents/BitcoinArmory/ui/Wizards.py", line 180, in createNewWalletFromWizard
extraEntropy=entropy,
File "/home/caleb/Documents/BitcoinArmory/armoryengine/PyBtcWallet.py", line 992, in createNewWallet
Progress=Progress, doRegister=doRegisterWithBDM)
File "/home/caleb/Documents/BitcoinArmory/armoryengine/PyBtcWallet.py", line 1107, in fillAddressPool
doRegister=False)))
File "/home/caleb/Documents/BitcoinArmory/armoryengine/PyBtcWallet.py", line 1054, in computeNextAddress
[[WLT_UPDATE_ADD, WLT_DATATYPE_KEYDATA, new160, newAddr]])
File "/home/caleb/Documents/BitcoinArmory/armoryengine/Decorators.py", line 124, in inner
rt = func(self, *args, **kwargs)
File "/home/caleb/Documents/BitcoinArmory/armoryengine/PyBtcWallet.py", line 2336, in walletFileSafeUpdate
touchFile(mainUpdateFlag)
File "/home/caleb/Documents/BitcoinArmory/armoryengine/ArmoryUtils.py", line 3732, in touchFile
os.fsync(f.fileno())
KeyboardInterrupt
-ERROR - : (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unexpected fcgi header version
(ERROR) Traceback (most recent call last):
File "/home/caleb/Documents/BitcoinArmory/ui/QtExecuteSignal.py", line 31, in methodSlot
_callable(*args)
File "ArmoryQt.py", line 4910, in handleCppNotification
self.nodeStatus = TheBDM.bdv().getNodeStatus()
File "/home/caleb/Documents/BitcoinArmory/CppBlockUtils.py", line 3027, in getNodeStatus
return _CppBlockUtils.BlockDataViewer_getNodeStatus(self)
RuntimeError: can't connect socket
Traceback (most recent call last):
File "/home/caleb/Documents/BitcoinArmory/ui/QtExecuteSignal.py", line 31, in methodSlot
_callable(*args)
File "ArmoryQt.py", line 4910, in handleCppNotification
self.nodeStatus = TheBDM.bdv().getNodeStatus()
File "/home/caleb/Documents/BitcoinArmory/CppBlockUtils.py", line 3027, in getNodeStatus
return _CppBlockUtils.BlockDataViewer_getNodeStatus(self)
RuntimeError: can't connect socket
New Block: 495701
New Block: 495701
New Block: 495701
New Block: 495701
New Block: 495701
-ERROR - : (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unknown fcgi header request byte
-ERROR - : (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unknown fcgi header request byte
Btw, noticed a typo in that dialog: "No one can help you recover you bitcoins if you forget the passphrase and don't have a paper backup!" |
|
|
|
I tried Armory 0.96.3 Ubuntu/Debian 64-bit with GCC 5.4 but it would not start at all: /home/caleb
Illegal instruction (core dumped)
Armory 0.96.3 Ubuntu/Debian 64-bit with GCC 4.7 starts but crashes when restoring from paper backup. I then built from source, v0.96.3, same thing, crashes when restoring from unencrypted paper backup. I read some threads in this forum and it was mentioned that my CPU might not support SSE4, but it is a Celeron J3455 which supports SSE4. Then, I tried the testing branch, same results. /home/caleb
(ERROR) ArmoryUtils.py:3716 - Unsupported language specified. Defaulting to English (en)
/usr/lib/armory/armoryengine/Transaction.py:2882: SyntaxWarning: import * only allowed at module level
def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
(WARNING) SDM.py:439 - Spawning bitcoind with command: /usr/bin/bitcoind -datadir=/home/caleb/.bitcoin
(WARNING) SDM.py:396 - Spawning DB with command: ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/home/caleb/.bitcoin/blocks" --datadir="/home/caleb/.armory/" --dbdir="/home/caleb/.armory/databases"
Illegal instruction (core dumped)
The wallet I was trying to restore was created a while ago using Armory 0.93.3 (really old, before btcarmory). For good measure, I tried to create a new wallet on the testing branch installation. Crashes./home/caleb
(ERROR) ArmoryUtils.py:3716 - Unsupported language specified. Defaulting to English (en)
/usr/lib/armory/armoryengine/Transaction.py:2882: SyntaxWarning: import * only allowed at module level
def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
(WARNING) SDM.py:439 - Spawning bitcoind with command: /usr/bin/bitcoind -datadir=/home/caleb/.bitcoin
(WARNING) SDM.py:396 - Spawning DB with command: ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/home/caleb/.bitcoin/blocks" --datadir="/home/caleb/.armory/" --dbdir="/home/caleb/.armory/databases"
BDM is ready!
Illegal instruction (core dumped)
Ideas? |
|
|
|
libqt4-dev required as well sudo apt-get install libqt4-dev |
|
|
|
|
