I can't get armory online and I am having difficulty migrating to another platfo

[nc50lc]

And to nc50lc's point, I guess maybe not necessary if I were to restore from seed on a fresh system with a new full node. I will wait and see.

Yeah, that's for existing Bitcoin Core and Armory setup.

Since it's a fresh setup anyways, it might be better to setup a proven working combination of Bitcoin Core and Armory versions.
So, in that new system, install Bitcoin Core v27.2 and Armory v0.96.5 for compatibility. (Windows11 shouldn't have issue with those versions)
You can download old versions of Core from here: bitcoincore.org/en/releases

That way, you don't have to wait for updates, those should work with their default settings (considering the system disk's space is enough)
Of course, do not enable pruning as mentioned by goatpig.

[newnube]

Excellent. Thanks for the info, I should have asked what version to go with. I will also use an external SSD rather than HDD. Once I get a spare system to run it on.

And yip, I will keep pruning off 👍


In relation to my current node:

You should check Bitcoin Core's logs if this is really necessary.
Find the "debug.log" file inside your bitcoin datadir in your '/appdata/roaming' or '/appdata/local' folder. (if you're using the default paths)
There should be an error line indicating a corrupted file or non-matching hash if it needs to be reindexed.
That'll also tell if you need to reindex the full block database or just the chainstate or just a simpler command to proceed.
[/quote]



There is no 'corrupted file' or 'non-matching hash' when searching the debug.log. so, I hope my current node is fine at least.

Maybe I could try a copy and paste to SSD, and then run this node with the more proven versions?

Or maybe even with my current system doing a rebuild rescan of databases in armory, if that does more than deleting the content in the databases folder?

[nc50lc]

There is no 'corrupted file' or 'non-matching hash' when searching the debug.log. so, I hope my current node is fine at least.

Great, then may just be a setup issue with the current RC
And you can still use your Bitcoin data directory once Armory v0.97 is stable.

If you're worried on Core's reliability, you can start Bitcoin Core without Armory and see if it'll return with an error since it auto-detects such issues.
Or to absolutely make sure, use verifychain command with "checklevel" 1 to 3 on the entire blockchain. (in Bitcoin Core)
e.g.:

Code:

verifychain 3 0

If it returns with "true", it's safe to assume that the blockchain isn't corrupted.

[newnube]

I often ran bitcoin core without armory, to keep the chain up-to-date, it synced fine. And with the trouble I was having with armory 96.5, I generally ran core until it was uptodate and synced, then I would run armory along side.


I will try the command in bitcoin core later today or tomorrow. Thanks

[newnube]

Ok it looks like I need to reindex 😣

'Verifychain 3 0' is coming back false.

The debug says:

2026-06-25T03:54:12Z Verifying last 955271 blocks at level 3
2026-06-25T03:54:12Z [0%]...ERROR: ReadBlockFromDisk: Errors in block header at FlatFilePos(nFile=4580, nPos=81813786)
2026-06-25T05:52:00Z ERROR: VerifyDB(): *** ReadBlockFromDisk failed at 860036, hash=000000000000000000002d7250815b8d194c6f4574bde61a0564607f61c621eb
2026-06-25T05:52:00Z Potential stale tip detected, will try using extra outbound peer (last tip update: 7688 seconds ago)
2026-06-25T05:52:02Z New outbound peer connected: version: 70016, blocks=955288, peer=101 (outbound-full-relay)