Does bitcoind accept batch RPC calls?


I'm interested in setting up a P2Pool node (which requires running bitcoind) to run a little mining pool for myself. Before you ask, nope I'm not even trying to break even, I know I'll lose money on this. Just want to play around and get a feel for how these things work.

My question is: I hear over and over again that it's important to take security precautions with bitcoind and wallets, but I've had trouble teasing out exactly what those security precautions are. If I have bitcoind not accepting RPC calls (as is the default), is there any danger to using the out-of-the-box unencrypted wallet?

If the information helps, I'll probably run the node in EC2, and have a cron job that frequently transfers any bitcoins earned through mining into an account in an exchange so I can play around with that side of things as well (so I'm not worried about large sums of bitcoin building up in my bitcoind...

0 0

There are two variations of the original bitcoin program available; one with a graphical user interface (usually referred to as just “Bitcoin”), and a 'headless' version (called bitcoind). They are completely compatible with each other, and take the same command-line arguments, read the same configuration file, and read and write the same data files. You can run one copy of either Bitcoin or bitcoind on your system at a time (if you accidently try to launch another, the copy will let you know that Bitcoin or bitcoind is already running and will exit).

Linux Quickstart

The simplest way to start from scratch with the command line client, automatically syncing blockchain and creating a wallet, is to just run this command (without arguments) from the directory containing your bitcoind binary:


To run with the standard GUI interface:


Command-line arguments

Give bitcoind the -? or –-help argument and it will print out a list of...

0 0

My Wallet users can interact with their wallet using our JSON RPC api. It is intended to be fully compatible with the original Bitcoind RPC protocol however some method calls are not supported.

No Blockchain Download - Save on bandwidth and disk space. No Need to run Bitcoind - Some VPS and shared hosting plans do not allow you to run custom processes Use Existing software - Most existing software that uses the bitcoind rpc calls will work transparently using Payment notifications Live synchronization with the web interface

Original Documentation available at


-rpcuser Should be set to your wallet identifier. This is a 36 character random string which can be found on your wallet login page.
-rpcpassword Should be set to your main wallet password. If double encryption is enabled your second password will need to be set using...

0 0

I am using bitcoind in my project and when I deploy it on my server bitcoind works strange. I use this lib to work with rpc On local dev server everything is fine but when I deploy it to vps it stops return data. The data is empty. I made some tests like this:

bitcoin.conf file: server=1 rpcuser=myuser rpcpassword=mypassword rpcconnect= rpcport=8332


def btc_rpc_connect(config): rpc_server_url = ("http://{user}:{password}@{host}:{port}").format( user=config.rpc_user, password=config.rpc_pass, host=config.rpc_host, port=config.rpc_port ) rpc_conn = AuthServiceProxy(rpc_server_url) return rpc_conn user = request.user # getting rpc settings from db config = ProjectSettings.objects.get(id=1) rpc_connection = btc_rpc_connect(config) btc_address = rpc_connection.getnewaddress(user.username)

I also tried to test from django's ./ shell and entered this code manually. The fact...

