Quote from: o_e_l_e_o on Today at 12:11:10 PM

Quote from: Kryptowerk on Today at 11:28:38 AM

That sounds interesting. Would it tell anything about the derivation path or other wallet properties? How does the script used to send help in my case?

It wouldn't tell you anything about the derivation path, but it would tell you if you are indeed looking for a standard nested segwit address. If you are, then we can tackle finding out the derivation path. If the script is something different, then checking derivation paths as you are doing with Electrum or similar will get you nowhere.

Quote from: Kryptowerk on Today at 11:28:38 AM

Can you guide me through the steps without me exposing my pub keys?

Find one of your addresses from the mSIGMA wallet which has sent coins out from it, and grab the TXID. Head over to https://mempool.space/ and look up that transaction. Click on where it says "Details" on the right hand side. Underneath your address the first field should be titled "ScriptSig (ASM)". Hopefully next to that it says "OP_PUSHBYTES_22", followed by "0014" and then 40 random characters. If it does, then you've got a nested segwit address. If not, then you've got something different.

Okay, wow how do you know this stuff? Cheesy

Ermm... yes so, there are several interesting things here:
ScriptSig says "OP_0
OP_PUSHBYTES_72" then followed by defintely more than 40 chars (looks like around 100)
and then it says OP_PUSHBYTES_37 followed by maybe 50 characters

Also it says multisig 1/1 - which isn't normal, right? Does a 1/1 multisig even make sense?
Seems like you were right and every mSIGNA wallet is indeed multisig - even when it actually isn't really. Huh