Quite right, yes, you can use a GPU Mining rig for cracking wallet passphrase as long as the software supports multiple GPUs and your GPU models.
But it's not logical to think that wallets uses the same method as mining, different wallets use different encryption and implementations.
In fact, I can't find any wallet that uses solely SHA256 for encryption.
That's why most wallet recovery software uses bruteforce (give random/pre-generated chracters & words until it hit the correct one) than reverse-engineering the encryption.

Example: Electrum encrypts the wallet file using AES-256-CBC; Bitcoin Core uses the same for the private keys but with an encrypted master key by the user's SHA512 encrypted passphrase with other "random" stuffs.

So, what you should research about is the most suitable GPU model that's supported by most passphrase cracking software available online.
That, I can't help you.

So it didn't work, there's no other way but use Bitcoin Core equivalent software for BCD then.

That command was designed to sign the transaction using one of the wallet's private key (The one required by the Tx).
Or using the given private key, I guess adding multiple keys wasn't supported.

One last time, try signing the Raw TX using only one key at a time:
Including the punctuation and parenthesis.

His point was for backup purposes, because with the current suggestions with LN implementation, it's not possible to recover the whole wallet with opened channels using only the Mnemonic Phrase.
I can't find any written articles if it's possible with their "Watchtower implementation" since it saves a backup and keep the channels online even if the client is offline.
Only this non-answered post of shivaenigma to the link below.

Late: https://github.com/spesmilo/electrum/issues/2557#issuecomment-438718104, yes it will be done by the client.
But according to the post, they haven't decided to enable the client to forward payments but keeping it disabled may lessen the traffic:

.
@nibor If you want your suggestions to be discussed, open a feature request in the official Github page (issues) with label: lightning: https://github.com/spesmilo/electrum/labels/lightning%20%E2%9A%A1

Next time, take the time to include all these info right from the start.

Have you already tried increasing the dbcache to half of your RAM? like 8192MB.
The cache isn't limited for verification but also start-up: Step7 Cache Sizes.
Note: the min-max value wasn't the same for the latest version.

If you have GUI, open "Options->Main Tab->Size of database cache"; if not, add dbcache=8192 to your bitcoin.conf file.

Hmm, when the other cores aren't needed, it wont be used.
Or it could be a problem with your system, do you have any other CPU-intensive applications for testing?

In addition to my post above, this statement quite bugged me:
Bitcoin never dropped below $200 in 2015 and it's impossible to buy 0.7BTC at $70 value.
If it was 2013, the price made sense (are you unsure of the date?) and the highest version that you must use is 1.9.x (like the example).

If it's some sort of a bargain and bought in Q4 2015, the highest version that you must try is 2.7 because of another wallet file format upgrade:

But as I said, in every attempt, always delete the "tempxx" wallet file and re-copy and rename your "original" wallet file to the wallet directory.

Try this, but first make sure to re-download your wallet file from dropbox and keep a copy and rename it into "original" or "clean-copy".
Because most of the time, old wallet files turned out corrupted when attempted to load using the latest versions and when you attempt to open it using the old version again, it won't open as the file itself was messed up by the previous process.

I suspect that the "upgrade process" is only available for 1.9 to 2.0 and later versions.

• Download Electrum version 1.9 from here.
• Copy the "clean-copy" to your default wallet directory and rename it into something like Test01 and load it.
• If it successfully opened, click wallet tab->Seed and enter your passphrase, then copy your SEED.
• Download the latest version and restore your wallet via the Option "Standard->I already have the SEED".
• If next isn't clickable, click option, enable BIP39.
• Select, "P2PKH" when prompted for address type.

It will just create and display the multisig address and its redeem script which he already have.
Wish Electrum had the "addmultisig()" command for spendable [imported] wallets.

---

@100bitcoin I don't know if "signtransaction()" will work but you'll lose nothing if you try.

Test [1] First create a watch-only wallet by importing your multisig address and create a (send-all) raw transaction - copy the Transaction HEX.
Next, go to the console tab (View->Show Console) and type the command:

Test [2] Create an imported wallet using the three private keys which will create a wallet with three separate standard addresses.
Go to Console tab, and type the command without the optional private keys.

If successful, broadcast the signed transaction hex.
Once again, I only tried it using standard address/wallet, there's a high chance that it wont work for multisig.

To be fair, there are indeed short phrases that can produce the same translated results.
Now if you can give us the exact two different pre-translated sentences that will result in your and SektorPiii's posts, mods may believe your claim.
(Whisper: Translate it vice-versa and/or change the prepositions: to, on , in)

Also, how come you've end up using a closing parenthesis without even using an open parenthesis on the beginning of your post just like SektorPii did?......
Quantum Entanglement?

I can agree with your explanation about the malware detection but,
since your software is closed-source, people will always be skeptical about it.

If I were you, I'll add reviews and testaments (from trusted source) or ask a trusted member to review this software to gain some reputation.

Regardless of the consequences stated above, you can do it using "Tools->pay to many"

