Here are the hash numbers in question:
021de0a9529da8cf4ec05d445bc1906efcf224d589cedfd330d883ae41e3695c
dcbcbbcb963960262589ccca393c39fa5f5456ecf3870896cc8ecc37c119773e
e252d4ec5cb5527de56abbcdfab577a5d59fa37cf92f70e40a460f56d2d9e863
Those transactions have been removed/double spent. This means these TX's won't go through -> you won't receive them. It was either a mistake by the vendor, or he did this on purpose and scammed you. You should definetly contact him and show him the ID's. He can't deny that you never received those coins. Where did you buy them? Did you buy them from a 'private' person? |
|
|
|
i unfortunatley deleted the wallet.dat file but i found it in my recycle bin..
Do you have a backup of your wallet.dat? Usually files don't get corrupted when moving them into the recycle bin, but in windows you can't be sure. i need to replace the wallet dat but i cant do it can someone with a little knowledge please help me try understand how i can replace my wallet dat
You need to place the wallet.dat into the data directory of core. To open the directory you can do the following (assuming you are on windows): - Press WinKey + R (Run command)
- Type: %APPDATA%\Bitcoin
- Press Enter
The right folder should open automatically. Backup your wallet.dat which is in the datadir (rename it) and move your recovered wallet.dat into the folder. The standard path of the datadir is: C:\Users\YourUserName\Appdata\Roaming\Bitcoin |
|
|
|
2. I had done the conversion from MultibitHD to Electrum on my prior mac some months ago; I then assumed that from that moment on it was now an Electrum wallet, but apparently it still behaves as an old MultibitHD wallet (?).
Basically you imported your multibitHD seed into electrum. Now the point is: MultibitHD and Electrum derive the private keys differently from the seed. Look at it like mathematical equations. MultibitHD and Electrum are "calculating different things" to get your private keys. With the derivation path you tell the program how exactly to derive the addresses from the private keys. That led to your wallet in electrum generating different private keys than MultibitHD had. The derivation path is composed like this: m / purpose' / coin_type' / account' / change / address_index
But electrum, somehow, uses its own derivation path.. ignoring the BIP44 specification. To be fair, quite a few wallets ignore those specifications. Bitcoins derivation path should be (according to BIP44): Electrum uses m/0'/<n>. |
|
|
|
As previously mentioned, btcrecover would be the way to go. But you have to remember at least something from your password. I want to add something very important which hasn't been mentioned in this thread yet: Do NOT give your wallet file or any other sensitive information to random people posting here / PMing you.For example, this one is spamming his 'recovery service' in every thread regarding lost passwords, even if those threads are 2 years old: A newbie, who 'offers to help' with retreiving passwords is not trustworthy at all: In the later case, let me know if you need help with this.
Those are 2 examples of untrustworthy 'offers'. 90%+ of PM's you will receive from people 'ready to help you are scam. Don't fall for them. |
|
|
|
Will a chromebook work for a hardware wallet?
No, not really. You could, if you try hard enough, reach a state where your chromebook 'basically' matches a hardware wallet. But this would you require to have it airgapped all the time. It won't be enough to just turn wlan off. You have to be sure there is nothing communicating anymore. You need to either turn off wlan/bluetooth/nfc system-wide (which is not too hard on linux) or just remove those modules completely. In the end it still won't be a 'true' hardware wallet because you won't be able to easily spend them anywhere. Its an offline airgapped storage (which is good!), but the usability is kinda bad. But if you do everything right there isn't much more you can do to secure your coins. I might suggest to install another OS. Maybe switch to ubuntu (or some other userfriendly linux). And make sure to not use this laptop for anything else than for storage (only). |
|
|
|
Yes, right. I had wipe my memory. But after that i never use this phone. So i think it is the chance.
There is definetely a chance. Files aren't completely removed from the storage until they are overwritten by new files. Its just very important that you make a correct image of your phone. So you can try to recover those files on an image without hurting the storage of your phone. You should make sure that your mobile won't be auto-updating any applications or whatsoever. Just turn it on, activae USB-debugging, make an image, copy that image and load this image into your recovery software. Chances are pretty high you will be successfull. The wallet/app was stored on your internal storage, right? |
|
|
|
|
There has been a soft fork which 'basically' increased the block size 4x.
But the majority of people didn't make use of this soft fork yet.. SegWit.
If exchanges/online wallets and the majority of users would switch over to segwit, the fees would be clearly lower.
The network was congested 2 months ago, but currently 50 sat/B are enough to get your TX confirmed within the next block and 20 sat/B are enough for the next 3 blocks.
Additional segwit usage could decrease the fees even more to < 10-15 sat/B (since more transactions would fit into a block).
In addition to that the Lightning network is being explored and tested at the moment. Once it will get ready (and will get a big userbase) you won't have to pay fees for every transaction anymore.
|
|
|
|
Could you just “export wallet” and specify [wallet.dat] location to desired location? If possible..
Thats not an option for OP currently. - His display is broken
- He has wiped his memory (factory reset)
He made a backup in terms of copying his files from his mobile over to his PC. His only options seems to be to create an image of his mobile and try to recover those deleted files. |
|
|
|
Created wallet from existing seed, so far so good.
But the interface of the wallet has a green dot on network, while showing no transactions in the history and a zero balance of bitcoins.
Did your existing seed have been created by electrum? If not, the problem is probably the wrong derivation path. Electrum uses m/0/n for receiving addresses and m/1/n for change addresses. Depending on which wallet you have used prior to electrum you might change the derivation path when restoring from the seed. You could also try to create a bunch of new addresses and see if those which contain your balance will appear. Use the following command: for x in range(0, 100):
print wallet.create_new_address(False)
|
|
|
|
Hmm kinda strange , how algorithms are going to find that it was exactly me who traded alts.
apparently you don't know a lot about algorithms. You need to look into it's fascinating You can code a few nice algorithms, yes. But its not that easy to just track every user trading on multiple exchanges. Without (inside) information directly from the exchanges, you won't be able to track users exchange behaviour. In the end you still have to program that algorithm.. And there is no fully functional way of tracking users like you are describing. |
|
|
|
|
This really depends on what your 'goal' is which you want to achieve with crypto.
If you are a daytrader there isn't much you can do on flat days.. try to ride the small waves which appear.
As a holder (when the fundamentals didn't change) just hold tight. In the end it will pay out.
Especially with LN being tested and Schnorr in (hopefully) near future, holding is the best option IMO.
Trading is fine, but in the end you should always be holding your stack tight.
|
|
|
|
I have several wallet.dat files from bitcoin core.
I want to export all the privkeys of all those wallets.
Then import them all into 1 single wallet.dat.
You can use pywallet[1] to dump your private keys without opening the wallet in core. The command would be the following: ./pywallet --dumpwallet --walletfile=YOUR_WALLET_FILE
You would have to run this command for every wallet seperately. But if you have quite a lot of wallet files, you could write a simple script (3 liner) to do this automatically for each wallet. [1] https://github.com/jackjack-jj/pywallet |
|
|
|
For a bitcoin wallet you can choose between several types of wallets: 1) Desktop wallet 1.1) Full node (bitcoin core [1]) 1.2) Lightweight wallet (e.g. electrum [2]) 2) Mobile wallet (e.g. Mycelium) 3) Hardware wallet (e.g. ledger, trezor) 4) Paper wallet Paper- and Hardware wallets are the safest options, since your private keys won't ever leave a safe "environment". A paperwallet is basically for free, but can be quite demanding when using the first time. Where a hardware wallet is easy to use, but costs a few bucks (50$+). Mobile and desktop wallets are roughly equally safe (You shouldn't store big amounts on them). A fullnode wallet (BTC Core) downloads and processes the whole blockchain (150GB+). A lightweight wallet does not need to download the whole blockchain. It uses an online service to communicate with a fullnode to get the current balance of all of your addresses. [1] https://bitcoin.org/en/download[2] https://electrum.org/#home |
|
|
|
You can send from P2SH segwit or bech32/bc1 addresses now. It's sending to segwit addresses from non-upgraded exchanges that's the issue.
Thats basically exactly what i've said. But since they are updating to segwit, does this mean that even if they use the P2SH I will be able to make transfer to them if I use the bech32 addresses from electrum?
You will always be able to send to any address from your bech32-type-address. You will also always be able to receive funds to your bech32 address. There only a problem occurs when you have to enter your btc-address anywhere to receive funds. Most websites/wallets hasn't been updated to regard bc1.. addresses as bitcoin addresses. Network-wise everything is fine. Its just the websites/wallets software which needs an update. |
|
|
|
If one private key and diffirent address. Can it possible?
Actually its the other way around. A private keys (ECDSA) has 256 bit -> 2^256 possible private keys. An "address" is a 160 bit long hash -> 2^160 possible addresses. So on average there are 2^96 (256-160) private keys which correspond to one address. Sounds like a lot. But nothing someone should be concerned about. |
|
|
|
It's only the bc1 addresses that won't work backwards compatibly, and that's kind of irrelevant seeing as there aren't many wallets that use bc1 addresses.
Best advice is to use nested 3-starting addresses for Segwit now, because they're completely backwards compatible for all services and wallets. So there's no need to wait for others to wait to update, you can use Segwit now backwards compatibly.
You seem to confuse the meaning of backwards compatibility. Bech32 addresses are backwards compatible. This means: - Transactions between legacy and bech32 addresses are compatible. - "Old" nodes do "understand" those transactions from/to bech32 addresses - There aren't any (network-)problems with bech32. Wallets/Exchanges/Online service provider not accepting bech32 yet is due to not upgraded software (non-network related). This has nothing to do with backwards compatibility. They just didn't update the software to accept those addresses. |
|
|
|
Just wonder that the work of finding a new block(mining) is it kind of decrypting these algorithm?
The work which has to be done to find a new block is not directly dependend on the algorithm. Additionally you can't decrypt anything in this scenario. Encryption != Hashing [1] Hashing is a one-way-function. This means: You can (relatively) easy calculate a hash of any value. But you can't get the original value out of the hash. When you are trying to find a new block (mining) you are basically calculating hashes until you find one hash that (for example) begins with 10 zeros. The difficulty adjusts to assure a new block every 10 minutes. You can look at the difficulty as "X zeros have to be at the beginning of the hash". On average there has to be Y hashes calculated until a valid one is found. Thats basically a "probability-game". [1] A more detailed explanation: https://en.wikipedia.org/wiki/Hash_function |
|
|
|
Some interesting facts: - Average participant has earned 28.7 merit - The total amount of earned merit is 1666 merit (at the time of this post - merit counts for most users should automatically update) LoyceV's vanity kinda applies here- Members in the campaign have received 2.7% of all merit given on the forum  (1666/61278) - 44 members have reached 10 or more merit earned - Range: 0 to 138 Just thought it was interesting, not doing anything else with it yet. Maybe one fact to add (since median is more meaningful when there is such a big range of values): 2.7% of all merits from only 58 campaign participants? Out of 1808548 total members!??!
Awesome!  |
|
|
|
I do not understand why you repeat what you wrote before? hutchdavidson wrote : Tried other usb cable, tried 3different computers at 3 different locations. Only thing i havent tried is a mac and i guess i will try that but i just dont think that will be the one thing that works after all this.
So i have 3 faulty ledgers now. How many do i have to buy... this is so ridiculous So I give him instruction how to try step by step one more time with Electrum as just user interface,and last solution is to import seed in any other wallet since this is only way to gain access to his coins. I repeated that because it seemed like noone is taking this serious. The chances of receiving 3 broken ledgers.. are like.. almost zero ? I can't really believe he ordered 3 ledgers, tried them at 3 different computers at 3 different locations.. and nothing worked. Either some firewall is blocking a connection to the ledger server (which i doubt, because it at least should get recognized by the application) or he is on some broken OS or its simply his own fault because of wrong usage. Another option of trying to access the nano s would be to pair it with MyCelium. Thats still by far better than importing the seed into a desktop wallet. If he use legit Electrum wallet on clean PC then his coins will be safe until he get some new hardware wallet of fix problem with Ledger.
This is true.. but thats a big IF. One shouldn't simply regard his PC as clean. Thats the mistake which leads to loss of funds in most cases. |
|
|
|
And it constantly crashed with fatal error after the 323 wallet in the stage "load wallet.." (although all of them are first verified ok) At this point the memory usage is about ~750 MB I have enough available memory. debug.log 2018-02-11 14:23:56 init message: Loading wallet...
2018-02-11 14:23:56 nFileVersion = 150100
2018-02-11 14:23:56 Keys: 2002 plaintext, 0 encrypted, 2002 w/ metadata, 2002 total
2018-02-11 14:23:56 wallet 47ms
2018-02-11 14:23:56 setKeyPool.size() = 2000
2018-02-11 14:23:56 mapWallet.size() = 0
2018-02-11 14:23:56 mapAddressBook.size() = 1
2018-02-11 14:23:56 init message: Loading wallet...
2018-02-11 14:23:56
************************
EXCEPTION: St13runtime_error
CDB: Error 12, can't open database wallet-333.dat
D:\Bitcoin\bitcoin-qt.exe in Runaway exception Runaway exception might be caused because the wallet you try to open (wallet-333.dat) is not a HD wallet? Are you able to open this wallet.dat individually? If not, you may try to start core with this command: -usehd=0Does the same issue also appear when replacing this wallet file with another (working) one? Or does it always crash after 323 loaded wallets? |
|
|
|
|
Show Posts
