|
You have to setup the RPC. Also, post armorylog.txt.
|
|
|
|
|
Please detail the layout of the paper you have the "root id" on. Armory puts out unencrypted backups for the most part. It is a convoluted process to get it to spit an encrypted paper backup. If that "root id" of recreated your wallet from scratch, you should be able to just spend the coins.
You should also elaborate on how "it is not working".
|
|
|
|
|
Remove the path setting in the GUI and try again.
|
|
|
|
|
Create a text file, rename it armoryqt.conf, put the one line in there. Make sure you display known file extensions or you won't be able to change the .txt to .conf.
|
|
|
|
Create a file named armoryqt.conf in your Armory datadir (where your wallets are), put this line in there: satoshi-datadir=D:\BitcoinCore\blocks
|
|
|
|
Is there any guide or info related to how to use ArmoryDB with a remote latest version bitcoind?
Not possible atm, ArmoryDB needs local access to the blockchain files. ArmoryQt does not however, i.e. the db has to live on the same OS as the node, but the clients can access it remotely. There's a plan to allow the db to connect to the node only over a p2p socket. Not a priority atm though. It *might* be possible to export bitcoind's data folder as an nfs mount on one machine, and mount it on a second one... I haven't tried this, so i don't know if it would work.
Won't work, can't mmap files on network drives. |
|
|
|
|
If you start BitcoinQt manually, does it crash? Also, how are you passing your custom blockchain path to Armory?
|
|
|
|
Ah, ok. Well, in that folder there's a 'ArmoryDB' file but not a 'ArmoryDB.exe' file? Are those 2 the same?
Yes, your system is probably set not to display known file extensions. Ok, I tried restarting the entire system and this time it has actually started building databases, the bar is at 9% and says 2 hours expected build time.
Node is still offline.
I'll get back to you with a status report tomorrow morning, it past 1 am here now.
We can deal with that next. |
|
|
|
C:\Users\hykki_000\AppData\Roaming\Armory\
That's your Armory datadir. The installation folder is where your binaries are, typically in '/program files (x86)/armory' on Windows. |
|
|
|
Great, thank you all.
Assuming i didn't touch my BCH since it was created.
If I just want to send a BCH offline transaction (let's say to my new wallet), Can I broadcast it with an offline node?
You can: 1) Create the transaction with pre fork Bitcoin data (assuming you have air dropped BCH and never touched it). 2) Sign it however you want (offline included) 3) Use a BCH push service to broadcast from there (typically provided by block explorer websites). |
|
|
|
|
What folder are we talking about?
|
|
|
|
1) In your Armory datadir folder (C:\Users\hykki_000\AppData\Roaming\Armory\), create a file named armorydb.conf. Add this line in there: satoshi-datadir=F:\Bitcoin
2) Start Bitcoin-Qt manually with the proper -datadir path (F:\Bitcoin) 3) Open the command line, browse to your Armory installation folder and run ArmoryDB.exe 4) At this point ArmoryDB will start building the database. You can now run ArmoryQt.exe and wait till it finishes scanning your wallets. |
|
|
|
So if I understand correctly, starting may 15th, you can't use armory on the BCH chain anymore?
Entirely depends on the span of the new HF. If it's just a block size increase and new opcodes, Armory should still "work" provided the network magic word part is fixed. Honestly, it would probably take me a single day to deal with this stuff assuming all they did was to increase the block size. I don't do it because I refuse to give up development time for BCH. |
|
|
|
|
Thanks for the bug report, will look into it.
|
|
|
|
Edit, that change alone isn't enough, armory won't connect to bitcoinABC.
Check your node log, should tell you why Armory is getting rejected. |
|
|
|
|
Been away for a couple weeks. You should nuke your DB and start from scratch, I'll try on a Debian9 VM in the meantime. Lastly, can you try with the testnet instead?
|
|
|
|
The only thing you're doing here is uncommenting an actual comment. This won't build no matter what you try. What I am guessing you're trying to do is to comment out the entire if branch. I would advise users not to do that, as their ABC node would be trying to process messages from actual Bitcoin nodes, which overwhelm BCH. Basically the equivalent of DDoSing yourself. Instead, you can try to change the P2P magic word in Armory (there's no guarantee that change alone will be enough): https://github.com/goatpig/BitcoinArmory/blob/master/cppForSwig/BlockUtils.cpp#L886 networkNode_ = make_shared<BitcoinP2P>("127.0.0.1", config_.btcPort_,
*(uint32_t*)config_.magicBytes_.getPtr());
Should be changed to: networkNode_ = make_shared<BitcoinP2P>("127.0.0.1", config_.btcPort_,
0xe3e1f3e8);
|
|
|
|
RBF gets much further than it used to, but I still can't RBF a transaction from a Watch-only wallet.
I get to the Sending from Wallet: / Enter Recipients: screen, and I can enter my details and click Continue, click Yes on the Insufficient Fee warning, and nothing happens - I'm back at the Wallet/Recipients screen, when I think I should be looking at the Review Offline Transaction screen to save it to my USB flash drive...
If I enter a huge fee to skip the Insufficient Fee warning, the Continue button just doesn't do anything - I can click it all day long.
Need to see your armorylog.txt |
|
|
|
|
Show Posts
