You need to get Armory to scan the blockchain to get out of offline mode. If you want help doing that, you need to post your logs first.

Not visible? Have you broadcasted the transaction?

Armory is fine for importing Cascacius coins. There is no write up that I can remember of, you'd have to search this subforum to unearth one from 2011.

The basics are straight forward however. Armory deterministic wallet backups do not cover imports, therefor if you import keys and want the funds to be covered by your backup, your best path is to move the BTC into your wallet after the import.

To import, you need the WIF base58 key (starts with 5) or the raw hex key. The process is as follows:

1) Start ArmoryQt in offline mode.

2) Go inside the Wallet Properties dialog of the wallet you want to import the key in.

3) Pick Import/Sweep Private Key on the right side menu. Pick import.

4) Once you're done adding in the keys, restart Armory in the regular mode. The wallet will be rescanned and the coins will be available to spend.

5) Make a transaction moving this coin into an address owned by your wallet.

Alternatively, you can cut on some of these steps by starting Armory the regular way and picking sweep instead of import when you input the private key. This will generate the transaction to move the coins for you.

If you are going to do it like this, start BitcoinQt manually first, then ArmoryDB, then finally ArmoryQt.

This is a leftover variable that has no effect since randomization of the db port. To see what port the DB is actually listening to, Go to the network tab of the resource monitor. In the process section, select ArmoryDB.exe, it will filter all activity in the other sections for that process. Then see for yourself in the listening port section.

For 0.96.5, the argument is "fcgi-port". Please stick to that version.

Are you running ArmoryDB manually? If so either add the arg to your command line:


You can set this either in the target for a shortcut of ArmoryDB.exe, or when you spawn the DB from the command line. 14000 is just a stand in value to show what the full argument looks like, use whatever value you want. Keep in mind you need admin privileges to use ports below 1024.

You can also use the config file. Add this line to armorydb.conf:


This config file can be found in your datadir (where you wallets are). If you do not see the file there, create a plain text file and name it accordingly.

If you let ArmoryQt spawn the db for you, it will randomize the port to a value within [49150, 64150]

Legacy Bitcoin addresses come with a 4 bytes checksum. It's virtually impossible to mess it up. Bech32 addresses have even stronger checksums. The only realistic way you could spend to an invalid address is if you are using wallet software that does not verify the checksum.

It's somewhere in the NSIS settings, I never remember to update that =(

Just run that line and try again.

Did you install the dependencies?

Start ArmoryDB.exe from the command line, what do you get? If it starts up fine, then run ArmoryQt.

try satoshi-datadir="o:\btc-core\blocks"

Why is your user name admin to begin with? The point of the user folder is for the account to have read/write path for processes to maintain the files they need.

From the looks of it, your blockchain data is either not accessible or you don't have any.

I can't really give you instructions until I know what user you are logging in as.

You can run as admin but that's not recommended. Armory needs write access to the files and folders in your datadir besides the .conf files.

Your user name is "Admin"? Chances are this is a permission issue, i.e. Armory cannot access this folder.

Gonna need to see your logs then.

With armoryd, all calls assume the context that a current wallet is selected. To get data from other wallets, you need to select the relevant one. The first wallet armoryd loads is set as the default one.

There's a somewhat large armoryd example you can find here:

https://github.com/goatpig/BitcoinArmory/blob/master/webshop/server.py

Unfortunately I don't know how much of it still works, as it was written in 2014.


It would be armoryd.conf

Need to see your logs.

./ArmoryDB



No.

Yeah that's not gonna work because the client randomizes the DB port when it automates it. Just run ArmoryDB on its own then armoryd.