Bitcoin Forum
December 14, 2024, 06:52:29 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: How to run bitcoin on the command line?  (Read 8699 times)
gmiwenht (OP)
Member
**
Offline Offline

Activity: 115
Merit: 10


View Profile
March 15, 2013, 07:09:13 PM
 #1

I am using OSX 10.8.2.

I want to get bitcoin running from the command line. I am doing this for several reasons, mainly just to learn more about what goes on under the hood, but also with a view to writing some applications.

Right now I am having the most basic problem: figuring out how/where bitcoin is installed. For the whole time I have been involved with Bitcoin I have been using blockchain.info, so I have been ignorant of the inner workings of the Bitcoin protocol.

I downloaded Bitcoin-Qt, which I thought was just bitcoind with a GUI. This gave me a .dmg file, which I then installed into my Applications directory. I now cd to /Applications and all I can see is Bitcoin-Qt.app. I am as new to OSX as I am to the Bitcoin client. I thought that OSX worked similarly to linux systems. So what is this monolithic Bitcoin-Qt.app file? How can I run the command line version, bitcoind?

I am looking for simple step-by-step instructions which will allow me to achieve the following:

1. Set up bitcoin on OSX so that I can run ./bitcoind from the terminal.
2. Set up a new wallet.dat and import some existing private keys from blockchain.info.
3. Figure out how to check balance, send, receive, etc. (i.e. make use of the same basic functionality that blockchain.info gives me)

Cheers,

1xsBEUVzo6EtAST5Bq96AztiTR5mBXNzt
Raoul Duke
aka psy
Legendary
*
Offline Offline

Activity: 1372
Merit: 1002



View Profile
March 15, 2013, 07:11:38 PM
 #2

If you insert
Code:
server=1
on the bitcoin.conf file you'll be able to run Bitcoin-qt and have the bitcoind functionality.
Stephen Gornick
Legendary
*
Offline Offline

Activity: 2506
Merit: 1010


View Profile
March 15, 2013, 07:23:30 PM
 #3

Right now I am having the most basic problem: figuring out how/where bitcoin is installed.

And for the data directory:
 - http://en.bitcoin.it/wiki/Data_directory#Mac

Unichange.me

            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █


christop
Member
**
Offline Offline

Activity: 84
Merit: 10



View Profile
March 15, 2013, 08:00:19 PM
 #4

Also see the manpage for bitcoin.conf, the existence of which I just discovered for myself.

According to the manpage, you also have to set rpcuser and rpcpassword to secure the JSON-RPC api.

Tips are always welcome: 17Z63hLi2ox4fCMhDqVJrLTJiXVcBMJpMo
Alpaca socks donations: 1sockzDWcF8mrC59CgiN7HAJm6xL7TiRW
gmiwenht (OP)
Member
**
Offline Offline

Activity: 115
Merit: 10


View Profile
March 15, 2013, 09:14:17 PM
 #5

Where is the bitcoin.conf file located?

1xsBEUVzo6EtAST5Bq96AztiTR5mBXNzt
Raoul Duke
aka psy
Legendary
*
Offline Offline

Activity: 1372
Merit: 1002



View Profile
March 15, 2013, 09:31:17 PM
 #6

Where is the bitcoin.conf file located?

Right now I am having the most basic problem: figuring out how/where bitcoin is installed.

And for the data directory:
 - http://en.bitcoin.it/wiki/Data_directory#Mac
gmiwenht (OP)
Member
**
Offline Offline

Activity: 115
Merit: 10


View Profile
March 15, 2013, 09:36:48 PM
 #7

Where is the bitcoin.conf file located?

Right now I am having the most basic problem: figuring out how/where bitcoin is installed.

And for the data directory:
 - http://en.bitcoin.it/wiki/Data_directory#Mac

Thanks, I saw his response, but I cannot find it there. So I thought maybe it is somewhere else.

Code:
31-35-122:Applications gmiwenht$ cd ~/Library/Application\ Support/Bitcoin
31-35-122:Bitcoin gmiwenht$ ls -l
total 1117104
-rw-------   2 mikhail  staff  364401850 Mar 14 05:43 blk0001.dat
-rw-------   1 mikhail  staff  166825984 Mar 14 05:43 blkindex.dat
drwx------  23 mikhail  staff        782 Mar 15 17:12 blocks
drwx------  50 mikhail  staff       1700 Mar 15 17:12 chainstate
drwx------   3 mikhail  staff        102 Mar 14 05:43 database
-rw-------   1 mikhail  staff          0 Dec 15 01:25 db.log
-rw-------   1 mikhail  staff   39762013 Mar 15 17:14 debug.log
-rw-------   1 mikhail  staff     895360 Mar 15 17:13 peers.dat
-rw-------   1 mikhail  staff      65536 Mar 15 14:54 wallet.dat

1xsBEUVzo6EtAST5Bq96AztiTR5mBXNzt
Raoul Duke
aka psy
Legendary
*
Offline Offline

Activity: 1372
Merit: 1002



View Profile
March 15, 2013, 09:39:03 PM
 #8

If it's not there you need to create it.
deepceleron
Legendary
*
Offline Offline

Activity: 1512
Merit: 1036



View Profile WWW
March 15, 2013, 09:41:40 PM
 #9

Where is the bitcoin.conf file located?

https://en.bitcoin.it/wiki/Data_directory

There won't be a conf file created by default. You need to create a text file, and save it as bitcoin.conf.

Here is a default bitcoin.conf template for you to modify and use:
Code:
### bitcoin.conf configuration file. Lines beginning with # are comments.
### Uncomment and edit options you wish to use.

## JSON-RPC options (for controlling a running bitcoin-qt/bitcoind process)

# server=1 tells Bitcoin to accept JSON-RPC commands.
server=1

# You must set rpcuser and rpcpassword to secure the JSON-RPC api
# You should create your own new random password.
# The username and password MUST NOT be the same.

rpcuser=bitcoinrpc
rpcpassword=3QtnxrB7P5y4EpBdad1MkCeB2RHmArvcarw7udgXsAce

# 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=10.1.1.*
#rpcallowip=192.168.1.*

# Listen for RPC connections on this TCP port:
rpcport=8332

# You can use bitcoind to send commands to bitcoin-qt/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


## Network-related settings:

# Run on the test network instead of the real bitcoin network.
#testnet=1

# Connect via a socks proxy
#proxy=127.0.0.1:9050

# Select the version of socks proxy to use (4-5, default: 5)
#socks=5

# Use proxy to reach tor hidden services (default: same as -proxy)
#tor=<ip:port>        

##############################################################
## 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 attempt connection 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=192.168.1.20:8333

# Do not use Internet Relay Chat to find peers.
noirc=0

# Maximum number of inbound+outbound connections.
#maxconnections=125

# Miscellaneous options

# Pre-generate this many public/private key pairs, so wallet backups will be valid
# after future transactions.
#keypool=100

# Add an optional transaction fee every time you send bitcoins.
#paytxfee=0.01

# Add timestamps to debug.log
#logtimestamps=1        


# User interface options

# Start Bitcoin minimized
#min=1

# Minimize to the system tray
minimizetotray=0
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!