No, the addresses will be generated from the Master Public Key... which as I understand you have to put in the EPS config.

As it isn't able to find any transactions relating to those generated addresses, it would appear that your Bitcoin Core node has not indexed them for whatever reason. Perhaps try asking the EPS dev for assistance here: https://bitcointalk.org/index.php?topic=2664747.msg27179198

Tails actually has a version of Electrum pre-installed... However, I am not sure if it is has been updated to Electrum 3.3+ as yet tho (so you may get Sync issues). Having said that, there are ways to manually update it yourself: https://blog.thestever.net/2019/02/26/upgrading-electrum-on-tails-to-3-3-4/

I don't see anywhere where he mentions they are going to send or "return" BTC to you... they're simply explaining about Bitcoin "change" outputs generated during a Bitcoin transaction.

In my opinion, the two things (email from BitPay support and the unknown transaction) are merely coincidental and not related. If you did not initiate the transaction, then someone else has access to your wallet.

This would likely be because someone has access to your 12 word seed mnemonic... Did you ever store your 12 words in a digital format? (screenshot, typed in a text document, sent via instant message or email etc)? Did you ever type it into a website to claim forked coins? Did you ever give those 12 words to another person?

I'm currently using Windows 10 PRO x64 + Bitcoin Core 0.18.0 + Armory 0.96.5 and it all works fine.

Can you please clarify exactly what you mean by "can't get it running". Does Armory start? Does it attempt to build the database? Is is just showing as "offline"? Is it not correctly updating the number of blocks?

Also, if you haven't already tried... a very simple thing to try is simply rebooting the PC, it's possible there are "ghost" ArmoryDB processes running in the background preventing Armory from running properly.


But, in all honesty, your best bet is to do as Carlton Banks already suggested and post your logs. Both the armorylog.txt and dbLog.txt.

I concur with jackg... I just checked on wallet.trezor.io using a Trezor ONE and can still see the "fiat" dropdown box where I can select from multiple currencies including USD.

What browser are you using?

Do you have a message from Bitpay saying they are "returning" the 0.0296 BTC to you?

What the agent is saying is technically correct... the 0.0296 BTC was spent from the "1FDwL..." address to the "bc1ql..." address in txid: 9c0f064ed686539c48dfd20d7f80b9d9d1f8519e0ce14d9b5e3a9ee4e5ac06f3

The big question now, is who created that transaction?

So... do you have a record of a Bitpay "agent" telling you that they sent this transaction?

That looks like the culprit right there... While it might have the correct addresses (based on what you said previously that the first 3 displayed addresses are correct), it would appear that EPS isn't actually finding any history.

Do these addresses/transactions actually show up within Bitcoin Core?

Does the EPS have any logs that show that your Electrum wallet is actually connecting to it and requesting the correct info? Seems odd that EPS "has" your info... but isn't returning it to Electrum??!?

For Electrum logs: Tools -> Preferences -> General... There is a "write logs to file" option


You'll need to restart... and a "logs" directory will be created in the Electrum data directory


Also, I believe Electrum has a debug mode if you run it from the commandline using the -v argument... I believe this will only work for Linux and possibly Mac OSX. Fairly certain it doesn't work on Windows.

I don't quite understand why you believe that donations made to an address published in Thread A should automatically default to the person running Thread C... simply because Thread C is similar to Thread A?  Whilst they cover the same territory and a somewhat similar purpose... Thread A =/= Thread C. By your logic... anyone could simply create "Known Alts Mk IV" and a new donation address and demand that you forward all donations to their new donation address.

I also don't see any written contract that has been violated.


Lutpin has offered to give you payment of some of those existing funds from Thread A to cover your contributions that were made to Thread A, as per the original intent of the contributions:


He also offered to refund any donations if any of the original contributors were not satisfied with his handling of said donations:

Unless those current contributors were the original contributors... their opinion does not matter in this case. It's not their money.

I don't see how you equate them making (relevant?) comments on a thread as encouraging plagiarism? Did you mean shit-posting? or spamming?

If anything... it's simply a "Thread Bumping" service

To expand on bob123's advise... you can see a detailed guide (with pics) of how to get your private keys out of Armory by reading my old post here: https://bitcointalk.org/index.php?topic=4746784.msg43255691#msg43255691

Note, you'll get a big list of keys in Armory when exporting, but you don't need to import ALL the private keys into Electrum, just the one that matches up with the address you sent coins to.

Address in question would appear to be: 1FDwLcvBNeFRXFhCGELzWJFfgfLEfkoaGC

You can see 3 transactions... Final Balance: 0.0296 BTC. So, the BTC is still there, the wallet is just not correctly displaying the right balance.


Sadly, I don't think that is the case.

Welcome to the ChipMixer SigCampaign Thread... where [FULL] means "post application whenever DarkStar_ posts (bonus points for not using SegWit address)"

Perhaps a silly question... but did you follow the instructions on the EPS Github for rescanning AFTER first run and new addresses added as watch-only to the Bitcoin Core node?

The short version is:
S = older, limited onboard storage for holding coin "apps"
X = newer, more onboard storage + wireless connectivity for use with iOS/Android companion wallets


huh??!? The entire point of hardware wallets is that you can use them on a "normal" internet connected computer or mobile device and you don't need to worry about your private keys being compromised as they're secured within the hardware wallet.

I believe it is a limitation of either the Trezor bridge or the Trezor device itself that it can only seem to handle having two concurrent "connections".

I've attempted to generate multiple wallets... using various combinations of the "bridge" and "web-usb" connections displayed in Electrum, but the max that you can have connected is 2. A possible workaround is to not encrypt the Electrum wallets when you create them. If they're not encrypted, you don't even need the device connected to be able to open them.

When you want to send, you'd need to close the wallet you want to send with... connect the Trezor then re-open the wallet. It should do the initialisation and ask for PIN etc.

Because Electrum is doing it "correctly" and using xpub for Legacy, ypub for P2SH-P2WPKH and zpub for P2WPKH:
It's been a known "issue" for quite a while that Ledger Live displays the "wrong" MPK by showing an xpub for the P2SH-P2WPKH wallets.


Having said that, you can use this converter to confirm you have the "correct" values: https://jlopp.github.io/xpub-converter/

Either put in the ypub from Electrum... select "xpub (mainnet P2WPKH or P2SH)" option. You'll see the xpub from Ledger Live
or
Put in the xpub from Ledger Live... select "ypub (mainnet P2WPKH in P2SH)" option. You'll see the ypub from Electrum


I haven't tried using EPS, but I'm successfully using Bitcoin Core + electrs (Electrum Server in Rust) + Electrum in "oneserver" mode.

What "extra software" did you download?

You should ONLY need to download and install Bitcoin Core... and Armory. What version of Armory did you download? and where did you download it from? You should have Armory version 0.96.5 and you should have downloaded it from btcarmory.com.

Last time I came across that error was here: https://bitcointalk.org/index.php?topic=5121435.msg50206337#msg50206337

It would appear that there is a transaction that has a scriptcode that Mycelium is not expecting, nor able to handle... hence the error.

As per the suggestion there, I would suggest contacting the Mycelium dev's via their Github Issues Register.

That's because fees are NOT related to the value of the transaction, but are directly linked to the data size of your transaction (ie. how much space they take up in a mined block)... and your transaction was 2107 bytes. That's close to 10 times the size of a simple "1 (legacy) input, 2 output" transaction.

You had 14 (legacy) inputs and 1 output.