0 0
-? This help message -alerts Receive and display P2P network alerts (default: 1) -alertnotify= Execute command when a relevant alert is received or we see a really long fork (%s in cmd is replaced by message) -blocknotify= Execute command when the best block changes (%s in cmd is replaced by block hash) -checkblocks= How many blocks to check at startup (default: 288, 0 = all) -checklevel= How thorough the block verification of -checkblocks is (0-4, default: 3) -conf= Specify configuration file (default: bitcoin.conf) -datadir= Specify data directory -dbcache= Set database cache size in megabytes (4 to 16384, default: 100) -loadblock= Imports blocks from external blk000??.dat file on startup -maxorphantx= Keep at most unconnectable transactions in memory (default: 100) -maxmempool= Keep the transaction memory pool below megabytes (default: 300) -mempoolexpiry= Do not keep transactions in the mempool longer than hours (default: 72) -par= Set the number of script verification threads (-2...
0 0

Provided by:



bitcoin.conf - bitcoin configuration file


All command-line options (except for '-datadir' and '-conf') may be specified in a configuration file, and all configuration file options may also be specified on the command line. Command-line options override values set in the configuration file. The configuration file is a list of 'setting=value' pairs, one per line, with optional comments starting with the '#' character. The configuration file is not automatically created; you can create it using your favorite plain-text editor. By default, bitcoind(1) will look for a file named bitcoin.conf(5) in the bitcoin data directory, but both the data directory and the configuration file path may be changed using the '-datadir' and '-conf' command-line arguments.


bitcoin.conf should be located in $HOME/.bitcoin


0 0
By : Javed Khan

In this blog post we'll talk about bitcoins and look at an overview of how to accept them from your python app.


Bitcoin is crypto-currency whose protocol allows fast, anonymous and secure digital transactions.

To know more about bitcoin and to install it, go to the "Developer Guide" guide.

Getting started:

To get started, install bitcoin (assuming Ubuntu):

$ sudo apt-get install bitcoind

Now edit ~/.bitcoin/bitcoin.conf and add:

This will allow us to run bitcoin in test mode.

Now start the bitcoind daemon using:

To check that it's working, do:

If you see a JSON output, you should be good to go.


Bitcoin includes a JSON RPC server as a part of the daemon.

Using a client library like "bitcoin-python", we can invoke bitcoin calls from python like so:

>>> import bitcoinrpc >>> bitcoin = bitcoinrpc.connect_to_local() >>> bitcoin.getinfo()


0 0
[Bitcoin-development] Raw Transaction RPC calls for bitcoind Gavin Andresen gavinandresen at
Thu Jun 14 20:00:57 UTC 2012 On Thu, Jun 14, 2012 at 10:37 AM, Peter Vessenes wrote: > This is super cool! > > I have a feature request: it would be awesome to be able to provide private > keys at the command line with the signature, turning the client into a > wallet-less signature machine. I like that idea. A third argument that is an array of private keys (in the same format as the dumpprivkey RPC call) should be easy to support, assuming the semantics are: + If third argument given, do not require that the wallet be unlocked, and only sign using the private key(s) given (ignore the bitcoind wallet entirely). + Private keys would stay in bitcoind memory only for the duration of the RPC call. -- -- Gavin Andresen More information about the bitcoin-dev mailing list
0 0

The .conf I have is principally the same for all Alt-TC.

So, for PPC is

rpcuser=someusername rpcpassword=somerandompassword rpcport=9902 daemon=1

with one exception; for PPC, I also have this line there too:


The server=1, allows me to then run a commandline

ppcoind walletpassphrase MyWalletUnlockPassword 9999999 true

and have the "unlocked for block minting only" message over the lock, which apparently in time will let the interest accrue.

I'm not sure you even need the rpcport, if you aren't looking to port-forward from your router more requests than the usual 8 connections.

Serious Proof of Work mining is not something I've tried, having been put off by recognising I haven't got the hardware for it. If you were to mine, then there are plenty of guides for that from pools looking for your contribution that would encourage use of the other options above. I think I've seen it suggest one of them is a count of the...

0 0

## ## 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 # Run a regression test network #regtest=0 # Connect via a SOCKS5 proxy #proxy= # Bind to given address and always listen on it. Use [host]:port notation for IPv6 #bind= # Bind to given address and whitelist peers connecting to it. Use [host]:port notation for IPv6 #whitebind= ############################################################## ## Quick Primer on addnode vs connect ## ## Let's say for instance you use addnode= ## ## addnode will connect you to and tell you about the ## ## nodes connected to 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 and no one else.## ## ...

0 0

This tutorial shows how to use django-bitcoin to receive and send money in your Python + Django application. The walkthrough guides how to create a bitcoin wallet in your Django application, buy bitcoins, transfers bitcoins into your application and then spend them. This all is done interactively from the command, Django shell and Python prompt.The tutorial was tested on OSX. It should work on Linux unmodified. On Windows you are on your own.

django-bitcoin is a proven open source solution for handling bitcoins in your service. However, it might be rough on the edges, it is being actively developed and lacks satisfying documentation. If you need a helping hand to set it up please pop up on #localbitcoins-chat on or poke me by email.

Setup and configure memcached first.

Installation (virtualenv based):

git clone cd django-bitcoin-example virtualenv venv # Create virtualenv folder caller...
0 0