 Show Posts
|
|
Pages: [1] 2 »
|
Finally, if I am satisfied, I will empty my Electrum Wallet and keep the Wasabi Wallet.
You might want to keep your Electrum wallet and it's backup in rare case someone send Bitcoin to your old address. True |
|
|
|
|
Thanks @BlackHatCoiner and @o_e_l_e_o for the insights.
I've already installed the Wasabi Wallet, generated a wallet and written down the 12 seed words and the password. I have also generated a receive address. Next step is to restore the wallet on a second computer, to verify that Wasabi is actually capable of restoring a wallet using the seed words and the password. If everything goes well I will send some BTC to it. Finally, if I am satisfied, I will empty my Electrum Wallet and keep the Wasabi Wallet.
|
|
|
|
Thanks @ETFbitcoin and @o_e_l_e_o for your answers. I checked the wasabi wallet and it says something like The process will also generate a set of recovery words, which you’ll need in case you forget your password. That's the feature I am looking for. Having a "paper backup" gives me some peace of mind. I will look further into it and hopefully I will drop electrum and switch to wasabi wallet. |
|
|
|
Unfortunately, already pretty much the only incentive for people to run electrum servers is to spy on the clients, and this eliminates that "benefit".  I am a bit worried about this. I am an occasional user of electrum. I like the fact that you can restore the walled with the seed and that is "instant on" in the sense that there is no need to download the blockchain. Is there any way to mitigate the risks of using electrum. Using a VPN maybe? What is this spying about? Recoding the IP associated with the addresses and transactions? Thanks in advance. |
|
|
|
|
As a summary, I want to list a few things I had to take into account when running armory:
- When downloading bitcoin core, use the tgz and not the snap. With the tgz, the blockchain files will be stored in the .bitcoin/blocks directory where armory looks for them.
- Disable bitcoin core pruning.
- Wait for bitcoin core to fully synchronize before launching armory.
- Use a decent computer. Both bitcoin core and armory are demanding. I used a six year old computer with an intel core i3, 6 gigs of ram and some 450 GB of HD and at some point it was too slow or even freezed.
- Use ubuntu 18.04 instead of the latest release.
- Run bitcoin core with the flag -server. bitcoin-qt -server
- Change the configuration of armory to disable the option "let armory manage bitcoin core".
|
|
|
|
Try to rescan the db.
Thanks goatpig I did a "rebuild" and now when I click on the "send bitcoin" button, the window to send bitcoins appears as it should be. Problem solved. |
|
|
|
I also get a fcgi error. Mine is a bit different. -ERROR - 15:36:48: (StringSockets.cpp:351) FcgiSocket::writeAndRead FcgiError: unknown fcgi header request byte
Now I'll try with "rebuild". $ armory
Gtk-Message: 15:41:01.203: Failed to load module "canberra-gtk-module"
/home/jbarcelo
(ERROR) ArmoryUtils.py:3735 - Unsupported language specified. Defaulting to English (en)
/usr/lib/armory/armoryengine/Transaction.py:3126: SyntaxWarning: import * only allowed at module level
def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
No systemtrayicon available
(WARNING) SDM.py:402 - Spawning DB with command: ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/home/jbarcelo/.bitcoin/blocks" --satoshi-port=8333 --datadir="/home/jbarcelo/.armory/" --dbdir="/home/jbarcelo/.armory/databases" --rebuild
(ERROR) ArmoryQt.py:1198 - 5 attempts to load blockchain failed. Remove mempool.bin.
(ERROR) ArmoryQt.py:1203 - File mempool.bin does not exist. Nothing deleted.
|
|
|
|
They way I used to run armory was 1) bitcoin-qt -server 2) armory Then I realized that there is an option in the configuration for armory to run bitcoin core. And that option was checked. That's why amory complained BitcoindError: bitcoind not found I told armory where my bitcoin binary is and let armory run bitcoin. Now everything runs smoother. Before I was running bitcoin core myself and also telling armory to run bitcoin core and the computer was very sluggish for some reason. Now it's much faster. But I think I broke something in the process as I cannot send bitcoin now. Traceback (most recent call last):
File "/usr/bin/../lib/armory/ArmoryQt.py", line 3451, in clickSendBitcoins
DlgSendBitcoins(self.getSelectedWallet(), self, self).exec_()
File "/usr/lib/armory/qtdialogs.py", line 4594, in __init__
spendFromLockboxID=spendFromLockboxID)
File "/usr/lib/armory/ui/TxFrames.py", line 151, in __init__
RBFcallback=RBFcallback)
File "/usr/lib/armory/ui/WalletFrames.py", line 232, in __init__
self.updateOnWalletChange()
File "/usr/lib/armory/ui/WalletFrames.py", line 347, in updateOnWalletChange
self.selectWltCallback(wlt)
File "/usr/lib/armory/ui/TxFrames.py", line 347, in setWallet
self.setupCoinSelectionInstance()
File "/usr/lib/armory/ui/TxFrames.py", line 396, in setupCoinSelectionInstance
self.coinSelection = self.wlt.cppWallet.getCoinSelectionInstance()
File "/usr/lib/armory/CppBlockUtils.py", line 2164, in getCoinSelectionInstance
def getCoinSelectionInstance(self): return _CppBlockUtils.WalletContainer_getCoinSelectionInstance(self)
<class 'CppBlockUtils.DbErrorMsg'>: <CppBlockUtils.DbErrorMsg; proxy of <Swig Object of type 'DbErrorMsg *' at 0x7f345c8a4450> >
So I am thinking about looking into the factory reset options... |
|
|
|
Wow, thanks for the whole explanation. I realize how armory has to constantly evolve to adapt to the changes of core. Now I use bitcoin-qt -server
|
|
|
|
Broadcast timeout doesn't mean the tx didn't make to the mempool, it only means Armory sent the tx to your node but failed to acknowledge delivery in the allotted time (hence the timeout). When that happens, it tries to fallback to the RPC interface to broadcast through that, but since yours isn't set up, you got that message.
Ok. Perfect. Now I know what happened. Mine is a very old computer. That may explain the timeout. Thanks for the explanation |
|
|
|
Did you try on the testnet? You have to run Core with -server to enable the RPC at any rate.
I was trying on the main network. And I didn't add the -server flag when I launched bitcoin-qt. Next time I will. Thanks again, goatpig. |
|
|
|
Now I get The transaction you just attempted to broadcast has timed out.
The RPC interface of your node is disabled, therefor Armory cannot use it to gather more information about the timeout. It is recommended that you enable the RPC and try again.
|
|
|
|
|
Ok. I managed to create some transactions and they have been accepted and confirmed by the network.
|
|
|
|
|
The gcc 4.9 version does work. Now armory is scanning the global transaction history.
|
|
|
|
Well, my first attempt with armory gcc7.2 failed. I will try with the gcc 4.9 version... $ armory
Gtk-Message: 18:20:00.871: Failed to load module "canberra-gtk-module"
/home/xxxx
(ERROR) ArmoryUtils.py:3735 - Unsupported language specified. Defaulting to English (en)
/usr/lib/armory/armoryengine/Transaction.py:3126: SyntaxWarning: import * only allowed at module level
def PyCreateAndSignTx_old(srcTxOuts, dstAddrsVals):
No systemtrayicon available
(ERROR) ArmoryQt.py:1862 - Failed to setup SDM
Traceback (most recent call last):
File "/usr/bin/../lib/armory/ArmoryQt.py", line 1857, in startBitcoindIfNecessary
TheSDM.setupSDM(extraExeSearch=self.satoshiExeSearchPath)
File "/usr/lib/armory/SDM.py", line 190, in setupSDM
if self.failedFindExe: raise self.BitcoindError, 'bitcoind not found'
BitcoindError: bitcoind not found
(WARNING) SDM.py:402 - Spawning DB with command: ArmoryDB --db-type="DB_FULL" --cookie --satoshi-datadir="/home/xxxx/.bitcoin/blocks" --satoshi-port=8333 --datadir="/home/xxxx/.armory/" --dbdir="/home/xxxx/.armory/databases"
Illegal instruction (core dumped)
|
|
|
|
Thanks HCP for your input. So far, I learned four things
- A system with some 400 Gbytes of HD is needed to store the blockchain.
Don't forget you'll need room for the OS and applications etc... go 1TB+ if you can I am using an old computer with some 450 GBytes of HD. Fingers crossed that's enough. I agree that a larger HD is needed. So far I downloaded 95% of the blockchain and used 75% of the HD. I haven't installed armory yet. |
|
|
|
Thanks goatpig I plan to install armory on a dedicated computer. A laptop that is some 7 years old. I will install ubuntu 18.04 lts |
|
|
|
|
Hi everyone!
I want to run armory and I will post here my steps.
So far, I learned four things
- A system with some 400 Gbytes of HD is needed to store the blockchain.
- When downloading bitcoin core, use the tgz and not the snap. With the tgz, the blockchain files will be stored in the .bitcoin/blocks directory where armory looks for them.
- Disable bitcoin core pruning.
- Wait for bitcoin core to fully synchronize before launching armory.
|
|
|
|
Definitely try the noasm builds.
Thank you goatpig for your dedication. Armory is already running and downloading the blockchain |
|
|
|
|
Answering to myself here ...
I will try the noasm .deb
|
|
|
|
|
