Well the site says: There are no fees, except the recommended 0.0001 BTC transaction fee for the miners. Do they pay fees when sending from their Bitcoin to the recipient or back to you? Probably not, 0 confirmation land... I thought I'd try it out for science. The site doesn't work right if you are blocking cross-site requests. Damn right. I don't do web bugs from just about every Google beacon there is, twitter, facebook, reddit, viglink.com ("make money with ordinary links"), etc. Without the off-site Ajax scripts, the submission appears to work, but no emails come. Ok, so we enable some scripts and fill out the form: And what do we get? So no go. Needs encrypted transport? Of course a simple email address typo will send the bitcoins to the wrong person too. BTW, the email addresses shown above are also disposable: https://bitcointalk.org/index.php?topic=84024.0
|
|
|
The forum user accounts and passwords have not been widely reported to be compromised in a way consistent with employment of a forum data breach, I would look elsewhere for the source. Can you tell from logs if they actually had your password?
|
|
|
Bitcoin is money. Knowing about money doesn't equal profit, and neither does just about any investment in mining you could make these days. That ship has sailed.
The most profitable thing you can do if you have loans is pay them off, highest interest rate first.
|
|
|
Have you checked the usual places, spam box, tried another email account, etc. They do seem to be answering support tickets in a timely fashion if you inquire directly.
|
|
|
I don't agree. btc is not money. Not unless my government accepts (tax)payments in btc it isn't. (snip)
Also, some of the btc I spent came from Satoshidice, which is a game of chance. Dutch law dictates you have to pay (income-) taxes over the net amount gained (wins minus losses) to retrace this (as a third party) is a next to impossible task. (to prove) No questions about tax can be answered in an informed manner without knowing your jurisdiction. In the US, both federal and state laws would apply, and the primary issue would be income tax. To pay income tax, you need income. Casinos in the US report your winnings directly to the IRS if over a certain amount, but few individuals self-report their smaller winnings. In fact most gamblers would have losses greater than their wins - to claim that you are a gambling loser for the year would require you keeping your own records that an IRS auditor would believe though. You can take a clue what the tax man expects from what happens when you win $100 cash on the blackjack table or a lottery scratch-off, vs win the big lottery jackpot. The gubmint would probably like you to pay sales tax on everything you buy off Craigslist or barter in exchange too. When businesses sell locally on the internet in the US, state sales tax laws apply. If government doesn't take bitcoins for taxes, how do they take 8% of the purchase price in bitcoins from a business, and what if the price of Bitcoin is 500% higher at the end of the year? Estate tax? My heirs get a private key, they send what to the government? The best way is typically to think of all of your bitcoin contact as a "sole proprietorship", taxable income only when you earn government currency gains. Your tax accountant would be the one to talk to, not bitcointalk.
|
|
|
Newer versions of Bitcoin are more highly optimized; they use a new database format and only fully verify recent transactions that have happened after a trusted "checkpoint" block. Your version also has old payment and fee rules and some security issues. Update.
The wallet.dat stores the keys for sending your bitcoins to other people. As long as you have a copy of your wallet, the bitcoins are yours. It can be backed up using the "backup wallet" feature in the client's file menu at any time, or the wallet.dat file copied directly after Bitcoin is completely closed (no tray icon or background processing).
To send a payment, your copy of bitcoin-qt also needs to be current and reflect the correct balance by having downloaded a full copy of the blockchain. The blockchain is the record of all payments made on the network, the public ledger that lets your client know how much is in every Bitcoin address and identify valid payments to you. This takes time as you have discovered if you have fallen significantly behind; the last 35,000 blocks is a few gigabytes to download.
Your bitcoin balance in your wallet may be stored in many addresses within the wallet, some not presented to you in the user interface. It is possible to export keys or use other services to spend your money, but I would recommend sticking with bitcoin-qt if you have a desktop pc and a high-speed internet connection.
|
|
|
It will not be cold storage, as in "private key is secure, by never being written to a computer system storage device and by being generated on a non-internet-accessible computer". Cold storage is a phrase used for the securest of offline Bitcoin addresses, stored as a private key or paper wallet, that are created in a way that the stored copy(s) of the address are the only ones that have ever been recorded. A simple way to make your own is to boot off a non-persistent live CD with the ethernet cable unplugged, and run a copy of vanitygen to generate a simple phrase address (use a seed file with a couple minutes of keyboard pounding in it). Write down the resulting address/private key on paper, or dump 100 copies of it to your USB stick. Alternately, use a saved copy of the bitaddress web page to generate your address: https://github.com/pointbiz/bitaddress.orgWhat you are creating instead is a wallet backup. If someone steals or has already stolen your wallet.dat now or in the future, they would be able to spend coins received by the wallet in the past, present, or future, even money you send to "new" addresses. Address information could be recovered off a hard drive, even if the wallet file is deleted or the drive is repartitioned or reformatted insecurely. If you plan on making a long-term backup, for the purpose of safeguard against data loss, after encrypting with a passphrase, you might consider starting Bitcoin once with a large keypool option such as bitcoin-qt -keypool=2000. This will fill the wallet with future keys that will keep your backup from becoming obsolete for a long time.
|
|
|
The headline should be: Some sucker paid Butterfly Labs money. A million dollars worth of Bitcoin money. Bitcoins they will never see again (if not for shady BFL, for the impossible ROI).
BitPay, the world’s largest payment processor for virtual currencies, announces that it has processed its largest bitcoin merchant transaction ever, a single order for $1,000,000 for Kansas City-based bitcoin mining hardware manufacturer Butterfly Labs.
|
|
|
This library seems to have no problem putting invalid private keys through math without validation: >>> pybitcointools.privtopub('0000000000000000000000000000000000000000000000000000000000000000') '0400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000' >>> pybitcointools.privtopub('ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffee') '04d3c3c891a4e05e520b01928b19cf7b56b7debc725dd915a42763a6c94bcdce54e171bf8daa5328e7ef955a8d60a9e72cc6fe5ac918eac04134d692a34654c6c4' >>> pybitcointools.get_privkey_format('ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffee') 'hex'
|
|
|
Several windows patches have been released over the years regarding daylight savings time rule changes also, make sure your PC is fully updated including "optional" patches.
|
|
|
I don't know that it's ever been done, but you could ask for a testnet alert to be set by a core dev if you are a client developer that wants to implement user presentation properly.
|
|
|
This seems to be a common theme with the OSX client, developers think they've fixed it, and problems keep coming back. It could be that a high percentage of Macs can't do math right, but more likely there is some leveldb database problem on Mac that really can't be fixed without the upstream library bug being identified and fixed.
|
|
|
bitcoind does not need any command line options; it runs as a daemon. I'll just quote the wikipedia definition of daemon for you: - a daemon (/ˈdeɪmən/ or /ˈdiːmən/)[1] is a computer program that runs as a background process, rather than being under the direct control of an interactive user.
What you can do is start the daemon, and then in a second window, issue RPC commands to the server: bitcoind getblockcount Returns the number of blocks in the longest block chain. bitcoind getbalance Returns the server’s total available balance. bitcoind sendtoaddress <bitcoinaddress> <amount> [comment] [comment-to] <amount> is a real and is rounded to the nearest 0.00000001 and then to stop the daemon without completely corrupting your wallet: bitcoind stop
|
|
|
This is one of few ways to be bit-rich, find your bitcoins after forgetting them. It would be nice if I found my Bitcoins now (or in five years) instead of selling at $2 or $15 or $50.
|
|
|
error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
There are log files that must not be touched in the database subdirectory. Put them back. Back up wallet.dat. You especially should not be modifying anything in that directory if Bitcoin is running; it can continue to run for a minute after you close it and the UI is gone.
You can rebuild your wallet.dat if this file is present but you were unable to restore other files. Bitcoin-qt -salvagewallet
We hope you didn't remove the file wallet.dat from the directory of course - if you deleted that and have no backup, any bitcoins you had in your wallet are GONE along with use of any addresses you had.
|
|
|
It's easy to pick holes in other peoples work especially when you just put on the grammar Nazi hat. I'd like to see one of your pieces of work.
I personally don't mind a good spell checker. If I ever want to update my thesis PDF I will have all the typos and mistakes in one place for easy reference . You are replying to someone who is criticizing a year-old post.
|
|
|
|