Click the image to view full size.


Just follow the image's format [Address, amount] and it will be sent to the same address as different outputs.

As you can see, the total transaction size is 395bytes (2inputs/6outputs) at 1sat/b with a total of 0.00000395BTC transaction fee (outputs doesn't add as much bytes as the inputs does).

Have you already tried the example above for testing purposes?

For ProHashing, you need to register (I think you already did) just use cgminer.exe -o stratum+tpc://prohashing.com:3335 you don't need to put your password as an argument (it's for the server's password for extra features).
The problem might be the "-p" argument that wasn't included here, the extra "x" and the last part "--gekko-r606800", but it will work with your username included.

I don't mine on ProHashing, 'tis may be wrong.
If there's a problem, seek help from Prohashing pool miners to the official thread (link in my 1st reply).

AFAIK, the next characters after the (lower-case) "-p" argument is the password but the example above was followed by "x" instead of a password (at least that was specified by the quoted post because ckpool doesn't requires it).
If you're using a pool that requires a password, specify the password instead of x.

And I think "--suggest-diff" was just added because of the expected hashrate of R606.

You can create a shortcut of cgminer.exe and add those to the Properties -> Shortcut Tab "Target", then save. (are you using Windows?).

Example: "C:\CGMiner_Folder_location\Cgminer_version.exe -o stratum+tcp://pool.ckpool.org:3333 -u 1bitcoinaddress -p x --suggest-diff 128"

FYI, "R606 miner" is BM1387 and here's the official support thread: GekkoScience NewPac / Terminus R606 (BM1387) Official Support Thread.

To get you started, select a mining pool first (example: ckpool) and select your server depending on your location.
After that, do whatever you were instructed to connect the R606 miner (I'm not familiar with USB miners)
then, open you cgminer and enter one of the command below (whole line).

I'll just explain the Windows syntax:
Yellow: The this depends on the Pool of your choice, some are stratum, http or socks5 (for ckpool: change the bolded part with the server of your choice).
Green: Worker ID, your earnings will be sent here (Bold: your wallet's Bitcoin address).

This site (bitnodes) will show you the total number of "visible" nodes and the global distribution of all nodes but not the varieties.

However, you seemed to have researched beforehand and mistook "wallet" or "clients" for "nodes",
that's why you've included "SPV nodes" and "light nodes" in your list, these aren't nodes but clients and often called light wallet or light client.
Those light wallets weren't individually included to the total number because these type of clients doesn't directly connect to the (Bitcoin) network but to a server which is a full node.

On the other hand, I can't tell if it's possible to differentiate pruned node and a full node if you're using a crawler to count them.
(crawler: used by those "node count" sites).

It's now confirmed with 11 confirmations.

Next time, if you have no idea what to put in the fee rate, make 10sat/byte your minimum
(Higher for SegWit because some sites often have errors in computation of the fee with Segwit addresses).
Why? Some free accelerators like the one suggested above only accept TXIDs with fees higher than 10sat/byte  

This will create a totally different watch-only wallet which isn't multisig, the addresses wont be the same thus the "real" wallet's balance won't show up.

Have you tested it with wallet(s) with balance?
Have you properly set you 2 of 2 wallet? Maybe you've selected 1 of 2 from the slider.

Refer to these image:
For 2/2 multisig wallet-

For 1/2 multisig wallet-


But even with 1/2 multisig, creating a watch-only wallet using only one public key will create a standard watch-only wallet.
But with 1/2, you will be able to spend using one signature.

Because of this, I ended up reading their Whitepaper.
And guess what, it's not even technical and details about "how they reward BTT from seeding" wasn't included (just mentioned)

I can't find anything online either, just all "how to" without the actual numbers and rewards.

My guess is, the user(s) who've been downloading your files need to have the "Speed Increase" toggle button enabled for you to gain BTT.
(this paid in BTT "speedup" system sounds sketchy though).

You just "woke up" last December 22, 2018 (about 10months from now), so we can call it your "start date".
Also, experience isn't all about the account's registration date, some members who've recently registered probably have more "experience" than me.

You need to be at least a Jr Member (1 merit) to be able to do that, or buy copper membership.

But you seem to be a genuine "gambler", I will look into your posts to find meritable post(s).
The thing is: users don't usually give merit to those boards, that's why.

---

-edit-
I've read your posts.
It's better to open a scam accusation against the casino/site if you think you're scammed than posting it to their own thread, that way DTs can tag the user.
A red flag is much "louder" than posting evidences to their own territory.

Have you both read this: Reply#2356? It's the long version of the one in the OP.
Based from the context, he wont be coming back, not just because of the free time but also because of the other competitors' update speed.

Also, the repository in Github, the OP (hover over on the last edit date) and JCE-Miner himself have been inactive since March 2019 (all at the same time).

Eh, those are just the pools and exchanges that haven't yet updated their node, wallet and API to the post-fork version (2.0.0+).
It wasn't a big issue; how long? ~differs per platform.

Read the official announcement specially about "Actions Required".