I'm trying to spend some mixed inputs but armory wont let me. Traceback (most recent call last):
File "/usr/local/lib/armory/ui/TxFrames.py", line 927, in createTxAndBroadcast
self.createUnsignedTxCallback(ustx)
File "/usr/local/lib/armory/qtdialogs.py", line 4607, in createUnsignedTxAndDisplay
dlg = DlgOfflineTxCreated(self.frame.wlt, ustx, self.parent, self.main)
File "/usr/local/lib/armory/qtdialogs.py", line 4651, in __init__
reviewOfflineTxFrame.setUSTX(ustx)
File "/usr/local/lib/armory/ui/TxFrames.py", line 1686, in setUSTX
self.txtUSTX.setText(ustx.serializeAscii())
File "/usr/local/lib/armory/armoryengine/AsciiSerialize.py", line 67, in serializeAscii
return makeAsciiBlock(self.serialize(), headStr)
File "/usr/local/lib/armory/armoryengine/Transaction.py", line 2510, in serialize
bp.put(VAR_STR, ustxi.serialize())
File "/usr/local/lib/armory/armoryengine/Transaction.py", line 1698, in serialize
bp.put(VAR_STR, self.p2shMap[BASE_SCRIPT])
KeyError: 'base_script'
Is this with the latest state of testing? Selecting only 1 type of inputs works.
Isn't it possible to mix segwit with non segwit inputs?
It should work. |
|
|
|
|
Delete the content of this folder and try again:
C:\Users\Jason\AppData\Roaming\Armory\databases
|
|
|
|
Where do I find Armory 0.96.4?
Read the forum stickies... I updated to that version and tried to send and now I am getting a different error message when I try to send.
Start your node. |
|
|
|
|
1) Delete C:\Users\seanb\AppData\Roaming\Armory\armorylog.txt
2) Update Armory to 0.96.4 RC1.
3) Run Armory, try to spend and report here if it fails again, posting the fresh armorylog.txt on the way.
|
|
|
|
|
1) Start BitcoinQt manually and let it sync.
2) Make sure no instance of ArmoryDB.exe is running
3) Delete the content of this folder:
C:\\Users\\martin\\AppData\\Roaming\\Armory\\databases
4) With BitcoinQt still running, start Armory.
|
|
|
|
I hope someone could help me connecting my Armory, getting it to an online mode
Install Core, let it download the blockchain then start Armory. If you're still having issues, post back here. goat is listening?!
He is but he won't help you cause he doesn't like people hijacking threads. |
|
|
|
|
You're probably receiving an empty reply from the server.
|
|
|
|
|
Do you have a node running?
|
|
|
|
By session I mean a temporary key for that particular signing day.
Just use a multisig script. |
|
|
|
|
1&2 will be easy with once BIP32 is supported. Doesn't work so well with the Armory chain derivation.
I don't get the point of 3. what's to stop whoever created a session from reusing it? The idea of a "session" is that there is a clear way to close/revoke the session.
|
|
|
|
Unfortunately i have no clue how to do this with armory which of course i paid for as it was the best at the time.
How in the hell did you pay for Armory? It's free open source software. 1) under the above conditions did i receive coins /should i be able to find my coins
Any coins you had in your Armory wallet on August 1st you'll have the BCH equivalent for. Moving BTC post fork does not change that. Having read page 1 if i am right , I need to somehow install Armory on a seperate machine, download a BCH chain or cut a copy of the existing chain to some unknown block between 950-960, use a BCH signer etc...all of which is a total mystery to me.
You are getting confused. Basically you want to setup a BCH node as if you were setting up Core. The point is, since you already have Core, and thanks to BCH being idiots, if you setup BCH on your regular system, it will conflict with the existing Core files and mess everything up. Therefor you want to setup BCH in a way that it doesn't shit all over your existing Core setup. The regular way to do this is configure the BCH node to use a different path, and later reflect that on Armory. If you're really a huge noob or can't be fucked to manually set paths, you could create a new user on your online computer for BCH only (user accounts come with their own set of data folders, and both node and Armory default to the active user data folders). Once you've done this (create new user and get a BCH node running), let sync the chain in full. With that done, grab you Armory wallets from the Core user (digital export is your best option), start Armory on the BCH side and import the wallets in then let it do its thing. Once this is over, the Armory on the BCH user account will show you your BCH balance and create transactions for the BCH network. You will still have to pick the BCH signer manually to sign something valid. Mr G...
To you it's mister Pig. Don't you get familiar on me yet, boy! |
|
|
|
|
What version of Armory are you running?
|
|
|
|
Assuming you're on a Debian based distro: sudo apt-get install python-psutil
|
|
|
|
|
Do you remember what version it was?
|
|
|
|
|
You have to run ArmoryDB manually.
|
|
|
|
Woot! Thanks, removing them, and with C++ signer, it worked.
I'm going to assume the situation has not change with the Python signer, right? Definitely something weird with the wallet state. Still have those 4 confirmed txs which Armory thinks aren't confirmed (and offers to bump fee). I'll append tomorrow this one gets similarly stuck.
There are 3 possible states: 1) The ZC DB is corrupt and still shows the tx as unconfirmed, while they also appear as confirmed in the ledger. In this case, you can clear unconfirmed tx from the Help menu and restart Armory. 2) The ZC never actually mined. In this case, they may or may not be in the in a miner's mempool. You can just RBF these. You'll probably have to build the current state of testing as it has the RBF fixes in there. If you want signed builds, you'll have to wait till I'm done with this accursed BTG signer. 3) Your DB is stuck and can't see new blocks, therefor will never see these tx mined. You can check for this state by comparing Armory's top block (bottom right corner) to your network's top block. In this case, I'd need to see dbLog.txt before I can give you recommendations on how to proceed. |
|
|
|
|
Show Posts
