|
Are you able to run the pre-compiled binary available for download on electrum.org using the Ubuntu 16.04 LTS and Wine 2.0.1 combination? Just wanting to rule out possible issues with attempting to run the Windows version under Wine.
|
|
|
|
Is anyone else getting an Uncaught Exception... looks like an SQLite Error of some description... but no idea what is causing it?  Uncaught exception: Error: Error: SQLITE_CONSTRAINT: FOREIGN KEY constraint failed INSERT INTO unit_authors (unit, address, definition_chash) VALUES(?,?,?) FDIOwPxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxO2/yE=, HZTYxxxxxxxxxxxxxxxxxxxxxxxxxxxxxCUE,
 |
|
|
|
Does it matter if I exported my private keys encrypted? Or should I keep them in plain text?
That really depends on what you want to do with the exported keys... if you're just wanting to back them up... then encrypted would definitely be the best option. If you're wanting to import them elsewhere, then having them encrypted will be problematic, as most other wallets will be unable to import the encrypted file. In fact, a lot of wallets will probably fail to import the unencrypted file as well as it isn't really in a "standard" format... as there aren't any standards!  But at least you're be able to open the file in a text editor and copy/paste the keys as required to import Some useful reading: https://multibit.org/help/v0.5/help_exportingPrivateKeys.htmlhttps://github.com/keepkey/multibit/wiki/Export%20and%20limited%20import%20of%20private%20keyspay close attention to the Development Notes which explains how to decrypt the encrypted file! |
|
|
|
That's a little tricky because you don't specify the "payout" when using scripts... you specify the "chance" and the site calculates the payout... and because sites have different house edge, the payouts and chances are not the same across all sites...  So, what you do is work out the "House Edge"... hopefully the site tells you what it is... then use that and the multiplier to work out what the chance is... also, figure out what the maxPayout number is for the site you're using and set that as well! -- UNTESTED!!
-- Set these 3 values to match the site you're using and what you want your baseBet to be
houseEdge = 0.8 -- ie HE = 0.8% = 0.8, HE = 1.1% = 1.1
maxPayout = 9920 -- set this to site max! 9920x = Crypto-Games.net
basebet = 0.00001000
---------------------- Don't Edit below here ;) --------------------------
basePayout = 1.1 -- start at 1.1x payout
firstLossPayout = 2
currPayout = basePayout
nextbet = basebet
chance = (100 - houseEdge) / currPayout
bethigh = true
function dobet()
if win then
--reset Payout to 1.1x
currPayout = basePayout
else
if currPayout == basePayout then
-- first loss
currPayout = firstLossPayout
else
currPayout = currPayout + 1
end
end
if currPayout > maxPayout then
stop()
nextbet = 0
else
chance = (100 - houseEdge) / currPayout
end
end
|
|
|
|
You need to send your coins to an address controlled by your TREZOR. If you have NOT received any coins since you last sync'd your bitcoin QT wallet... and you still have all the old blockchain data on your computer along with your wallet file... then you could effectively just setup the TREZOR, generate a receiving address and then create and sign a transaction offline that sends all your coins to that receiving address. You would then just need to transfer that signed raw transaction to an online computer and broadcast it to the network using one of these: https://coinb.in/#broadcasthttp://blockr.io/tx/pushhttps://live.blockcypher.com/btc/pushtx/https://btc.com/tools/tx/publishIf you have received coins or you no longer have the old blockchain data, then you either have to let Bitcoin Core sync up... will take a while and gobble up some 120+Gigs of diskspace... and then send your coins to your TREZOR. or You can dump out your private keys from Bitcoin-QT (dumpwallet or dumpprivkey) and then sweep them into an address that is controlled by your TREZOR using Electrum. If you need to dump out your private keys, then you'll want to do this either on an airgapped computer or a virtual machine with no networking etc... maybe even consider using a "live" distro like TailsOS or something with all the networking disabled. |
|
|
|
|
Simplest solution if you can't get Bitcoin Core to sync due to lack of available space is to run in "pruned" mode.
Just use the "-prune=<n>" commandline argument, where <n> = Amount of Megabytes you want to store on the harddrive... minimum is 550. So you can use: \path\to\bitcoin\bitcoin-qt -prune=550
This method won't expose your private keys, but will take time as it still needs to sync the whole blockchain.
Otherwise, it you just want your coins "now" and don't mind exposing private keys:
1. Download and install Electrum
2. Create a new Electrum wallet (make sure you back up the 12 word seed some place nice and safe offline)
3. Export the private key out of Bitcoin Core for the address that you sent the coins to (Help -> Debug Window -> Console. Use the "dumpprivkey" command)
4. Sweep the private key to Electrum
Electrum is an SPV (aka lightweight) wallet, so will "sync" in a matter of seconds.
You can also create a non-HD wallet in Electrum at step 2. if you use the option "use public or private keys". You can then enter your private key and have direct access to your coins, but you lose the advantages of having an HD wallet.
|
|
|
|
You realise you can just "edit" your previous post right? There is no need to create 3 posts in a row...  Do I run salvagewallet from the shortcut I created for Bitcoin Qt by opening properties then typing salvagewallet after exe leaving a space first, then hit apply and okay?.
I believe it should be: -salvagewallet So your shortcut should look like this:  If you managed to get the -salvagewallet option working OK and that is the output you're getting then it would seem that the wallet file that was recovered was totally corrupted... At this point maybe pywallet is likely to be your best option. |
|
|
|
|
Only if you still have the private key for the address that the 0.14 BTC is currently attached to.
In Bitcoin Core, if you goto "File -> Receiving Addresses"... do you see the btc address with the coins? Alternatively, if you use the "dumpprivkey" command from the debug console ("Help -> Debug Window -> Console")... does it output the private key for that address?
If it doesn't, then there is a chance that you no longer have that private key in your current wallet.dat file. Do you still have a copy of the original wallet.dat file backed up?
|
|
|
|
Again... I refer to what I said earlier: Adding on a passphrase (or even two) gives you the option to "hide" extra wallet(s) with your "real" stash of coins... As there is no evidence that you even have a passphrase (it's stored in your head right? and the mnemonic WILL generate a valid decoy wallet that shows some coins/history)... so even a relatively "short" but complex passphrase (10-12 chars with alphanumerics and symbols) should easily give you time to move your coins should you learn that your mnemonic has been compromised... assuming that the thief believes you even have a passphrase setup and are hiding coins.
How would these theoretical hackers even know you have a passphrase? Why would they continue looking after discovering the decoy 0.1 BTC in the "default" wallet (ie. mnemonic only, no passphrase)? Given that people use 10-12 character passphrases to encrypt wallet files... I don't see why using a 10-12 character passphrase to secure a mnemonic would be any less secure... especially given that any attacker cannot simply test that their generated passphrase "works"... it isn't a simple "boolean" check like testing username/password combinations... ANY passphrase entered in combination with a valid mnemonic will generate a valid master private key and valid keys/addresses... so they have to generate a master private key... generate a number of receive addresses AND change addresses... and check for balances. Maybe try playing with these: https://www.grc.com/haystack.htmhttps://apps.cygnius.net/passtest/ |
|
|
|
Are you double clicking on the btcrecover.py script to run it? If so, and you don't have a properly created btcrecover-tokens-auto.txt file, then the script won't run. How did you create the btcrecover-tokens-auto.txt and what commands did you put in that file? If it is just an empty file... then it won't work. Did you read this: https://github.com/gurnec/btcrecover/blob/master/TUTORIAL.md#command-line-options-inside-the-tokens-file ? So your btcrecover-tokens-auto.txt file needs to have commands and tokens in it like: #--wallet wallet.dat --autosave progress.sav --pause --otherCommandsHere
Your Lists of
Tokens
Go Here and
Here
Set "wallet.dat" to be whatever your wallet file is. |
|
|
|
That is really handy info! You saying those conversion tools can be used to convert Electrum priv keys? That would be easier then having your own Electrum full node server =) ... in the event Electrums server network goes down.
Yes. Assuming that by "Electrum priv keys" you mean the master private key that is generated by the "Mnemonic -> Seed -> xprv" conversion in Electrum. Once you have the "master" xprv, you can just put it into the BIP39 tool as described above and it will do most of the hard work for you... AFAIK no-one has, as yet, created a standalone Electrum Mnemonic converter... but I've had a quick look at the existing BIP39 tool code and compared it with the Electrum source code... it seems like it would be a relatively trivial task to modify it to accept Electrum Mnemonics so you wouldn't even need to use the "getmasterprivate()" command to get the xprv... you could just put in your 12 word seed (and/or custom words) and away you go. The only difference in "Mnemonic -> Seed -> xprv" conversion between Electrum and BIP39 is that Electrum uses a "default" passphrase of "electrum" instead of "mnemonic"... the other differences relate to the structure and checksum validation of the mnemonic, which would probably be just as trivial to implement, but aren't necessarily required if all you want is to convert the seed to addresses/keys. NOTE: I actually did a quick dirty mod on the BIP39 tool code to test it... I just forced the mnemonic checksum validation to always return true, changed the default passphrase from "mnemonic" to "electrum" and voilą... it will take an Electrum seed, you set BIP32 and path as m/0 (or m/1 for change addresses) and it spits out the correct addresses/private keys |
|
|
|
I think what you might be missing is that some of the big sites that "only" charge 20K-30K sats for withdraws... will do so in a "batch transaction". So, for example, you get 10 users all decide to withdraw in a given hour... you charge them all 20K sats... then you bundle up all their requests into one transaction and set the fee as required to try and achieve the confirmation time you require. This gives you 200K sats to play with as a "total" fee... but you can reduce your total transaction size by quite a bit... from 2260 bytes (~226 bytes * 10 transactions) down to as low as 532 bytes (1x 148 byte input + 11x 34 byte outputs + 10 byte fixed)... so instead of having 10 transactions with 88 sats/byte fees (20K / 226 bytes), you could have one transaction with 375 sats/byte fees (200K / 532)... or do what most of the sites do and set the fee to something lower say 200 sats/byte and pocket the rest as 'profit' without most of the users even noticing   As for the actual values you should be using for fees... those goal posts are constantly moving... right now, the number of unconfirmed transactions is averaging somewhere near 5K... last month it was like 150K!! Similiarly, with fees... now you can get transactions with fees of 0.00025 BTC/kB (25 sats/byte) confirmed in a couple of hours... last month you were lucky if 0.0025 BTC/kB (or 250 sats/Byte) would confirm in less than a day! |
|
|
|
The only other reasons for it that I can think of is that they're trying to artificially raise the amount of BTC they're "paying out" and/or the amount of BTC people are depositing by paying money to themselves... or it is some sort of arrangement where the pool claims a share of the "profit" or something? otherwise there is simply no point doing it... they're just wasting money on fees and making the unconfirmed transaction chain longer. |
|
|
|
It will probably be a lot longer than a few days... even with the fees and the number of unconfirmed transactions being a lot lower than last month. Sadly, you can't even use the ViaBTC TX Accelerator as you're below 10 sats/byte...  However, if you post the TXID I can try and accelerate it via another method. |
|
|
|
To be honest, with all the issues with MultiBit classic and MultiBit HD at the moment... and the complete lack of updates from the developers... leaving your coins in MultiBit is a bit of gamble regardless of whether or not there is a fork. Just check all the threads in this board with people having issues. The ONLY thing in their favour is that MB Classic supports exporting your private keys... so you'll be able to "rescue" your coins relatively easily... and MB HD uses BIP39 mnemonic from which you can somewhat easily derive your private keys (ie. by using https://iancoleman.github.io/bip39/)... Given that the devs have declared Classic is no longer supported, don't expect any updates for BIP148 ever... and given that MB HD has not been updated since March despite so major errors, don't expect an update for BIP148 any time soon |
|
|
|
You can verify that it belongs to that address... if you right click on the original "3" address in your 2FA wallet, you should be able to view the three public keys that belong to that "3" address. You can then generate the redeem script for this address by following the instructions here: https://bitcointalk.org/index.php?topic=1989369.msg19830190#msg19830190 (credit to Abdussamad for the Electrum console commands) Once you have the redeemscript, there are instructions for determining the "1" addresses here: https://bitcointalk.org/index.php?topic=1989369.msg19853098#msg19853098 (Basically, just do steps 2 and 3, you only need to do the other steps if people want a signed message) And finally, by using an offline copy of bitaddress.org (use the Github or zip download links at the bottom of the page and use in a VM or airgapped PC), you can input the two private keys you have generated and see if they match up with the addresses... or alternatively, you can just import those private keys into a new Non-HD Electrum wallet (select the "use public or private keys" option when creating a new "Standard wallet") and see if the "1" addresses match up with those from the redeemscript. |
|
|
|
|
If you mean specifically from Electrum for Android... there doesn't seem to be a way to access the private keys directly from the GUI. One method would be using your seed and importing it into the desktop version of Electrum. From there you will be able to easily get your private keys for your addresses.
|
|
|
|
|
Show Posts
