It was the Bitcointalk forum that inspired us to create Bitcointalksearch.org - Bitcointalk is an excellent site that should be the default page for anybody dealing in cryptocurrency, since it is a virtual gold-mine of data. However, our experience and user feedback led us create our site; Bitcointalk's search is slow, and difficult to get the results you need, because you need to log in first to find anything useful - furthermore, there are rate limiters for their search functionality.
The aim of our project is to create a faster website that yields more results and faster without having to create an account and eliminate the need to log in - your personal data, therefore, will never be in jeopardy since we are not asking for any of your data and you don't need to provide them to use our site with all of its capabilities.
We created this website with the sole purpose of users being able to search quickly and efficiently in the field of cryptocurrency so they will have access to the latest and most accurate information and thereby assisting the crypto-community at large.
Bitcoin version v0.6.3-beta (2012-06-19 16:44:55 -0400)
Default data directory C:\Users\brendan\AppData\Roaming\Bitcoin
Loading addresses...
dbenv.open LogDir=C:\Users\brendan\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\brendan\AppData\Roaming\Bitcoin\db.log
Loaded 12521 addresses
addresses 157ms
Loading block index...
LoadBlockIndex(): hashBestChain=00000000000008170660 height=191188
Verifying last 2500 blocks at level 1
block index 34394ms
Loading wallet...
nFileVersion = 60300
wallet 93ms
Done loading
mapBlockIndex.size() = 191194
nBestHeight = 191188
setKeyPool.size() = 100
mapWallet.size() = 65
mapAddressBook.size() = 4
Bound to port 8333
ThreadRPCServer started
addrLocalHost = 192.168.2.3:8333
ThreadSocketHandler started
ThreadIRCSeed exiting
ThreadDNSAddressSeed started
Loading addresses from DNS seeds (could take a while)
ThreadMessageHandler started
ThreadOpenConnections started
ThreadOpenAddedConnections started
ThreadOpenAddedConnections exiting
GetMyExternalIP() received [67.189.41.174] 67.189.41.174:0
GetMyExternalIP() returned 67.189.41.174
trying connection 109.188.130.74:8333 lastseen=-2.2hrs
Added 3 addresses from 0:0:0:0:0:0:0:0: 696 tried, 11826 new
Added 1 addresses from 178.18.90.41: 696 tried, 11826 new
Added 8 addresses from 173.242.112.53: 696 tried, 11827 new
69 addresses found from DNS seeds
ThreadDNSAddressSeed exiting
connection timeout
trying connection 46.138.157.39:8333 lastseen=-2.8hrs
connection timeout
trying connection 84.108.105.80:8333 lastseen=-16.9hrs
EnvShutdown exception: DbEnv::close: Invalid argument (22)
# bitcoin.conf configuration file. Lines beginning with # are comments.
# Network-related settings:
# Run on the test network instead of the real bitcoin network.
#testnet=0
# Connect via a socks4 proxy
#proxy=127.0.0.1:9050
##############################################################
## Quick Primer on addnode vs connect ##
## Let's say for instance you use addnode=4.2.2.4 ##
## addnode will connect you to and tell you about the ##
## nodes connected to 4.2.2.4. In addition it will tell ##
## the other nodes connected to it that you exist so ##
## they can connect to you. ##
## connect will not do the above when you 'connect' to it. ##
## It will *only* connect you to 4.2.2.4 and no one else.##
## ##
## So if you're behind a firewall, or have other problems ##
## finding nodes, add some using 'addnode'. ##
## ##
## If you want to stay private, use 'connect' to only ##
## connect to "trusted" nodes. ##
## ##
## If you run multiple nodes on a LAN, there's no need for ##
## all of them to open lots of connections. Instead ##
## 'connect' them all to one node that is port forwarded ##
## and has lots of connections. ##
## Thanks goes to [Noodle] on Freenode. ##
##############################################################
# Use as many addnode= settings as you like to connect to specific peers
#addnode=69.164.218.197
#addnode=10.0.0.2:8333
# ... or use as many connect= settings as you like to connect ONLY
# to specific peers:
#connect=69.164.218.197
#connect=10.0.0.1:8333
# Do not use Internet Relay Chat (irc.lfnet.org #bitcoin channel) to
# find other peers.
#noirc=0
# Maximum number of inbound+outbound connections.
#maxconnections=
# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)
# server=1 tells Bitcoin-QT to accept JSON-RPC commands.
server=1
# You must set rpcuser and rpcpassword to secure the JSON-RPC api
rpcuser=
rpcpassword=
# How many seconds bitcoin will wait for a complete RPC HTTP request.
# after the HTTP connection is established.
#rpctimeout=30
# By default, only RPC connections from localhost are allowed. Specify
# as many rpcallowip= settings as you like to allow connections from
# other hosts (and you may use * as a wildcard character):
#rpcallowip=127.0.0.1
#rpcallowip=192.168.2.3*
# Listen for RPC connections on this TCP port:
rpcport=8332
# You can use Bitcoin or bitcoind to send commands to Bitcoin/bitcoind
# running on another host using this option:
rpcconnect=127.0.0.1
# Use Secure Sockets Layer (also known as TLS or HTTPS) to communicate
# with Bitcoin -server or bitcoind
#rpcssl=1
# OpenSSL settings used when rpcssl=1
#rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
#rpcsslcertificatechainfile=server.cert
#rpcsslprivatekeyfile=server.pem
# Miscellaneous options
# Set gen=1 to attempt to generate bitcoins
#gen=0
# Use SSE instructions to try to generate bitcoins faster.
#4way=1
# Pre-generate this many public/private key pairs, so wallet backups will be valid for
# both prior transactions and several dozen future transactions.
#keypool=100
# Pay an optional transaction fee every time you send bitcoins. Transactions with fees
# are more likely than free transactions to be included in generated blocks, so may
# be validated sooner.
paytxfee=0.00
# Allow direct connections for the 'pay via IP address' feature.
#allowreceivebyip=1
# User interface options
# Start Bitcoin minimized
#min=1
# Minimize to the system tray
#minimizetotray=1