1. The BTC address where the BTC is stored starts with a 3... and is 30 characters long in total
2. The public key: 04de... 130 characters long in total
3. The passphrase I used as a first password: @2... This is a personal password 18 characters long in total
4. The second password which was hidden under a hologram on a physical Bitcoin coin: ELG... 30 characters long in total
Private keys were not given to me.
That's a start.
You can try to follow the "
watch-only" part in my instructions above to check if you can restore the correct address and if you have a synced Bitcoin Core, you can scan for transactions (
balance).
You may try it multiple times depending on the number of public keys you have.
Based from your feedback, you might have two; (1) your uncompressed public key and (2) the public key from the "
physical bitcoin coin" which should be available somewhere since you can't create a MultiSig address associated with that coin without it.
E.g.: For two pubKeys, try a
sh(sortedmulti(2,<pubKey1>,<pubKey2>)) descriptor or even a
sh(sortedmulti(1,<pubKey1>,<pubKey2>)) if the former failed to restore the correct address.
Or to try to different arrangements of the public keys with
sh(multi(2,<pubKey1>,<pubKey2>)) and
sh(multi(2,<pubKey2>,<pubKey1>)), then each's single required signature variants;
sh(multi(1,......