The problem is that the transaction script is not valid...

Blockcypher returns this error when you attempt to rebroadcast the transaction:
The script that has been generated to spend this UTXO is invalid. The most obvious reason would be that the transaction has been signed with the wrong private key...

Where did this transaction actually originate from? Is it a transaction you are creating from within your own wallet? If so, did you just create the transaction using the GUI or did you attempt to manually create and sign the transaction from the console?

@OP, as the original UTXO has not been spent yet, you should be able to simply rebroadcast the transaction.

Firstly, copy the raw transaction hex... right-click on the transaction and select "copy raw transaction". Then rebroadcast the transaction... "Help -> Debug Window -> Console" and use the sendrawtransaction command:

sendrawtransaction "PASTE_THE_RAW_TRANSACTION_HEX_HERE"

Thanks for taking the time to report this... hopefully it might help others spot similar shenanigans... if it helps just one person avoid getting scammed, it will be worth it!

One (or possibly both) of these two users is either confused, or not telling the truth.

My understanding of the timeline for this incident goes something like:

- polypusx talked to "someone" on Telegram using Telegram account advertised in Developerx11 thread
- polypusx and "someone" negotiated a deal and polypusx sent BTC to "someone"
- polypusx starts scam thread
- Developerx11 claims he no longer has access to that Telegram
- Developerx11 admits that because he had left that Telegram account on his thread, he would cover the loss
- Shit fight develops because Developerx11 wants to use discord, and polypusx wants to stay in public on BCT forum


Proposed Solution:

- polypusx should post a BTC address in this thread
- Developerx11 should sent the agreed amount of BTC to that address
- polypusx can change the thread title to "RESOLVED" and then lock the thread
- Any "red tags" left because of THIS scam accusation should be removed
- All users can get on with their lives

That is because it wasn't a hack... it was social engineering. The exploit simply allowed the attackers to display a message with a clickable link. It did NOT give any access to private keys or seeds.

So, any funds held in the legitimate wallet were "safe"... Funds were only lost if users then manually downloaded, installed and ran the "fake" version of the wallet (that failed digital signature validation!) that was being advertised via this software bug/exploit. Users who did nothing were safe.

If users attempted to validate the digital signature of the wallet (that they had to manually download) before they installed/ran it... then they would have found it was fake, and would have most likely avoided losing funds.

From memory, Ledger originally used a slightly different derivation (m/44'/60'/0') for ETH/ETC wallets to what became the "standard" (m/44'/60'/0'/0)...

MEW and MyCrypto used to ask which path you wanted to use... I'm wondering if the "Metamask accounts" are simply ETH accounts using a different ("standard") derivation path?

There shouldn't be any API or webservice that does this... because it is a "Bad Idea"™... you're essentially broadcasting your private keys to an online service.

If you need to be able to convert from a seed mnemonic to your private/public keys and addresses, I suugest that you read up on BIP39: https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki

It even has a list of implementations for a whole variety of programming languages at the bottom of that github page. I can almost guarantee that whatever language you are currently using for your project, already has existing libraries to convert from seed mnemonic to keys/addresses, so you will be able to do the conversion locally without needing an external service.

Yeah, I don't understand... All they've said is that they returned the funds because it was cancelled, but I still don't see any justification for why the bet was cancelled in the first place? They simply say "we always cancel said lines".

I'm thinking there is more correspondence that we have not seen. Did they provide any reason for why it got cancelled? Did they claim it was a "bad" line with incorrect odds or something?

Have you actually contacted Nitrogen Sports asking for an explanation?

If so, did they provide any information as to why the bet was cancelled? It's quite possible it was just an error on their part. Mistakes do happen from time to time... however if they have responded with some rubbish reason, then you should post proof.

You'll need to talk to the devs of the "BTCP Electrum" fork... as this is the BTC Electrum support board.

You can try asking on the BTCPrivate github here: https://github.com/BTCPrivate/electrum-btcp/issues but it looks like the project is fairly dead...

I suspect your problem is that there are no BTCPrivate Electrum servers running... or the ones that are, are woefully out of date/unsynced...

Your other option would be to export your private keys and import them into another BTCP wallet: https://btcprivate.org/wallets

This is NOT something that should be done using an online service!

The "BIP39 words" are a mnemonic used to derive the BIP39 seed... from this seed, ALL of your private keys, public keys and addresses can be derived.

Putting your BIP39 seed mnemonic into an online service, basically compromises your entire wallet.


That website will allow you to enter the words and get the public keys... it just isn't provided via an API etc... you have to manually enter the words into the BIP39 mnemonic box and your addresses are displayed at the bottom of the page.

It is advisable to download the page and run it "offline" to avoid compromising your seed mnemonic and wallet keys. Instructions are on the github repo: https://github.com/iancoleman/bip39#standalone-offline-version

