Bitcoin Wiki - User contributions [en]

Talk:BIP 0013

2012-02-20T10:51:37Z

Gronager:

Personally, I don't like the nomenclature "version". It's signalling far more than just a version. How about "address class"?
--[[User:Andyparkins|Andyparkins]] 11:49, 9 December 2011 (GMT)

The "version" portion of the address has so far been labeled "network id", and signals from which network and which chain the address can be used for. I thin that this change from network id to version is much more fundamental and should not just be squeezed in alone with bip16/17.
The right way to do this is to structure the bitcoin address into:

base58-encode: [one-byte network ID][20-byte hash][one-byte address class][3-byte checksum]

This will move the possibility of using a faulty address from 1 to 4bill to 1 to 24mio. Recall that for most other payment systems this checksum is 1 to 9! So it should be sufficient.
An old client will then render the new addresses as useless and they will still maintain their old familiar 1xxx look - the whole point in multisig is that it should not be a matter of the paying party to worry about securing wallet of the receiver, hence he should not be bothered with a new "3" kind of address now...
--[[User:gronager|Michael Gronager/libcoin]] 10:49, 20 February 2012 (GMT)

Talk:BIP 0013

2012-02-20T10:50:53Z

Gronager:

Personally, I don't like the nomenclature "version". It's signalling far more than just a version. How about "address class"?
--[[User:Andyparkins|Andyparkins]] 11:49, 9 December 2011 (GMT)

The "version" portion of the address has so far been labeled "network id", and signals from which network and which chain the address can be used for. I thin that this change from network id to version is much more fundamental and should not just be squeezed in alone with bip16/17.
The right way to do this is to structure the bitcoin address into:

base58-encode: [one-byte version][20-byte hash][1-bytes one for version][3-byte checksum]

This will move the possibility of using a faulty address from 1 to 4bill to 1 to 24mio. Recall that for most other payment systems this checksum is 1 to 9! So it should be sufficient.
An old client will then render the new addresses as useless and they will still maintain their old familiar 1xxx look - the whole point in multisig is that it should not be a matter of the paying party to worry about securing wallet of the receiver, hence he should not be bothered with a new "3" kind of address now...
--[[User:gronager|Michael Gronager/libcoin]] 10:49, 20 February 2012 (GMT)

Talk:BIP 0013

2012-02-20T10:50:37Z

Gronager:

Personally, I don't like the nomenclature "version". It's signalling far more than just a version. How about "address class"?
--[[User:Andyparkins|Andyparkins]] 11:49, 9 December 2011 (GMT)

The "version" portion of the address has so far been labeled "network id", and signals from which network and which chain the address can be used for. I thin that this change from network id to version is much more fundamental and should not just be squeezed in alone with bip16/17.
The right way to do this is to structure the bitcoin address into:
base58-encode: [one-byte version][20-byte hash][1-bytes one for version][3-byte checksum]

This will move the possibility of using a faulty address from 1 to 4bill to 1 to 24mio. Recall that for most other payment systems this checksum is 1 to 9! So it should be sufficient.
An old client will then render the new addresses as useless and they will still maintain their old familiar 1xxx look - the whole point in multisig is that it should not be a matter of the paying party to worry about securing wallet of the receiver, hence he should not be bothered with a new "3" kind of address now...
--[[User:gronager|Michael Gronager/libcoin]] 10:49, 20 February 2012 (GMT)

Talk:BIP 0013

2012-02-20T10:50:02Z

Gronager:

Personally, I don't like the nomenclature "version". It's signalling far more than just a version. How about "address class"?
--[[User:Andyparkins|Andyparkins]] 11:49, 9 December 2011 (GMT)
The "version" portion of the address has so far been labeled "network id", and signals from which network and which chain the address can be used for. I thin that this change from network id to version is much more fundamental and should not just be squeezed in alone with bip16/17.
The right way to do this is to structure the bitcoin address into:
base58-encode: [one-byte version][20-byte hash][1-bytes one for version][3-byte checksum]

This will move the possibility of using a faulty address from 1 to 4bill to 1 to 24mio. Recall that for most other payment systems this checksum is 1 to 9! So it should be sufficient.
An old client will then render the new addresses as useless and they will still maintain their old familiar 1xxx look - the whole point in multisig is that it should not be a matter of the paying party to worry about securing wallet of the receiver, hence he should not be bothered with a new "3" kind of address now...
--[[User:gronager|Michael Gronager/libcoin]] 10:49, 20 February 2012 (GMT)

Data directory

2011-09-02T09:12:40Z

Gronager: wallet.dat does use BDB and also added adds.dat

The location where Bitcoin's data files are stored, including the [[Wallet|wallet]] data file.

==Default Location==
=== Windows ===

Go to Start -> Run (or press WinKey+R) and run this:

explorer %APPDATA%\Bitcoin

Bitcoin's data folder will open. For most users, this is the following locations:

C:\Documents and Settings\YourUserName\Application data\Bitcoin (XP)

C:\Users\YourUserName\Appdata\Roaming\Bitcoin (Vista and 7)

"AppData" and "Application data" are hidden by default.

=== Linux ===

By default Bitcoin will put its data here:

~/.bitcoin/

You need to do a "ls -a" to see directories that start with a dot.

If that's not it, you can do a search like this:

find / -name wallet.dat -print 2>/dev/null

=== Mac ===

By default Bitcoin will put its data here:

~/Library/Application Support/Bitcoin/

==Directory Contents==

===Subdirectories===
* database
**Contains journaling files for the block database
* testnet
**Contains testnet versions of these files (if running with -testnet)

===Files===
* .lock
**BDB lock file
* bitcoin.conf [optional]
**Contains [[Running_Bitcoin#Bitcoin.conf_Configuration_File|configuration options]].
* blk''xxxx''.dat
**Contains concatenated raw blocks
* blkindex.dat
**Indexing information used with blk''xxxx''.dat
* __db.''xxx''
**Used by BDB
* db.log
* debug.log
**Bitcoin's verbose log file. Automatically trimmed from time to time.
* wallet.dat
**Storage for keys, transactions, metadata, and options.
* addr.dat
** Storage for ip addresses to make a reconnect easier
The data, index and log files are used by Oracle [http://en.wikipedia.org/wiki/Berkeley_DB Berkeley DB], the embedded key/value data store that Bitcoin uses.

==See Also==

* [[Securing your wallet]]

[[Category:Technical]]