This parameter is set -allpools 0
not "- allpools", -allcoins 0, or try -allcoins exp: -allcoins Specify "-allcoins 1" to be able to mine Ethereum forks, in this mode miner will use some default pools for devfee Ethereum mining.
Note that if devfee mining pools will stop, entire mining will be stopped too.
Miner has to use two DAGs in this mode - one for Ethereum and one for Ethereum fork, it can cause crashes because DAGs have different sizes. |
|
|
|
The thing is, you've mentioned " you have to use a file from GitHub" and that's the first thing that I remember ( &it was, I guess) That's why the example was about using that mnemonic generation tool. Additionally, Electrum doesn't guarantee that " BIP39 support" and it might be depreciated in the future, If that happened, you can still use your BIP39 Mnemonic in other tools/clients that support BIP39; something you cannot do with set of random words that has an invalid checksum. ( though you can download the older version that still support it) |
|
|
|
So maybe we should stop telling people to create a Legacy address over the 3 segwit ones?
I still have not tried to create a Nested Segwit (starting with 3) address using Electrum. I think one needs a file for github and use it with Electrum to create the address. Not convenient for regular users. You mean this: https://iancoleman.io/bip39/? It quite easy really, all they need to provide is the BIP39 Mnemonic Phrase from that link/code and select " BIP39" in the option below the " I already have a SEED" input box. After that Electrum will provide options for the user if he want any of the three address types of a standard wallet ( not available for old versions). Pretty same difficulty as creating a standard wallet. The only " sensitive" part is the part when the user create the BIP39 SEED ( S...E..E...D....  ). Not rocket science, but a security risk if not done right. |
|
|
|
If the fees used for this transaction are too low how do I go about this? I've tried using a btc accelerator and it says my transaction is already confirmed. At this point I'm completely baffled. Hope someone can help!
No one mentioned that it's already confirmed... yes it was. If blockexplorers like blockchain.com doesn't show " x confirmations" or " unconfirmed", it already have hundreds of confirmations. Additionally, it got the first confirmation in just 2 hours after you broadcast it, so it should be your Ledger live app. |
|
|
|
It is abnormal to see there are very little nodes in China, that has the biggest bitcoin mining farms, globally. Nodes in China account for only 4.2% of current bitcoin nodes.
All I can tell is Mining farms doesn't usually require a full node in exception to solo mining farms, all they need to have is a secure bitcoin client/wallet to receive the their payouts. Plus, Bitcoin is partially banned there: wiki: Legality of Bitcoin. |
|
|
|
|
Try to set "-allcoins" to 0.
If it didn't work, post your question on Claymore's official thread;
the OP here haven't logged in since February 27, I doubt he will respond.
|
|
|
|
Yes, it's quite normal but the " fix" isn't just for the x86 (32bit) version, it was intentionally removed in 0.18.0 ( 15471). @ AquaRegia1If you really want it to be removed, update your client to 0.18.1 or even 0.18.0. |
|
|
|
First, make sure not to add a "#" in front of the line 'cause it will be considered as a comment. And use one line per config. The value uses BTC/kB unit so: 0.00001BTC/kB is the default which is 1sat/B. Try to use these values ( 0.1 sat/B you said?) instead of 0: minrelaytxfee=0.000001
mintxfee=0.000001
Or did you mean 0.1sat/kB? I haven't tried it because it's way too low and probably wouldn't work but, try to use these values: minrelaytxfee=1e-9
mintxfee=1e-9
for 1 sat/kB | 0.001 sat/B | 0.00000001 BTC/kB 1e-7 for 10 sat/kB | 0.01 sat/B | 0.0000001 BTC/kB
Y tho? |
|
|
|
Hello, I'll start with the fact that half a year ago I downloaded the electrum wallet and used it successfully until today, today I decided to go to my wallet to check my balance, then I went out and came in 10 minutes, my transaction was already gone and there were 2 confirmations, I'll tell you right away that I downloaded everything only from official sites, the version of my wallet was up to 3.3.4. The password was 40 characters and I didn't give it to anyone but me, nobody knew it in my head! And if it matters I used linux ubuntu. Eventually, all my accumulated money was stolen, is that how it will stay?
Hmm, version 3.3.4 should be safe from phishing scam but having a very long passphrase doesn't guarantee your fund's safety especially if your SEED was already leaked before that incident. It's very hard to tell what happened but to give you somewhere to start, verify the signatures of your current Electrum or/and the previous version(s) if you've updated it. By the way, the transaction already had 2 confirmations, so there's no way to reverse it. In Russian: Hmm, Bepcия 3.3.4 дoлжнa быть зaщищeнa oт фишингoвoгo мoшeнничecтвa, нo нaличиe oчeнь длиннoй ключeвoй фpaзы нe гapaнтиpyeт бeзoпacнocть вaшeгo фoндa, ocoбeннo ecли вaш SEED yжe был yтeчён дo этoгo инцидeнтa.
Oчeнь тpyднo cкaзaть, чтo пpoизoшлo, кpoмe кaк дaть вaм мecтo для нaчaлa, пpoвepить пoдпиcь вaшeгo тeкyщeгo Electrum и/или/и пpeдыдyщeй вepcии (вepcий), ecли вы oбнoвили eгo.
Кcтaти, тpaнзaкция yжe имeлa 2 пoдтвepждeния, тaк чтo ee нeвoзмoжнo пepeвepнyть.
Translated with www.DeepL.com/Translator |
|
|
|
*Sigh*, guys, please read the discussion before replying. OP somehow able to get the SEED using the wallet->SEED option that should be grayed-out for 2FA wallets, with that, LoyceV mentioned: I've never used 2FA on Electrum, but doesn't this make 2FA totally worthless?
And someone replied an irrelevant answer and I told him " that" reply. To be precise: 2FA's purpose is to protect the user's funds even if the wallet file together with the passphrase got hacked. If the ( view) SEED option is enabled ( which looks like the case here), then 2FA for that particular wallet file is worthless because a hacker can just view the SEED.
|
|
|
|
-snip- ...or the electrum team are willing to help
" Electrum team" won't be able to help you directly on recovering your wallet, all they can do is to inform you about the possible options. They don't have access to your private keys, wallet files or even public keys. I've never used 2FA on Electrum, but doesn't this make 2FA totally worthless?
Also, I never used 2FA on Electrum. Question so how to safe them? -snip-That's not what she meant, The problem is: if someone got access to the wallet file and its passphrase, he can just extract the SEED from it and restore into a 2FA disabled wallet; the 2FA Authenticator app wont be even needed by the culprit to steal the funds in it. AFAK, " Wallet->SEED" should be grayed out for F2A wallets and will only be available if user disabled 2FA. OP has multiple wallet files, let's wait for his reply. |
|
|
|
I'm going to ask a painfully obvious question here, has the OP tried to re-broadcast their transaction to the network? -snip-
It will not make a big difference as his transaction was probably already included in the miner's node at that time. You'll know that it's all over the network the moment you can see it in all blockexplorers. Rebroadcasting may be an option if the node where he broadcast the TX was connected to peers that didn't relayed his tx. |
|
|
|
[1]  Yes it's pretty obvious that he's using the latest version 0.18.1 ( Aug 9). [2] Actually, I missed the timestamps that he's almost at the latest height ( so those were definitely "ASIC boost" blocks) but there are few block-version-related issues that will result with that error... old issues. BTW, that linked " error msg" was removed in 0.18.0. ( https://github.com/bitcoin/bitcoin/pull/15471).
|
|
|
|
|
Try to set it to intensity 1 and use --intensity=1 argument instead of -i 1.
|
|
|
|
socket recv error An existing connection was forcibly closed by the remote host. (10054) There seems to be a problem with your current connection to a peer that's why you've received that error. Are there any issues with your ISP or are you using any IP-changing setting/software? Are you having trouble syncing or connecting to other nodes? Your log looks fine to me as it continued to sync. Additionally: warning='45 of last 100 blocks have unexpected version.' This is quite common for newly updated nodes with blocks verified by the older version. |
|
|
|
simple one... how to print wallet.dat to a paper  ? Simple question  Say no more: [1] Close all network connections, [2] open the console, [3] use walletpassphrase "your_passphrase" 600, [4] then dumpwallet "C:/file_name.txt" command. [5] Find that "file_name.txt" in your C directory and print it. You might need 10 sheets of paper if your wallet.dat have used hundreds of addresses. Or do 1-3 and... [4] dumpprivkey "type_one_of_your_address", print the result. Is it troublesome?; use bitaddress' code ( downloaded from github) instead. |
|
|
|
Linking an unreliable/outdated source isn't good for beginners, there's a lot of inconsistencies in that article. First paragraph: the maximum block size isn't limited to 1MB, it could reach more than 1MB if there were more SegWit transactions in that particular block ( theoretically <4MB). Wiki: Segregated_WitnessHistory? : 2.25MB block height 540107Second Paragraph: They aren't adding " extra fee" to increase the chance of confirmation, they are charging " service fee" for their paid service which is a simple prioritisetransaction "txid" 0.0 <virtual fee> command. If they want to " increase their mining fees & reward", they can just mine normally because it will automatically select the transactions with the highest fee. It's a mix of public service and taking advantage of other people's mistakes. |
|
|
|
There's a "delete from history" function on android as far as I can remember... Maybe it got removed at some point...
It's only possible with " local transactions", the ones that you've saved by importing signed TX hex. Because you haven't sent them to the network yet. Unconfirmed/Confirmed TXs can't be deleted, AFAIK. |
|
|
|
depends on what your budget is - -snip-
You also need to remind him about the power consumption, noise and heat of an Antminer S9.
Each consume more or less 1,400W, 5 of them might flip an ordinary home office's breaker. The ASIC's Fans are really loud ( more or less like an old vacuum cleaner), it's not suitable for living areas with non-soundproof walls. Heat isn't much of a problem for a single ASIC, but with 5, you wont be needing a heater. |
|
|
|
|
Show Posts