It is a single, self-contained .html file that you can open locally and provides exactly the same functionality as the online website.

Thanks for the report...


Can confirm that "electrumd o w n l o a d.com" (DO NOT VISIT - SCAM URL!) is a phishing URL... with version "4.0.0" available for download...

Chrome initially warned that the website was unsafe... After manually "proceeding" to the website, I attempted to download it onto the sandboxed VM... and Windows Defender detected a trojan (Trojan:Win32/Spursint.F!cl) and removed the download. After manually allowing it... I tried to GPG check the file and got "gpg: Can't check signature: No public key"

Be safe out there!

Honestly... in the current climate of Crypto, I think that they will find it difficult to gain any traction with a closed-source wallet solution.

With the constant scams and fake wallets etc... users are becoming more and more paranoid. Best of luck to them... but I doubt I would use it for any more than petty cash.

I'm glad to see that Ledger have not only admitted that they screwed up, but are actively working on fixing it. It is a shame that the fix is not likely to arrive until Q2... but at least they are working on it.

No, it is not correct.

If you receive bitcoin in 1200 different addresses, when you recover using the backup, it will find all the transactions in the first 1000, then start generating "new" addresses which, because of the nature of HD wallets, will be identical to the original 200 "missing" addresses... and thus it will find all 1200 bitcoin addresses... it will then top up the keypool again with more addresses until it has 1000 unused.

As TryNinja and LoyceV have indicated, even if you didn't receive any coins on the first 1000 addresses... you will still be able to recover the funds received, by manually forcing the wallet to generate the "missing" addresses. Again, because of the nature of HD wallets, it will always generate the same group of addresses as it always starts from the same starting point and follows the same path when generating the keypool.


In short, you will be able to recover ALL your funds. What you will not be able to recover will be any custom labels that you manually added to addresses after the backup was taken (as the backup will not contain these labels).

That sounds exactly like using a "watching only" wallet + "offline signer" (air-gapped PC or hardware wallet) solution...

It would appear that your issue is that you need "coin control"/"spend from address" features + "Hardware wallet" support in the wallet software that you are using... for Ethereum. I know that what you're wanting would probably be possible with Electrum, but that is bitcoin only.

Electrum has really good coin control features and you can see a list of addresses (set to 25 by default, but possible to increase the gap limit if required)... and you can "spend from address". It also supports Trezor and Ledger.

Unfortunately, as far as I'm aware, no-one has created something similar for Ethereum... as most people just use MyEtherWallet or MyCrypto wallet... and most simply use one ETH address due to the way that network works.

Try this... major NZ Newspaper... they had this article in today's paper: https://www.nzherald.co.nz/technology/news/article.cfm?c_id=5&objectid=12203358

Jaxx is a Hierarchical Deterministic (HD) wallet... it can generate an infinite number of private keys from the seed that is generated from your 12/24 word seed mnemonic.

However, if you simply imported private keys into Electrum, it can only ever know about that specific group of private keys... it cannot generate new keys (and new addresses) that match any new keys/addresses generated in Jaxx.

For instance:

Jaxx:
"seed12345" generates keys:
privKeyA => Address1
privKeyB => Address2
privkeyC => Address3
privKeyD => Address4
...
etc

If you were to export privKeyA through privKeyD and then import them into an Electrum Wallet... that wallet would contain this:

Electrum:
<NO SEED>
privKeyA => Address1
privKeyB => Address2
privkeyC => Address3
privKeyD => Address4


Now, if in Jaxx you then generate a new key/address... you will have the following two wallets:

Jaxx:
"seed12345" generates keys:
privKeyA => Address1
privKeyB => Address2
privkeyC => Address3
privKeyD => Address4
privKeyE => Address5

Electrum:
<NO SEED>
privKeyA => Address1
privKeyB => Address2
privkeyC => Address3
privKeyD => Address4


Note that Electrum does NOT know about privKeyE/Address5... unless you were to also export it and import into Electrum.


TLDR; If you want to import an HD wallet into another wallet... you should import the seed/seed mnemonic to ensure that you can generate ALL the private keys/addresses.

Yes.

Just like the OS that you're running... unless you're compiling your own OS from source code and have personally verified and checked all the code

This is a very "chicken and egg" problem... the (less than ideal) "solution" is that unless you have a LOT of technical ability and knowledge... then, at some point, you have to trust something/someone.

One begins to wonder "why" someone would campaign so hard for Electrum to reduce security by switching to using simple hashes for binary file verification?

Perhaps a "long con" to try and get the Electrum devs to help condition less knowledgeable users to implicitly trust file hashes to prove authenticity... so that they can then setup a fake site, with fake .exe and fake hashes to fool users who now believe that file hash = secure. 

Although, I think I'm probably giving some people too much credit.