They would if they could, I'm glad the Bitcoin developers aren't really paying attention to them lol this is why I'm also accepting Litecoin just in case.
The Bitcoin developers aren't paying attention to them?
|
|
|
I'm pretty certain a very large amount of bitcoins have been lost. I'm sure many people played with bitcoin and then forgot about it in the early days, leaving their wallets to be abandoned forever.
Speculation. Well personally I know at least 4000 bitcoins were lost because that's the amount of bitcoins I have lost.
|
|
|
I don't generally offer escrow services, but my minimum about escrowed would be 100 BTC with a 1% fee.
|
|
|
Is this still going? I'd probably look into inputs.io and likely add it to my signature.
Yes.
|
|
|
Paid up to May 10th.
Why I did'nt get pay for the period June 10th - July 10th? Just sent (was up to).
|
|
|
ASICMINER is ordering 800 - 1000 TH of hashpower this year. Of course they are going to sell them for cheap.
|
|
|
Yeah if anyone falls for this scam you're a dumbass.
|
|
|
http://p2pfoundation.ning.com/forum/topics/bitcoin-open-source?commentId=2003008%3AComment%3A9493Could be. They're talking about the old Chaumian central mint stuff, but maybe only because that was the only thing available. Maybe they would be interested in going in a new direction.
A lot of people automatically dismiss e-currency as a lost cause because of all the companies that failed since the 1990's. I hope it's obvious it was only the centrally controlled nature of those systems that doomed them. I think this is the first time we're trying a decentralized, non-trust-based system. Read that and read Ripple.
|
|
|
I've said it before and I'll say it again, go fuck yourselves, you're nothing more than a wannabe Federal Reserve.
Yes, because the Bitcoin Foundation totally issues currency. Disclaimer: Inputs.io is a silver member.
|
|
|
Free private key to 0.1 BTC
|
|
|
Any specific reason why? Do you believe there is a security flaw in the later versions?
Nope, trying an experiment for curiosity Were you going "hmm if I run two wallets can I spend the same coinz twice!!"
|
|
|
- Get the transaction ID from blockchain, and write down the sending address. - Get the private key for this address from your account on blockchain. - Backup your wallet. - Delete the private key of the sending address from your blockchain account (else, it will continue spamming the network with this transaction). - Wait for a few hours (24 to be safe ?) until your TX has been forgotten on the network. - Reimport the private key on your blockchain account, balance should be back.
I'm not 100% sure it will work - still kinda learning.
But from what I understood, the unprocessed TX expire after a few hours, to avoid a possible spam attack of 0 fee TX. The client (blockchain) does try to resend it regularly, though.
So by taking out the private key from your account, blockchain should quit spamming this TX to the network, and when you reimport the key, the TX is completely forgotten, both by client and network.
Worth a try.
Would not work, blockchain stores the TX and will not let you spend it. You'll have to craft a raw transaction. Blockchain should not allow users to send fees unacceptable by the default fee policy. It just results in troubles like these.
|
|
|
It's not coded in the client, when you create a passphrase it appends a random salt at the end for it so that it will take on average 0.1 seconds to try and decrypt.
Example: your password is password.
Your computer can do 20,000 decryptions per second.
So your real password would be between password000 to password999. (So on average 0.1 seconds, because on average you're going to decrypt it halfway through).
When you decrypt, bitcoind tries all the keyspace which on average will take 0.1 seconds.
|
|
|
Except that Google Auth has nothing to do with Google's servers and you don't even need an internet connection to use it.
Have a link for that? I tried a bunch of searches looking for the technical details, but all I could find was ways to enable it on my gmail account and get SMS, so I assumed the worst. Google Auth is just a fancy name for this: function GoogleAuthenticatorCode(string secret) key := base32decode(secret) message := current Unix time ÷ 30 hash := HMAC-SHA1(key, message) offset := last nibble of hash truncatedHash := hash[offset..offset+3] //4 bytes starting at the offset Set the first bit of truncatedHash to zero //remove the most significant bit code := truncatedHash mod 1000000 pad code with 0 until length of code is 6 return code
|
|
|
You'll need to web scrap. Shouldn't be too hard, you can probably get by with file_get_contents and splitting strings
|
|
|
Doesn't seem down to me. theymos it was down for me too for about ~30 minutes or so. same error message as the post above. Yes, the forum was down.
|
|
|
I've adjusted the limits to make spamming more difficult. Activity | Min. seconds between post actions | Max PM recipients | PMs per hour | 0 | 360 | 3 | 5 | 16 | 74 | 5 | 30 | 30 | 60 | 5 | 60 | 60 | 30 | 5 | 60 | 100 | 12 | 10 | 120 | 200 | 10 | 15 | 120 | 300 | 8 | 20 | 120 |
This does not help much. They can use phished accounts to spam.
|
|
|
The first wallet you recommend is a referral link.
|
|
|
Are you aware that Bit bond was one of the the biggest scams in Bitcoin history?
It is like calling yourselves Bitcoin Savings and Trust
|
|
|
|