How much will I save on fees really though that's my question. I get paid out from slushpool every .02 and my list of coins in electrum is really long so I figure big transactions of moving lots of coins I could pay less fees.
The answer is... it depends. The two main factors will be how many UTXOs do you have? (that is to say, in Electrum, how many individual entries are on the "coins" tab?)... and what the fee "rates" are like when you create a transaction. In terms of %, the numbers often quoted for fee reduction are: Legacy (aka P2PKH) transaction: 226 bytes Nested SegWit (aka P2SH-P2WPKH) tx: 168 bytes =~ 26% saving Native SegWit (aka P2WPKH aka bc1) tx: 141 bytes =~ 38% saving However, those values are for your "typical" 1 input, 2 output type transactions. Using something like the coinb.in/#fees calculator you can mess around with different values and we can see: 100 "legacy" inputs + 2 outputs = Chargable Transaction Size: 14874 bytes 100 "Nested SegWit" inputs + 2 outputs = Chargable Transaction Size: 10076 bytes A difference of ~32%... which would equate to quite a substantial amount of BTC in times like this when BTC is pumping and "recommended" fees start pushing the 100+ sats/vByte mark!  Although, you'd probably be advised to wait until the network isn't quite as busy and aim for that sweet sweet 1 sat/vByte fee rate  One other thing to consider... is it possible to increase the slushpool minimum payout level so that you generate less UTXOs in the first place?  |
|
|
|
Moral of the story is... don't just trust ONE blockexplorer! That's why I wrote myself a little custom extension for Chrome that allows me to highlight a transaction (or address), right click and look it up on background tabs on blockchain.com, blockcypher, blockchair, btc.com or all 4 at once  |
|
|
|
So... some positive news... I received this email overnight  Domain Registrars usually take abuse claims relatively seriously... especially in the case of malware and phishing. It's worth reporting! Namecheap Legal & Abuse Team < abuse@namecheap.com> 15 May 2019, 22:46 to me Hello, This is to inform you that the electrum[ . ]mx domain was suspended. It has been placed on the clientHold status and locked to prevent modifications in our system. Thank you for letting us know about the issue. ----------------------- Regards, Nikita O. Legal & Abuse Department Namecheap.com |
|
|
|
I've installed the Electrum software. My mac is operating at OSX 10.9.5 but the application doesn't open. It begins the process but doesn't complete and just quits. I've also tried to install earlier versions of the app but nothing has worked. To get back to the OPs issue... I don't think the newer versions (ie v3.x) of Electrum will run on such an "old" version of OSX. It appears to be an issue with the version of Python (and related libraries) Refer: https://github.com/spesmilo/electrum/issues/3685Also, you need at least v3.0.0 to be able to get the SegWit features... so, even if you went REALLY old an used v2.9.3 (which should run on OSX 10.9) you wouldn't be able to sign the transaction for your Ledger SegWit address anyway  So you will need to either update your OS or try and borrow a computer from a friend/relative that is using a newer version of OSX or Windows 10 (note: even Windows 7 can be problematic!) and then install Electrum 3.3.5. |
|
|
|
I find it odd you were able to get 3.0.5 to synchronize, there may be a server floating around the network that has not been patched with the latest update.
Most likely OP was simply connected to a "bad" server... I suspect that these "bad" servers have not implemented the patches that break syncing on older versions for exactly this reason. If an old version just happens to try connecting to them first, it will be able to sync and everything will look "normal"... User tries to send and gets the fake popup message... And another possible victim is created. But at least this episode had a happy ending! |
|
|
|
The 175 char key you keep talking about is likely not a "key" but (encrypted) text in a .key file right? If all 6 transactions are black... They're all incoming transactions where you "received" coins. If you have a positive balance then the private key you imported should be able to be used to spend them. So, you should be able to send that 350 mBTC (0.350 BTC) to wherever you like. Have you actually tried a send transaction? |
|
|
|
What does "continue posting / sending PMs" truly means ? Continue posting anything on forum is considered as ban evasion or posting something particular on forum (for example person does shitposting in Binance topic -> got banned -> creates new account and continues to shitpost) ?
Exactly what it says... and the ONLY exception is creating a thread in Meta to query/appeal your ban. Anything else is ban evasion. |
|
|
|
Does anyone have any experience with Exodus?
I don't recommend Exodus (even as a desktop wallet)... and it certainly isn't useful for creating paper wallets. Yes, I def meant a paper wallet
If you're interested in paper wallets, try having a read of the resources on: https://bitcoinpaperwallet.com/It has some very good explanations of the entire process and precautions you should take when generating and printing paper wallets. |
|
|
|
My question is if i can register new account post freely on the forum?
It would appear you still haven't read the rules: 25. Ban evasion (using or creating accounts while one of your accounts is banned) is not allowed.[e]
Which is explained in a bit more detail in the examples section a bit further down that post: 25. If you get banned (temporarily or permanently) and create a new account to continue posting / sending PMs, it's considered ban evasion. The only exception is creating a thread in Meta about your ban.
|
|
|
|
Yeah... that's correct, now you need to find the wallet file ( http://docs.electrum.org/en/latest/faq.html#where-is-my-wallet-file-located) and open it in a text editor... at the end will be a section that has something similar to: "wallet_type": "2fa",
"x1/": {
"pw_hash_version": 1,
"seed": "harvest ensure test voice oven story crater garbage spawn phone cause weird",
"type": "bip32",
"xprv": "xprv9uELvPiTpnhXw5PeLBThFc98p3VF6KiLdAyy1a8d9kERhShTfFqj9zVUc6g5myFoZnUBrAdYukt TVidpoeoxVYYG99urGzDeMNhHx3BMXdC",
"xpub": "xpub68DhKuFMfAFq9ZU7SCzhck5sN5KjVnSBzPuZoxYEi5mQaF2cCo9yhnoxTPhRXQvWip4BWyRaUGi nvVr33Dj2SgQAT3axBBdDzTyBskVgXTJ"
},
"x2/": {
"pw_hash_version": 1,
"type": "bip32",
"xprv": "xprv9uELvPiTpnhY1VPzNwmBCnNLuiez1L4JjSAYcdsT1hkyDbB3mhEZ7WTYP1hVLjoSYUbPX3znhZW p7692PfBxA8511k688fN3BYY4TMn5BaT",
"xpub": "xpub68DhKuFMfAFqDyUTUyJBZvK5TkVUQnnA6f69R2H4a3Hx6PWCKEYofJn2EGNZdweXW591FxHdwhY 3syDbVmw6NJMev2drZUtEKMoYzDiYKqt"
},
"x3/": {
"pw_hash_version": 1,
"type": "bip32",
"xprv": null,
"xpub": "xpub661MyMwAqRbcGi6rn7XyNpt5eGaihvKZEqG4frwzcWHQE4NrbHYDDGChfmHdhcTjqZfX39kCGCa KrGCMsysi5V2YhqsH2cWPju4drPjdDk5"
}
You need the x prv's from the x1/ and x2/ sections... and the x pub from the x3/ section as highlighted above. You then need to create a multisig wallet in ElectrumSV... using those co-signer keys in order... so co-signer1 = x1/ xprv... co-signer2 = x2/ xprv... co-signer3 = x3/ xpub NOTE: do not publish your xprv's (or seed) anywhere! They're you're private keys! |
|
|
|
my Electrum BTC is 2fa (password protected)
That is going to greatly complicate getting hold of your BitcoinSV. An Electrum (BTC) 2FA wallet is a 2-of-3 "Multi-Sig" wallet... it is created using 3 different keys. You can get hold of 2 of them by using your 12 word seed mnemonic. However, the third is actually held by TrustedCoin. Only they have access to it, and they will likely not give it to you. It's still possible that you might be able to recreate your wallet in ElectrumSV... if ElectrumSV allows creation of multisig wallets. You would need your original Electrum BTC 2fa wallet 12 word seed mnemonic. If you restore a copy of that 2fa wallet using your 12 word seed mnemonic, and select "DISABLE" when asked if you want to keep or disable 2FA... and then DO NOT set a password on the wallet file so you can open the wallet file as plain text. Doing this will restore 2 xprvs and 1 xpub into your "disabled" 2fa wallet file. Theoretically, using these 2 xprvs... and the xpub, you should be able to recreate a 2of3 multisig wallet that is a copy of your 2FA wallet... and will allow you to create and sign transactions from it. I've done a quick dirty test with a test 2FA wallet in Electrum and recreated it in ElectrumSV and it appears to create identical addresses in ElectrumSV... so it should work. |
|
|
|
It isn't a problem... You can either use the 3.3.5 installer or just download the new 3.3.5 "standalone" version... Either way, it should continue to use your existing wallet. The only reason it wouldn't would be if you are currently using the "portable" version. In that case you would simply need to copy the wallet file to a new location and the new version will be able to find it. If you have the 12 word backup seed mnemonic for your wallet, you can recover using just that... So a wallet backup isn't strictly necessary. Having said that, backing up the wallet file is never a bad idea |
|
|
|
Versions older than 3.3 won't sync any more... Changes were made to try and prevent users losing coins due to phishing attacks. Goto www.electrum.org and download and install the latest version (currently 3.3.5). Once you update the wallet will connect and sync just fine. Make sure you enter the website in your browser carefully, there are a lot of very convincing scam websites with fake versions of Electrum. Note that there is currently NO v4.0.0 and NO v3.3.6. If you see any message or link promoting these versions or websites that are not electrum.org they are FAKE! |
|
|
|
Mycelium wallet is known as a " Hierarchical Deterministic" or "HD" wallet. It doesn't contain just a single private key... it generates multiple private keys, so that you can get a different address every time you deposit. It does this to try and help avoid " address re-use". It is perfectly normal behaviour. Note that you can still reuse an address that it creates, multiple times if you wish... it just isn't recommended for privacy reasons. |
|
|
|
Thanks for highlighting that thread... I really do need to browse the B&H board a bit more frequently, as I totally missed that one. I think it got buried in amongst all the helpful "guides"  |
|
|
|
A couple of others to add to your list... The first was being shilled on the boards yesterday... the later is an old fake website that seems to have resurfaced. |
|
|
|
The only reference I can find regarding KYC and withdrawals is here: 5.5.8 Your winnings from settled bets are credited to your account and may be withdrawn in accordance with our withdrawal policy and if required by us, upon provision of the below materials to our satisfaction:
* a copy of valid photographic identification (passport, driver's license)
* proof of address (recent utility bill)
* credit/debit card to our satisfaction
* photo of yourself containing proof of date and identification materials
ArchivedBut that seems related more to withdrawal of "winnings", as opposed to getting your BTC refunded because they've decided to lock your account until you complete KYC. And I can't seem to find a "withdrawal policy" anywhere. In addition, they have this listed in the FAQ: If bitcoin is anonymous, do I still need to provide Cloudbet with personal information?
No, all you need to create an account and start betting is a valid email address. ArchivedThe increasing number of episodes similar to this are an indication that sites and services really need to be a lot more upfront about their KYC requirements.  I understand sites are loath to do so because they're (rightfully) concerned that users will simply skip over them and move onto the next site that (supposedly) doesn't have KYC, but then you are opening yourself up to scam accusations when incidents like this occur. If you are also from an area prohibited from betting on their site, they state you will lose your deposit and close your account.
Actually they don't... they say (twice) that they reserve the right to shut your account down and refund you money... but again, no mention of KYC 5.4.2. We reserve the right to close your account and to refund to you the Account Balance at our sole and absolute discretion and without any obligation to state a reason or give prior notice.
8.3. Cloudbet reserves the right to close your account and refund the balance of your account without further explanation. Subject to any provision of these Terms and Conditions to the contrary, outstanding bets will ordinarily be honored. Further, we retain the right to suspend the whole or any part of the service for any reason at our sole discretion and in such event we may but shall not be obliged to give you any notice, however, we shall endeavor to provide you with such notice as we deem practicable.
Personally, I think they should honour these T&Cs... and simply give the OP their funds back... and then seriously consider updating their T&Cs and FAQ. |
|
|
|
First he never said it was his key, only a key,
First, stop trying to look intelligent by play semantic games... it's very tiresome and doesn't assist the OP in anyway. next blockchain no longer allows import from key,
Next, that's inccorect. I see this in my old blockchain.com wallet:  so the ability to import from key is still available within blockchain.com wallets. thirdly, you can use an opendime to do such a thing I suppose, and there may be other ways to do something similar these days.
Why would you want to use an opendime to convert BTC to fiat? That seems like a long winded (and expensive) way to achieve the stated goal. One would have to order an opendime... at an advertised minimum cost of US$39.94 for a set of 3 (+ taxes + shipping)... wait for them to arrive, then send the bitcoin to the opendime deposit address... then try and find someone to buy the opendime from you. Or you could do as suggested by others and simply import/sweep the BTC from the private key to a web wallet (like blockchain.com) or an SPV wallet like Electrum. Then you can send the BTC to an exchange that supports fiat withdrawals in your location or you could use localbitcoins and find someone in your local area to trade the BTC for cash. |
|
|
|
|
Is there anything obvious in the debug.log file that indicates why your node is stopping at block 569512?
It's possible there is a corrupted block causing issues (seems to be a fairly common occurrence when running with the blocks data on external drives). If you see something in the debug.log that inidicates something like that, you could try deleting the last block file and then restarting the node with -reindex to see if that helps...
otherwise, try pasting the last couple of hundred (thousand?) lines from debug.log to pastebin and then post the link here so peeps can check if there is anything obvious in the log as to why your node is not working properly.
|
|
|
|
|
Show Posts
