Why would Mark Karpeles need $245 million? Five days ago this was published: Mt. Gox Head Mark Karpeles May Gain Almost $1 Billion Despite Bankruptcy. I don't know how they got away with this. Apparently, instead of paying back with whatever was available in the bankrupt company, he waited a few years until the remaining Bitcoins were worth much more than he owed people. Basically, he got a loan in Bitcoins that he can pay back in dollars at the price it had in 2014!
|
|
|
so I think best practice is shrink HDD to 200gb for BTC db, then BTC will not write to middle of whole drive and decrease overall system performance.
Why do you think some fragmentation reduces your overall system performance? It only influences sequential reads, which is something you barely do, unless you're copying large files. If you create a separate partition on the same disk, the read arm of the hdd has to travel to that location anway, in those cases is can be faster if the data is all closer together. Your 200 GB partition will be filled soon anyway, after which you'll need to increase it again. If you really want to increase your system performance, install a SSD.
|
|
|
Both parties simply agree on a certain exchange rate, that's all.
Say you have 1 Bitcoin and I have 100 Litecoins, we agree to exchange them. We can do that right now, but one of us has to trust the other party, or we can involve a third party (escrow). Atomic swaps replace the trust-part, the exchange rate is still up to us.
|
|
|
You could send a message to https://walletrecoveryservices.com/, see if he can help you. If you have any idea what the password can be, he might be able to find the right combination. If you're really done trying, you can just upload the wallet to a public location, post the link here, and whoever cracks it first "wins"! It will all depend on your password though, if it's strong enough, it's not worth the electricity you need to crack it.
|
|
|
Maybe it's the fact that the fraction of people who would have had those coins are no longer participating in the market as sellers that really influences that supply vs. demand equation. Correct. Less accessible Bitcoins lead to a lower market supply. Estimates go up to a few million Bitcoins that have been lost, such as this hard drive holding 7500 Bitcoin. If he wouldn't have lost it, he would for sure have sold at least part of it by now, to live a life in luxory.
|
|
|
Stop spamming the forum for Activity! I just reported a couple of your posts, expect to see it drop more.
|
|
|
Every lost Bitcoin reduces the number of Bitcoins in circulation. The scarcer it gets, the higher the value per Bitcoin. So in a way every Bitcoin owner benefits from this.
|
|
|
This doesn't work with Tor, if it worked then Tor wouldn't be anonymous.
Tor switches IP automatically each time, also Tor does not save anything including cookies, everything that happens in the Tor Browser windows is kept on the RAM so there is nothing persistent. You can save bookmarks on the browser but that's about it. There is no browser history to save because Tor doesn't save anything by design.
Even in Tor Browser you can set your preferences to remember history and accept cookies. This doesn't tell Bitcointalk anything about you, so you're still anonymous. A man in the middle attack is also not possible. If you make this your default settings in your Tor browser, it should work to stay logged in. You're probably right that it compromises your privacy somewhat, but I don't know how to rate that risk. A simple solution to still have the full privacy when needed would be to use Tor in private browsing mode for sites other than Bitcointalk.
|
|
|
Is it possible to link the report to moderator button to a mod-only subforum where we can write decent posts to report someone. You can create a thread right here in Meta, like this. I find it hard to write or link every spampost a user has written in that 1x1 box That box is meant to report just one post, although I sometimes say "please check his post history". Yes we can place it in the meta section and link it there, but with so many posts everyday i think this suggestion would make it easier for the mods to get rid of every report 1 by 1. If you write long stories in the report-box, it will be more work for Mods. If you have many different posts from one user to report, you can report them one by one. Just a short description is enough.
|
|
|
I have the client / wallet called "Bitcoin" version 0.3.20.2 BETA. It is a wallet and mines as well using CPU. I didn't forget I had the wallet, I've been keeping my eye on it and had it backed up in 3 locations, but I never tested it on a different computer. I would open the wallet occasionally and see everything still there. Apparently backing up "mykey.txt" and the application and all its data wasn't enough and "mykey.txt" is a public address I'm finding out now. I can see my coins but the wallet.dat file you mention is not here. I just did a search and it's located in /roaming/bitcoin/wallet.dat Arg, thinking of it now because of the price. My backups are useless and I just formatted my computer 2 weeks ago. Looks like I'll be doing some unerasing to try to find that wallet.dat file. Thanks, but my easily mined free coins are most likely lost forever at this point.
You should stop using your old computer immediately: every write action to the disk reduces the chance of recovering your wallet.dat. Plug the disk into another computer, clone it, and use data recovery from there. Good luck!
|
|
|
I do not consider SSD as safe when it comes to storing sensitive data (such as your wallet.dat) since in the event that you needed to wipe it out, you couldn't, that I know off. In classic HDD drives, you could delete it easily. An easy way to wipe it, is simply remove it and then fill the disk with other data. Just copy your music collection until the disk is full, then remove it again. So my idea was to try to make Bitcoin Core run faster by allocating chainstate files in an SSD, then store wallet.dat and blockchain files in an external HDD. I have an SSD and HDD in my laptop. My wallet.dat used to be in my home directory, the rest of the Bitcoin Core data is on the hdd. Since the 0.15-upgrade though, Bitcoin Core doesn't allow the wallet.dat to be symlinked outside it's data directory. I haven't tried to symlink the chainstate yet, if it improves speed I'll go that way. And you just gave me the idea to symlink the blocks-directory, so I can have my data-directory and wallet on my SSD again. Normally, a program just follows any symlink the file system shows. I disagree with the way Bitcoin Core rejects a symlinked wallet.dat. (im not sure how fast it will be with this method, but I heard that the important files to have in the SSD are the chainstate files Normally, I just keep it running, but when it starts, it takes a while indeed. It does make sense faster access to chainstate can improve that. I wouldn't be so happy storing it on a USB disk though, that risks unplugging and corrupting your data. Test resultschainstate on hddWhen starting, "Verifying blocks" takes a long time. Total time to start Bitcoin Core 0.15.1, and close it directly after popping up: 1m20.391s. chainstate on ssdWhen starting, "Verifying blocks" is much faster. Total time to start Bitcoin Core 0.15.1, and close it directly after popping up: 0m22.246s. For testing, I made sure my file cache was empty. All data has to come from disk while loading Bitcoin Core. I'd say you're on to something It's much faster, and as a bonus I can have my wallets on my ssd again. Thanks for giving me the idea! The only drawback is that the chainstate directory performs many write actions, adding to the wear level of my SSD. Basically, from your perspective, I did this: cd ~/.bitcoin # my home directory is on the ssd mv blocks/ /media/hdd/bitcoin/ ln -s /media/hdd/bitcoin/blocks blocks You want to move your chainstate, so use some variation to this: In ~/.config/Bitcoin/Bitcoin-Qt.conf , edit the location of your bitcoin data directory to point it at your USB-disk strDataDir=/media/usd-disk/bitcoin You'll need to format the usb disk with a Linux file system to deny other users access to that directory. mkdir /home/directory-on-ssd/bitcoin mv chainstate/ /home/directory-on-ssd/bitcoin/ ln -s /home/directory-on-ssd/bitcoin/chainstate chainstate
|
|
|
I have the old Bitcoin client 0.3.20.2 BETA It was all backed up and I ran the program on my new computer but the bitcoin address is different. There doesn't appear to be a way to manually change it back to the old one. Which program did you run on your new computer? I assume you have an old wallet.dat, which would load in a modern Bitcoin Core. This will take a long time to download 150 GB, but it will quite quickly show your transactions from 2011. If your wallet.dat still works, this is the way to go. There are other possibilities (extract private keys for example), but without more information about what files and software you're using that's just guessing. There is a file that is called mykey.txt and I tried to transfer it to a new wallet and it shows my bitcoins but it is "watch only" and requires the private key. I thought that WAS the private key. How do I get the private key from this old client on my new computer?
If your mykey.txt doesn't hold private keys, your only chance is your wallet. Start searching there. In 2011 Bitcoin was worth $1 to $10, if you find a few in your wallet you're looking at $7700 each. What made you forget you had that wallet all these years?
|
|
|
Warning, sent some coins yesterday. (above 0.001) Woke up today to see them confirmed both on the transaction log and also on the mixer, however chipmixer says "all chips withdrawn" This happens sometimes, it's an unfortunate side effect of the unique way ChipMixer works. Chips are prepared before you deposit, and sometimes all chips are withdrawn due to popularity. New chips will be funded soon. I'm unable to export to electrum all i get is a blank output field where the keys are supposed to be..
I assume you got a voucher code, right? Just safe the voucher code and try back later. Sent an email to support, but i assume my coins are lost. I know how it feels to not be able to withdraw your funds (it feels bad!), but in this case I wouldn't worry about it. Your funds are not lost.
|
|
|
I'm tempted to do this, 5% interest on my Bitcoins sounds very nice. But it seems very shady too. I guess you can't post what message you want to be signed? if you're not okay with my offer just walk away, im not here to give you details about any of my plans. it's like going to a job interview with no diploma and asking them if they deserve you. i expect you to start hating after this message but at least i was honest with you, walk away. Hating? Didn't I say "I'm tempted to do this"? I'm just curious what I'm getting in to, and before anyone can sign any message, you'll have to tell him what message he'll have to sign anyway.I did misinterpret the part about signing a message, you want to have the wallet itself. Would a private key be enough, or do you want any specific HD-wallet? As for the diploma part: I'm qualified for this job, asking questions in a job interview is normal. I can't imagine you'll pay 5 BTC when someone moves 100 BTC back and forth though, so how much are yoou looking for?
|
|
|
but to make it clear, i need to claim that i own x ammount of bitcoins to join a 'certain group'. that's it
So the message won't be "Dear IRS, Trance104 owns this address filled with legit money"? Shady at best to be honest. He could use it to lure people into whatever he tells them because he has some signed message having that much btc on the address. Who falls for that? I can't think of a single way where a signature from an empty address adds credibility, and if someone shows many different signatures from many different emptied addresses he has no credibility left. sign a message then send back your money to your original wallet and sell me the wallet after that If whatever you're planning to do accepts this, why don't they just ask you to sign from the original wallet? I'm tempted to do this, 5% interest on my Bitcoins sounds very nice. But it seems very shady too. I guess you can't post what message you want to be signed? Addition: I just noticed you didn't post for 3.5 years before you opened this thread.
|
|
|
Is there any solution to this in just a regular browser? If it's your own PC, you can tick the " Always stay logged in:" box. I can't remember the last time I had to login, that's how long it has been. I don't use Tor so can't test it, but can't you just tick this box to remember your login? Unless you want to erase your browser history after every session, this should stop the captcha login.
|
|
|
If only people would stop competing to pay the maximum fee, fees wouldn't be so high! https://btc.com/stats/unconfirmed-tx now says 150 Satoshis/byte is enough to be included in the next block. The moment blocks are full, this jumps to 400, and then quickly continues to 600. Last weekend, it reached more than 1000! The problem here is: no matter how much you pay, blocks are still full! I only use a high fee if I'm in a rush, yesterday I made a transaction with less than 30 Satoshis/byte, it took 12 hours to confirm. If you let your wallet set the "best" fee (and most wallets do this by default now!), fees can spiral upwards very quickly. Set your own fee to stay in charge.
|
|
|
When I try to register for the airdrop, I get this error: Error: BTX public key or signed message not valid
I've had this before in the past, back then it was a server side problem with certain adresses if I recall correctly. I'm signing from an uncompressed address.
(I already asked this question a few days ago, but the thread is going so fast it got lost many pages back)
Do you sign it correct with the singning-msg created with the Bitcore wallet? I signed it correctly with Electrum. BitCore doesn't have it's own message signing convention, does it? I assumed it's still compatible with Bitcoin signatures.
|
|
|
When I try to register for the airdrop, I get this error: Error: BTX public key or signed message not valid
I've had this before in the past, back then it was a server side problem with certain adresses if I recall correctly. I'm signing from an uncompressed address.
(I already asked this question a few days ago, but the thread is going so fast it got lost many pages back)
|
|
|
|