switched to hiveos, was able to lower it to 650mv. core 1100 mem 1880. stock bios and getting 41mhs. Much better in linux than windows. And because of lower voltage, the gddr6 memory runs a lot cooler, ~85c, which allows me to push the mem clock higher. In windows, I can only do 1780 stable @  measly 38-39mhs.

I see you undervolt core to 680mv. The lowest I can uv in windows 10 with my MSI 5600xt MECH is 800mv. Did you flash your bios with lower voltage limit? Or is it stock?

Electrum isn't safe in regards to how easy your bitcoin will be stolen if someone can put their hands on your seed.
Armory  wins in this regard if you have n-m fragments wallet backup. You split the seed into multiple different paper backups and store them at different geographical locations. It's pretty much impossible to steal your bitcoin since you will need to steal all of the required fragmented paper backups to restore the wallet.

Armory is best in physical security. If setup right, Armory provide the kind of physical security that even hardware wallet like ledger and trezor can't compete with since all of them uses single seed for backup, single point of failure.

Both are equally good in cyber security if you utilize the cold wallets as it prevent hackers' cyber attacks.

Electrum is faster since it's not a full node wallet.

agree. stay with apple or bread wallet. It's easier and more secure if you dont know what you doing in PC world.

another question related to this, since we are already discussing about segwit address.
If one private key can generate a P2PKH address and a segwit address, when you spend from the P2PKH address, will the spending also reflect on the segwit address? I mean you are spending from the same private key, which hold just one amount of bitcoin right?

i want to have the ability to import private keys into whatever wallet from my segwit address. currently i can only do so with the p2pkh addresses.

i guess i can import private keys one by one into another whatever wallet to get all my coin eventually. But having the ability to know exactly which private keys corresponding to my segwit address will make the job easier.

ahhh i see. Just so it will be less confusing for the general public, can you append the segwit address next to the public key in the export list for the future version?

Can team Armory implement this feature in the future versions of Armory? The latest version can only export list of private keys for P2PKH.

I am pretty certain I'm not mismatching Fragment vs Wallet ID.  The Fragment field do not match my Fragment ID in my paper backup nor the Wallet ID in my paper backup. I generated the fragmented backup and test it both with 0.96.3

here's the screenshot of where I found the bug. In the Verify Fragment ID windows. the fragment ID displayed will never match my Fragment ID on my paper backup. However, if I click "yes", it will resolved to the correct wallet ID. I don't know how else can i explain it better. You have to go thru the restoration of the fragmented wallet backup to see what I discovered.

if you restore from a fragmented paper wallet backup, you will enter the keys into the program, it will then ask you to verify the fragment ID is the same as the one on your paper. You won't miss it. And the fragment ID will always be different from the paper backup because now the fragment IDs are always random.

Understand. but when testing the backup or restoring a wallet from paper backup, the program prompts user to verify the fragment ID which do not match what was printed on the paper. It's a GUI issue i suppose. The wallet works perfectly after restoration. It's not a problem for veteran users but i think it will confuse new users.

The fragment ID does not match my paper backup during backup testing, however, it does resolved into the right wallet ID.
Would be nice to have the same fragment ID as my paper backup during backup testing as it currently confuses people.

I guess this is due to the new randomized SSS implementation?
Keep up the good work Armory team.