I'm trying to create a cold storage for some BTC. I don't have any prior experiece with Armory.
The guides talk about having a computer that you never connect to the internet, the one you use to create a wallet file.
How about booting to a linux distribution from an USB drive and doing it there? Is there some key layer of security I lose?
What if I literally remove all the prior HDDs on the machine, then boot from the USB? In essence this would be a new computer that hasn't ever been connected to the internet, or what am I missing?
Don't, that's a terrible idea. |
|
|
|
|
You can use 32bit hardware as long as you're running some Debian like distro. If you are thinking x86 WinXP, then no can do.
|
|
|
|
Using 0.96.2 expert mode in Debian VM. Any news on fixing this?
Ummm, try 0.96.4 RC1? You're posting in this thread, after all.... Coin Control still freezes GUI with 0.96.3.99 It's not frozen, the dialog is modal and reduced. You have to find the reduced title bar and expand the dialog anew. |
|
|
|
|
That's debug output, ignore it.
|
|
|
|
|
How did you manage to do create it with that password to begin with?
|
|
|
|
Armory: 0.96-beta-a3d01aa722
For starters, update. Check the stickies on this forum. |
|
|
|
|
Ask someone from Core, not familiar with that. I think the basic idea is deleting the mempool file in your datadir.
|
|
|
|
|
Should be easy enough to reproduce anyways, just wanted to make sure it was with current code.
|
|
|
|
Since then my 4-5 subsequent trans have all failed with: txn-mempool-conflict
This means a tx already trying to spend your outputs is in the mempool. You'd have to clear your node's mempool. |
|
|
|
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?
|
|
|
|
|
Show Posts
