|
1581
|
Other / Beginners & Help / Re: Bitcoin rebrand
|
on: February 22, 2013, 01:35:42 PM
|
Okay, that's enough pink! I was going to re-make the OP's post from memory, but since I didn't have a font like that one (fat sans, dots of letter i above ascender line), I started to do some typography. Then I decided to do my own logo font treatment, and then put it all together in a way that's not a big departure from previous looks. It's also the plain white icon style of windows 8/windows phone.  |
|
|
|
|
1587
|
Bitcoin / Development & Technical Discussion / Re: What is stored in the wallet.dat file?
|
on: February 20, 2013, 10:48:25 PM
|
|
1. The wallet can be encrypted, you must know how to recognize this and properly decrypt and reencrypt data,
2. Examine the code of pywallet, and run pywallet to do a wallet dump to get an idea what data is stored,
3. Understand what you are doing 110%, there's stuff in there like reserve keys, transactions, address book, etc.
|
|
|
|
|
1588
|
Bitcoin / Bitcoin Discussion / Re: Bitcoin-Qt / bitcoind version 0.8.0 released
|
on: February 20, 2013, 10:35:32 PM
|
Wow, so my datadir went from ~7GB to ~13.5GB.
Is there any of this that is deprecated and can be pruned? I regularly backup the entire datadir and having it double in size in one day as opposed to over a couple of years is kind of harsh.
You can remove blk0001.dat, blk0002.dat, blk0003.dat and blkindex.dat from the data directory after a reindex is complete and you are caught up with the blockchain (and you don't plan on going back to an older version). Only blkindex should actually be using disk space, as the old BLK000x data are moved upon upgrade, and the blk000x.dat files you see there are hardlinks (shortcuts) on any filesystem that supports hardlinking. |
|
|
|
|
1589
|
Bitcoin / Bitcoin Discussion / Re: [ANN] Bitcoin blockchain data torrent
|
on: February 20, 2013, 10:09:02 PM
|
If I already have some block data and want to replace them with this, do I need to delete my blk*.dat files? How about the blocks or chainstate directory?
This is not a replacement for block data you already have. This is a separate file, that is only used once, during data import. After data import, the file is renamed to bootstrap.dat.old, and never touched again. Most will want to manually delete it, after use. More specifically answering the question, if your Bitcoin client is already close to block 216116 (January 11) or even halfway completed (block 190000), the bootstrap.dat likely won't be of much use to you. It may take more time to download and then import the torrent than to complete the blockchain synchronization normally. This torrent is also only for those using the v0.8.0 release or after, as 0.7.1-0.7.2 are not able to import more than 2.0GiB of the 4.7GiB file. You can use the bootstrap.dat torrent with no ill effects regardless of your current block. When you restart and Bitcoin sees the bootstrap.dat that you have dropped in it's data directory, any block hashes you already have will be skipped quickly, and the import will pick up at the blocks you don't have. |
|
|
|
|
1591
|
Bitcoin / Project Development / Re: Developers - Best practises for decimal handling
|
on: February 20, 2013, 01:28:44 AM
|
|
Your site may need more integer math accuracy than 1 satoshi = 1
example: 1 satoshi - 1.3% fee = .987 satoshis
>>> print int(.987)
0
>>> print int(round(.987))
1
However, even using arbitrary precision, these libraries don't necessary give you the correct answer anywhere near the magnitude of the float precision defined.
>>> getcontext().prec = 6
>>> Decimal (.00000001) * Decimal (.987)
Decimal('9.87000E-9')
>>>getcontext().prec = 2000
>>> Decimal (.00000001) * Decimal (.987)[/b]
Decimal('9.87000000000000009104248083235174268563047313600349515597682205532708579013502123676582211686536 538763903081417083740234375E-9')
It's close enough though - you'd get an extra 9 satoshi if your transaction was 10 billion BTC.
|
|
|
|
|
1592
|
Bitcoin / Mining / Re: Flops to hashes question
|
on: February 20, 2013, 12:36:10 AM
|
One can only approximate because: - Different hardware performs differently on integer operations vs floating point operations. Floating point uses different CPU instructions that use different transistor circuits that are optimized differently (or don't exist in hardware at all, see 386SX). - a FLOPS test has to be optimized to a GPU platform, without taking advantage of hardware specific features it may not get full performance possible, - Hashing requires optimized programming too, you ask for FLOPS to hashes, but GPU miners have also nearly doubled in efficiency since the first releases from optimized coding. Core 2 Q6600 = 11.0 Mhash/s & 5 GFLOPS doesn't compare at all with 5870: 400Mhash/s:  |
|
|
|
|
1593
|
Bitcoin / Bitcoin Discussion / Note: marked as duplicate of topic 140223
|
on: February 19, 2013, 05:37:26 AM
|
There is no indications that any core developer want to change the block size. Maybe when you can't get a transaction in the next block by paying an adequate fee it might be time to consider such a change. There was just one thread with a whole bunch of me too responses from people who think they should get to spam the network with their martingale bot. That's where your post should have been added. |
|
|
|
|
1595
|
Economy / Trading Discussion / Re: BTC Price History Chart/Table?
|
on: February 16, 2013, 02:56:47 AM
|
I don't think he really wants raw data, but just in case, I exported the trade data for the entire history of mtgox to a csv file, 3.5M trades (that's 3.5 million lines of text file), 221MB (12.7MB with 7-zip and some ultra compression) format: Date Time Open High Low Last Volume Number of Trades Bid Volume Ask Volume
7/17/2010 16:09:17 0.05 0.05 0.05 0.05 2000 2000 0 0
7/17/2010 20:43:06 0.059 0.059 0.059 0.059 5001 5001 0 0
7/18/2010 10:48:56 0.081 0.081 0.081 0.081 500 500 0 0
7/18/2010 14:44:11 0.086 0.086 0.086 0.086 1000 1000 0 0
7/18/2010 15:00:26 0.086 0.086 0.086 0.086 500 500 0 0
7/18/2010 15:00:36 0.086 0.086 0.086 0.086 500 500 0 0
7/18/2010 20:53:04 0.091 0.091 0.091 0.091 500 500 0 0
7/19/2010 09:24:13 0.093 0.093 0.093 0.093 8000 8000 0 0
7/19/2010 10:03:33 0.089 0.089 0.089 0.089 10000 10000 0 0
7/19/2010 10:07:58 0.088 0.088 0.088 0.088 10000 10000 0 0
7/19/2010 10:12:27 0.091 0.091 0.091 0.091 9000 9000 0 0
7/19/2010 13:44:16 0.084 0.084 0.084 0.084 2000 2000 0 0
7/19/2010 13:55:25 0.079 0.079 0.079 0.079 10000 10000 0 0
7/19/2010 13:56:29 0.079 0.079 0.079 0.079 1000 1000 0 0
7/19/2010 13:57:00 0.077 0.077 0.077 0.077 2000 2000 0 0
7/19/2010 14:02:17 0.081 0.081 0.081 0.081 4900 4900 0 0
7/19/2010 19:36:22 0.082 0.082 0.082 0.082 10000 10000 0 0
7/19/2010 20:54:28 0.082 0.082 0.082 0.082 1200 1200 0 0
7/20/2010 05:48:55 0.081 0.081 0.081 0.081 400 400 0 0
7/20/2010 05:50:34 0.079 0.079 0.079 0.079 1000 1000 0 0
7/20/2010 07:37:28 0.078 0.078 0.078 0.078 1000 1000 0 0
7/20/2010 07:39:09 0.077 0.077 0.077 0.077 1000 1000 0 0
7/20/2010 08:01:54 0.076 0.076 0.076 0.076 1000 1000 0 0
7/20/2010 10:08:05 0.077 0.077 0.077 0.077 1000 1000 0 0
7/20/2010 10:09:38 0.077 0.077 0.077 0.077 1000 1000 0 0
7/20/2010 10:09:48 0.077 0.077 0.077 0.077 2000 2000 0 0
7/20/2010 13:09:44 0.074 0.074 0.074 0.074 450 450 0 0
7/20/2010 13:38:13 0.074 0.074 0.074 0.074 550 550 0 0
7/20/2010 13:38:13 0.074 0.074 0.074 0.074 450 450 0 0
7/20/2010 13:41:49 0.074 0.074 0.074 0.074 4550 4550 0 0
7/20/2010 14:24:20 0.075 0.075 0.075 0.075 300 300 0 0
7/20/2010 14:28:39 0.075 0.075 0.075 0.075 100 100 0 0
7/20/2010 14:29:15 0.075 0.075 0.075 0.075 100 100 0 0
7/20/2010 14:29:58 0.075 0.075 0.075 0.075 100 100 0 0
7/20/2010 19:27:48 0.074 0.074 0.074 0.074 6000 6000 0 0
7/20/2010 19:30:30 0.073 0.073 0.073 0.073 1000 1000 0 0
7/20/2010 19:41:25 0.072 0.072 0.072 0.072 1000 1000 0 0
7/20/2010 19:41:43 0.071 0.071 0.071 0.071 1000 1000 0 0
7/21/2010 07:11:25 0.07 0.07 0.07 0.07 1000 1000 0 0
7/21/2010 07:45:07 0.069 0.069 0.069 0.069 1000 1000 0 0
7/21/2010 07:56:53 0.068 0.068 0.068 0.068 1000 1000 0 0
7/21/2010 11:58:28 0.067 0.067 0.067 0.067 1000 1000 0 0
|
|
|
|
|
1597
|
Bitcoin / Bitcoin Technical Support / Re: if i put a wallet.dat file on a stick in a safe
|
on: February 16, 2013, 02:37:10 AM
|
The concern would be bit rot on a cold storage flash memory. For power-off data retention in flash, the charge that is the store of a bit degrades over time, and thus far storage times have only been estimated based on accelerated testing, since MLC chips have only been out a short while. Manufacturer estimates vary from 1 year to 10 years, but in many cases are not given at all. This paper details some testing, "we typically target three months of data retention time for solid-state in enterprise applications". http://storageconference.org/2011/Papers/SNAPI/1.Sun.pdf |
|
|
|
|
1598
|
Bitcoin / Bitcoin Discussion / Re: I was charged extra for using my credit card
|
on: February 16, 2013, 01:29:51 AM
|
|
That's not a rip off. Credit card customers should bear the full burden of the credit card expenses: sign up fees, annual membership fees, terminal fees, PCI compliance fees, the cost of terminals and POS systems, leased phone lines and internet, IRS reporting fees, lost interest and opportunity from capital locked up by the credit card companies, reversals and chargebacks, fraud, accounting costs. All those should go into the credit card markup.
The money charged on a credit card is also not cash that can just be put in the owner's pocket at the end of the day. Tipping on a credit card is like giving 70% to the server and 30% to the government.
|
|
|
|
|
1599
|
Economy / Economics / Re: Another extreme on the planet
|
on: February 16, 2013, 01:06:16 AM
|
Park Nam-ki, was dismissed in January as chief of the planning and finance department of the Workers' Party and reportedly executed in March for his failure to lead the currency exchange successfully.
At least they got something right. This would shape up wall street, banks, and the fed. |
|
|
|
|
Show Posts
